The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Hyper – Standards-first React alternative
Author here. This is an attempt to simplify frontend development:<p>1. Standards first: User interfaces should be assembled with HTML, styled with CSS, and enhanced with JavaScript.<p>2. Less abstractions: UI composition should be easy and require as few idioms and abstractions as possible, both on client and server.<p>3. Design Systems: Design should be a separate subsystem, easily accessible for developers who care about and understand design.<p>4. Scalability: Complex UIs should retain simplicity as the application grows.<p>Eager to hear your thoughts!
Show HN: Hyper – Standards-first React alternative
Author here. This is an attempt to simplify frontend development:<p>1. Standards first: User interfaces should be assembled with HTML, styled with CSS, and enhanced with JavaScript.<p>2. Less abstractions: UI composition should be easy and require as few idioms and abstractions as possible, both on client and server.<p>3. Design Systems: Design should be a separate subsystem, easily accessible for developers who care about and understand design.<p>4. Scalability: Complex UIs should retain simplicity as the application grows.<p>Eager to hear your thoughts!
Show HN: Aberdeen – An elegant approach to reactive UIs
Yes, another reactive UI framework for JavaScript. Bear with me, please... :-)<p>I 'invented' the concept for this back in 2011, and it was used (as a proprietary lib) in various startups. Even though <i>many</i> similar open source libs have been released since, and boy have I tried a lot of them, none have been able to capture the elegance and DX of what we had back then. I might be biased though. :-)<p>So I started creating a cleaned-up, modern, TypeScript, open source implementation for the concept about five years ago. After many iterations, working on the project on and off, I'm finally happy with its API and the developer experience it offers. I'm calling it 1.0!<p>The concept: It uses many small, anonymous functions for emitting DOM elements, and automatically reruns them when their underlying proxied data changes. This proxied data can be anything from simple values to complex, typed, and deeply nested data structures.<p>As I'm currently free to spend my time on labors of love like this, I'm planning to expand the ecosystem around this to include synchronizing data with a remote server/database, and to make CRUD apps very rapid and perhaps even pleasurable to implement.<p>I've celebrated 1.0 by creating a tutorial with editable interactive examples! <a href="https://aberdeenjs.org/Tutorial/" rel="nofollow">https://aberdeenjs.org/Tutorial/</a><p>I would love to hear your feedback. The first few people to actually give Aberdeen a shot can expect fanatical support from me! :-)
Show HN: Aberdeen – An elegant approach to reactive UIs
Yes, another reactive UI framework for JavaScript. Bear with me, please... :-)<p>I 'invented' the concept for this back in 2011, and it was used (as a proprietary lib) in various startups. Even though <i>many</i> similar open source libs have been released since, and boy have I tried a lot of them, none have been able to capture the elegance and DX of what we had back then. I might be biased though. :-)<p>So I started creating a cleaned-up, modern, TypeScript, open source implementation for the concept about five years ago. After many iterations, working on the project on and off, I'm finally happy with its API and the developer experience it offers. I'm calling it 1.0!<p>The concept: It uses many small, anonymous functions for emitting DOM elements, and automatically reruns them when their underlying proxied data changes. This proxied data can be anything from simple values to complex, typed, and deeply nested data structures.<p>As I'm currently free to spend my time on labors of love like this, I'm planning to expand the ecosystem around this to include synchronizing data with a remote server/database, and to make CRUD apps very rapid and perhaps even pleasurable to implement.<p>I've celebrated 1.0 by creating a tutorial with editable interactive examples! <a href="https://aberdeenjs.org/Tutorial/" rel="nofollow">https://aberdeenjs.org/Tutorial/</a><p>I would love to hear your feedback. The first few people to actually give Aberdeen a shot can expect fanatical support from me! :-)
Show HN: Hyvector – A fast and modern SVG editor
I have been working on Hyvector for the last five years and finally decided to present the result of my work.<p>Hyvector is an SVG editor that runs in all modern browsers. It is stable, very fast, and capable of handling complex SVG images.<p>Big new features like art strokes, vector tracing, colorizing are in the making, but for now the focus is on pushing a polished first release out of the door.<p>I would love to hear any feedback on what you like, missing features, or any bugs you encounter via our issue tracker: <a href="https://github.com/hyvectorapp/hyvector-issues">https://github.com/hyvectorapp/hyvector-issues</a><p>Note that while Hyvector should work on a phone, it is much more usable on a desktop computer or tablet.
Show HN: Hyvector – A fast and modern SVG editor
I have been working on Hyvector for the last five years and finally decided to present the result of my work.<p>Hyvector is an SVG editor that runs in all modern browsers. It is stable, very fast, and capable of handling complex SVG images.<p>Big new features like art strokes, vector tracing, colorizing are in the making, but for now the focus is on pushing a polished first release out of the door.<p>I would love to hear any feedback on what you like, missing features, or any bugs you encounter via our issue tracker: <a href="https://github.com/hyvectorapp/hyvector-issues">https://github.com/hyvectorapp/hyvector-issues</a><p>Note that while Hyvector should work on a phone, it is much more usable on a desktop computer or tablet.
Show HN: Hyvector – A fast and modern SVG editor
I have been working on Hyvector for the last five years and finally decided to present the result of my work.<p>Hyvector is an SVG editor that runs in all modern browsers. It is stable, very fast, and capable of handling complex SVG images.<p>Big new features like art strokes, vector tracing, colorizing are in the making, but for now the focus is on pushing a polished first release out of the door.<p>I would love to hear any feedback on what you like, missing features, or any bugs you encounter via our issue tracker: <a href="https://github.com/hyvectorapp/hyvector-issues">https://github.com/hyvectorapp/hyvector-issues</a><p>Note that while Hyvector should work on a phone, it is much more usable on a desktop computer or tablet.
Show HN: Extension for full-text browser history search
Hey. I’ve been working on Rearview, a browser extension that makes browsing history more useful. It’s available for Chrome, Edge, and Firefox.<p>What it does:<p>- Full-text Search: Search page content, not just URLs or titles.<p>- More Filter: Organize history by date, time, or visits.<p>- AI Assistant: Get insights from your history. (Optional, with your own api key.)<p>Everything stays local in IndexedDB.<p>Feedback & Feature request welcome.<p>BTW, since Firefox does not provide a favicon URLs implementation (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1315616" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1315616</a>),I am currently requesting icons in Firefox via <a href="https://icon.horse/" rel="nofollow">https://icon.horse/</a>, the performance seems not ideal.
Is there a more recommended solution?
Show HN: US Routing – Python library for fast local routing in the US
Show HN: US Routing – Python library for fast local routing in the US
Show HN: Using eBPF to see through encryption without a proxy
Hi HN, I'm Tyler Flint, one of the creators of qtap.<p>For a while now, my team and I at Qpoint.io have been grappling with the challenge of understanding what's actually happening inside the encrypted traffic leaving our production systems. Modern apps rely heavily on third-party APIs (think payment processors, data providers, etc.), but once TLS kicks in, figuring out exactly what data is being sent, identifying PII exposure, or debugging integration issues becomes incredibly difficult without resorting to complex and often brittle solutions.<p>Traditional approaches like forward proxies require terminating TLS (MITM), managing certificates, and often introduce performance bottlenecks or single points of failure. Network firewalls usually operate at L3/L4 and lack payload visibility. We felt there had to be a better way.<p>That's why we built qtap. It's a lightweight agent that uses eBPF to tap into network traffic at the kernel level. The key idea is to hook into common TLS libraries (like OpenSSL) before encryption and after decryption. This gives us deep visibility into the actual request/response payloads of HTTPS/TLS traffic without needing to terminate the connection or manage certs. Because it leverages eBPF, the performance impact is minimal compared to traditional methods.<p>With qtap, we can now see exactly which external services our apps are talking to, inspect the payloads for debugging or security auditing (e.g., spotting accidental PII leaks), monitor API performance/errors for third-party dependencies, and get a much clearer picture of our egress traffic patterns.<p>We've found this approach really powerful for improving reliability and security posture. We've packaged qtap as a Linux Binary, Docker container, and Helm chart for deployment.<p>This is still evolving, but we're excited about the potential of using eBPF for this kind of deep, yet non-intrusive, visibility.<p>We'd love to get the HN community's feedback:<p><pre><code> Do you face similar challenges monitoring encrypted egress traffic?
What are your thoughts on using eBPF for this compared to other methods?
Any suggestions or potential use cases we haven't considered?
</code></pre>
Happy to answer any questions!
Show HN: Using eBPF to see through encryption without a proxy
Hi HN, I'm Tyler Flint, one of the creators of qtap.<p>For a while now, my team and I at Qpoint.io have been grappling with the challenge of understanding what's actually happening inside the encrypted traffic leaving our production systems. Modern apps rely heavily on third-party APIs (think payment processors, data providers, etc.), but once TLS kicks in, figuring out exactly what data is being sent, identifying PII exposure, or debugging integration issues becomes incredibly difficult without resorting to complex and often brittle solutions.<p>Traditional approaches like forward proxies require terminating TLS (MITM), managing certificates, and often introduce performance bottlenecks or single points of failure. Network firewalls usually operate at L3/L4 and lack payload visibility. We felt there had to be a better way.<p>That's why we built qtap. It's a lightweight agent that uses eBPF to tap into network traffic at the kernel level. The key idea is to hook into common TLS libraries (like OpenSSL) before encryption and after decryption. This gives us deep visibility into the actual request/response payloads of HTTPS/TLS traffic without needing to terminate the connection or manage certs. Because it leverages eBPF, the performance impact is minimal compared to traditional methods.<p>With qtap, we can now see exactly which external services our apps are talking to, inspect the payloads for debugging or security auditing (e.g., spotting accidental PII leaks), monitor API performance/errors for third-party dependencies, and get a much clearer picture of our egress traffic patterns.<p>We've found this approach really powerful for improving reliability and security posture. We've packaged qtap as a Linux Binary, Docker container, and Helm chart for deployment.<p>This is still evolving, but we're excited about the potential of using eBPF for this kind of deep, yet non-intrusive, visibility.<p>We'd love to get the HN community's feedback:<p><pre><code> Do you face similar challenges monitoring encrypted egress traffic?
What are your thoughts on using eBPF for this compared to other methods?
Any suggestions or potential use cases we haven't considered?
</code></pre>
Happy to answer any questions!
Show HN: Feedsmith — Fast parser & generator for RSS, Atom, OPML feed namespaces
Hi HN! While working on a project that involves frequently parsing a lot of feeds, I needed a fast JavaScript-based parser to extract specific fields from feed namespaces. Existing Node packages were either too slow or merged all feed formats, losing namespace information. So I decided to write it myself and created this NPM package with a simple API.<p>Feedsmith supports all feed formats and many popular namespaces, including: Podcast, Media, iTunes, Dublin Core, and more. It can also parse and generate OPML files.<p>I am currently adding support for more namespaces and feed generation for RSS, Atom and RDF. The library grew into something bigger than I initially anticipated, so I also started creating a dedicated documentation website to describe all the features.
Show HN: Feedsmith — Fast parser & generator for RSS, Atom, OPML feed namespaces
Hi HN! While working on a project that involves frequently parsing a lot of feeds, I needed a fast JavaScript-based parser to extract specific fields from feed namespaces. Existing Node packages were either too slow or merged all feed formats, losing namespace information. So I decided to write it myself and created this NPM package with a simple API.<p>Feedsmith supports all feed formats and many popular namespaces, including: Podcast, Media, iTunes, Dublin Core, and more. It can also parse and generate OPML files.<p>I am currently adding support for more namespaces and feed generation for RSS, Atom and RDF. The library grew into something bigger than I initially anticipated, so I also started creating a dedicated documentation website to describe all the features.
Show HN: Whippy Term - GUI terminal for embedded development (Linux and Windows)
Show HN: Whippy Term - GUI terminal for embedded development (Linux and Windows)
Show HN: Reverse Pac-Man
Keep one eye on the first ghost and the other on the second
Show HN: eInk optimized manga with Kindle Comic Converter (+Kobo/ReMarkable)
Kindle Comic Converter optimizes comics and manga for eink readers like Kindle, Kobo, ReMarkable, and more. Pages display in fullscreen without margins, with proper fixed layout support. Its main feature is various optional image processing steps to look good on eink screens, which have different requirements than normal LCD screens. It also does filesize optimization by downscaling to your specific device's screen resolution, which can improve performance on underpowered ereaders. Supported input formats include folders/CBZ/CBR/PDF of JPG/PNG files and more. Supported output formats include MOBI/AZW3, EPUB, KEPUB, and CBZ.<p>Hey everyone! I'm the current maintainer of KCC since 2023, thanks for using it! I’ve been reading manga on Kindle ever since I got the big 9.7” Kindle DX from 2010 using mangle, and upgraded to the even bigger 10.2” Kindle Scribe 2022 using KCC.<p>The biggest contributions I've made to KCC are:<p>- added modern macOS support and removed homebrew requirement
- ported code to run on native Apple silicon M1 chip and later for a 2x speed boost (qt5->qt6)
- free open source windows codesign with SignPath - fixed Kindle Scribe support
- and tons of other various features and bug fixes and developer friendly changes
- created a legacy Windows 7 build with 300+ downloads…<p>The biggest community PRs were:<p>- huge 2x speed boosts due to various CPU/IO optimizations
- Kobo/Remarkable support<p>Enjoy using KCC and let me know if you have any questions!
Show HN: eInk optimized manga with Kindle Comic Converter (+Kobo/ReMarkable)
Kindle Comic Converter optimizes comics and manga for eink readers like Kindle, Kobo, ReMarkable, and more. Pages display in fullscreen without margins, with proper fixed layout support. Its main feature is various optional image processing steps to look good on eink screens, which have different requirements than normal LCD screens. It also does filesize optimization by downscaling to your specific device's screen resolution, which can improve performance on underpowered ereaders. Supported input formats include folders/CBZ/CBR/PDF of JPG/PNG files and more. Supported output formats include MOBI/AZW3, EPUB, KEPUB, and CBZ.<p>Hey everyone! I'm the current maintainer of KCC since 2023, thanks for using it! I’ve been reading manga on Kindle ever since I got the big 9.7” Kindle DX from 2010 using mangle, and upgraded to the even bigger 10.2” Kindle Scribe 2022 using KCC.<p>The biggest contributions I've made to KCC are:<p>- added modern macOS support and removed homebrew requirement
- ported code to run on native Apple silicon M1 chip and later for a 2x speed boost (qt5->qt6)
- free open source windows codesign with SignPath - fixed Kindle Scribe support
- and tons of other various features and bug fixes and developer friendly changes
- created a legacy Windows 7 build with 300+ downloads…<p>The biggest community PRs were:<p>- huge 2x speed boosts due to various CPU/IO optimizations
- Kobo/Remarkable support<p>Enjoy using KCC and let me know if you have any questions!
Show HN: Klavis AI – Open-source MCP integration for AI applications
Hi HN, we are excited to show you Klavis AI. It is an open source project and we provide hosted versions with API access as well. (Website: <a href="https://www.klavis.ai/">https://www.klavis.ai/</a>, Github repo: <a href="https://github.com/Klavis-AI/klavis">https://github.com/Klavis-AI/klavis</a>)<p>We're addressing a couple of key problems with using MCPs. First, many available MCP servers lack native or used-based authentications, creating security vulnerabilities and adding complexity during development.<p>Second, many MCP servers are personal projects, not designed for the reliability needed in production.<p>Connecting to these servers usually requires writing custom MCP client code for the MCP protocol itself, which is a barrier, especially if you already have function calling systems in place.<p>Klavis AI aims to address these issues. To simplify access, we offer an API to launch production-ready, hosted MCP servers quickly via our API. The API also provides built-in OAuth and multi-tenancy auth support for MCP servers.<p>We also want to remove the need for developers to write MCP client code. You can use our API to interact with any remote MCP servers directly from your existing backend infrastructure. For faster prototyping or direct user interaction, we also provide open-source client interfaces for Web, Slack, and Discord.<p>The MCP servers and clients code is open source because we want to contribute to the MCP community.<p>For a quick start in the hosted verions, log in to our website and generate an API key. Then start calling our APIs directly. You can find more details in our doc: <a href="https://docs.klavis.ai">https://docs.klavis.ai</a><p>For a quick start in the open source version, go to our github repository and check out the detailed readme on each MCP server and client.<p>A little note about myself: my background includes working on the function calling for Google Gemini. During that time, I saw firsthand the challenges teams face when trying to connect AI agents to external tools. I want to bring my insights and energy to accelerate MCP adoption.<p>This is an early release, and we’d appreciate feedback from the community. What are your worst pain points related to MCPs, either as a developer or a general user? What other MCP servers or features would be most valuable to you?<p>We'll be around in the comments. Thanks for reading!