Show HN: How to Kill the Dead Internet https://ift.tt/oXiVdCn

Show HN: How to Kill the Dead Internet Ok, so maybe "how to revive the internet" would be more accurate, but if you're reading this, I got your attention, right? Here's why I want you to read on: I built a free extension, D-slop, to disincentivize anyone from posting AI writing, and eventually images and video as well, on the internet. For writing, it checks known vocab and punctuation tells, as well as subtler tells related to cadence, and assigns it a score subject to an adjustable threshold. If the text fails, users have the option to flag offending text, hide it, or block the page entirely (with the option to see anyway). For media, it's admittedly fairly weak, as it relies on C2PA metadata which is stripped from all of the social media sites where it would be most helpful. (Anyone else have chronically online boomer parents continually gobbling up slop like it's real information?) I have a D-slop+ version in the works that should be able to handle the media itself, but it's going to have to make API calls to have real teeth, which means I can't offer it for free. If this extension validates the concept, I'm happy to build it for y'all. Yes, I vibe-coded it, but an ancillary bonus to the project accrued when it inspired me to cook dinner listening to Metallica's "Fight Fire with Fire," which in turn brought my 5 y/o running into the kitchen with every musical instrument in the house for an impromptu karaoke speed metal session. It's MIT license open-source, full brief at https://ift.tt/kAxDcdh ; This forum is full of people smarter than me, so I'm open to suggestions. https://ift.tt/uYFES9M May 18, 2026 at 05:35AM

Show HN: Serene Bach – a Go weblog engine that runs as CGI or HTTP https://ift.tt/6kyYjPC

Show HN: Serene Bach – a Go weblog engine that runs as CGI or HTTP I originally made Serene Bach in the 2000s as a weblog engine written in Perl CGI. I rebuilt it from scratch in Go as a single binary that can run either as a CGI program or as a normal HTTP server. I know CGI is generally considered legacy technology now, but I still rely on it for shared hosting. In this version, I added Markdown support, a responsive default theme, Open Graph image generation, and static output generation. It is still in beta, but the repository includes a Docker image published on GHCR, documentation, and a local quick start. I'd appreciate feedback from anyone interested in small self-hosted publishing tools, especially if you still care about shared hosting or CGI-style deployment. https://ift.tt/VTpaF3z May 17, 2026 at 07:47AM

Show HN: Codiff, a local diff review tool https://ift.tt/fPjtok1

Show HN: Codiff, a local diff review tool Nowadays I review a lot of code locally that was written by llms. I used to review my own code using git + delta. It started to feel limiting with the amount of code written by llms. When looking at a large diff on Friday I pointed an llm at diffs.com and trees.software and told it to build an app. It only took 16 minutes, is extremely fast for large diffs, beautiful and minimal. Today I polished it up and added all the features that I need. It has file filters, search, an llm walkthrough mode, and review comments that you can paste back into your llm. I will be using Codiff a lot, and can finally review the large diff from Friday that led me to build this If you like it, fork it! https://ift.tt/b3ph4MU May 17, 2026 at 09:30AM

Show HN: I built a screen recorder that captures console logs, requests and more https://ift.tt/3TlQHpq

Show HN: I built a screen recorder that captures console logs, requests and more https://userplane.io/ May 16, 2026 at 11:34PM

Show HN: Got ghosted by tech companies so I built a tool to track ghost jobs https://ift.tt/BlOY7rh

Show HN: Got ghosted by tech companies so I built a tool to track ghost jobs Last year I was looking for a new role. I sent out applications, did the prep, waited. What came back was mostly nothing. Not rejection emails, just silence. The job listings I'd applied to stayed live for weeks. Some for months. As a software engineer, I decided to dig into it properly. I built a system to continuously track job postings across companies, logging posting dates and measuring how long roles stay open before closing or don't. After 35,000+ listings across 200+ companies, some patterns are hard to ignore. Some listings have been open for 700+ days at companies you'd recognize. Others post 90% of their open roles within a single month, a signal that's harder to fake than a press release. I published two initial insight pages based on this work: - Which companies are posting most aggressively right now - Job listings that have been open for over a year What I didn't expect is that the same signals useful for detecting ghost jobs also say something broader about a company's hiring momentum, recruiting intensity, pipeline health, where talent bottlenecks might exist. I'm not sure yet where this leads, but I'll keep expanding the dataset and publishing more insights as I go. Would genuinely love feedback on the methodology, interpretation, or obvious blind spots in the data. https://ift.tt/w5TN1uR May 17, 2026 at 12:43AM

Show HN: SwarmWright, structured multi-agent AI defined in markdowns https://ift.tt/4ESZTPM

Show HN: SwarmWright, structured multi-agent AI defined in markdowns I had a bunch of custom AI pipelines and a growing folder of markdown files and Python scripts holding it together. Built this to give that chaos some structure. Agents are markdown files, topology is a JSON file the runtime enforces hard. The agents are still fully autonomous: they make their own decisions, but the graph they operate in isn't. You declare who can call whom upfront and the runtime holds that line. No auth yet, fine if you don't expose the port, i guess. Two Docker commands to run it. https://ift.tt/HPLpkuc May 16, 2026 at 12:50AM

Show HN: Epiq – Distributed Git based issue tracker TUI https://ift.tt/iZB8eVG

Show HN: Epiq – Distributed Git based issue tracker TUI Issue trackers typically live outside of your workflow, with poor ergonomics. Epiq aims to solve that, bringing issue tracking into your terminal. Multi-user collaboration is achieved via git using user-scoped immutable event logs that converge in memory. Put my all into it. Let me know what you think. https://ljtn.github.io/epiq/ May 16, 2026 at 04:18AM