The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Ellipsis – Automated PR reviews and bug fixes
Hi HN, hunterbrooks and nbrad here from Ellipsis (<a href="https://www.ellipsis.dev">https://www.ellipsis.dev</a>). Ellipsis automatically reviews your PRs when opened and on each new commit. If you tag @ellipsis-dev in a comment, it can make changes to the PR (via direct commit or side PR) and answer questions, just like a human.<p>Demo video: <a href="https://www.youtube.com/watch?v=X61NGZpaNQA" rel="nofollow">https://www.youtube.com/watch?v=X61NGZpaNQA</a><p>So far, we have dozens of open source projects and companies using Ellipsis. We seem to have landed in a kind of sweet spot where there’s a good match between the current capabilities of AI tools and the actual needs of software engineers - this doesn’t replace human review, but it saves you time by catching/fixing lots of small silly stuff.<p>Here’s an example in the wild: <a href="https://github.com/relari-ai/continuous-eval/pull/38">https://github.com/relari-ai/continuous-eval/pull/38</a>. Ellipsis (1) adds a PR summary; (2) finds a bug and adds a review comment; (3) after a (human) user comments, generates a side PR with the fix; and (4) after a (human) user merges the side PR and adds another commit, re-reviews the PR and approves it<p>Here’s another example: <a href="https://github.com/SciPhi-AI/R2R/pull/350#pullrequestreview-204013694">https://github.com/SciPhi-AI/R2R/pull/350#pullrequestreview-...</a>, where Ellipsis adds several comments with inline suggestions that were directly merged by the developer.<p>You can configure Ellipsis in natural language to enforce custom rules, style guides, or conventions. For example, here’s how the `jxnl/instructor` repo uses natural language rules to make sure that docs are kept in sync: <a href="https://github.com/jxnl/instructor/blob/main/ellipsis.yaml#L13-L14">https://github.com/jxnl/instructor/blob/main/ellipsis.yaml#L...</a>, and here’s an example PR that Ellipsis came up with based on those rules: <a href="https://github.com/jxnl/instructor/pull/346">https://github.com/jxnl/instructor/pull/346</a>.<p>Installing into your repo takes 2 clicks at <a href="https://www.ellipsis.dev">https://www.ellipsis.dev</a>. You do have to sign up to try it out because we need you to authorize our GitHub app to read your code. Don’t worry, your code is never stored or used to train models (<a href="https://docs.ellipsis.dev/security">https://docs.ellipsis.dev/security</a>).<p>We’d really appreciate your feedback, thoughts, and ideas!
Show HN: An SQS Alternative on Postgres
Show HN: An SQS Alternative on Postgres
Show HN: An SQS Alternative on Postgres
Show HN: Exploring HN by mapping and analyzing 40M posts and comments for fun
Show HN: Exploring HN by mapping and analyzing 40M posts and comments for fun
Show HN: Exploring HN by mapping and analyzing 40M posts and comments for fun
Show HN: Exploring HN by mapping and analyzing 40M posts and comments for fun
Show HN: Serverless collaborative notion-level note editor using CRDT in GO
Show HN: Serverless collaborative notion-level note editor using CRDT in GO
Show HN: Serverless collaborative notion-level note editor using CRDT in GO
Show HN: I made a better Perplexity for developers
Hi HN,<p>I am Jiayuan, and I'm here to introduce a tool we've been building over the past few months: Devv (<a href="https://devv.ai" rel="nofollow">https://devv.ai</a>). In simple terms, it is an AI-powered search engine specifically designed for developers.<p>Now, you might ask, with so many AI search engines already available—Perplexity, You.com, Phind, and several open-source projects—why do we need another one?<p>We all know that Generative Search Engines are built on RAG (Retrieval-Augmented Generation)[1] combined with Large Language Models (LLMs). Most of the products mentioned above use indexes from general search engines (like Google/Bing APIs), but we've taken a different approach.<p>We've created a vertical search index focused on the development domain, which includes:<p>- Documents: These are essentially the single source of truth for programming languages or libraries; I believe many of you are users of Dash (<a href="https://kapeli.com/dash" rel="nofollow">https://kapeli.com/dash</a>) or devdocs (<a href="https://devdocs.io/" rel="nofollow">https://devdocs.io/</a>).<p>- Code: While not natural language, code contains rich contextual information. If you have a question related to the Django framework, nothing is more convincing than code snippets from Django's repository.<p>- Web Search: We still use data from search engines because these results contain additional contextual information.<p>Our reasons for doing this include:<p>- The quality of the index is crucial to the RAG system; its effectiveness determines the output quality of the entire system.<p>- We focus more on the Index (RAG) rather than LLMs because LLMs evolve rapidly; even models performing well today may be superseded by better ones in a few months, and fine-tuning an LLM now has relatively low costs.<p>- All players are currently exploring what kind of LLM product works best; we hope to contribute some different insights ourselves (and plan to open source parts of our underlying infrastructure in return for contributions back into open source communities).<p>Some brief product features:<p>- Three modes: - Fast mode: Offers quick answers within seconds. - Agent mode: For complex queries where Devv Agent infers your question before selecting appropriate solutions. - GitHub mode(currently in beta): Links directly with your own GitHub repositories allowing inquiries about specific codebases.<p>- Clean & intuitive UI/UX design.<p>- Currently only available as web version but Chrome extension & VSCode plugin planned soon!<p>Technical details regarding how we build our Index:<p>- Documents section involves crawling most documentation sources using scripts inspired by devdocs project’s crawler logic then slicing them up according function/symbol dimensions before embedding into vector databases;<p>- Codes require special treatment beyond just embeddings alone hence why custom parsers were developed per language type extracting logical structures within repos such as architectural layouts calling relationships between functions definitions etc., semantically processed via LMM;<p>- Web searches combine both selfmade indices targeting developer niches alongside traditional API based methods. We crawled relevant sites including blogs forums tech news outlets etc..<p>For the Agent Mode, we have actually developed a multi-agent framework. It first categorizes the user's query and then selects different agents based on these categories to address the issues. These various agents employ different models and solution steps.<p>Future Plans:<p>- Build a more comprehensive index that includes internal context (The Devv for Teams version will support indexing team repositories, documents, issue trackers for Q&A)<p>- Fully localized: All of the above technologies can be executed locally, ensuring privacy and security through complete localization.<p>Devv is still in its very early stages and can be used without logging in. We welcome everyone to experience it and provide feedback on any issues; we will continue to iterate on it.<p>[1]: <a href="https://arxiv.org/abs/2005.11401" rel="nofollow">https://arxiv.org/abs/2005.11401</a>
Show HN: I made a better Perplexity for developers
Hi HN,<p>I am Jiayuan, and I'm here to introduce a tool we've been building over the past few months: Devv (<a href="https://devv.ai" rel="nofollow">https://devv.ai</a>). In simple terms, it is an AI-powered search engine specifically designed for developers.<p>Now, you might ask, with so many AI search engines already available—Perplexity, You.com, Phind, and several open-source projects—why do we need another one?<p>We all know that Generative Search Engines are built on RAG (Retrieval-Augmented Generation)[1] combined with Large Language Models (LLMs). Most of the products mentioned above use indexes from general search engines (like Google/Bing APIs), but we've taken a different approach.<p>We've created a vertical search index focused on the development domain, which includes:<p>- Documents: These are essentially the single source of truth for programming languages or libraries; I believe many of you are users of Dash (<a href="https://kapeli.com/dash" rel="nofollow">https://kapeli.com/dash</a>) or devdocs (<a href="https://devdocs.io/" rel="nofollow">https://devdocs.io/</a>).<p>- Code: While not natural language, code contains rich contextual information. If you have a question related to the Django framework, nothing is more convincing than code snippets from Django's repository.<p>- Web Search: We still use data from search engines because these results contain additional contextual information.<p>Our reasons for doing this include:<p>- The quality of the index is crucial to the RAG system; its effectiveness determines the output quality of the entire system.<p>- We focus more on the Index (RAG) rather than LLMs because LLMs evolve rapidly; even models performing well today may be superseded by better ones in a few months, and fine-tuning an LLM now has relatively low costs.<p>- All players are currently exploring what kind of LLM product works best; we hope to contribute some different insights ourselves (and plan to open source parts of our underlying infrastructure in return for contributions back into open source communities).<p>Some brief product features:<p>- Three modes: - Fast mode: Offers quick answers within seconds. - Agent mode: For complex queries where Devv Agent infers your question before selecting appropriate solutions. - GitHub mode(currently in beta): Links directly with your own GitHub repositories allowing inquiries about specific codebases.<p>- Clean & intuitive UI/UX design.<p>- Currently only available as web version but Chrome extension & VSCode plugin planned soon!<p>Technical details regarding how we build our Index:<p>- Documents section involves crawling most documentation sources using scripts inspired by devdocs project’s crawler logic then slicing them up according function/symbol dimensions before embedding into vector databases;<p>- Codes require special treatment beyond just embeddings alone hence why custom parsers were developed per language type extracting logical structures within repos such as architectural layouts calling relationships between functions definitions etc., semantically processed via LMM;<p>- Web searches combine both selfmade indices targeting developer niches alongside traditional API based methods. We crawled relevant sites including blogs forums tech news outlets etc..<p>For the Agent Mode, we have actually developed a multi-agent framework. It first categorizes the user's query and then selects different agents based on these categories to address the issues. These various agents employ different models and solution steps.<p>Future Plans:<p>- Build a more comprehensive index that includes internal context (The Devv for Teams version will support indexing team repositories, documents, issue trackers for Q&A)<p>- Fully localized: All of the above technologies can be executed locally, ensuring privacy and security through complete localization.<p>Devv is still in its very early stages and can be used without logging in. We welcome everyone to experience it and provide feedback on any issues; we will continue to iterate on it.<p>[1]: <a href="https://arxiv.org/abs/2005.11401" rel="nofollow">https://arxiv.org/abs/2005.11401</a>
Show HN: AI climbing coach – visualize how to climb any route based on your body
I made SABR - an AI model that helps you visualize the beta/technique on any route, based on your body parameters. You can input a video of you climbing any route, in any orientation or lighting condition (it's truly versatile!). SABR then creates a virtual avatar of your body shape and uses it to climb the route you're climbing. Then, you can compare/contrast.<p>You can see the demo here:
<a href="https://www.youtube.com/watch?v=cnvNPWoYZz4" rel="nofollow">https://www.youtube.com/watch?v=cnvNPWoYZz4</a><p>Will be open sourcing the model, backend, and frontend codebase soon!
Show HN: AI climbing coach – visualize how to climb any route based on your body
I made SABR - an AI model that helps you visualize the beta/technique on any route, based on your body parameters. You can input a video of you climbing any route, in any orientation or lighting condition (it's truly versatile!). SABR then creates a virtual avatar of your body shape and uses it to climb the route you're climbing. Then, you can compare/contrast.<p>You can see the demo here:
<a href="https://www.youtube.com/watch?v=cnvNPWoYZz4" rel="nofollow">https://www.youtube.com/watch?v=cnvNPWoYZz4</a><p>Will be open sourcing the model, backend, and frontend codebase soon!
Show HN: AI climbing coach – visualize how to climb any route based on your body
I made SABR - an AI model that helps you visualize the beta/technique on any route, based on your body parameters. You can input a video of you climbing any route, in any orientation or lighting condition (it's truly versatile!). SABR then creates a virtual avatar of your body shape and uses it to climb the route you're climbing. Then, you can compare/contrast.<p>You can see the demo here:
<a href="https://www.youtube.com/watch?v=cnvNPWoYZz4" rel="nofollow">https://www.youtube.com/watch?v=cnvNPWoYZz4</a><p>Will be open sourcing the model, backend, and frontend codebase soon!
Show HN: AI climbing coach – visualize how to climb any route based on your body
I made SABR - an AI model that helps you visualize the beta/technique on any route, based on your body parameters. You can input a video of you climbing any route, in any orientation or lighting condition (it's truly versatile!). SABR then creates a virtual avatar of your body shape and uses it to climb the route you're climbing. Then, you can compare/contrast.<p>You can see the demo here:
<a href="https://www.youtube.com/watch?v=cnvNPWoYZz4" rel="nofollow">https://www.youtube.com/watch?v=cnvNPWoYZz4</a><p>Will be open sourcing the model, backend, and frontend codebase soon!
Show HN: I built a non-linear UI for ChatGPT
Hi HN,<p>I built this out of frustration of the evergrowing list of AI models and features to try and to fit my workflow.<p>The visual approach clicks for me so i went with it, it provides more freedom and control of the outcome, because predictable results and increased productivity is what I’m after when using conversational AI.<p>The app is packed with features, my most used are prompt library, voice input and text search, narration is useful too.<p>The app is local-first and works right in the browser, no sign up needed and it's absolutely free to try.<p>BYOAK – bring your own API Keys.<p>Let me know what you think, any feedback is appreciated!
Show HN: I built a non-linear UI for ChatGPT
Hi HN,<p>I built this out of frustration of the evergrowing list of AI models and features to try and to fit my workflow.<p>The visual approach clicks for me so i went with it, it provides more freedom and control of the outcome, because predictable results and increased productivity is what I’m after when using conversational AI.<p>The app is packed with features, my most used are prompt library, voice input and text search, narration is useful too.<p>The app is local-first and works right in the browser, no sign up needed and it's absolutely free to try.<p>BYOAK – bring your own API Keys.<p>Let me know what you think, any feedback is appreciated!