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: DrawDB – open-source online database diagram editor (a retro)

One year ago I open-sourced my very first 'real' project and shared it here. I was a college student in my senior year and desperately looking for a job. At the time of sharing it i couldn't even afford a domain and naively let someone buy the one i had my eyes on lol. It's been a hell of a year with this blowing up, me moving to another country, and switching 2 jobs.<p>In a year we somehow managed to hit 26k stars, grow a 1000+ person discord community, and support 37 languages. I couldn't be more grateful for the community that helped this grow, but now i don't know what direction to take this project in.<p>All of this was an accident. But now I feel like I'm missing out on not using this success. I have been thinking of monetization options, but not sure if I wanna go down that route. I like the idea of it being free and available for everyone but also can't help but think of everything that could be done if committed full-time or even had a small team. I keep telling myself(and others) i'll do something if i meet a co-founder, but doubt and fear of blowing this up keeps back.<p>How would you proceed?

Show HN: DrawDB – open-source online database diagram editor (a retro)

One year ago I open-sourced my very first 'real' project and shared it here. I was a college student in my senior year and desperately looking for a job. At the time of sharing it i couldn't even afford a domain and naively let someone buy the one i had my eyes on lol. It's been a hell of a year with this blowing up, me moving to another country, and switching 2 jobs.<p>In a year we somehow managed to hit 26k stars, grow a 1000+ person discord community, and support 37 languages. I couldn't be more grateful for the community that helped this grow, but now i don't know what direction to take this project in.<p>All of this was an accident. But now I feel like I'm missing out on not using this success. I have been thinking of monetization options, but not sure if I wanna go down that route. I like the idea of it being free and available for everyone but also can't help but think of everything that could be done if committed full-time or even had a small team. I keep telling myself(and others) i'll do something if i meet a co-founder, but doubt and fear of blowing this up keeps back.<p>How would you proceed?

Show HN: DrawDB – open-source online database diagram editor (a retro)

One year ago I open-sourced my very first 'real' project and shared it here. I was a college student in my senior year and desperately looking for a job. At the time of sharing it i couldn't even afford a domain and naively let someone buy the one i had my eyes on lol. It's been a hell of a year with this blowing up, me moving to another country, and switching 2 jobs.<p>In a year we somehow managed to hit 26k stars, grow a 1000+ person discord community, and support 37 languages. I couldn't be more grateful for the community that helped this grow, but now i don't know what direction to take this project in.<p>All of this was an accident. But now I feel like I'm missing out on not using this success. I have been thinking of monetization options, but not sure if I wanna go down that route. I like the idea of it being free and available for everyone but also can't help but think of everything that could be done if committed full-time or even had a small team. I keep telling myself(and others) i'll do something if i meet a co-founder, but doubt and fear of blowing this up keeps back.<p>How would you proceed?

Show HN: Minimal MCP server in Go showcasing project architecture

I'm relatively new to Go, but recently got interested in how MCP servers work. I started thinking about what the architecture of such a project might look like, and decided to build a minimalist version as an experiment.<p>I based it on my past experience writing regular REST API servers and figured it might be useful or interesting to others as well.

Show HN: I built a tool to find devs based on code, not LinkedIn titles

Hey HN<p>After years working in software engineering and helping with hiring, I noticed a frustrating pattern:<p>Companies often rely on résumés and LinkedIn titles to find developers instead of looking at what they've actually built.<p>So I built GitMatcher.<p>It analyzes GitHub profiles to surface developers based on:<p>Their public repos<p>Commit history<p>Originality and usefulness of code<p>Patterns that show consistency and real skill<p>No keywords. No job titles. Just code.<p>GitMatcher is useful if you're:<p>- A recruiter tired of resume roulette<p>- A founder looking for a technical co-founder<p>- An OSS maintainer searching for genuine contributors<p>It’s still early, so I’d love your feedback especially around what signals you’d care about most when discovering devs.

Show HN: I built a tool to find devs based on code, not LinkedIn titles

Hey HN<p>After years working in software engineering and helping with hiring, I noticed a frustrating pattern:<p>Companies often rely on résumés and LinkedIn titles to find developers instead of looking at what they've actually built.<p>So I built GitMatcher.<p>It analyzes GitHub profiles to surface developers based on:<p>Their public repos<p>Commit history<p>Originality and usefulness of code<p>Patterns that show consistency and real skill<p>No keywords. No job titles. Just code.<p>GitMatcher is useful if you're:<p>- A recruiter tired of resume roulette<p>- A founder looking for a technical co-founder<p>- An OSS maintainer searching for genuine contributors<p>It’s still early, so I’d love your feedback especially around what signals you’d care about most when discovering devs.

Show HN: Badgeify – Add Any App to Your Mac Menu Bar

Show HN: Badgeify – Add Any App to Your Mac Menu Bar

Show HN: Connecting an IBM 3151 terminal to a mainframe [video]

The IBM 3151 from 1987 is an interesting ASCII terminal. Unlike "normal" serial terminals, it not only supports the so-called "character mode", where after each keypress there is an interaction with the host computer (like with a Unix terminal), but it also has a "block mode". This means, you can send it commands to define fields for input and output on the screen (like a form to fill out). The terminal then handles autonomously all the the user input, and when the user is done and presses a special key (Enter or a function key), all the entries in the form are transferred to the host in one go.<p>This is very similar but unfortunately not identical to the so-called 3270 terminals used by IBM mainframe computers. Therefore, I wrote a little C program to translate between the differing protocols of 3270 and 3151 terminals enabling a 3151 to be connected to a mainframe.<p>I made a video describing a little bit the 3151 terminal and the interface program and showing how it looks like to work with the (emulated) mainframe on an 3151. The source code and Windows binary are on github for you to try out, if you happen to have a 3151 terminal. The link is in the description of the video.

Show HN: Connecting an IBM 3151 terminal to a mainframe [video]

The IBM 3151 from 1987 is an interesting ASCII terminal. Unlike "normal" serial terminals, it not only supports the so-called "character mode", where after each keypress there is an interaction with the host computer (like with a Unix terminal), but it also has a "block mode". This means, you can send it commands to define fields for input and output on the screen (like a form to fill out). The terminal then handles autonomously all the the user input, and when the user is done and presses a special key (Enter or a function key), all the entries in the form are transferred to the host in one go.<p>This is very similar but unfortunately not identical to the so-called 3270 terminals used by IBM mainframe computers. Therefore, I wrote a little C program to translate between the differing protocols of 3270 and 3151 terminals enabling a 3151 to be connected to a mainframe.<p>I made a video describing a little bit the 3151 terminal and the interface program and showing how it looks like to work with the (emulated) mainframe on an 3151. The source code and Windows binary are on github for you to try out, if you happen to have a 3151 terminal. The link is in the description of the video.

Show HN: Coroot – eBPF-based, open source observability with actionable insights

A common open source approach to observability will begin with databases and visualizations for telemetry - Grafana, Prometheus, Jaeger. But observability doesn’t begin and end here: these tools require configuration, dashboard customization, and may not actually pinpoint the data you need to mitigate system risks.<p>Coroot was designed to solve the problem of manual, time-consuming observability analysis: it handles the full observability journey — from collecting telemetry to turning it into actionable insights. We also strongly believe that simple observability should be an innovation everyone can benefit from: which is why our software is open source.<p>Features:<p>- Cost monitoring to track and minimise your cloud expenses (AWS, GCP, Azure.)<p>- SLO tracking with alerts to detect anomalies and compare them to your system’s baseline behaviour.<p>- 1-click application profiling: see the exact line of code that caused an anomaly.<p>- Mapped timeframes (stop digging through Grafana to find when the incident occurred.)<p>- eBPF automatically gathers logs, metrics, traces, and profiles for you.<p>- Service map to grasp a complete at-a-glance picture of your system.<p>- Automatic discovery and monitoring of every application deployment in your kubernetes cluster.<p>We welcome any feedback and hope the tool can improve your workflow!

Show HN: Coroot – eBPF-based, open source observability with actionable insights

A common open source approach to observability will begin with databases and visualizations for telemetry - Grafana, Prometheus, Jaeger. But observability doesn’t begin and end here: these tools require configuration, dashboard customization, and may not actually pinpoint the data you need to mitigate system risks.<p>Coroot was designed to solve the problem of manual, time-consuming observability analysis: it handles the full observability journey — from collecting telemetry to turning it into actionable insights. We also strongly believe that simple observability should be an innovation everyone can benefit from: which is why our software is open source.<p>Features:<p>- Cost monitoring to track and minimise your cloud expenses (AWS, GCP, Azure.)<p>- SLO tracking with alerts to detect anomalies and compare them to your system’s baseline behaviour.<p>- 1-click application profiling: see the exact line of code that caused an anomaly.<p>- Mapped timeframes (stop digging through Grafana to find when the incident occurred.)<p>- eBPF automatically gathers logs, metrics, traces, and profiles for you.<p>- Service map to grasp a complete at-a-glance picture of your system.<p>- Automatic discovery and monitoring of every application deployment in your kubernetes cluster.<p>We welcome any feedback and hope the tool can improve your workflow!

Show HN: Uncurl.dev – Convert curl commands to a shareable, executable UI

Hey HN,<p>I built uncurl.dev to scratch my own itch: I kept getting curl commands in API docs, bug reports, or Slack messages and wanted a quick way to visualize, run, and debug them without firing up Postman or writing code to dissect them. It was also sometimes painful to create a test page specifically for non-tech users to consume an API. I originally vibe-coded this over a weekend just to make it easier for myself to debug API requests shared as curl commands. It slowly grew into something I found surprisingly useful in my workflow, so I decided to clean it up and share it.<p>uncurl.dev takes a curl command and: - Converts it into a visual representation - Lets you edit and inspect all parts of the request - Allows sharing via a unique link - (Optionally) executes it from the server, so business or non-technical users can see results<p>Execution is currently behind login, with a cap (5/min) to avoid abuse and manage costs. Non-logged-in users can still build and share curl commands—they just can’t execute them. The server runs each request in a Docker sandbox with strict resource/time limits (cpu, memory, timeout, no network access outside the request).<p>It’s not meant to replace full-featured tools like Postman or Hoppscotch. It’s more of a “CLI-to-UI bridge” for fast sharing and debugging, especially in dev workflows where curl is the starting point. Think of it like Pastebin or JSFiddle, but for curl commands.<p>If you’ve ever copied a curl from an API doc and wanted a cleaner way to see it or send it to someone else, I’d love your feedback.<p>Thanks! (You can try it without signup here: <a href="https://uncurl.dev" rel="nofollow">https://uncurl.dev</a>)

Show HN: Uncurl.dev – Convert curl commands to a shareable, executable UI

Hey HN,<p>I built uncurl.dev to scratch my own itch: I kept getting curl commands in API docs, bug reports, or Slack messages and wanted a quick way to visualize, run, and debug them without firing up Postman or writing code to dissect them. It was also sometimes painful to create a test page specifically for non-tech users to consume an API. I originally vibe-coded this over a weekend just to make it easier for myself to debug API requests shared as curl commands. It slowly grew into something I found surprisingly useful in my workflow, so I decided to clean it up and share it.<p>uncurl.dev takes a curl command and: - Converts it into a visual representation - Lets you edit and inspect all parts of the request - Allows sharing via a unique link - (Optionally) executes it from the server, so business or non-technical users can see results<p>Execution is currently behind login, with a cap (5/min) to avoid abuse and manage costs. Non-logged-in users can still build and share curl commands—they just can’t execute them. The server runs each request in a Docker sandbox with strict resource/time limits (cpu, memory, timeout, no network access outside the request).<p>It’s not meant to replace full-featured tools like Postman or Hoppscotch. It’s more of a “CLI-to-UI bridge” for fast sharing and debugging, especially in dev workflows where curl is the starting point. Think of it like Pastebin or JSFiddle, but for curl commands.<p>If you’ve ever copied a curl from an API doc and wanted a cleaner way to see it or send it to someone else, I’d love your feedback.<p>Thanks! (You can try it without signup here: <a href="https://uncurl.dev" rel="nofollow">https://uncurl.dev</a>)

Show HN: Uncurl.dev – Convert curl commands to a shareable, executable UI

Hey HN,<p>I built uncurl.dev to scratch my own itch: I kept getting curl commands in API docs, bug reports, or Slack messages and wanted a quick way to visualize, run, and debug them without firing up Postman or writing code to dissect them. It was also sometimes painful to create a test page specifically for non-tech users to consume an API. I originally vibe-coded this over a weekend just to make it easier for myself to debug API requests shared as curl commands. It slowly grew into something I found surprisingly useful in my workflow, so I decided to clean it up and share it.<p>uncurl.dev takes a curl command and: - Converts it into a visual representation - Lets you edit and inspect all parts of the request - Allows sharing via a unique link - (Optionally) executes it from the server, so business or non-technical users can see results<p>Execution is currently behind login, with a cap (5/min) to avoid abuse and manage costs. Non-logged-in users can still build and share curl commands—they just can’t execute them. The server runs each request in a Docker sandbox with strict resource/time limits (cpu, memory, timeout, no network access outside the request).<p>It’s not meant to replace full-featured tools like Postman or Hoppscotch. It’s more of a “CLI-to-UI bridge” for fast sharing and debugging, especially in dev workflows where curl is the starting point. Think of it like Pastebin or JSFiddle, but for curl commands.<p>If you’ve ever copied a curl from an API doc and wanted a cleaner way to see it or send it to someone else, I’d love your feedback.<p>Thanks! (You can try it without signup here: <a href="https://uncurl.dev" rel="nofollow">https://uncurl.dev</a>)

Show HN: Lux – A luxurious package manager for Lua

Show HN: Lux – A luxurious package manager for Lua

Show HN: Lux – A luxurious package manager for Lua

Show HN: Browser MCP – Automate your browser using Cursor, Claude, VS Code

Show HN: Browser MCP – Automate your browser using Cursor, Claude, VS Code