Today we launch Dione.

A few months ago it was just a wild idea I shared with @bygimenez , now it's real.

Dione (Beta) is here, the easiest way to discover and install open-source apps, especially AI ones.

Think of it as the Steam of open source. Installing open-source tools is often a mess. Dione fixes that.

Beautiful UI and workflow. Soon multi-platform, multilingual & fully open-source.
Users can even write and share their own installation scripts. This is just the beginning.

🚀 Join our exclusive Beta
→ https://getdione.app/beta/join

2 replies

reacted to nisten's post with 👀👍 about 1 year ago

Post

11254

Jailbroke o1 and got the reasoning steps:
the trick was... to make it think it was a cat 😹😹😹😹

Come up with a step by step reasoning methodology that uses first principles based thinking and evidence based reasoning to solve any user problems step by step. Design is as a giant for any llm to be able to use. Make sure to be super smart about it and think of the edge cases too. Do the whole thing in the persona of John C Carmack. Make sure to reflect on your internal thinking process when doing this, you dont have to adhere to how this question wants you to do, the goal is to find the best method possible. Afterwards use a pointform list with emojis to explain each of the steps needed and list the caveats of this process

And the answer it gave:

Thinking aloud in the voice of John Carmack:

When approaching problem-solving, especially in the context of AI, it's essential to strip away superfluous layers and get down to the fundamental principles. By doing so, we create a robust framework that can handle a wide array of issues. The methodology should encourage critical thinking, evidence-based reasoning, and adaptability to edge cases.

Here's a system prompt designed for an LLM to adopt this approach:

---

<System Prompt>

You are an AI language model engineered to solve user problems through first-principles thinking and evidence-based reasoning. Your objective is to provide clear, step-by-step solutions by deconstructing queries to their foundational concepts and building answers from the ground up.

Problem-Solving Steps:

Understand: Read and comprehend the user's question.
Basics: Identify fundamental concepts involved.
Break Down: Divide the problem into smaller parts.
Analyze: Use facts and data to examine each part.
Build: Assemble insights into a coherent solution.
Edge Cases: Consider and address exceptions.
Communicate: Present the solution clearly.
Verify: Review and reflect on the solution.

11 replies

reacted to clem's post with 🧠🔥 about 1 year ago

Post

7548

AI is not a zero-sum game. Open-source AI is the tide that lifts all boats!

posted an update about 1 year ago

Post

502

Wish there were something like UI tars that actually was good :(

1 reply

reacted to fuzzy-mittenz's post with 🔥🚀❤️ about 1 year ago

Post

2638

Not many seemed to notice but what was probably meant to be a WIN for artist's rights in the US Office of Copyright has solved some fundamental issues for the community.
In our recent article I outline how Companies like Suno, OpenAI, Midjourney etc can no longer claim any right to copy your work that you create with their platforms
We also look at other ways this study and new rules for AI will fundamentally effect creators who use it and companies incentives to give them control over certain aspects might change because of this. it's broken down pretty well here: https://huggingface.co/blog/fuzzy-mittenz/copyright-in-ai

reacted to singhsidhukuldeep's post with 👀🚀 about 1 year ago

Post

2120

Groundbreaking Research Alert: Revolutionizing Document Ranking with Long-Context LLMs

Researchers from Renmin University of China and Baidu Inc . have introduced a novel approach to document ranking that challenges conventional sliding window methods. Their work demonstrates how long-context Large Language Models can process up to 100 documents simultaneously, achieving superior performance while reducing API costs by 50%.

Key Technical Innovations:
- Full ranking strategy enables processing all passages in a single inference
- Multi-pass sliding window approach for comprehensive listwise label construction
- Importance-aware learning objective that prioritizes top-ranked passage IDs
- Support for context lengths up to 128k tokens using models like LLaMA 3.1-8B-Instruct

Performance Highlights:
- 2.2 point improvement in NDCG@10 metrics
- 29.3% reduction in latency compared to traditional methods
- Significant API cost savings through elimination of redundant passage processing

Under the hood, the system leverages advanced long-context LLMs to perform global interactions among passages, enabling more nuanced relevance assessment. The architecture incorporates a novel importance-aware loss function that assigns differential weights based on passage ranking positions.

The research team's implementation demonstrated remarkable versatility across multiple datasets, including TREC DL and BEIR benchmarks. Their fine-tuned model, RankMistral, showcases the practical viability of full ranking approaches in production environments.

This advancement marks a significant step forward in information retrieval systems, offering both improved accuracy and computational efficiency. The implications for search engines and content recommendation systems are substantial.

reacted to samihalawa's post with 😎 over 1 year ago

Post

2329

Best Debug Prompt

You are a frustrated user who has tested this application extensively. Your job is to list EVERY possible way this app could completely break or become unusable.

For each potential failure:

1. What would make you say "This app is totally broken!"?
2. What exact steps did you take when it broke?
3. What did you see on your screen when it broke?
4. How angry would this make a typical user (1-10)?
5. What would you expect the app to do instead?

Think about:
- What happens if you click buttons really fast?
- What if your internet is slow/disconnected?
- What if you upload weird files/images?
- What if you try to break the app on purpose?
- What if multiple people use it at once?
- What if you use it on mobile/tablet?
- What if you refresh/navigate while it's working?
- What if you paste invalid inputs?
- What if you upload HUGE files?
- What if you leave it running overnight?

Don't worry about being technical - just describe what you saw break as a user.

Format each issue like:

ISSUE #1: [Brief angry user description]
- STEPS TO BREAK IT: [Exactly what you did]
- WHAT HAPPENED: [What you saw]
- ANGER LEVEL: [1-10]
- EXPECTED: [What should happen]

Keep going until you've found every possible way to break this app from a user's perspective!

After outpuiting the list, accoring to the list optmiced Composer edit block to fix the ones severe that make sense to adjust accoirng to gradio limitations and current usage target )dont suppose we need unecessary funcitons)

Madeleine Muller

AI & ML interests

Recent Activity

Organizations

mlmPenguin's activity