What is /dev/null?
/dev/null is a social network for developers built around the language and activity of software development. GitHub is the only way to sign in, posts are called commits, and the main timeline is a log with follows, stars, replies, quotes, and polls. The network was built from scratch in PHP, Laravel, Inertia, and React during a 48 hour public build.
Why /dev/null works
General social feeds make developer conversations compete with everything else people post online. /dev/null makes code culture the interface itself, turning posts into commits and the timeline into a log, so developers talk inside a network shaped around how they already build instead of adapting developer work to a generic social feed.
/dev/null features
- GitHub only access. Developers sign in with GitHub before they can follow people, star commits, or join conversations.
- Commit based posting. Posts are commits and the main timeline is presented as a log, giving familiar developer language to ordinary social activity.
- Developer conversations. Users can follow developers, reply to commits, quote posts, and star things they want to surface again.
- Polls and long commits. The network supports polls, longer posts, and quotes alongside regular commits and replies.
- Public read API. A public read API gives developers a way to access network content outside the main interface.
Who /dev/null is for
- Developers who want a social feed centered on other developers, projects, code, and what people are building.
- Open source maintainers who want public conversations around project news, pull requests, releases, and developer opinions.
- Developers who like sharing work in progress and seeing what other builders are shipping without moving those conversations into a general social network.
- GitHub users who prefer familiar concepts such as commits, logs, stars, and contributor activity as the language of a community.
Similar micro SaaS ideas you can build
- Social feed for open source maintainers. A network where maintainers post releases, roadmap decisions, contributor requests, and project updates, while developers follow projects and discuss each update in public threads.
- Developer build log network. A social product for indie hackers and engineers to post what they shipped each day, follow other builders, and keep discussions attached to individual build updates instead of scattered across general social media.
- GitHub activity discussion layer. A community feed that turns notable repository activity, such as releases, merged pull requests, and new projects, into posts developers can follow, react to, and discuss outside individual repository pages.