The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Open-Source Video Editor Web App
Hey everyone, for the past like six months I've been working on a portfolio project. I got tired of doing easy projects, so I decided to tackle something bigger and more challenging. That's when I came up with the idea of a video editor. This piece of work is intended to showcase my skills and land me a job, but I like to think when working on projects that my idea is so cool that people will like to use it, and I treat every project like a startup idea. Also I havent seen many open source video editors especially on web so that was one of the points why I decided to make that and not something else, but in the end its learning experience and im not expecting much if at all.<p>A bit about the video editor itself:<p>-website: <a href="https://omniclip.app/" rel="nofollow">https://omniclip.app/</a><p>-its free<p>-its open source (MIT Licensed)<p>-its using Webcodecs API for quick rendering<p>-works fully inside browser, client side, no private data is kept<p>-I made some readme with more details, im not expecting contributions but I added bit about it: <a href="https://github.com/aegir-assembly/omni-clip">https://github.com/aegir-assembly/omni-clip</a><p>Features:<p>-Trimming<p>-Splitting<p>-Supports - Text, Audio, Video (mp4) and Images<p>-Clip editing on preview - rotating, resizing, text styling and more<p>-Undo/Redo<p>-Render in different resolutions, up to 4k.<p>Things to know before using this editor:<p>-it is simple editor, but its my main project im working on and improving it.<p>-right now it only works with videos 25 fps and more but not less<p>-only 4 tracks -- its something I could improve quickly but forgot<p>-bug here and there (eg. filmstrip not rendering until timeline scroll moved)<p>-its not working on phones yet (drag and drop API problems)<p>I'd love to hear your thoughts and feedback on it.
Show HN: Open-Source Video Editor Web App
Hey everyone, for the past like six months I've been working on a portfolio project. I got tired of doing easy projects, so I decided to tackle something bigger and more challenging. That's when I came up with the idea of a video editor. This piece of work is intended to showcase my skills and land me a job, but I like to think when working on projects that my idea is so cool that people will like to use it, and I treat every project like a startup idea. Also I havent seen many open source video editors especially on web so that was one of the points why I decided to make that and not something else, but in the end its learning experience and im not expecting much if at all.<p>A bit about the video editor itself:<p>-website: <a href="https://omniclip.app/" rel="nofollow">https://omniclip.app/</a><p>-its free<p>-its open source (MIT Licensed)<p>-its using Webcodecs API for quick rendering<p>-works fully inside browser, client side, no private data is kept<p>-I made some readme with more details, im not expecting contributions but I added bit about it: <a href="https://github.com/aegir-assembly/omni-clip">https://github.com/aegir-assembly/omni-clip</a><p>Features:<p>-Trimming<p>-Splitting<p>-Supports - Text, Audio, Video (mp4) and Images<p>-Clip editing on preview - rotating, resizing, text styling and more<p>-Undo/Redo<p>-Render in different resolutions, up to 4k.<p>Things to know before using this editor:<p>-it is simple editor, but its my main project im working on and improving it.<p>-right now it only works with videos 25 fps and more but not less<p>-only 4 tracks -- its something I could improve quickly but forgot<p>-bug here and there (eg. filmstrip not rendering until timeline scroll moved)<p>-its not working on phones yet (drag and drop API problems)<p>I'd love to hear your thoughts and feedback on it.
Show HN: Jacinda, a functional Awk (text stream processing on the comamnd-line)
Typed, functional (folds, scans) stream processing backed by Andrew Gallant/burntsushi's regular expressions library.<p>There's a guide here! <a href="https://vmchale.github.io/jacinda/" rel="nofollow">https://vmchale.github.io/jacinda/</a>
Show HN: Wag, MFA and Enrollment for WireGuard
Howdy folk,<p>I've been building this project as both a side project and my job for a little while now. The rationale behind it is while wireguard is a fantastic protocol cryptographically it leaves a lot to be desired when it comes to enrollment and end user device security.<p>Obviously instead of using an off the shelf solution like tailscale, I decided to reinvent the wheel which has honestly been quite fun with learning about eBPF, and recently clustering and HA with etcd!<p>The most recent version (in the docker container) contains about 6 months of very new work bringing it all from sqlite3 to etcd. So please be forgiving if it does some weird things!<p>Hope you all enjoy!<p>P.s Im not a web developer and any tips on that front to make it less teeth pullingly awful are welcome!
Show HN: Wag, MFA and Enrollment for WireGuard
Howdy folk,<p>I've been building this project as both a side project and my job for a little while now. The rationale behind it is while wireguard is a fantastic protocol cryptographically it leaves a lot to be desired when it comes to enrollment and end user device security.<p>Obviously instead of using an off the shelf solution like tailscale, I decided to reinvent the wheel which has honestly been quite fun with learning about eBPF, and recently clustering and HA with etcd!<p>The most recent version (in the docker container) contains about 6 months of very new work bringing it all from sqlite3 to etcd. So please be forgiving if it does some weird things!<p>Hope you all enjoy!<p>P.s Im not a web developer and any tips on that front to make it less teeth pullingly awful are welcome!
Show HN: A simple 2D fluid and gravity simulation with WASM and WebGL
The little particles will gravitate to your cursor (or touch location), and can even enter stable orbits if the conditions are right!<p>Mainly an excuse for me to experiment with wasm and WebGL, but it makes for a surprisingly good fidget toy.
Show HN: A simple 2D fluid and gravity simulation with WASM and WebGL
The little particles will gravitate to your cursor (or touch location), and can even enter stable orbits if the conditions are right!<p>Mainly an excuse for me to experiment with wasm and WebGL, but it makes for a surprisingly good fidget toy.
Show HN: A simple 2D fluid and gravity simulation with WASM and WebGL
The little particles will gravitate to your cursor (or touch location), and can even enter stable orbits if the conditions are right!<p>Mainly an excuse for me to experiment with wasm and WebGL, but it makes for a surprisingly good fidget toy.
I created 3,800+ Open Source React Icons (Beautiful, Rounded Style)
I’ve created a library of beautiful rounded icons and would like to share it with the Hacker News community. Any suggestions are highly appreciated.<p>Features:<p>- Beautifully rounded style
- Over 3,800 icons
- Editable stroke
- Regularly adding new icons
- Another standard version (less rounded) coming soon
- Easy installation via npm or yarn
Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. <a href="https://jam.dev" rel="nofollow">https://jam.dev</a><p>It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create).<p>It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer wasn't sure if I meant that it returned an error or if it was unresponsive. So the engineer would be frustrated, I would be frustrated, and fixing stuff would slow to a halt while we went back and forth to clarify how to repro the issue over async Jira comments.<p>It’s actually pretty crazy that while so much has changed in how we develop software (heck, we have types in javascript now*), the way we capture and report bugs is just as manual and lossy as it was in the 1990’s. We can run assembly in the browser but there’s still no tooling to help a non-engineer show a bug to an engineer productively.<p>So that’s what Jam is. Dev tools + video in a link. It’s like a shareable HAR file synced to a video recording of the session. And besides video, you can use it to share an instant replay of a bug that just happened — basically a 30 second playback of the DOM as a video.<p>We’ve spent a lot of time adding in a ton of niceties, like Jam writes automatic repro steps for you, and Jam’s dev tools use the same keyboard shortcuts you’re used to in Chrome dev tools, and our team’s personal favorite: Jam parses GraphQL responses and pulls out mutation names and errors (which is important because GraphQL uses one endpoint for all requests and always returns a 200, meaning you usually have to sift through every GraphQL request when debugging to find the one you’re looking for)<p>We’re now 2 years in to the product being live and people have used Jam to fix more than 2 million bugs - which makes me so happy - but there’s still a ton to do. I wanted to open up for discussion here and get your feedback and opinions how can we make it even more valuable for you debugging?<p>The worst part of the engineering job is debugging and not even being able to repro the issue, it’s not even really engineering, it’s just a communication gap, one that we should be able to solve with tools. So yeah excited to get your feedback and hear your thoughts how we can make debugging just a little less frustrating.<p>(Jam is free to use forever — there is a paid tier for features real companies would need, but we’re keeping a large free plan forever. We learned to build products at Cloudflare and free tier is in our ethos, both my co-founder and I and about half the team is ex-Cloudflare) and what we loved there is how much great feedback we’d get because the product was mostly free to use. We definitely want to keep that going at Jam.)<p>By the way, we’re hiring engineers and if this is a problem that excites you, we’d love to chat: jam.dev/careers
Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. <a href="https://jam.dev" rel="nofollow">https://jam.dev</a><p>It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create).<p>It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer wasn't sure if I meant that it returned an error or if it was unresponsive. So the engineer would be frustrated, I would be frustrated, and fixing stuff would slow to a halt while we went back and forth to clarify how to repro the issue over async Jira comments.<p>It’s actually pretty crazy that while so much has changed in how we develop software (heck, we have types in javascript now*), the way we capture and report bugs is just as manual and lossy as it was in the 1990’s. We can run assembly in the browser but there’s still no tooling to help a non-engineer show a bug to an engineer productively.<p>So that’s what Jam is. Dev tools + video in a link. It’s like a shareable HAR file synced to a video recording of the session. And besides video, you can use it to share an instant replay of a bug that just happened — basically a 30 second playback of the DOM as a video.<p>We’ve spent a lot of time adding in a ton of niceties, like Jam writes automatic repro steps for you, and Jam’s dev tools use the same keyboard shortcuts you’re used to in Chrome dev tools, and our team’s personal favorite: Jam parses GraphQL responses and pulls out mutation names and errors (which is important because GraphQL uses one endpoint for all requests and always returns a 200, meaning you usually have to sift through every GraphQL request when debugging to find the one you’re looking for)<p>We’re now 2 years in to the product being live and people have used Jam to fix more than 2 million bugs - which makes me so happy - but there’s still a ton to do. I wanted to open up for discussion here and get your feedback and opinions how can we make it even more valuable for you debugging?<p>The worst part of the engineering job is debugging and not even being able to repro the issue, it’s not even really engineering, it’s just a communication gap, one that we should be able to solve with tools. So yeah excited to get your feedback and hear your thoughts how we can make debugging just a little less frustrating.<p>(Jam is free to use forever — there is a paid tier for features real companies would need, but we’re keeping a large free plan forever. We learned to build products at Cloudflare and free tier is in our ethos, both my co-founder and I and about half the team is ex-Cloudflare) and what we loved there is how much great feedback we’d get because the product was mostly free to use. We definitely want to keep that going at Jam.)<p>By the way, we’re hiring engineers and if this is a problem that excites you, we’d love to chat: jam.dev/careers
Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. <a href="https://jam.dev" rel="nofollow">https://jam.dev</a><p>It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create).<p>It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer wasn't sure if I meant that it returned an error or if it was unresponsive. So the engineer would be frustrated, I would be frustrated, and fixing stuff would slow to a halt while we went back and forth to clarify how to repro the issue over async Jira comments.<p>It’s actually pretty crazy that while so much has changed in how we develop software (heck, we have types in javascript now*), the way we capture and report bugs is just as manual and lossy as it was in the 1990’s. We can run assembly in the browser but there’s still no tooling to help a non-engineer show a bug to an engineer productively.<p>So that’s what Jam is. Dev tools + video in a link. It’s like a shareable HAR file synced to a video recording of the session. And besides video, you can use it to share an instant replay of a bug that just happened — basically a 30 second playback of the DOM as a video.<p>We’ve spent a lot of time adding in a ton of niceties, like Jam writes automatic repro steps for you, and Jam’s dev tools use the same keyboard shortcuts you’re used to in Chrome dev tools, and our team’s personal favorite: Jam parses GraphQL responses and pulls out mutation names and errors (which is important because GraphQL uses one endpoint for all requests and always returns a 200, meaning you usually have to sift through every GraphQL request when debugging to find the one you’re looking for)<p>We’re now 2 years in to the product being live and people have used Jam to fix more than 2 million bugs - which makes me so happy - but there’s still a ton to do. I wanted to open up for discussion here and get your feedback and opinions how can we make it even more valuable for you debugging?<p>The worst part of the engineering job is debugging and not even being able to repro the issue, it’s not even really engineering, it’s just a communication gap, one that we should be able to solve with tools. So yeah excited to get your feedback and hear your thoughts how we can make debugging just a little less frustrating.<p>(Jam is free to use forever — there is a paid tier for features real companies would need, but we’re keeping a large free plan forever. We learned to build products at Cloudflare and free tier is in our ethos, both my co-founder and I and about half the team is ex-Cloudflare) and what we loved there is how much great feedback we’d get because the product was mostly free to use. We definitely want to keep that going at Jam.)<p>By the way, we’re hiring engineers and if this is a problem that excites you, we’d love to chat: jam.dev/careers
Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. <a href="https://jam.dev" rel="nofollow">https://jam.dev</a><p>It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create).<p>It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer wasn't sure if I meant that it returned an error or if it was unresponsive. So the engineer would be frustrated, I would be frustrated, and fixing stuff would slow to a halt while we went back and forth to clarify how to repro the issue over async Jira comments.<p>It’s actually pretty crazy that while so much has changed in how we develop software (heck, we have types in javascript now*), the way we capture and report bugs is just as manual and lossy as it was in the 1990’s. We can run assembly in the browser but there’s still no tooling to help a non-engineer show a bug to an engineer productively.<p>So that’s what Jam is. Dev tools + video in a link. It’s like a shareable HAR file synced to a video recording of the session. And besides video, you can use it to share an instant replay of a bug that just happened — basically a 30 second playback of the DOM as a video.<p>We’ve spent a lot of time adding in a ton of niceties, like Jam writes automatic repro steps for you, and Jam’s dev tools use the same keyboard shortcuts you’re used to in Chrome dev tools, and our team’s personal favorite: Jam parses GraphQL responses and pulls out mutation names and errors (which is important because GraphQL uses one endpoint for all requests and always returns a 200, meaning you usually have to sift through every GraphQL request when debugging to find the one you’re looking for)<p>We’re now 2 years in to the product being live and people have used Jam to fix more than 2 million bugs - which makes me so happy - but there’s still a ton to do. I wanted to open up for discussion here and get your feedback and opinions how can we make it even more valuable for you debugging?<p>The worst part of the engineering job is debugging and not even being able to repro the issue, it’s not even really engineering, it’s just a communication gap, one that we should be able to solve with tools. So yeah excited to get your feedback and hear your thoughts how we can make debugging just a little less frustrating.<p>(Jam is free to use forever — there is a paid tier for features real companies would need, but we’re keeping a large free plan forever. We learned to build products at Cloudflare and free tier is in our ethos, both my co-founder and I and about half the team is ex-Cloudflare) and what we loved there is how much great feedback we’d get because the product was mostly free to use. We definitely want to keep that going at Jam.)<p>By the way, we’re hiring engineers and if this is a problem that excites you, we’d love to chat: jam.dev/careers
Show HN: Browser-based knitting (pattern) software
I wrote some simple open source web-based app to (1) dynamically compute knitting patterns (based on input parameters, such as the exact desired size), and (2) display these patterns and help me keep track of which row I'm on (as I start knitting), similar to minimalist "row counters" that other knitters use. It also gives you a simple visualization of the shape of what you're knitting. You can see it in action at <a href="https://alefore.github.io/knit/" rel="nofollow">https://alefore.github.io/knit/</a> (and read about it in <a href="https://github.com/alefore/knit">https://github.com/alefore/knit</a>).<p>Right now I only implemented on simple pattern: Sophie scarfs. After knitting one that came out somewhat … asymmetric, I decided to just write some software to help me (1) easily adjust the length/width of the scarf (using Bézier curves), and (2) keep track of which row I'm on (so that I can make sure I apply increases/decreases at the right places). In the future, I expect to extend this with many other knitting patterns for other types of items.<p>The application is 100% browser (JavaScript, tested in only in Chrome in Linux/Android) based (no server-side component): all state is kept in the URL hash. I've used it to knit two scarves, including <a href="https://github.com/alefore/knit/blob/main/images/000.jpg">https://github.com/alefore/knit/blob/main/images/000.jpg</a>.<p>The current state of knitting patterns is far from optional, stuck in pre-computer times. Perhaps knitters are not the most technically minded group. Most knitters just download patterns as PDF files. These files will show multiple numbers from which you should choose one depending on the size you're knitting, saying things like "Purl 24 (32 38 42 50 64) times" (you're supposed to pick the right number depending on the size you're knitting). They'll say things like "repeat rows 4 to 6 sixteen times".<p>I think software can display patterns much better (including not being limited to a few pre-selected sizes, but letting you choose the _exact_ size you want, and adjusting everything accordingly), and keep track of your progress much more easily. For example, for my scarf, the user inputs the desired number of rows (based on the desired length, which makes the pattern agnostic to the needle size), and the software computes where to apply increases/decreases.<p>I have many other ideas for improvements (e.g., track how much time I've spent in each row, show a clock), but I figured I'd share this early and ask for feedback. Hopefully there are other fellow knitters in HN. :-) Check it out and let me know what you think!
Show HN: Browser-based knitting (pattern) software
I wrote some simple open source web-based app to (1) dynamically compute knitting patterns (based on input parameters, such as the exact desired size), and (2) display these patterns and help me keep track of which row I'm on (as I start knitting), similar to minimalist "row counters" that other knitters use. It also gives you a simple visualization of the shape of what you're knitting. You can see it in action at <a href="https://alefore.github.io/knit/" rel="nofollow">https://alefore.github.io/knit/</a> (and read about it in <a href="https://github.com/alefore/knit">https://github.com/alefore/knit</a>).<p>Right now I only implemented on simple pattern: Sophie scarfs. After knitting one that came out somewhat … asymmetric, I decided to just write some software to help me (1) easily adjust the length/width of the scarf (using Bézier curves), and (2) keep track of which row I'm on (so that I can make sure I apply increases/decreases at the right places). In the future, I expect to extend this with many other knitting patterns for other types of items.<p>The application is 100% browser (JavaScript, tested in only in Chrome in Linux/Android) based (no server-side component): all state is kept in the URL hash. I've used it to knit two scarves, including <a href="https://github.com/alefore/knit/blob/main/images/000.jpg">https://github.com/alefore/knit/blob/main/images/000.jpg</a>.<p>The current state of knitting patterns is far from optional, stuck in pre-computer times. Perhaps knitters are not the most technically minded group. Most knitters just download patterns as PDF files. These files will show multiple numbers from which you should choose one depending on the size you're knitting, saying things like "Purl 24 (32 38 42 50 64) times" (you're supposed to pick the right number depending on the size you're knitting). They'll say things like "repeat rows 4 to 6 sixteen times".<p>I think software can display patterns much better (including not being limited to a few pre-selected sizes, but letting you choose the _exact_ size you want, and adjusting everything accordingly), and keep track of your progress much more easily. For example, for my scarf, the user inputs the desired number of rows (based on the desired length, which makes the pattern agnostic to the needle size), and the software computes where to apply increases/decreases.<p>I have many other ideas for improvements (e.g., track how much time I've spent in each row, show a clock), but I figured I'd share this early and ask for feedback. Hopefully there are other fellow knitters in HN. :-) Check it out and let me know what you think!
Show HN: Browser-based knitting (pattern) software
I wrote some simple open source web-based app to (1) dynamically compute knitting patterns (based on input parameters, such as the exact desired size), and (2) display these patterns and help me keep track of which row I'm on (as I start knitting), similar to minimalist "row counters" that other knitters use. It also gives you a simple visualization of the shape of what you're knitting. You can see it in action at <a href="https://alefore.github.io/knit/" rel="nofollow">https://alefore.github.io/knit/</a> (and read about it in <a href="https://github.com/alefore/knit">https://github.com/alefore/knit</a>).<p>Right now I only implemented on simple pattern: Sophie scarfs. After knitting one that came out somewhat … asymmetric, I decided to just write some software to help me (1) easily adjust the length/width of the scarf (using Bézier curves), and (2) keep track of which row I'm on (so that I can make sure I apply increases/decreases at the right places). In the future, I expect to extend this with many other knitting patterns for other types of items.<p>The application is 100% browser (JavaScript, tested in only in Chrome in Linux/Android) based (no server-side component): all state is kept in the URL hash. I've used it to knit two scarves, including <a href="https://github.com/alefore/knit/blob/main/images/000.jpg">https://github.com/alefore/knit/blob/main/images/000.jpg</a>.<p>The current state of knitting patterns is far from optional, stuck in pre-computer times. Perhaps knitters are not the most technically minded group. Most knitters just download patterns as PDF files. These files will show multiple numbers from which you should choose one depending on the size you're knitting, saying things like "Purl 24 (32 38 42 50 64) times" (you're supposed to pick the right number depending on the size you're knitting). They'll say things like "repeat rows 4 to 6 sixteen times".<p>I think software can display patterns much better (including not being limited to a few pre-selected sizes, but letting you choose the _exact_ size you want, and adjusting everything accordingly), and keep track of your progress much more easily. For example, for my scarf, the user inputs the desired number of rows (based on the desired length, which makes the pattern agnostic to the needle size), and the software computes where to apply increases/decreases.<p>I have many other ideas for improvements (e.g., track how much time I've spent in each row, show a clock), but I figured I'd share this early and ask for feedback. Hopefully there are other fellow knitters in HN. :-) Check it out and let me know what you think!
Show HN: Browser-based knitting (pattern) software
I wrote some simple open source web-based app to (1) dynamically compute knitting patterns (based on input parameters, such as the exact desired size), and (2) display these patterns and help me keep track of which row I'm on (as I start knitting), similar to minimalist "row counters" that other knitters use. It also gives you a simple visualization of the shape of what you're knitting. You can see it in action at <a href="https://alefore.github.io/knit/" rel="nofollow">https://alefore.github.io/knit/</a> (and read about it in <a href="https://github.com/alefore/knit">https://github.com/alefore/knit</a>).<p>Right now I only implemented on simple pattern: Sophie scarfs. After knitting one that came out somewhat … asymmetric, I decided to just write some software to help me (1) easily adjust the length/width of the scarf (using Bézier curves), and (2) keep track of which row I'm on (so that I can make sure I apply increases/decreases at the right places). In the future, I expect to extend this with many other knitting patterns for other types of items.<p>The application is 100% browser (JavaScript, tested in only in Chrome in Linux/Android) based (no server-side component): all state is kept in the URL hash. I've used it to knit two scarves, including <a href="https://github.com/alefore/knit/blob/main/images/000.jpg">https://github.com/alefore/knit/blob/main/images/000.jpg</a>.<p>The current state of knitting patterns is far from optional, stuck in pre-computer times. Perhaps knitters are not the most technically minded group. Most knitters just download patterns as PDF files. These files will show multiple numbers from which you should choose one depending on the size you're knitting, saying things like "Purl 24 (32 38 42 50 64) times" (you're supposed to pick the right number depending on the size you're knitting). They'll say things like "repeat rows 4 to 6 sixteen times".<p>I think software can display patterns much better (including not being limited to a few pre-selected sizes, but letting you choose the _exact_ size you want, and adjusting everything accordingly), and keep track of your progress much more easily. For example, for my scarf, the user inputs the desired number of rows (based on the desired length, which makes the pattern agnostic to the needle size), and the software computes where to apply increases/decreases.<p>I have many other ideas for improvements (e.g., track how much time I've spent in each row, show a clock), but I figured I'd share this early and ask for feedback. Hopefully there are other fellow knitters in HN. :-) Check it out and let me know what you think!
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: 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: 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!