On October 15, 2026, Nuno Maduro, Brent Roose, Matthieu Napoli, and Pauline Vos sat down live in the JetBrains office, opened an empty repository, and built a complete social network in 48 hours — in PHP, live on stream, pull requests from outsiders welcome. The result is called /dev/null, and it’s one of the strangest yet most consistent products the PHP community has produced this year. I took it for a spin.
The concept: GitHub as login, commits as posts
The trick behind /dev/null is sticking consistently to developer metaphors instead of building yet another Twitter clone. Signing in happens exclusively through GitHub — there’s no email registration. A post is called a “commit,” the timeline is the “log.” Writing a long message means posting a “long commit,” a poll is a “poll,” and there’s even a mode called “pastéis,” whose only apparent purpose is to be a running in-joke among the core group. It sounds like a gimmick, but it genuinely carries the product’s identity through every corner of the interface.
Under the hood sits a fully conventional, modern Laravel stack: PHP, Laravel, Inertia, React, hosted on Laravel Cloud. Nothing exotic — the story here isn’t “we invented a new framework,” it’s “we reached production readiness with standard tools in 48 hours,” and that’s really the flex behind the project.
How fast this escalated
The numbers from the public timeline of the first few days are unusually steep for a niche product: 155 commits from 20 contributors and 39 open pull requests on day one alone. Day two added quotes, polls, automatic AI moderation for incoming commits, and a public read API — 221 more commits. Then the launch post went viral on Hacker News (176 points, 167 comments), and within two days of the first commit, 2,000 developers had signed up; by day three, over 3,000, with more than 300 pull requests submitted to the public repository.
The fact that Taylor Otwell (Laravel’s creator) joined mid-stream, and shortly after Guillermo Rauch (Vercel’s CEO) commented “This is really well done,” matters for reach within the PHP bubble — both posts are among the most “starred” commits on the platform.
What the timeline actually looks like
Content-wise, /dev/null is currently almost exclusively a PHP and Laravel audience: discussions about orchestrating agents between Claude and GPT, questions about people’s first web framework (“CodeIgniter!”), debates about AI agent setups, and a lot of inside humor between the same familiar, well-known names in the scene. That makes the platform pleasantly focused, but also small — if you’re not in the Laravel/PHP bubble, there isn’t much here for you. It’s explicitly not a Twitter replacement for the broader developer world, but a clubhouse for a very specific community.
Open development, literally
What’s notable is how seriously “open” is meant here: anyone could (and can) open a pull request against the live production instance. The “Contributors” list on the About page is sorted by real commit counts — and with 185 commits, the leader isn’t one of the four founders but an external contributor (Márk Magyar), who has since been officially added to the core team. For a product born in 48 hours, that’s an unusually open development process — most launches of this kind stay closed-source marketing stunts.
The open questions
- The GitHub-only login excludes anyone who doesn’t want to maintain a (public) GitHub account — a sensible positioning for developers, a dealbreaker as a general-purpose social network.
- Whether the current virality (the Hacker News wave, high-profile joins) holds up or fades in a few weeks like many “launch week” communities is simply not something a few days of runtime can answer yet.
- The namesake premise — posts vanishing like
/dev/null— isn’t taken particularly seriously on the platform itself: commits stay visible, get quoted, and collect “stars.” The name is a joke, not a feature description.
Verdict
/dev/null isn’t another Twitter clone — it’s a well-executed inside joke that happens to also work as a functioning social network. The technical achievement alone — production readiness in 48 hours, live, with hundreds of external pull requests in the first week — is worth a look. As a place for daily discussion, it’s currently worthwhile mainly for anyone already deep in the Laravel/PHP ecosystem; for everyone else, it remains an entertaining glimpse at what a focused group of good developers can pull off in a weekend when they do it in public.
