The best Hacker News stories from Show from the past day

from

All Show

from the past*

day week month

with these search terms:

Create follow Go back

Latest posts:

Show HN: Scream to Unlock – Blocks social media until you scream “I'm a loser”

Hi all,<p>I kept wasting time on social media, even though I’d promised myself I’d stay focused. Regular site blockers didn’t help.<p>I needed something that felt annoying enough to break the habit. That’s how the idea came up: make the blocker ask me to say something embarrassing out loud before it lets me back in. If I actually have to yell “I’m a loser” into my mic. Even better - the louder I screamed, the more time I’d get.<p>So I put together Scream to Unlock. It’s silly, but so far it’s done its job. My social feeds stay locked unless I really want them.<p>Extension link - <a href="https://chromewebstore.google.com/detail/scream-to-unlock-yell-to/pmmikajpbkehhpomkmelipgiafampkah?authuser=0&hl=en" rel="nofollow">https://chromewebstore.google.com/detail/scream-to-unlock-ye...</a><p>Its open source and transparent - <a href="https://github.com/Pankajtanwarbanna/scream-to-unlock">https://github.com/Pankajtanwarbanna/scream-to-unlock</a>. No data collection or tracking, Audio processing happens locally in your browser. No recordings saved or transmitted.

Show HN: Scream to Unlock – Blocks social media until you scream “I'm a loser”

Hi all,<p>I kept wasting time on social media, even though I’d promised myself I’d stay focused. Regular site blockers didn’t help.<p>I needed something that felt annoying enough to break the habit. That’s how the idea came up: make the blocker ask me to say something embarrassing out loud before it lets me back in. If I actually have to yell “I’m a loser” into my mic. Even better - the louder I screamed, the more time I’d get.<p>So I put together Scream to Unlock. It’s silly, but so far it’s done its job. My social feeds stay locked unless I really want them.<p>Extension link - <a href="https://chromewebstore.google.com/detail/scream-to-unlock-yell-to/pmmikajpbkehhpomkmelipgiafampkah?authuser=0&hl=en" rel="nofollow">https://chromewebstore.google.com/detail/scream-to-unlock-ye...</a><p>Its open source and transparent - <a href="https://github.com/Pankajtanwarbanna/scream-to-unlock">https://github.com/Pankajtanwarbanna/scream-to-unlock</a>. No data collection or tracking, Audio processing happens locally in your browser. No recordings saved or transmitted.

Show HN: I built an under-the-door fan duct to lower bedroom CO2

Hi HN,<p>This is my attempt to fix groggy mornings by lowering my bedroom CO2 from 1700 ppm to ~900 ppm.<p>I designed a simple, 3D-printed fan duct that directs air under the door to improve air circulation.<p>A note on the design process: I used CadQuery, a Python library for creating parametric 3D models. I didn't know tools like this existed and highly recommend it if you can program; it turned out to be more convenient than manually iterating on prototypes in a GUI.<p>The project is open source and the post explains the full build. Happy to answer any questions.

Show HN: I built an under-the-door fan duct to lower bedroom CO2

Hi HN,<p>This is my attempt to fix groggy mornings by lowering my bedroom CO2 from 1700 ppm to ~900 ppm.<p>I designed a simple, 3D-printed fan duct that directs air under the door to improve air circulation.<p>A note on the design process: I used CadQuery, a Python library for creating parametric 3D models. I didn't know tools like this existed and highly recommend it if you can program; it turned out to be more convenient than manually iterating on prototypes in a GUI.<p>The project is open source and the post explains the full build. Happy to answer any questions.

Show HN: Weather Watching

I was walking around New York last month during some light rain and noticed about half the people had umbrellas open. When the rain picked up a few minutes later, that number jumped closer to 80%.<p>It got me thinking it'd be cool to track this somehow, so I built a website! I am taking a sidewalk livestream, feeding it into a YOLO model for people tracking, then sending a frame of each detected person to Gemini 2.0 Flash, which returns structured JSON about each person's clothing and if they're holding an umbrella. I also had fun making the site look like a TV weather channel.<p>I showed some friends this project and someone mentioned how the legendary Tasks xkcd comic (<a href="https://xkcd.com/1425" rel="nofollow">https://xkcd.com/1425</a>) is out of date now. If you want to check whether a photo has birds in it (or if someone is holding an umbrella), you can just ask an inexpensive vision model for JSON.

Show HN: Weather Watching

I was walking around New York last month during some light rain and noticed about half the people had umbrellas open. When the rain picked up a few minutes later, that number jumped closer to 80%.<p>It got me thinking it'd be cool to track this somehow, so I built a website! I am taking a sidewalk livestream, feeding it into a YOLO model for people tracking, then sending a frame of each detected person to Gemini 2.0 Flash, which returns structured JSON about each person's clothing and if they're holding an umbrella. I also had fun making the site look like a TV weather channel.<p>I showed some friends this project and someone mentioned how the legendary Tasks xkcd comic (<a href="https://xkcd.com/1425" rel="nofollow">https://xkcd.com/1425</a>) is out of date now. If you want to check whether a photo has birds in it (or if someone is holding an umbrella), you can just ask an inexpensive vision model for JSON.

Show HN: Comparator - I built a free, open-source app to compare job offers

Show HN: Comparator - I built a free, open-source app to compare job offers

Show HN: Oasis – An open-source, 3D-printed smart terrarium

See the website for a demo video: <a href="https://oasis-terrarium.com" rel="nofollow">https://oasis-terrarium.com</a><p>This project is an enclosure for growing plants. Features include:<p><pre><code> - high-power LED lighting - a built-in water tank and mister - fans for airflow - temperature and humidity sensing - wi-fi connectivity and a web-based interface for control and monitoring (see https://oasis-terrarium.com/docs/usage_guide/#web-interface) </code></pre> The entire project is open-source:<p><pre><code> - electronics: designed in KiCad - 3D models: designed in CadQuery - software: written in Rust </code></pre> I initially started this project during COVID and built a working prototype using a Raspberry Pi and off-the-shelf parts. The first prototype worked, but was pretty rough. Several months ago, I picked up the project again and began a complete re-design. After two rounds of circuit board design and countless iterations of the 3D-printed parts, I'm finally happy with the results. Along the way I learned a lot about electronics design and fabrication, 3D modeling, and Rust.<p>Happy to answer any questions - thanks for checking it out!<p>Here are some direct links to parts of the project you may find interesting:<p><pre><code> - demo video: https://oasis-terrarium.com - detailed build guide with pictures: https://oasis-terrarium.com/docs/build_guide/ - interactive 3D model: https://oasis-terrarium.com/docs/3dmodel/ - detailed info on electronics design: https://oasis-terrarium.com/docs/electronics/ - 3D-printable models: https://www.printables.com/model/1315117-oasis-smart-terrarium</code></pre>

Show HN: Oasis – An open-source, 3D-printed smart terrarium

See the website for a demo video: <a href="https://oasis-terrarium.com" rel="nofollow">https://oasis-terrarium.com</a><p>This project is an enclosure for growing plants. Features include:<p><pre><code> - high-power LED lighting - a built-in water tank and mister - fans for airflow - temperature and humidity sensing - wi-fi connectivity and a web-based interface for control and monitoring (see https://oasis-terrarium.com/docs/usage_guide/#web-interface) </code></pre> The entire project is open-source:<p><pre><code> - electronics: designed in KiCad - 3D models: designed in CadQuery - software: written in Rust </code></pre> I initially started this project during COVID and built a working prototype using a Raspberry Pi and off-the-shelf parts. The first prototype worked, but was pretty rough. Several months ago, I picked up the project again and began a complete re-design. After two rounds of circuit board design and countless iterations of the 3D-printed parts, I'm finally happy with the results. Along the way I learned a lot about electronics design and fabrication, 3D modeling, and Rust.<p>Happy to answer any questions - thanks for checking it out!<p>Here are some direct links to parts of the project you may find interesting:<p><pre><code> - demo video: https://oasis-terrarium.com - detailed build guide with pictures: https://oasis-terrarium.com/docs/build_guide/ - interactive 3D model: https://oasis-terrarium.com/docs/3dmodel/ - detailed info on electronics design: https://oasis-terrarium.com/docs/electronics/ - 3D-printable models: https://www.printables.com/model/1315117-oasis-smart-terrarium</code></pre>

Show HN: Oasis – An open-source, 3D-printed smart terrarium

See the website for a demo video: <a href="https://oasis-terrarium.com" rel="nofollow">https://oasis-terrarium.com</a><p>This project is an enclosure for growing plants. Features include:<p><pre><code> - high-power LED lighting - a built-in water tank and mister - fans for airflow - temperature and humidity sensing - wi-fi connectivity and a web-based interface for control and monitoring (see https://oasis-terrarium.com/docs/usage_guide/#web-interface) </code></pre> The entire project is open-source:<p><pre><code> - electronics: designed in KiCad - 3D models: designed in CadQuery - software: written in Rust </code></pre> I initially started this project during COVID and built a working prototype using a Raspberry Pi and off-the-shelf parts. The first prototype worked, but was pretty rough. Several months ago, I picked up the project again and began a complete re-design. After two rounds of circuit board design and countless iterations of the 3D-printed parts, I'm finally happy with the results. Along the way I learned a lot about electronics design and fabrication, 3D modeling, and Rust.<p>Happy to answer any questions - thanks for checking it out!<p>Here are some direct links to parts of the project you may find interesting:<p><pre><code> - demo video: https://oasis-terrarium.com - detailed build guide with pictures: https://oasis-terrarium.com/docs/build_guide/ - interactive 3D model: https://oasis-terrarium.com/docs/3dmodel/ - detailed info on electronics design: https://oasis-terrarium.com/docs/electronics/ - 3D-printable models: https://www.printables.com/model/1315117-oasis-smart-terrarium</code></pre>

Show HN: Autumn – Open-source infra over Stripe

Hey HN, I’m Ayush from Autumn (<a href="https://useautumn.com/">https://useautumn.com/</a>). Autumn is an open source layer over Stripe that decouples pricing and billing logic from your application. We let you efficiently manage pricing plans, feature permissions, and payments, regardless of the pricing model being used. It’s a bit like if Supabase and Stripe had a baby.<p>Typically, you have to write code to handle checkouts, upgrades/downgrades, failed payments, then receive webhooks to provision features, reset usage limits etc. We abstract this into one function call for all payments flows (checkouts, upgrades, downgrades etc), one function to record usage (so we can track usage limits), and a customer state React hook you can access from your frontend (to handle paywalls, display usage data etc).<p>Here’s a demo: <a href="https://www.youtube.com/watch?v=SFARthC7JXc" rel="nofollow">https://www.youtube.com/watch?v=SFARthC7JXc</a><p>Stripe’s great! But there are 2 main reasons people use Autumn over a direct Stripe setup:<p>(1) Billing infra can get complex. After payments, there’s still handling webhooks, permission management, metering, usage resets, and connecting them all to upgrade, downgrade, cancellation and failed payments states.<p>(2) Growing companies iterate on pricing often: raising prices, experimenting with credits or charging for new features, etc. We save you from having to handle usage-based limits (super common in pricing today), rebuilding in-app flows, DB migrations, internal dashboards for custom pricing, and grandfathering users on different pricing.<p>Ripping out billing flows etc, really sucks. With Autumn, you just make pricing changes in our UI and it all auto-updates. We have a shadcn/ui component library that helps with this.<p>Because we support a lot of different pricing models (subscriptions, usage, credits, seat based etc), we have to handle a lot of different scenarios and cases under the hood. We try to keep setup simple while maintaining flexibility of a native integration. Here’s a little snippet of the architecture of our main endpoint: <a href="https://useautumn.com/blog/attach">https://useautumn.com/blog/attach</a><p>Currently, the users who get the most value out of us are founders that need to move fast and keep things flexible, but also new/non-technical devs that are more AI native.<p>You can clone the project and explore the repo, or try it out at <a href="https://useautumn.com/">https://useautumn.com/</a>, where it’s free for builders. Our repo is <a href="https://github.com/useautumn/autumn">https://github.com/useautumn/autumn</a>, docs are at <a href="https://docs.useautumn.com/">https://docs.useautumn.com/</a> and demo at <a href="https://www.youtube.com/watch?v=SFARthC7JXc" rel="nofollow">https://www.youtube.com/watch?v=SFARthC7JXc</a><p>We’d love to hear your feedback and how we could make it better!

Show HN: Autumn – Open-source infra over Stripe

Hey HN, I’m Ayush from Autumn (<a href="https://useautumn.com/">https://useautumn.com/</a>). Autumn is an open source layer over Stripe that decouples pricing and billing logic from your application. We let you efficiently manage pricing plans, feature permissions, and payments, regardless of the pricing model being used. It’s a bit like if Supabase and Stripe had a baby.<p>Typically, you have to write code to handle checkouts, upgrades/downgrades, failed payments, then receive webhooks to provision features, reset usage limits etc. We abstract this into one function call for all payments flows (checkouts, upgrades, downgrades etc), one function to record usage (so we can track usage limits), and a customer state React hook you can access from your frontend (to handle paywalls, display usage data etc).<p>Here’s a demo: <a href="https://www.youtube.com/watch?v=SFARthC7JXc" rel="nofollow">https://www.youtube.com/watch?v=SFARthC7JXc</a><p>Stripe’s great! But there are 2 main reasons people use Autumn over a direct Stripe setup:<p>(1) Billing infra can get complex. After payments, there’s still handling webhooks, permission management, metering, usage resets, and connecting them all to upgrade, downgrade, cancellation and failed payments states.<p>(2) Growing companies iterate on pricing often: raising prices, experimenting with credits or charging for new features, etc. We save you from having to handle usage-based limits (super common in pricing today), rebuilding in-app flows, DB migrations, internal dashboards for custom pricing, and grandfathering users on different pricing.<p>Ripping out billing flows etc, really sucks. With Autumn, you just make pricing changes in our UI and it all auto-updates. We have a shadcn/ui component library that helps with this.<p>Because we support a lot of different pricing models (subscriptions, usage, credits, seat based etc), we have to handle a lot of different scenarios and cases under the hood. We try to keep setup simple while maintaining flexibility of a native integration. Here’s a little snippet of the architecture of our main endpoint: <a href="https://useautumn.com/blog/attach">https://useautumn.com/blog/attach</a><p>Currently, the users who get the most value out of us are founders that need to move fast and keep things flexible, but also new/non-technical devs that are more AI native.<p>You can clone the project and explore the repo, or try it out at <a href="https://useautumn.com/">https://useautumn.com/</a>, where it’s free for builders. Our repo is <a href="https://github.com/useautumn/autumn">https://github.com/useautumn/autumn</a>, docs are at <a href="https://docs.useautumn.com/">https://docs.useautumn.com/</a> and demo at <a href="https://www.youtube.com/watch?v=SFARthC7JXc" rel="nofollow">https://www.youtube.com/watch?v=SFARthC7JXc</a><p>We’d love to hear your feedback and how we could make it better!

Show HN: Turn a paper's DOI into its full reference list (BibTeX/RIS, etc.)

Show HN: Ariadne – A Rust implementation of aperiodic cryptography

Hello HN, we're CipherNomad, the research initiative behind this project.<p>The Ariadne Protocol is our exploration of a different cryptographic model. The work began with an observation of primitives like the Lion transform, which use a static, hardcoded sequence of operations. This led us to ask: What if the cryptographic "program" wasn't a constant, but a dynamic, history-dependent variable?<p>Our first step was a "Cryptographic Virtual Machine" that took an explicit list of operations (a "Path"). This worked, but required sharing the Path object—an explicit dependency that needed to be managed.<p>The Ariadne Protocol is the maturation of that idea. It eliminates the explicit Path by making it implicit and emergent.<p>The core design is:<p>The Labyrinth: A large, deterministically-generated binary tree of cryptographic rounds.<p>The Thread: The secret path taken through the Labyrinth. This path is not stored or transmitted. It's rediscovered for each block of data by computing a keyed hash of the CVM's secret state and the public ciphertext chunk: hash(key, state, chunk).<p>This makes the cipher aperiodic: because the state ratchets forward after every block, the sequence of operations is guaranteed to never repeat. It also creates inherent tamper evidence—any modification to the ciphertext "snaps the thread" and turns subsequent output into noise.<p>This is experimental, unaudited alpha software. We are publishing it under CC0 because we believe foundational work like this should be an unrestricted public good.

Show HN: I made a screenshot beautifier

I’ve always seen talented designers and developers post their work, only for it to get lost in the noise. I realized a major reason is that they often just post a simple, unstyled screenshot. As a result, nobody pays attention.<p>My solution is a tool where you can drop in a screenshot, pick from a collection of hand-picked gradients, style it, and export it—all in a few seconds. I’ve carefully designed every element of the app to be efficient, simple, and intuitive.<p>On making it "Free, Forever": I don't plan on ever charging a subscription for Moocup. I dislike the subscription model as much as you do. Instead, my plan is to include a donation option for those who wish to support the project. This allows me to keep my promise of making the app free and useful for everyone, without being burdened by hosting and maintenance costs.<p>My goal is simple: to provide a high-quality tool that is genuinely useful and doesn't waste your time. If you find it helpful, the best thing you can do is share it with others. I've included all my contact links for feedback and suggestions.<p>Happy designing :)

Show HN: Pickaxe – A TypeScript library for building AI agents

Hey HN, Gabe and Alexander here from Hatchet. Today we're releasing Pickaxe, a Typescript library to build AI agents which are scalable and fault-tolerant.<p>Here's a demo: <a href="https://github.com/user-attachments/assets/b28fc406-f501-4427-9574-e4c756b29dd4">https://github.com/user-attachments/assets/b28fc406-f501-442...</a><p>Pickaxe provides a simple set of primitives for building agents which can automatically checkpoint their state and suspend or resume processing (also known as durable execution) while waiting for external events (like a human in the loop). The library is based on common patterns we've seen when helping Hatchet users run millions of agent executions per day.<p>Unlike other tools, Pickaxe is not a framework. It does not have any opinions or abstractions for implementing agent memory, prompting, context, or calling LLMs directly. Its only focus is making AI agents more observable and reliable.<p>As agents start to scale, there are generally three big problems that emerge: 1. Agents are long-running compared to other parts of your application. Extremely long-running processes are tricky because deploying new infra or hitting request timeouts on serverless runtimes will interrupt their execution. 2. They are stateful: they generally store internal state which governs the next step in the execution path 3. They require access to lots of fresh data, which can either be queried during agent execution or needs to be continuously refreshed from a data source.<p>(These problems are more specific to agents which execute remotely -- locally running agents generally don't have these problems)<p>Pickaxe is designed to solve these issues by providing a simple API which wraps durable execution infrastructure for agents. Durable execution is a way of automatically checkpointing the state of a process, so that if the process fails, it can automatically be replayed from the checkpoint, rather than starting over from the beginning. This model is also particularly useful when your agent needs to wait for an external event or human review in order to continue execution. To support this pattern, Pickaxe uses a Hatchet feature called `waitFor` which durably registers a listener for an event, which means that even if the agent isn't actively listening for the event, it is guaranteed to be processed by Hatchet and stored in the execution history and resume processing. This infrastructure is powered by what is essentially a linear event log, which stores the entire execution history of an agent in a Postgres database managed by Hatchet.<p>Full docs are here: <a href="https://pickaxe.hatchet.run/">https://pickaxe.hatchet.run/</a><p>We'd greatly appreciate any feedback you have and hope you get the chance to try out Pickaxe.

Show HN: Pickaxe – A TypeScript library for building AI agents

Hey HN, Gabe and Alexander here from Hatchet. Today we're releasing Pickaxe, a Typescript library to build AI agents which are scalable and fault-tolerant.<p>Here's a demo: <a href="https://github.com/user-attachments/assets/b28fc406-f501-4427-9574-e4c756b29dd4">https://github.com/user-attachments/assets/b28fc406-f501-442...</a><p>Pickaxe provides a simple set of primitives for building agents which can automatically checkpoint their state and suspend or resume processing (also known as durable execution) while waiting for external events (like a human in the loop). The library is based on common patterns we've seen when helping Hatchet users run millions of agent executions per day.<p>Unlike other tools, Pickaxe is not a framework. It does not have any opinions or abstractions for implementing agent memory, prompting, context, or calling LLMs directly. Its only focus is making AI agents more observable and reliable.<p>As agents start to scale, there are generally three big problems that emerge: 1. Agents are long-running compared to other parts of your application. Extremely long-running processes are tricky because deploying new infra or hitting request timeouts on serverless runtimes will interrupt their execution. 2. They are stateful: they generally store internal state which governs the next step in the execution path 3. They require access to lots of fresh data, which can either be queried during agent execution or needs to be continuously refreshed from a data source.<p>(These problems are more specific to agents which execute remotely -- locally running agents generally don't have these problems)<p>Pickaxe is designed to solve these issues by providing a simple API which wraps durable execution infrastructure for agents. Durable execution is a way of automatically checkpointing the state of a process, so that if the process fails, it can automatically be replayed from the checkpoint, rather than starting over from the beginning. This model is also particularly useful when your agent needs to wait for an external event or human review in order to continue execution. To support this pattern, Pickaxe uses a Hatchet feature called `waitFor` which durably registers a listener for an event, which means that even if the agent isn't actively listening for the event, it is guaranteed to be processed by Hatchet and stored in the execution history and resume processing. This infrastructure is powered by what is essentially a linear event log, which stores the entire execution history of an agent in a Postgres database managed by Hatchet.<p>Full docs are here: <a href="https://pickaxe.hatchet.run/">https://pickaxe.hatchet.run/</a><p>We'd greatly appreciate any feedback you have and hope you get the chance to try out Pickaxe.

Show HN: Pickaxe – A TypeScript library for building AI agents

Hey HN, Gabe and Alexander here from Hatchet. Today we're releasing Pickaxe, a Typescript library to build AI agents which are scalable and fault-tolerant.<p>Here's a demo: <a href="https://github.com/user-attachments/assets/b28fc406-f501-4427-9574-e4c756b29dd4">https://github.com/user-attachments/assets/b28fc406-f501-442...</a><p>Pickaxe provides a simple set of primitives for building agents which can automatically checkpoint their state and suspend or resume processing (also known as durable execution) while waiting for external events (like a human in the loop). The library is based on common patterns we've seen when helping Hatchet users run millions of agent executions per day.<p>Unlike other tools, Pickaxe is not a framework. It does not have any opinions or abstractions for implementing agent memory, prompting, context, or calling LLMs directly. Its only focus is making AI agents more observable and reliable.<p>As agents start to scale, there are generally three big problems that emerge: 1. Agents are long-running compared to other parts of your application. Extremely long-running processes are tricky because deploying new infra or hitting request timeouts on serverless runtimes will interrupt their execution. 2. They are stateful: they generally store internal state which governs the next step in the execution path 3. They require access to lots of fresh data, which can either be queried during agent execution or needs to be continuously refreshed from a data source.<p>(These problems are more specific to agents which execute remotely -- locally running agents generally don't have these problems)<p>Pickaxe is designed to solve these issues by providing a simple API which wraps durable execution infrastructure for agents. Durable execution is a way of automatically checkpointing the state of a process, so that if the process fails, it can automatically be replayed from the checkpoint, rather than starting over from the beginning. This model is also particularly useful when your agent needs to wait for an external event or human review in order to continue execution. To support this pattern, Pickaxe uses a Hatchet feature called `waitFor` which durably registers a listener for an event, which means that even if the agent isn't actively listening for the event, it is guaranteed to be processed by Hatchet and stored in the execution history and resume processing. This infrastructure is powered by what is essentially a linear event log, which stores the entire execution history of an agent in a Postgres database managed by Hatchet.<p>Full docs are here: <a href="https://pickaxe.hatchet.run/">https://pickaxe.hatchet.run/</a><p>We'd greatly appreciate any feedback you have and hope you get the chance to try out Pickaxe.

Show HN: Lego Island Playable in the Browser