Help us shape Clansurf
Clansurf helps people help each other with technology they already own, even in a blackout. We're still deciding how it should run.
We're looking for research contributors, anywhere in the world. No degree needed. Remote, local or both.
HuyoWorld is building Clansurf for everyday needs such as food, clothing, repairs and computing. It should keep working when the services people rely on switch off.
We want each node to be productive: people help each other, and what they do is recorded honestly.
You might care about:
• Community governance and co-operatives
• How people help each other
• LoRa and mesh networks
• Getting everyone online
You may help us research questions such as:
• How can the first Clansurf node get started?
• What should the network's governing body look like?
• How can people in different countries build trust?
• How can communities manage resources fairly and transparently?
• What real-world use cases could Clansurf support?
• How can local technology help people during blackouts or other disruptions?
Your contribution may involve:
• Developing use cases
• Conducting local or remote field surveys
• Speaking with people in your community
• Documenting local needs and resources
• Researching co-operatives, communities and decentralised networks
• Gathering reliable sources
• Writing findings and recommendations
You may be a good fit if you:
• Care about people and how communities work
• Can support your ideas with reliable sources or experience
• Communicate clearly in writing and conversation
• Are curious, independent and willing to learn
• Have worked with co-operatives, local groups, mesh networks or open-source projects
Clansurf nodes bring together:
• Makers, who make or provide what others need: skills, products, services or crafts
• Supporters, who use what makers offer, share it with others and help keep the node going
• Maintainers, who help people join, keep notes on what works and keep the node true to its principles
Research is the starting point. As Clansurf grows, contributors may become maintainers, start a node in their own community and build it with the people there.
Early access: contributors are the first we invite to help start one of the first 25 nodes.
Contributors can get credit in their name. With your permission, your name, topic, contribution and links can go in our docs and the working paper. Nothing about you is published until you've approved it.
You choose how much time you give.
Email [email protected], or reply here. Three lines is enough:
• Where you are
• What you know about
• A question from the list, or "not sure yet"
How to contribute: https://t.co/xviRDtsAwi
Thanks to @typesafeai, Jev is helping bring precision to Community Signals
Scheduled to be open-sourced next week!
An effort to map signal over noise, especially around AI-generated code, AI slop for developer communities
https://t.co/kpaKdjOULi
A few patterns I keep seeing among COSS founders who fall behind. Sharing them because they’re worth sitting with before you partner with someone.
1/ They don’t really understand OSS. They use it as a positioning story, a vague narrative for investors, without ever nurturing the community that gives the work its actual value.
2/ They can’t bring things to fruition. Three areas to look for - personal, team, and the collective vision - all these never quite becomes real.
3/ They aim at everything that looks like an opportunity. There’s often a high-narcissism streak: they present themselves as the ones carrying everyone, when what’s actually happening is they’re taking credibility and leveraging other people’s work for their own reasons, not even for a productive, desired outcome.
They’re observations that are always worth weighing before you shake hands.
Agents can ship 30 PRs a day. Humans can’t review them.
Let's actually talk about what's breaking in our repos because of this.
Calling engineers, builders, founders, and maintainers for Engineering Unscripted -- a community-led technical talk series running through Q4 (Oct–Dec 2026).
We’ll be breaking down:
• Spec-driven development
• Open Source in 2027
• The review queue
Drop your questions below or tag someone who should be on the mic. 🎙️