The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Keypub.sh – OAuth for the terminal using SSH keys
Hi HN! I built KeyPub.sh to solve the problem of user verification for CLI applications. It's essentially OAuth for the terminal, but using SSH keys that developers and users already have.<p>- No installation needed - works with existing SSH setup
- Privacy-focused: users control what email info is shared
- Simple email verification process
- Free public service
- Perfect for CLI app developers who don't want to build user verification<p>Try it with:
`$ ssh keypub.sh about`<p>Source code: <a href="https://github.com/skariel/keypub">https://github.com/skariel/keypub</a>
Show HN: Keypub.sh – OAuth for the terminal using SSH keys
Hi HN! I built KeyPub.sh to solve the problem of user verification for CLI applications. It's essentially OAuth for the terminal, but using SSH keys that developers and users already have.<p>- No installation needed - works with existing SSH setup
- Privacy-focused: users control what email info is shared
- Simple email verification process
- Free public service
- Perfect for CLI app developers who don't want to build user verification<p>Try it with:
`$ ssh keypub.sh about`<p>Source code: <a href="https://github.com/skariel/keypub">https://github.com/skariel/keypub</a>
Show HN: Keypub.sh – OAuth for the terminal using SSH keys
Hi HN! I built KeyPub.sh to solve the problem of user verification for CLI applications. It's essentially OAuth for the terminal, but using SSH keys that developers and users already have.<p>- No installation needed - works with existing SSH setup
- Privacy-focused: users control what email info is shared
- Simple email verification process
- Free public service
- Perfect for CLI app developers who don't want to build user verification<p>Try it with:
`$ ssh keypub.sh about`<p>Source code: <a href="https://github.com/skariel/keypub">https://github.com/skariel/keypub</a>
Show HN: Get e-signatures & pay per signed doc
Woke up today with a 100-degree fever & found out Google is now our competitor.<p>Last week, we started building signwith.co/ - a simple, pay-per-use e-signature tool for people who are struggling with complex e-sign tools.<p>The plan was to build quietly, run a private beta, get 50 users in 15 days, and then do a launch. Easy peasy.<p>But since Google dropped into the e-signature space - we needed to talk.<p>So after 30 minutes of existential dread, a lot of “what are we even doing?” thoughts, and one strong dose of paracetamol<p>we said, screw it. - let’s change gears.<p>So now we're opening our beta, and here's the deal:<p>• All the people who join will get free credits worth 10 signed docs
• 12 months credit validity
• No complexity
• No hidden cost
• No subscription commitment<p>You can join the beta here - <a href="http://signwith.co" rel="nofollow">http://signwith.co</a><p>That said, we see Google's entry in the signature space as validation.<p>This event expanded the market with such massive awareness.<p>Let me be clear: We’re not trying to be DocuSign, Google, or any other enterprise beast.<p>We’re indie makers and building for:
• The freelancers
• The consultants
• The indie and small business owners
• and anyone who just needs a contract signed—fast, simple, no headaches.<p>Here’s how SignWith works:
• Upload your doc
• Drop signature spots
• Send it out and track
• Pay per signed document<p>That’s it. No subscriptions. No feature bloat. No crazy hidden charges and no complex pricing tiers.<p>If you've read it so far, would love to see you on the other side.<p>And hey, if you’ve got any feedback, suggestions, or just want to tell us what you need, reply here or drop me a DM. We’re all ears!<p>Cheers!
Show HN: Yakari – Interactive TUIs for CLI tools
Hi HN!<p>I wanted to share Yakari, a tool I built to make command-line interfaces more approachable through interactive TUIs. If you've ever forgotten CLI flags or needed to look up command syntax, this might help.<p>Yakari turns complex commands into interactive menus. Users can navigate through options with simple key presses instead of memorizing complex command structures. If you've used Emacs and Magit (or any other Transient) before, the interface will feel familiar.<p>Features:
- Transform CLIs into guided menus
- Create custom menus for any CLI
- Support for flags, named parameters, choices, and interactive inputs
- Command history and contextual help<p>You can try it out without installing thanks to uv [1]:<p><pre><code> uvx --from yakari ykr demo # Play with a demo showcasing different argument types
uvx --from yakari ykr git # Try the git menu in any git repo
</code></pre>
The project is built with Python using Textual and is heavily inspired by Emacs' Transient.<p>I'd love feedback from both CLI users and developers. What tools would you find most useful to have menus for? How could this make your terminal workflows easier?<p>[1] <a href="https://docs.astral.sh/uv/" rel="nofollow">https://docs.astral.sh/uv/</a>
Show HN: Yakari – Interactive TUIs for CLI tools
Hi HN!<p>I wanted to share Yakari, a tool I built to make command-line interfaces more approachable through interactive TUIs. If you've ever forgotten CLI flags or needed to look up command syntax, this might help.<p>Yakari turns complex commands into interactive menus. Users can navigate through options with simple key presses instead of memorizing complex command structures. If you've used Emacs and Magit (or any other Transient) before, the interface will feel familiar.<p>Features:
- Transform CLIs into guided menus
- Create custom menus for any CLI
- Support for flags, named parameters, choices, and interactive inputs
- Command history and contextual help<p>You can try it out without installing thanks to uv [1]:<p><pre><code> uvx --from yakari ykr demo # Play with a demo showcasing different argument types
uvx --from yakari ykr git # Try the git menu in any git repo
</code></pre>
The project is built with Python using Textual and is heavily inspired by Emacs' Transient.<p>I'd love feedback from both CLI users and developers. What tools would you find most useful to have menus for? How could this make your terminal workflows easier?<p>[1] <a href="https://docs.astral.sh/uv/" rel="nofollow">https://docs.astral.sh/uv/</a>
Show HN: NoSQL, but it's SQLite
Manipulate your SQLite database like a giant Javascript object. Built with o1.
Show HN: NoSQL, but it's SQLite
Manipulate your SQLite database like a giant Javascript object. Built with o1.
Show HN: NoSQL, but it's SQLite
Manipulate your SQLite database like a giant Javascript object. Built with o1.
Show HN: celine/bibhtml: a Web Components referencing system for HTML documents
Show HN: celine/bibhtml: a Web Components referencing system for HTML documents
Show HN: Rivet Actors – Durable Objects build with Rust, FoundationDB, Isolates
Hello! We posted a Show HN for Rivet last year for our container orchestration project (<a href="https://news.ycombinator.com/item?id=37188659">https://news.ycombinator.com/item?id=37188659</a>). In that time, a lot has changed that I think HN will find interesting.<p>Rivet is open-source actor infrastructure similar to Cloudflare's Durable Objects. Rivet itself already serves millions of MAU in production using our current container runtime – primarily for multiplayer games – and Rivet Actors are a new extension to support actor-like workloads. Rivet Actor's core primitives are RPC, state, and events.<p>Actors are powered by Rust, V8 isolates (supports Deno), and FoundationDB. An architecture diagram is available here for [1]. If you're not familiar with FoundationDB, you're overdue to watch Dave Rosenthal's talk [3]. (I firmly believe it's by far the best permissively licensed database; if only it had a well maintained SQL layer.)<p>Here's where Rivet's architecture gets fun – we don't rely on a traditional orchestrator like Kubernetes or Nomad for our runtime. Instead, our orchestrator is powered by an in-house actor-like workflow engine – similar to how FoundationDB is powered by their own actor library (Flow [4]) internally. It lets us reliably & efficiently build complex logic – like our orchestrator – that would normally be incredibly difficult to build correctly. For example, here's the logic that powers Rivet Actors themselves with complex mechanisms like retry upgrades, retry backoffs, and draining [2].<p>One of the reasons we built Rivet Actors is because we tried to replace most of our Redis-based realtime infrastructure with Durable Objects. The architecture allowed us to build realtime features much faster & efficiently, but the platform & APIs were needlessly rigid and difficult to use. Our goal is to build an actor-like platform that includes the bells and whistles required for developers to benefit from the actor model without the learning curve of tools like Erlang/OTP, Akka, or Orleans.<p>Rivet Actors provides a few key benefits in flexibility over Durable Objects:<p>- Open-source (Apache 2.0) – built to be self-hosted and deployed on-prem<p>- Provides observability out of the box, no Logpush required<p>- Rivet Actors support the Deno runtime, so NPM & JSR just works<p>- @rivet-gg/actor [5] framework provides RPC, state, and events out of the box for faster bootstrapping; you can modify and deploy it yourself<p>- Supports both V8 isolates & Docker-compatible containers so you can run any software you'd like, like Godot/Unity servers or video transcoding<p>- Also supports TCP & UDP (we run games!)<p>- Provides vanilla HTTP API for easy use with existing apps<p>- Full control over regions<p>There's plenty more that I don't have space to talk about. Give our docs a read if you'd like to learn more [6] or read about internal design decisions [7]. I'll be in the comments answering questions!<p>Cheers,
Nathan<p>[1] <a href="https://github.com/rivet-gg/rivet?tab=readme-ov-file#diagram">https://github.com/rivet-gg/rivet?tab=readme-ov-file#diagram</a><p>[2] <a href="https://github.com/rivet-gg/rivet/blob/a3db31f3b5c351061d665003a6a8dfbf3372690b/packages/services/ds/src/workflows/server/pegboard/mod.rs#L49">https://github.com/rivet-gg/rivet/blob/a3db31f3b5c351061d665...</a><p>[3] <a href="https://www.youtube.com/watch?v=9g84y_60VGM" rel="nofollow">https://www.youtube.com/watch?v=9g84y_60VGM</a><p>[4] <a href="https://apple.github.io/foundationdb/flow.html" rel="nofollow">https://apple.github.io/foundationdb/flow.html</a><p>[5] <a href="https://jsr.io/@rivet-gg/actor/doc" rel="nofollow">https://jsr.io/@rivet-gg/actor/doc</a><p>[6] <a href="https://rivet.gg/docs">https://rivet.gg/docs</a><p>[7] <a href="https://rivet.gg/docs/internals/design-decisions">https://rivet.gg/docs/internals/design-decisions</a>
Show HN: Rivet Actors – Durable Objects build with Rust, FoundationDB, Isolates
Hello! We posted a Show HN for Rivet last year for our container orchestration project (<a href="https://news.ycombinator.com/item?id=37188659">https://news.ycombinator.com/item?id=37188659</a>). In that time, a lot has changed that I think HN will find interesting.<p>Rivet is open-source actor infrastructure similar to Cloudflare's Durable Objects. Rivet itself already serves millions of MAU in production using our current container runtime – primarily for multiplayer games – and Rivet Actors are a new extension to support actor-like workloads. Rivet Actor's core primitives are RPC, state, and events.<p>Actors are powered by Rust, V8 isolates (supports Deno), and FoundationDB. An architecture diagram is available here for [1]. If you're not familiar with FoundationDB, you're overdue to watch Dave Rosenthal's talk [3]. (I firmly believe it's by far the best permissively licensed database; if only it had a well maintained SQL layer.)<p>Here's where Rivet's architecture gets fun – we don't rely on a traditional orchestrator like Kubernetes or Nomad for our runtime. Instead, our orchestrator is powered by an in-house actor-like workflow engine – similar to how FoundationDB is powered by their own actor library (Flow [4]) internally. It lets us reliably & efficiently build complex logic – like our orchestrator – that would normally be incredibly difficult to build correctly. For example, here's the logic that powers Rivet Actors themselves with complex mechanisms like retry upgrades, retry backoffs, and draining [2].<p>One of the reasons we built Rivet Actors is because we tried to replace most of our Redis-based realtime infrastructure with Durable Objects. The architecture allowed us to build realtime features much faster & efficiently, but the platform & APIs were needlessly rigid and difficult to use. Our goal is to build an actor-like platform that includes the bells and whistles required for developers to benefit from the actor model without the learning curve of tools like Erlang/OTP, Akka, or Orleans.<p>Rivet Actors provides a few key benefits in flexibility over Durable Objects:<p>- Open-source (Apache 2.0) – built to be self-hosted and deployed on-prem<p>- Provides observability out of the box, no Logpush required<p>- Rivet Actors support the Deno runtime, so NPM & JSR just works<p>- @rivet-gg/actor [5] framework provides RPC, state, and events out of the box for faster bootstrapping; you can modify and deploy it yourself<p>- Supports both V8 isolates & Docker-compatible containers so you can run any software you'd like, like Godot/Unity servers or video transcoding<p>- Also supports TCP & UDP (we run games!)<p>- Provides vanilla HTTP API for easy use with existing apps<p>- Full control over regions<p>There's plenty more that I don't have space to talk about. Give our docs a read if you'd like to learn more [6] or read about internal design decisions [7]. I'll be in the comments answering questions!<p>Cheers,
Nathan<p>[1] <a href="https://github.com/rivet-gg/rivet?tab=readme-ov-file#diagram">https://github.com/rivet-gg/rivet?tab=readme-ov-file#diagram</a><p>[2] <a href="https://github.com/rivet-gg/rivet/blob/a3db31f3b5c351061d665003a6a8dfbf3372690b/packages/services/ds/src/workflows/server/pegboard/mod.rs#L49">https://github.com/rivet-gg/rivet/blob/a3db31f3b5c351061d665...</a><p>[3] <a href="https://www.youtube.com/watch?v=9g84y_60VGM" rel="nofollow">https://www.youtube.com/watch?v=9g84y_60VGM</a><p>[4] <a href="https://apple.github.io/foundationdb/flow.html" rel="nofollow">https://apple.github.io/foundationdb/flow.html</a><p>[5] <a href="https://jsr.io/@rivet-gg/actor/doc" rel="nofollow">https://jsr.io/@rivet-gg/actor/doc</a><p>[6] <a href="https://rivet.gg/docs">https://rivet.gg/docs</a><p>[7] <a href="https://rivet.gg/docs/internals/design-decisions">https://rivet.gg/docs/internals/design-decisions</a>
Show HN: Rivet Actors – Durable Objects build with Rust, FoundationDB, Isolates
Hello! We posted a Show HN for Rivet last year for our container orchestration project (<a href="https://news.ycombinator.com/item?id=37188659">https://news.ycombinator.com/item?id=37188659</a>). In that time, a lot has changed that I think HN will find interesting.<p>Rivet is open-source actor infrastructure similar to Cloudflare's Durable Objects. Rivet itself already serves millions of MAU in production using our current container runtime – primarily for multiplayer games – and Rivet Actors are a new extension to support actor-like workloads. Rivet Actor's core primitives are RPC, state, and events.<p>Actors are powered by Rust, V8 isolates (supports Deno), and FoundationDB. An architecture diagram is available here for [1]. If you're not familiar with FoundationDB, you're overdue to watch Dave Rosenthal's talk [3]. (I firmly believe it's by far the best permissively licensed database; if only it had a well maintained SQL layer.)<p>Here's where Rivet's architecture gets fun – we don't rely on a traditional orchestrator like Kubernetes or Nomad for our runtime. Instead, our orchestrator is powered by an in-house actor-like workflow engine – similar to how FoundationDB is powered by their own actor library (Flow [4]) internally. It lets us reliably & efficiently build complex logic – like our orchestrator – that would normally be incredibly difficult to build correctly. For example, here's the logic that powers Rivet Actors themselves with complex mechanisms like retry upgrades, retry backoffs, and draining [2].<p>One of the reasons we built Rivet Actors is because we tried to replace most of our Redis-based realtime infrastructure with Durable Objects. The architecture allowed us to build realtime features much faster & efficiently, but the platform & APIs were needlessly rigid and difficult to use. Our goal is to build an actor-like platform that includes the bells and whistles required for developers to benefit from the actor model without the learning curve of tools like Erlang/OTP, Akka, or Orleans.<p>Rivet Actors provides a few key benefits in flexibility over Durable Objects:<p>- Open-source (Apache 2.0) – built to be self-hosted and deployed on-prem<p>- Provides observability out of the box, no Logpush required<p>- Rivet Actors support the Deno runtime, so NPM & JSR just works<p>- @rivet-gg/actor [5] framework provides RPC, state, and events out of the box for faster bootstrapping; you can modify and deploy it yourself<p>- Supports both V8 isolates & Docker-compatible containers so you can run any software you'd like, like Godot/Unity servers or video transcoding<p>- Also supports TCP & UDP (we run games!)<p>- Provides vanilla HTTP API for easy use with existing apps<p>- Full control over regions<p>There's plenty more that I don't have space to talk about. Give our docs a read if you'd like to learn more [6] or read about internal design decisions [7]. I'll be in the comments answering questions!<p>Cheers,
Nathan<p>[1] <a href="https://github.com/rivet-gg/rivet?tab=readme-ov-file#diagram">https://github.com/rivet-gg/rivet?tab=readme-ov-file#diagram</a><p>[2] <a href="https://github.com/rivet-gg/rivet/blob/a3db31f3b5c351061d665003a6a8dfbf3372690b/packages/services/ds/src/workflows/server/pegboard/mod.rs#L49">https://github.com/rivet-gg/rivet/blob/a3db31f3b5c351061d665...</a><p>[3] <a href="https://www.youtube.com/watch?v=9g84y_60VGM" rel="nofollow">https://www.youtube.com/watch?v=9g84y_60VGM</a><p>[4] <a href="https://apple.github.io/foundationdb/flow.html" rel="nofollow">https://apple.github.io/foundationdb/flow.html</a><p>[5] <a href="https://jsr.io/@rivet-gg/actor/doc" rel="nofollow">https://jsr.io/@rivet-gg/actor/doc</a><p>[6] <a href="https://rivet.gg/docs">https://rivet.gg/docs</a><p>[7] <a href="https://rivet.gg/docs/internals/design-decisions">https://rivet.gg/docs/internals/design-decisions</a>
Show HN: Demo of my web game about social persuasion
I just released a free demo (no login!) for "Talk to Me Human", a game about social persuasion. You speak out loud to play a variety of conversational challenges, and the NPCs talk back.<p>I hope you enjoy, and would love to get your feedback!
Show HN: Demo of my web game about social persuasion
I just released a free demo (no login!) for "Talk to Me Human", a game about social persuasion. You speak out loud to play a variety of conversational challenges, and the NPCs talk back.<p>I hope you enjoy, and would love to get your feedback!
Show HN: Demo of my web game about social persuasion
I just released a free demo (no login!) for "Talk to Me Human", a game about social persuasion. You speak out loud to play a variety of conversational challenges, and the NPCs talk back.<p>I hope you enjoy, and would love to get your feedback!
Show HN: Eonfall – A new third-person co-op action game built for the web
Hi all, I'm excited to share Eonfall with Hacker News Community!<p>It's been 2-years in the making built by a 2 man team. Eonfall, is a new third-person co-op action game with rogue-lite elements built exclusively for the web! We've finally reached a release candidate state and set our official public release date for Jan 15th! The game's current version 5.0.0-beta is live and available to test play today!<p>Unity game engine was used to develop the game along with other services to handle the backend, and Nuxt 3 + Nuxt UI to handle the front-end.<p>We welcome any and all questions, feedback & suggestions!<p>Thanks all, Jon
Show HN: Eonfall – A new third-person co-op action game built for the web
Hi all, I'm excited to share Eonfall with Hacker News Community!<p>It's been 2-years in the making built by a 2 man team. Eonfall, is a new third-person co-op action game with rogue-lite elements built exclusively for the web! We've finally reached a release candidate state and set our official public release date for Jan 15th! The game's current version 5.0.0-beta is live and available to test play today!<p>Unity game engine was used to develop the game along with other services to handle the backend, and Nuxt 3 + Nuxt UI to handle the front-end.<p>We welcome any and all questions, feedback & suggestions!<p>Thanks all, Jon
Show HN: Eonfall – A new third-person co-op action game built for the web
Hi all, I'm excited to share Eonfall with Hacker News Community!<p>It's been 2-years in the making built by a 2 man team. Eonfall, is a new third-person co-op action game with rogue-lite elements built exclusively for the web! We've finally reached a release candidate state and set our official public release date for Jan 15th! The game's current version 5.0.0-beta is live and available to test play today!<p>Unity game engine was used to develop the game along with other services to handle the backend, and Nuxt 3 + Nuxt UI to handle the front-end.<p>We welcome any and all questions, feedback & suggestions!<p>Thanks all, Jon