Developer Questions Cost of Free Source Code Hosting
Software engineer explores who should pay for reliable code repository availability as GitHub instability raises concerns.
Conversation activity · last 24 hours peak 10/hr
Summary, timeline and people extracted by Claude from 31 items across 2 sources · 9h ago. Quotes are verbatim.
A developer published an essay examining source code availability and dependency resilience, arguing the core question is not how to make hosting reliable but rather who should pay for it. The post discusses forking and vendoring strategies while critiquing the industry's reliance on free services from tech companies and mentions Radicle as a decentralized alternative, prompting discussion about cryptocurrency-linked projects in the comments.
- Developer essay frames source code availability as an economic question: who should fund reliable hosting rather than treating it as a technical problem.
- GitHub instability prompts discussion of forking and vendoring strategies, plus decentralized alternatives like Radicle.
- Radicle's cryptocurrency origins raise skepticism among commenters despite its technical innovations in distributed code hosting.
- Core tension remains unresolved: the open source ecosystem has relied on free corporate infrastructure while avoiding explicit funding models.
How it unfolded
-
Reaction Historical web3 connection confirmed
Patryk confirms Radicle's web3-related past, citing 2019 archives mentioning IPFS and blockchain associations.
-
Analysis Technical explanation of Radicle's namespace model
Lorenzleutgeb explains Radicle's Git namespace architecture and seeding options, describing how users can control which namespaces to replicate.
-
Reaction Concerns raised about Radicle's cryptocurrency ties
Commenter xales expresses skepticism about Radicle, noting cryptocurrency association and concerns about potential astroturfing or 'reasonable-washing' of the project.
-
Reaction Questions about CRDT maintenance costs
Commenter sebastiancarlos asks about practical CRDT implementation in Radicle and potential maintenance overhead for resolving causality or concurrency issues.
-
Reaction Author clarifies Radicle terminology
Kristoff clarifies that in Radicle, a 'fork' acts as a mirror (called 'seed') while also allowing creation of personal branches.
-
Report Same essay shared on Hacker News
The essay is cross-posted to Hacker News by the same author, reaching a wider audience.
-
Report Essay published on source code availability
Kristoff Zychowski publishes essay "Who Should Pay for Source Code Availability?" on Lobsters, discussing dependency management across GitHub, Codeberg, and self-hosted Forgejo instances.
What people are saying verbatim
“the question is not "how can we make source code hosting reliable?". We do know how to make code hosting reliable, if we really want to. The question is rather: how much should it cost, and who should pay for it?”
Kristoff Zychowski, Developer, essay author · kristoff.it blog (posted to Lobsters and Hacker News) · Aug 9, 9:42 AM
“we've been happy to leech off big tech companies but, as always, eventually an answer to the question must be given and, when that happens, we're quick to point the finger at the company, yelling "enshittification!" with righteous indignation.”
Kristoff Zychowski, Developer, essay author · kristoff.it blog (posted to Lobsters and Hacker News) · Aug 9, 9:42 AM
“I found Radicle interesting at a high level, but I think there's been some amount of reasonable-washing or astroturfing or something of it.”
xales, Lobsters commenter · Lobsters · Aug 9, 11:16 AM
“I'm wondering how well the CRDTs work in practice, and how much of a maintaince cost is involved in manual resolution or clarification”
sebastiancarlos, Lobsters commenter · Lobsters · Aug 9, 11:12 AM
Voices from the web unedited
-
I found Radicle interesting at a high level, but I think there’s been some amount of reasonable-washing or astroturfing or something of it. I recall having a really strong negative association with the name, and looking back, it seems like Radicle is/was some kind of cryptocurrency project, which appears consistent with the funding / organization…
-
> As is often the case in our industry, we never wanted to face that question, and we’ve been happy to leech off big tech companies but, as always, eventually an answer to the question must be given and, when that happens, we’re quick to point the finger at the company, yelling “enshittification!” with righteous indignation. This is some serious…
-
The non-profit's [own documents](https://community.radworks.org/t/rfc-foundation-org-proposal-2025/3606) show that it's largely a crypto funding / advocacy entity: [Q1-Q4] Administer RAD allocations for Radworks Orgs (and their Contributors), if desired by Org. [Q1] Create a template market integrity policy in light of novel regulatory crypto…
-
A lot of this really doesn't sit right with me, because I keep finding links back to the crypto company every time I dig more into this. It sounds like that link is talking about "Radicle Garden" (radicle.garden) which is a separate entity from Radworks which is the main crypto-company entity (and also funding DRIPS, which is a crypto-heavy…
-
I would have far less of an issue if there was more transparency in the relationship and how governance is or is not linked. If the idea is that whomever holds the RAD cryptocurrency has eventual control, that doesn't change both the day-to-day (who actually owns the distribution channels, domain names, etc.), nor that it's just capitalism with…
-
I think you're not appreciating the core superpower that decentralization offers: there is no de facto control. The network is made up of many individuals, independently *choosing* to run a node, and choosing which version of that node to run, and choosing which fork (or perhaps [alternate implementation of the…
-
My concern mostly lies with not seeing this as a cost worth paying. If the entity pushing forward development (and in the case of a decentralized thing, with de facto control over the "main network" which is effectively centralized by e.g. protocol agreement and software distribution control) is at core incentivized by creating software which…
-
I think you're over-indexing on the crypto stuff. Radicle as an idea is solid as-is. Yes, it's possible that the crypto affiliation ends up playing a role in the future, but the way I see is that people who are used to working on decentralized networks (i.e. crypto stuff) happened to stumble upon an idea that uses those same techniques and that is…
-
I don't know about the full history of Radicle, but nowadays it seems that the ownership of the development of the network [belongs to a Swiss non-profit](
-
I love the way the Zig community is building a sustainable ecosystem, one that depends on individuals showing up rather than big tech companies shouldering the weight. Keep up the good work!