/dev/null Wants to Be a Social Network Built on GitHub Profiles
/dev/null describes itself as a social network for developers. Sign-in uses GitHub, profiles are imported from GitHub with nothing to fill in, and the two core actions are following people who write code and adding plain text to a shared log dev-null.sh.
The official site is at dev-null.sh. Entries to the shared log are limited to 280 characters each dev-null.sh.
As documented on Oct. 16, 2026, the description covers three functions. GitHub provides identity and profiles, following people provides discovery, and publishing means adding plain-text entries to a shared log.
The broader context here is onboarding friction, which hits developer tools especially hard. Engineers will put up with complex setup in a work tool but will quickly leave a social app that demands the same effort. Pulling in the GitHub profile removes forms, photo choices, and bio writing in one step. It also ties identity to a place where usernames already carry work history and peer context. The tradeoff is straightforward. Setup takes almost no time, but what others see is limited to what GitHub already says.
Looking at posting more closely, plain text and one shared log are deliberate limits. There is no photo or video pipeline to run, and no formatting differences between apps to fix. Each entry is a small packet of text, which keeps storage needs low and makes small apps easy to build. The 280-character limit supports that pattern. Short posts suit quick updates, links, and questions rather than long essays. For readers with some technical background, think of it less like a forum with threads and more like a continuous feed that only grows.
In my view, the decision to center follows on people rather than code projects is the part to watch. Code sites already track interest in projects through stars, forks, and watchers, which are counts of approval or copies. A follow graph tracks interest in judgment instead. It points to who explains a bug clearly or shares a useful snippet late at night. That signal builds if the log stays public and searchable. It can also weaken as the shared feed grows, with more noise, pile-ons, and low-value posts.
Worth flagging for the longer term is how that shared space is managed. A common log needs common rules for spam, abuse, and automated posts. Requiring GitHub identity makes throwaway accounts harder without removing the problem. Access for programs, rules for bots, and how long posts are kept will decide whether the feed stays readable or fills with automated build notices. None of that is spelled out in the current description. What is spelled out is small enough that independent developers could build for it in a weekend, and that may be the point.
