The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Host a Website in the URL
I wrote this silly thing a couple of weeks ago. It's absolutely useless but it's a fun tech demo for my web server library. Enjoy!
Show HN: Host a Website in the URL
I wrote this silly thing a couple of weeks ago. It's absolutely useless but it's a fun tech demo for my web server library. Enjoy!
Show HN: Host a Website in the URL
I wrote this silly thing a couple of weeks ago. It's absolutely useless but it's a fun tech demo for my web server library. Enjoy!
Show HN: Transform any website or eBook into a research paper (no LLM required)
Show HN: Transform any website or eBook into a research paper (no LLM required)
Show HN: Pgs.sh – A zero-dependency static site hosting service for hackers
Hey all<p>I wanted to show a sneak peak of something I've been working on the for the past few months.<p>I build a lot of projects that involve static hosting and became frustrated by how complicated it is in 2023. All I need to do is move files from my CI onto a server that can serve the files. It shouldn't be as complicated as it is on GCP, AWS, etc. And the ones that are marketed as easy (e.g. Cloudflare Pages, surge.sh) still require the end-user to install a tool first.<p>With pgs.sh the user doesn't need to install anything. Signup is as simple as SSHing into pgs.sh and creating an account. Creating new static sites is as easy as copying files to pgs.sh.<p>To go even further, we have added features like instant promotion and rollback to make it easier to manage deployments safely.<p>The entire service can be managed via SSH commands. Pasted below is our help SSH command: <a href="https://erock.pastes.sh/pgs-cmds.md" rel="nofollow noreferrer">https://erock.pastes.sh/pgs-cmds.md</a><p>This service is in closed beta, but if you join our irc channel #pico.sh @ libera.chat we will invite you to test it out.<p>I'd love to read some feedback on this service, thanks!
Show HN: Bedframe – open-source Browser Extension Development framework
Show HN: Bedframe – open-source Browser Extension Development framework
Show HN: Keep – GitHub Actions for your monitoring tools
Hi Hacker News! Shahar and Tal from Keep here.<p>A few months ago, we introduced here at HN (<a href="https://news.ycombinator.com/item?id=34806482">https://news.ycombinator.com/item?id=34806482</a>) Keep as an “open source alerting CLI” and got some interesting feedback - mainly around UI, automation, and supporting more tools. We were VERY early back then, and we understood that although the current DX around creating alerts is not great, it's not that critical and developers don’t need another tool just for that.<p>But we did find something else.<p>While talking to developers and devops, we found that a lot of companies use many tools that generate alerts - from Cloudwatch, Prometheus, Grafana, and Datadog to tools such as Zabbix or Nagios. We definitely agree consolidation in the observability space is a real thing, but while talking to those companies we feel that there are still real use cases for having more than one tool (and for example, according to Grafana’s 2023 observability survey, 52% of the companies uses more than 6 observability tools <a href="https://grafana.com/observability-survey-2023/" rel="nofollow noreferrer">https://grafana.com/observability-survey-2023/</a>).<p>So we that in mind, we rebuilt Keep with a simple mindset: (1) Integrate with every tool that triggers alerts - it can be either pushing alerts to Keep via webhooks or routing policies or Keep to pull alerts via the tools API. (2) Create a simple abstraction layer to run workflows on top of these alerts. (3) Maintain a great developer experience - open source, API-first, workflows as code and generally having a developer mindset while building Keep.<p>During the time we rebuilt Keep, Datadog released their workflow automation tool (<a href="https://docs.datadoghq.com/service_management/workflows/" rel="nofollow noreferrer">https://docs.datadoghq.com/service_management/workflows/</a>) which led us to the understanding that's exactly what we solve - but for everyone who uses tools other than Datadog.<p>A short demo of Keep with a simple use case: <a href="https://www.youtube.com/watch?v=FPMRCZM8ZYg">https://www.youtube.com/watch?v=FPMRCZM8ZYg</a><p>You can try it yourself by signing into <a href="https://platform.keephq.dev">https://platform.keephq.dev</a><p>Like always - we invite you to try Keep and we are eager to hear any feedback.
Show HN: Keep – GitHub Actions for your monitoring tools
Hi Hacker News! Shahar and Tal from Keep here.<p>A few months ago, we introduced here at HN (<a href="https://news.ycombinator.com/item?id=34806482">https://news.ycombinator.com/item?id=34806482</a>) Keep as an “open source alerting CLI” and got some interesting feedback - mainly around UI, automation, and supporting more tools. We were VERY early back then, and we understood that although the current DX around creating alerts is not great, it's not that critical and developers don’t need another tool just for that.<p>But we did find something else.<p>While talking to developers and devops, we found that a lot of companies use many tools that generate alerts - from Cloudwatch, Prometheus, Grafana, and Datadog to tools such as Zabbix or Nagios. We definitely agree consolidation in the observability space is a real thing, but while talking to those companies we feel that there are still real use cases for having more than one tool (and for example, according to Grafana’s 2023 observability survey, 52% of the companies uses more than 6 observability tools <a href="https://grafana.com/observability-survey-2023/" rel="nofollow noreferrer">https://grafana.com/observability-survey-2023/</a>).<p>So we that in mind, we rebuilt Keep with a simple mindset: (1) Integrate with every tool that triggers alerts - it can be either pushing alerts to Keep via webhooks or routing policies or Keep to pull alerts via the tools API. (2) Create a simple abstraction layer to run workflows on top of these alerts. (3) Maintain a great developer experience - open source, API-first, workflows as code and generally having a developer mindset while building Keep.<p>During the time we rebuilt Keep, Datadog released their workflow automation tool (<a href="https://docs.datadoghq.com/service_management/workflows/" rel="nofollow noreferrer">https://docs.datadoghq.com/service_management/workflows/</a>) which led us to the understanding that's exactly what we solve - but for everyone who uses tools other than Datadog.<p>A short demo of Keep with a simple use case: <a href="https://www.youtube.com/watch?v=FPMRCZM8ZYg">https://www.youtube.com/watch?v=FPMRCZM8ZYg</a><p>You can try it yourself by signing into <a href="https://platform.keephq.dev">https://platform.keephq.dev</a><p>Like always - we invite you to try Keep and we are eager to hear any feedback.
Show HN: Open-source Postman alternative with type safety
Hello! This is Jeane and Samuel and we’re building RecipeUI. RecipeUI is an open source Postman alternative that uses TypeScript to statically type and autocomplete requests.<p>We built this because current API tools don’t deal with the fact that some APIs are just painful to work with. For us, it’s usually error after error as we try to figure out how to properly form the first request.<p>We recorded a demo to show you how TypeScript helps us autocomplete a request correctly.
<a href="https://youtu.be/O_Mly_p-g5s" rel="nofollow noreferrer">https://youtu.be/O_Mly_p-g5s</a><p>How does our platform improve the developer experience? The analogy is similar to using a statically typed language vs dynamically typed. Most API tools are dynamically typed. You’re guessing the params and relying on the request to magically work at runtime, only for you to go back to stack overflow or the docs when it doesn’t.<p>We take the approach of defining parameters and the schema first. When you add a new parameter, you need to mention upfront if it’s required and what type it is (integer, string, boolean). While this can be painful in the beginning, it will save you and anyone you share this with the hassle of understanding how this API works.<p>Our app is cross-platform on web and desktop. Our desktop app is <20mb and built on top of Rust with Tauri, NextJS, and Supabase. We open source our code because we want to be transparent about how API requests and secrets are handled (all local IndexDB).<p>I built the first version of this at Robinhood when my colleagues were sharing bash scripts and internal APIs on slack to test things. I wanted to make it easier for anyone to use an API quickly and made use of our OpenAPI specs to generate a nice autocomplete API tool. Soon after, the Options team, then the Crypto team, and then the whole eng org at Robinhood adopted this tool!<p>Try it out at recipeui.com! Please star us on GitHub if you like the product <a href="https://github.com/RecipeUI/RecipeUI">https://github.com/RecipeUI/RecipeUI</a>.
Show HN: Open-source Postman alternative with type safety
Hello! This is Jeane and Samuel and we’re building RecipeUI. RecipeUI is an open source Postman alternative that uses TypeScript to statically type and autocomplete requests.<p>We built this because current API tools don’t deal with the fact that some APIs are just painful to work with. For us, it’s usually error after error as we try to figure out how to properly form the first request.<p>We recorded a demo to show you how TypeScript helps us autocomplete a request correctly.
<a href="https://youtu.be/O_Mly_p-g5s" rel="nofollow noreferrer">https://youtu.be/O_Mly_p-g5s</a><p>How does our platform improve the developer experience? The analogy is similar to using a statically typed language vs dynamically typed. Most API tools are dynamically typed. You’re guessing the params and relying on the request to magically work at runtime, only for you to go back to stack overflow or the docs when it doesn’t.<p>We take the approach of defining parameters and the schema first. When you add a new parameter, you need to mention upfront if it’s required and what type it is (integer, string, boolean). While this can be painful in the beginning, it will save you and anyone you share this with the hassle of understanding how this API works.<p>Our app is cross-platform on web and desktop. Our desktop app is <20mb and built on top of Rust with Tauri, NextJS, and Supabase. We open source our code because we want to be transparent about how API requests and secrets are handled (all local IndexDB).<p>I built the first version of this at Robinhood when my colleagues were sharing bash scripts and internal APIs on slack to test things. I wanted to make it easier for anyone to use an API quickly and made use of our OpenAPI specs to generate a nice autocomplete API tool. Soon after, the Options team, then the Crypto team, and then the whole eng org at Robinhood adopted this tool!<p>Try it out at recipeui.com! Please star us on GitHub if you like the product <a href="https://github.com/RecipeUI/RecipeUI">https://github.com/RecipeUI/RecipeUI</a>.
Show HN: Open-source Postman alternative with type safety
Hello! This is Jeane and Samuel and we’re building RecipeUI. RecipeUI is an open source Postman alternative that uses TypeScript to statically type and autocomplete requests.<p>We built this because current API tools don’t deal with the fact that some APIs are just painful to work with. For us, it’s usually error after error as we try to figure out how to properly form the first request.<p>We recorded a demo to show you how TypeScript helps us autocomplete a request correctly.
<a href="https://youtu.be/O_Mly_p-g5s" rel="nofollow noreferrer">https://youtu.be/O_Mly_p-g5s</a><p>How does our platform improve the developer experience? The analogy is similar to using a statically typed language vs dynamically typed. Most API tools are dynamically typed. You’re guessing the params and relying on the request to magically work at runtime, only for you to go back to stack overflow or the docs when it doesn’t.<p>We take the approach of defining parameters and the schema first. When you add a new parameter, you need to mention upfront if it’s required and what type it is (integer, string, boolean). While this can be painful in the beginning, it will save you and anyone you share this with the hassle of understanding how this API works.<p>Our app is cross-platform on web and desktop. Our desktop app is <20mb and built on top of Rust with Tauri, NextJS, and Supabase. We open source our code because we want to be transparent about how API requests and secrets are handled (all local IndexDB).<p>I built the first version of this at Robinhood when my colleagues were sharing bash scripts and internal APIs on slack to test things. I wanted to make it easier for anyone to use an API quickly and made use of our OpenAPI specs to generate a nice autocomplete API tool. Soon after, the Options team, then the Crypto team, and then the whole eng org at Robinhood adopted this tool!<p>Try it out at recipeui.com! Please star us on GitHub if you like the product <a href="https://github.com/RecipeUI/RecipeUI">https://github.com/RecipeUI/RecipeUI</a>.
Show HN: Puck – Open-source visual editor for React
Hey hackers, OP here!<p>I've been dipping in and out of this problem space for the last few years with many of my clients.<p>Puck sits somewhere between an old-school WYSIWYG-powered CMS and headless one, allowing content teams to author content using real React components.<p>Traditional CMS solutions were flexible but often resulted in page that completely broke the brand guidelines. Headless CMS solutions are a fantastic way of controlling brand by restricting UI changes to developers, but makes layout changes restrictive and slow as developers often need to get involved.<p>Puck provides a visual editor for React that can sit on top of your existing headless CMS (or act as standalone). We've been dog-fooding it on a few pages at <a href="https://measured.co" rel="nofollow noreferrer">https://measured.co</a> and on <a href="https://wellpaid.io" rel="nofollow noreferrer">https://wellpaid.io</a>. So far, so good<p>The API is built for React, which allows FE devs to quickly integrate their existing component and add some form fields for author input, or connect it to a headless CMS of choice.<p>It's open-source under MIT, and pairs nicely with Next.js (check out the demo application). Next in the pipeline: support for multi-column layouts, richer demos, new plugins.<p>Looking forward to hearing your comments!
Show HN: Puck – Open-source visual editor for React
Hey hackers, OP here!<p>I've been dipping in and out of this problem space for the last few years with many of my clients.<p>Puck sits somewhere between an old-school WYSIWYG-powered CMS and headless one, allowing content teams to author content using real React components.<p>Traditional CMS solutions were flexible but often resulted in page that completely broke the brand guidelines. Headless CMS solutions are a fantastic way of controlling brand by restricting UI changes to developers, but makes layout changes restrictive and slow as developers often need to get involved.<p>Puck provides a visual editor for React that can sit on top of your existing headless CMS (or act as standalone). We've been dog-fooding it on a few pages at <a href="https://measured.co" rel="nofollow noreferrer">https://measured.co</a> and on <a href="https://wellpaid.io" rel="nofollow noreferrer">https://wellpaid.io</a>. So far, so good<p>The API is built for React, which allows FE devs to quickly integrate their existing component and add some form fields for author input, or connect it to a headless CMS of choice.<p>It's open-source under MIT, and pairs nicely with Next.js (check out the demo application). Next in the pipeline: support for multi-column layouts, richer demos, new plugins.<p>Looking forward to hearing your comments!
Show HN: Puck – Open-source visual editor for React
Hey hackers, OP here!<p>I've been dipping in and out of this problem space for the last few years with many of my clients.<p>Puck sits somewhere between an old-school WYSIWYG-powered CMS and headless one, allowing content teams to author content using real React components.<p>Traditional CMS solutions were flexible but often resulted in page that completely broke the brand guidelines. Headless CMS solutions are a fantastic way of controlling brand by restricting UI changes to developers, but makes layout changes restrictive and slow as developers often need to get involved.<p>Puck provides a visual editor for React that can sit on top of your existing headless CMS (or act as standalone). We've been dog-fooding it on a few pages at <a href="https://measured.co" rel="nofollow noreferrer">https://measured.co</a> and on <a href="https://wellpaid.io" rel="nofollow noreferrer">https://wellpaid.io</a>. So far, so good<p>The API is built for React, which allows FE devs to quickly integrate their existing component and add some form fields for author input, or connect it to a headless CMS of choice.<p>It's open-source under MIT, and pairs nicely with Next.js (check out the demo application). Next in the pipeline: support for multi-column layouts, richer demos, new plugins.<p>Looking forward to hearing your comments!
Show HN: TTop – System monitoring tool with historical data, triggers and TUI
It is not top/htop replacement because of historical snapshots which can help you to find problems back in time
Show HN: Cross-platform dotfiles manager written in Rust
Show HN: Recognize license plates using fine-tuned yolov8, OCR and IP camera
Hey, just a work related project I made, which could be open sourced :D<p>If you're looking for an example on how to use/fine-tune yolov8, I feel like taking a look at this repo and reading the README could help you get up to speed (also linked some nice refs)!<p>This is actually a full rewrite of a proprietary project I made (and documented on my site) like a year ago, will do some finishing touches (write blog post about it, mark the old version deprecated, record a tutorial on how to set it up on an Ubuntu server, etc, etc) in the following month, but felt like sharing it now, cuz I consider it done<p>The only proprietary part is the client, which receives the images and does stuff with db (has to interact with internal APIs, so there's no reason to make it oss anyways). Also, the client contains only the business logic, all of the fun ai/web server stuff is fully open under AGPL-3.0 (and an example client without the business logic is available ... in rust btw xdd).
Show HN: Rapidgzip – Truly Parallel Gzip Decompression with 10 GB/s
I have posted a much earlier version of this over a year ago [0].<p>Since then a lot has changed. Obviously, the name has changed. This happened for the paper publication [1].<p>I have also optimized the speed, integrated ISA-L for special cases, limited the compression-ratio-dependent maximum memory consumption, and finally added parallelized CRC32 computation, which adds ~5% overhead no matter the number of cores used. At this point, I am leaning towards calling it production-ready although there are still many ideas for improvements.<p>Redoing the benchmarks of the older Show HN, would look like this:<p><pre><code> time pigz -d -c 4GiB-base64.gz | wc -c # real ~13.4 s -> ~320 MB/s
time rapidgzip -d -c 4GiB-base64.gz | wc -c # real ~1.26 s -> ~3.4 GB/s
</code></pre>
However, at this point, the piping itself becomes a problem. Rapidgzip is actually slightly faster than cat when comparing the piped bandwidth! E.g., compare these additional benchmarks:<p><pre><code> time cat 4GiB-base64.gz | wc -c # real ~1.06 s -> ~3.1 GB/s
time fcat 4GiB-base64.gz | wc -c # real ~0.41 s -> ~8.0 GB/s
time rapidgzip -o /dev/null -d 4GiB-base64.gz # real ~0.68 s -> ~6.5 GB/s
</code></pre>
fcat is an alternative cat implementation that uses vmsplice to speed up piping. According to the ReadMe it currently is broken, but it works fine on my system and piping it to md5sum yields consistent results [2].<p>So, at this point, I/O and actually also allocations have become a limiting factor and if you want full speed, you would have to interface with the rapidgzip library interface directly (in C++ or via the Python bindings) and process the decompressed data in memory.<p>The project ReadMe contains further benchmarks with Silesia and FASTQ data and scaling up to 128 cores, for which rapidgzip achieves 12 GB/s for Silesia and 24 GB/s when an index has been created with --export-index and is used with --import-index.<p>It can also be tested with ratarmount 0.14.0, which now uses rapidgzip as a backend by default for .gz and .tar.gz files [3].<p>[0] <a href="https://news.ycombinator.com/item?id=32366959">https://news.ycombinator.com/item?id=32366959</a>
[1] <a href="https://dl.acm.org/doi/10.1145/3588195.3592992" rel="nofollow noreferrer">https://dl.acm.org/doi/10.1145/3588195.3592992</a>
[2] <a href="https://github.com/mre/fcat">https://github.com/mre/fcat</a>
[3] <a href="https://github.com/mxmlnkn/ratarmount">https://github.com/mxmlnkn/ratarmount</a>