The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Mapping the Unix Magic Poster – An Interactive Annotation Project
Hi HN,<p>We've discussed the Unix Magic poster before (<a href="https://news.ycombinator.com/item?id=27029196">https://news.ycombinator.com/item?id=27029196</a>). Like many of you, I love this poster and all the Unix references hidden in it.<p>I built this as a static site that lets us annotate the Unix Magic poster by placing markers on references and adding descriptions to explain them. I've added a few so far, but there's much more to document.<p>What I love about this approach is that contributions happen not just on the site itself but also through PRs, where we can discuss and refine the details of each reference. Feel free to send a PR!<p>Code: <a href="https://github.com/drio/unixmagic">https://github.com/drio/unixmagic</a>
Live site: <a href="https://drio.github.io/unixmagic" rel="nofollow">https://drio.github.io/unixmagic</a><p>Would love feedback, suggestions, and PRs from the community!<p>Thanks!<p>—drd
Show HN: Mapping the Unix Magic Poster – An Interactive Annotation Project
Hi HN,<p>We've discussed the Unix Magic poster before (<a href="https://news.ycombinator.com/item?id=27029196">https://news.ycombinator.com/item?id=27029196</a>). Like many of you, I love this poster and all the Unix references hidden in it.<p>I built this as a static site that lets us annotate the Unix Magic poster by placing markers on references and adding descriptions to explain them. I've added a few so far, but there's much more to document.<p>What I love about this approach is that contributions happen not just on the site itself but also through PRs, where we can discuss and refine the details of each reference. Feel free to send a PR!<p>Code: <a href="https://github.com/drio/unixmagic">https://github.com/drio/unixmagic</a>
Live site: <a href="https://drio.github.io/unixmagic" rel="nofollow">https://drio.github.io/unixmagic</a><p>Would love feedback, suggestions, and PRs from the community!<p>Thanks!<p>—drd
Show HN: Mikey – No bot meeting notetaker for Windows
Show HN: Mikey – No bot meeting notetaker for Windows
Show HN: Mikey – No bot meeting notetaker for Windows
Show HN: A no-build fullstack SSR TypeScript web framework
Hi HN!<p>I'd love to seek your insights on a fullstack web framework that employs a different approach: no build.<p>It's not a new concept. The folks as Preact mentioned it: <a href="https://preactjs.com/guide/v10/no-build-workflows/" rel="nofollow">https://preactjs.com/guide/v10/no-build-workflows/</a><p>However, in the Web Framework market, I've yet to find many that support both "no build" and "SSR". There's always some sorts of "client mount" and "server mount" and either has (or both have) to go through a build (bundling) process.<p>With the build process, there comes additional maintenance efforts and cognitive load. I've enjoyed wrestling with tsconfig, webpack config, all sorts of presets and plugins countless times... When things work, they just work, but when we need sth a bit custom or unconventional, then we're almost always in for a tough ride. (or it's just me )<p>Not to say I'm against any existing build workflow. In fact I benefited a lot in the past from webpack, and i'm very positive about modern bundlers like Parcel 2, Turbopack, rspack, etc.<p>I just feel it'd be fair to save some slots for the "no build" route :)<p>To this end, I spent the last month working on a prototype of a TypeScript fullstack SSR web framework. It's compatible with Deno and Bun runtimes. I'd love to make it compatible with Node.js as well (at some point).<p>The framework registry page (<a href="https://jsr.io/@fullsoak/fullsoak" rel="nofollow">https://jsr.io/@fullsoak/fullsoak</a>) summarizes the motives expressed so far.<p>An example deployment is available at: <a href="https://fullsoak.onrender.com/app" rel="nofollow">https://fullsoak.onrender.com/app</a><p>The code behind the deployment above: <a href="https://github.com/fullsoak/bun-examples">https://github.com/fullsoak/bun-examples</a><p>PS: you may see Preact being used & mentioned everywhere but I'm positive that React is 100% supported as well (just drop-in & use). I just happened to choose Preact to experience it more for myself.<p>I look forward to your thoughts :) and learning if this might (or might not) be a feasible idea at scale. And perhaps, which future directions you would see this (or something like it) goes. Thank you much for any insight!
Show HN: A no-build fullstack SSR TypeScript web framework
Hi HN!<p>I'd love to seek your insights on a fullstack web framework that employs a different approach: no build.<p>It's not a new concept. The folks as Preact mentioned it: <a href="https://preactjs.com/guide/v10/no-build-workflows/" rel="nofollow">https://preactjs.com/guide/v10/no-build-workflows/</a><p>However, in the Web Framework market, I've yet to find many that support both "no build" and "SSR". There's always some sorts of "client mount" and "server mount" and either has (or both have) to go through a build (bundling) process.<p>With the build process, there comes additional maintenance efforts and cognitive load. I've enjoyed wrestling with tsconfig, webpack config, all sorts of presets and plugins countless times... When things work, they just work, but when we need sth a bit custom or unconventional, then we're almost always in for a tough ride. (or it's just me )<p>Not to say I'm against any existing build workflow. In fact I benefited a lot in the past from webpack, and i'm very positive about modern bundlers like Parcel 2, Turbopack, rspack, etc.<p>I just feel it'd be fair to save some slots for the "no build" route :)<p>To this end, I spent the last month working on a prototype of a TypeScript fullstack SSR web framework. It's compatible with Deno and Bun runtimes. I'd love to make it compatible with Node.js as well (at some point).<p>The framework registry page (<a href="https://jsr.io/@fullsoak/fullsoak" rel="nofollow">https://jsr.io/@fullsoak/fullsoak</a>) summarizes the motives expressed so far.<p>An example deployment is available at: <a href="https://fullsoak.onrender.com/app" rel="nofollow">https://fullsoak.onrender.com/app</a><p>The code behind the deployment above: <a href="https://github.com/fullsoak/bun-examples">https://github.com/fullsoak/bun-examples</a><p>PS: you may see Preact being used & mentioned everywhere but I'm positive that React is 100% supported as well (just drop-in & use). I just happened to choose Preact to experience it more for myself.<p>I look forward to your thoughts :) and learning if this might (or might not) be a feasible idea at scale. And perhaps, which future directions you would see this (or something like it) goes. Thank you much for any insight!
Show HN: A no-build fullstack SSR TypeScript web framework
Hi HN!<p>I'd love to seek your insights on a fullstack web framework that employs a different approach: no build.<p>It's not a new concept. The folks as Preact mentioned it: <a href="https://preactjs.com/guide/v10/no-build-workflows/" rel="nofollow">https://preactjs.com/guide/v10/no-build-workflows/</a><p>However, in the Web Framework market, I've yet to find many that support both "no build" and "SSR". There's always some sorts of "client mount" and "server mount" and either has (or both have) to go through a build (bundling) process.<p>With the build process, there comes additional maintenance efforts and cognitive load. I've enjoyed wrestling with tsconfig, webpack config, all sorts of presets and plugins countless times... When things work, they just work, but when we need sth a bit custom or unconventional, then we're almost always in for a tough ride. (or it's just me )<p>Not to say I'm against any existing build workflow. In fact I benefited a lot in the past from webpack, and i'm very positive about modern bundlers like Parcel 2, Turbopack, rspack, etc.<p>I just feel it'd be fair to save some slots for the "no build" route :)<p>To this end, I spent the last month working on a prototype of a TypeScript fullstack SSR web framework. It's compatible with Deno and Bun runtimes. I'd love to make it compatible with Node.js as well (at some point).<p>The framework registry page (<a href="https://jsr.io/@fullsoak/fullsoak" rel="nofollow">https://jsr.io/@fullsoak/fullsoak</a>) summarizes the motives expressed so far.<p>An example deployment is available at: <a href="https://fullsoak.onrender.com/app" rel="nofollow">https://fullsoak.onrender.com/app</a><p>The code behind the deployment above: <a href="https://github.com/fullsoak/bun-examples">https://github.com/fullsoak/bun-examples</a><p>PS: you may see Preact being used & mentioned everywhere but I'm positive that React is 100% supported as well (just drop-in & use). I just happened to choose Preact to experience it more for myself.<p>I look forward to your thoughts :) and learning if this might (or might not) be a feasible idea at scale. And perhaps, which future directions you would see this (or something like it) goes. Thank you much for any insight!
Show HN: I made my own OS from scratch because I was bored
I've wanted to make my own OS since I started programming. Now, 5 years later, I did it (kind of).<p>Sure, it is really basic, has very little functionality, but I made it and I'm proud of that. Oh, and I'm just 16 btw.
Show HN: I made my own OS from scratch because I was bored
I've wanted to make my own OS since I started programming. Now, 5 years later, I did it (kind of).<p>Sure, it is really basic, has very little functionality, but I made it and I'm proud of that. Oh, and I'm just 16 btw.
Show HN: I made my own OS from scratch because I was bored
I've wanted to make my own OS since I started programming. Now, 5 years later, I did it (kind of).<p>Sure, it is really basic, has very little functionality, but I made it and I'm proud of that. Oh, and I'm just 16 btw.
Show HN: Game Bub – open-source FPGA retro emulation handheld
Hey HN,<p>Over the past ~1.5 years, I built an open-source FPGA retro emulation handheld that can play Game Boy, Game Boy Color, and Game Boy Advance cartridges. To my knowledge, there isn't an existing open-source FPGA emulator that can play physical cartridges like this.<p>One of my main goals was to do all of the pieces myself, and be able to understand every component of it, so I designed my own PCB, wrote the firmware, wrote a Game Boy and Game Boy Advance emulator for the FPGA (using the Chisel HDL), and designed a 3D-printed case.<p>I detailed the design and development process in the linked post. It's quite long, but there are a lot of pictures and videos.<p>Code and design files available on GitHub: <a href="https://github.com/elipsitz/gamebub">https://github.com/elipsitz/gamebub</a>, and an overview of the architecture: <a href="https://github.com/elipsitz/gamebub/blob/handheld/docs/architecture.md">https://github.com/elipsitz/gamebub/blob/handheld/docs/archi...</a>
Show HN: Game Bub – open-source FPGA retro emulation handheld
Hey HN,<p>Over the past ~1.5 years, I built an open-source FPGA retro emulation handheld that can play Game Boy, Game Boy Color, and Game Boy Advance cartridges. To my knowledge, there isn't an existing open-source FPGA emulator that can play physical cartridges like this.<p>One of my main goals was to do all of the pieces myself, and be able to understand every component of it, so I designed my own PCB, wrote the firmware, wrote a Game Boy and Game Boy Advance emulator for the FPGA (using the Chisel HDL), and designed a 3D-printed case.<p>I detailed the design and development process in the linked post. It's quite long, but there are a lot of pictures and videos.<p>Code and design files available on GitHub: <a href="https://github.com/elipsitz/gamebub">https://github.com/elipsitz/gamebub</a>, and an overview of the architecture: <a href="https://github.com/elipsitz/gamebub/blob/handheld/docs/architecture.md">https://github.com/elipsitz/gamebub/blob/handheld/docs/archi...</a>
Show HN: Game Bub – open-source FPGA retro emulation handheld
Hey HN,<p>Over the past ~1.5 years, I built an open-source FPGA retro emulation handheld that can play Game Boy, Game Boy Color, and Game Boy Advance cartridges. To my knowledge, there isn't an existing open-source FPGA emulator that can play physical cartridges like this.<p>One of my main goals was to do all of the pieces myself, and be able to understand every component of it, so I designed my own PCB, wrote the firmware, wrote a Game Boy and Game Boy Advance emulator for the FPGA (using the Chisel HDL), and designed a 3D-printed case.<p>I detailed the design and development process in the linked post. It's quite long, but there are a lot of pictures and videos.<p>Code and design files available on GitHub: <a href="https://github.com/elipsitz/gamebub">https://github.com/elipsitz/gamebub</a>, and an overview of the architecture: <a href="https://github.com/elipsitz/gamebub/blob/handheld/docs/architecture.md">https://github.com/elipsitz/gamebub/blob/handheld/docs/archi...</a>
Show HN: Nstart, a Nostr's Onbarding Tool
Nstart aims to guide new users to Nostr offering a easy and no-nonsense onboarding wizard, with useful hints about the protocol and some really exclusive features:<p>- Easy local backup of your nsec or ncryptsec
- Email yourself your ncryptsec, as an additional backup location
- Create a multi-signer bunker URL for Nostr Connect (more info below)
- Auto follow the contacts list of some old and trusted Nostr users
- Customize of contact suggestions, useful for onboarding friends & family<p>Try Nstart live at <a href="https://start.njump.me" rel="nofollow">https://start.njump.me</a> or watch this video to understand how it works: <a href="https://chronicle.dtonon.com/77b9a397cbbcd63f3bfc78ff2b2c0607e4ffa698a1fad33ab4736593c8ad4f90.mp4" rel="nofollow">https://chronicle.dtonon.com/77b9a397cbbcd63f3bfc78ff2b2c060...</a><p>For devs: it can also be used by any Nostr application, web or mobile, to offer an easy onboarding flow! You can integrate it effortlessly via a simple redirect, modal or popup: in the end, the user is automagically logged into the app, without needing to touch their keys/bunker.
<a href="https://jumble.social" rel="nofollow">https://jumble.social</a>, <a href="https://flotilla.social" rel="nofollow">https://flotilla.social</a>, <a href="https://nosotros.app" rel="nofollow">https://nosotros.app</a>, nostr-login (and so every website that uses it, like <a href="https://npub.pro" rel="nofollow">https://npub.pro</a>, <a href="https://nostr.band" rel="nofollow">https://nostr.band</a>, <a href="https://www.whynostr.org" rel="nofollow">https://www.whynostr.org</a>, etc..) are already using Nstart, check them.<p>Example of the integration: <a href="https://chronicle.dtonon.com/5a55f1db7efdc2b19a09284c360909e7397316e67ea671e3e6eea35cc1c2dc3b.mp4" rel="nofollow">https://chronicle.dtonon.com/5a55f1db7efdc2b19a09284c360909e...</a><p>Docs: <a href="https://github.com/dtonon/nstart/blob/master/APPS-INTEGRATION.md">https://github.com/dtonon/nstart/blob/master/APPS-INTEGRATIO...</a><p>A note about the multi-signer bunker. This is really cool stuff made by @fiatjaf, that uses FROST to split your nsec in 3 (or more) and distribute each shard to an independent trusted remote signer. This will give you a bunker code that you can use to log in to many web, mobile and desktop apps without exposing your nsec. If you ever lose your bunker code, if the signers vanish from Earth, and it stops working, or if it gets stolen by a malware virus, you can use your nsec to create a new one and invalidate the old one.<p>More info and source code: <a href="https://github.com/dtonon/nstart">https://github.com/dtonon/nstart</a><p>Enjoy it and send back any feedback, thanks!
Show HN: Wordle Charts – insights about Wordle you don't need
Hello HN! I'm a big fan of Wordle and I originally got this idea from seeing people gripe about Wordle suddenly being "harder" than usual. Wondering if this was true, I set out to snoop around the NYT's publicly available data, which gave me some pretty cool insights. I've put some of them on this simple site made with React and Claude.<p>There's a grand total of 7 visualizations, with some fun little touches here and there. My favorite is probably "Clairvoyant Guesses," which shows some (to put it nicely) suspicious day-to-day guessing patterns. There's also a fun little easter egg when you type "cat" and then enter a word into the "Find Word:" box. Let me know if you have any suggestions, and any feedback at all :)<p>Github Repo: <a href="https://github.com/crtez/is_wordle_harder_or_am_i_just_stupid">https://github.com/crtez/is_wordle_harder_or_am_i_just_stupi...</a>
Show HN: I built an AI coloring page generator
This webiste allows you to create black and white coloring page from text prompt. Generate, create collections, download your image and start coloring :)
Show HN: Seen – Virtual list rendering with 1M+ notes
Edit: Thank you so much for taking a look at Seen! Yes, I know, it's really slow. And scrolling does not render notes instantly. And the title is a bit clickbait-y. I'll try my best to improve on it though. This is just a preview, the most basic version of Seen, and it's getting there. But, oh God, I almost got a heart attack when I opened up Vercel Analytics and saw ~1,500 page views, up from 10 or 12. Thank you again! It's such a weird experience showing something to the world for the first time as a 16-year-old and seeing so many people look at it.<p>Hello HN!
I've been working on creating a new note-taking app called Seen. Right now, it's really just a preview: virtual-list rendering ~1,000,000 notes in a masonry layout, while trying to minimize CPU and memory usage as much as possible.<p>Seen currently has:<p>- A client-side search feature<p>- Creating, updating, deleting the topmost note (locally; no changes are saved to any server)<p>- Automatic repacking of the masonry layout when the window width changes<p>- A lot of bugs, I'm sure<p>I reached a point where I thought I was ready to show the Seen to the world, and this is it. It's pretty basic, I know, but I'm really proud of it.<p>Seen was born out of an experiment to see just how fast things can become if you use the right techniques, and will (hopefully) achieve this dream sometime in the near future. My vision for Seen is to create something that can handle a lot of notes while using the least amount of resources. If you've got any suggestions or bugs, they're welcome in the comments!<p>A little about how Seen works: during the first visit, Seen caches note heights for the specific window width. Seen also caches the HTML output for the Markdown notes. It caches height by the key SHA256(title + note content), and the Markdown-to-HTML renders by the key SHA256(note content). It uses this cache every other time instead of recalculating, meaning that if most of the content remains unchanged, Seen can render things pretty fast. Caches are saved to IndexedDB.<p>When window width changes, the amount of text that can fit in a line also changes. So, Seen caches heights for specific window widths as well, putting the width in the key. Scrolling triggers an event handler that calculates the current viewport and finds & renders all notes that are visible (or partially visible) with a buffer of a 600px.<p>When a note is deleted or inserted, the entire layout is re-rendered. I plan on optimizing this to only re-render the specific column, which is what happens anyway when a note is updated. Updated notes create new caches (as they should).
Show HN: Seen – Virtual list rendering with 1M+ notes
Edit: Thank you so much for taking a look at Seen! Yes, I know, it's really slow. And scrolling does not render notes instantly. And the title is a bit clickbait-y. I'll try my best to improve on it though. This is just a preview, the most basic version of Seen, and it's getting there. But, oh God, I almost got a heart attack when I opened up Vercel Analytics and saw ~1,500 page views, up from 10 or 12. Thank you again! It's such a weird experience showing something to the world for the first time as a 16-year-old and seeing so many people look at it.<p>Hello HN!
I've been working on creating a new note-taking app called Seen. Right now, it's really just a preview: virtual-list rendering ~1,000,000 notes in a masonry layout, while trying to minimize CPU and memory usage as much as possible.<p>Seen currently has:<p>- A client-side search feature<p>- Creating, updating, deleting the topmost note (locally; no changes are saved to any server)<p>- Automatic repacking of the masonry layout when the window width changes<p>- A lot of bugs, I'm sure<p>I reached a point where I thought I was ready to show the Seen to the world, and this is it. It's pretty basic, I know, but I'm really proud of it.<p>Seen was born out of an experiment to see just how fast things can become if you use the right techniques, and will (hopefully) achieve this dream sometime in the near future. My vision for Seen is to create something that can handle a lot of notes while using the least amount of resources. If you've got any suggestions or bugs, they're welcome in the comments!<p>A little about how Seen works: during the first visit, Seen caches note heights for the specific window width. Seen also caches the HTML output for the Markdown notes. It caches height by the key SHA256(title + note content), and the Markdown-to-HTML renders by the key SHA256(note content). It uses this cache every other time instead of recalculating, meaning that if most of the content remains unchanged, Seen can render things pretty fast. Caches are saved to IndexedDB.<p>When window width changes, the amount of text that can fit in a line also changes. So, Seen caches heights for specific window widths as well, putting the width in the key. Scrolling triggers an event handler that calculates the current viewport and finds & renders all notes that are visible (or partially visible) with a buffer of a 600px.<p>When a note is deleted or inserted, the entire layout is re-rendered. I plan on optimizing this to only re-render the specific column, which is what happens anyway when a note is updated. Updated notes create new caches (as they should).
Show HN: Infinite horizontal arrays of text editors
I made this app to write books chapter by chapter, while taking & browsing through temporary notes for each chapter.<p>The leftmost sidebar is the list of chapters. The sidebar to the right of that is the list of editors in the current chapter.<p>The UI & UX are a bit weird, but they have a basic logic to them.