Jump to content

ForgeFed and federated code forges: Difference between revisions

From IdeaWazaWiki
No edit summary
Tighten wikitext layout (no content changes)
 
Line 3: Line 3:
== Why federation matters for code ==
== Why federation matters for code ==
On 23 October 2020 the Recording Industry Association of America sent GitHub a takedown notice under the Digital Millennium Copyright Act targeting youtube-dl, a popular video download tool, and GitHub disabled the repository.<ref name="riaa" /> GitHub reinstated it on 16 November 2020 after receiving new information, and among its policy changes it promised that owners of disabled repositories would be able to export their issues and pull requests where legally possible.<ref name="ghblog" />
On 23 October 2020 the Recording Industry Association of America sent GitHub a takedown notice under the Digital Millennium Copyright Act targeting youtube-dl, a popular video download tool, and GitHub disabled the repository.<ref name="riaa" /> GitHub reinstated it on 16 November 2020 after receiving new information, and among its policy changes it promised that owners of disabled repositories would be able to export their issues and pull requests where legally possible.<ref name="ghblog" />
That promise points to a structural fact. Git is distributed, so every clone of youtube-dl still held the full code history. The issues, reviews and discussion around that code, however, lived only on the platform. Codeberg makes a similar argument in its mission statement: millions of volunteers produce free software that ends up hosted on closed commercial platforms, and it cites the fate of SourceForge as a warning.<ref name="codeberg" />
<!-- Last checked: November 2026 -->
<!-- Last checked: November 2026 -->
That promise points to a structural fact. Git is distributed, so every clone of youtube-dl still held the full code history. The issues, reviews and discussion around that code, however, lived only on the platform. Codeberg makes a similar argument in its mission statement: millions of volunteers produce free software that ends up hosted on closed commercial platforms, and it cites the fate of SourceForge as a warning.<ref name="codeberg" />
== How ForgeFed works ==
== How ForgeFed works ==
ForgeFed is an extension of ActivityPub, the protocol that the World Wide Web Consortium published as a Recommendation on 23 January 2018 and that underlies the fediverse.<ref name="ap" /> In ActivityPub every actor has an inbox for receiving messages and an outbox for sending them. ForgeFed extends that idea so that repositories and issue trackers have inboxes too. The project compares it to email, except that the messages are structured JSON objects instead of free text.<ref name="ffhome" />
ForgeFed is an extension of ActivityPub, the protocol that the World Wide Web Consortium published as a Recommendation on 23 January 2018 and that underlies the fediverse.<ref name="ap" /> In ActivityPub every actor has an inbox for receiving messages and an outbox for sending them. ForgeFed extends that idea so that repositories and issue trackers have inboxes too. The project compares it to email, except that the messages are structured JSON objects instead of free text.<ref name="ffhome" />
Line 12: Line 12:


Vervis is the reference implementation, used as a demonstration platform for testing the protocol. The ForgeFed site lists Forgejo as implementing federation and notes that a ForgeFed plugin for the Pagure forge is unmaintained.<ref name="ffhome" />
Vervis is the reference implementation, used as a demonstration platform for testing the protocol. The ForgeFed site lists Forgejo as implementing federation and notes that a ForgeFed plugin for the Pagure forge is unmaintained.<ref name="ffhome" />
== Where Forgejo stands ==
== Where Forgejo stands ==
Codeberg e.V. is a registered nonprofit association in Berlin whose members elect its board. Its site runs Forgejo, a hard fork of Gitea that Codeberg has backed as an umbrella organization since 2022.<ref name="codeberg" />
Codeberg e.V. is a registered nonprofit association in Berlin whose members elect its board. Its site runs Forgejo, a hard fork of Gitea that Codeberg has backed as an umbrella organization since 2022.<ref name="codeberg" />
Line 19: Line 18:


Federation is disabled by default. In September 2026 a security report described how Forgejo's inbox handlers accepted the actor named in a message body without checking that it matched the key that signed the request, which allowed forged stars and follows on instances with federation turned on. In the discussion that followed, stricter signature checks were proposed as a mitigation.<ref name="sec" />
Federation is disabled by default. In September 2026 a security report described how Forgejo's inbox handlers accepted the actor named in a message body without checking that it matched the key that signed the request, which allowed forged stars and follows on instances with federation turned on. In the discussion that followed, stricter signature checks were proposed as a mitigation.<ref name="sec" />
== What federation does not solve ==
== What federation does not solve ==
Federation moves messages between servers, but it does not replicate or preserve them. Under ForgeFed an actor hosts its own child objects, so a project's issues still live on its home instance.<ref name="ffspec" /> If that instance shuts down without a mirror, its history goes with it, and every instance remains a server that someone must fund and maintain.
Federation moves messages between servers, but it does not replicate or preserve them. Under ForgeFed an actor hosts its own child objects, so a project's issues still live on its home instance.<ref name="ffspec" /> If that instance shuts down without a mirror, its history goes with it, and every instance remains a server that someone must fund and maintain.
Line 26: Line 24:


Other projects take a different path. Radicle is a peer-to-peer forge in which repositories are replicated across peers, and issues, discussions and patches are stored as signed Git objects instead of being hosted by one server.<ref name="radicle" /> Pairing federation with a permanent archive is another option, explored in [[Permanent wiki and Git forges on AO]].
Other projects take a different path. Radicle is a peer-to-peer forge in which repositories are replicated across peers, and issues, discussions and patches are stored as signed Git objects instead of being hosted by one server.<ref name="radicle" /> Pairing federation with a permanent archive is another option, explored in [[Permanent wiki and Git forges on AO]].
== Practical steps today ==
== Practical steps today ==
Projects that want less platform risk can act now. They can host on Codeberg or another Forgejo instance, keep mirrors on more than one forge, export issues on a schedule, and keep federation for test instances until it matures. Developers interested in the protocol can read the ForgeFed specification and try Vervis, and the Forgejo federation repository publishes its architecture and threat analysis openly for review.
Projects that want less platform risk can act now. They can host on Codeberg or another Forgejo instance, keep mirrors on more than one forge, export issues on a schedule, and keep federation for test instances until it matures. Developers interested in the protocol can read the ForgeFed specification and try Vervis, and the Forgejo federation repository publishes its architecture and threat analysis openly for review.
== Discussion questions, essay ideas, and learning related AI prompt ideas ==
== Discussion questions, essay ideas, and learning related AI prompt ideas ==
* Why did the youtube-dl code survive its takedown more easily than its issues and discussions?
* Why did the youtube-dl code survive its takedown more easily than its issues and discussions?
Line 39: Line 35:
* Design a backup routine that would let a small open source project survive the loss of its forge.
* Design a backup routine that would let a small open source project survive the loss of its forge.
* How could federated forges and a permanent storage network divide the work of live collaboration and long-term preservation?
* How could federated forges and a permanent storage network divide the work of live collaboration and long-term preservation?
== Readings from Wikipedia ==
== Readings from Wikipedia ==
* [[Wikipedia:ActivityPub|ActivityPub]]
* [[Wikipedia:ActivityPub|ActivityPub]]
Line 53: Line 48:
* [[Wikipedia:Youtube-dl|Youtube-dl]]
* [[Wikipedia:Youtube-dl|Youtube-dl]]
* [[Wikipedia:Censorship of GitHub|Censorship of GitHub]]
* [[Wikipedia:Censorship of GitHub|Censorship of GitHub]]
== See also ==
== See also ==
{{Col}}
{{Col}}
Line 72: Line 66:
* [[Distributed technology]]
* [[Distributed technology]]
{{colend}}
{{colend}}
== External links ==
== External links ==
* [https://forgefed.org/ ForgeFed project site]
* [https://forgefed.org/ ForgeFed project site]
Line 81: Line 74:
* [https://ideawaza.com/index.php?search=federation&fulltext=Search Search this wiki for federation]
* [https://ideawaza.com/index.php?search=federation&fulltext=Search Search this wiki for federation]
* [https://ideawaza.com/index.php?search=Git+forge&fulltext=Search Search this wiki for Git forge]
* [https://ideawaza.com/index.php?search=Git+forge&fulltext=Search Search this wiki for Git forge]
== References ==
== References ==
<references>
<references>
Line 95: Line 87:
<ref name="radicle">{{cite web |url=https://radicle.xyz/ |title=Radicle: the sovereign forge |publisher=Radicle |access-date=15 November 2026}}</ref>
<ref name="radicle">{{cite web |url=https://radicle.xyz/ |title=Radicle: the sovereign forge |publisher=Radicle |access-date=15 November 2026}}</ref>
</references>
</references>
[[Category:Decentralization]]
[[Category:Decentralization]]
[[Category:Free software]]
[[Category:Free software]]
[[Category:Open source software]]
[[Category:Open source software]]
[[Category:Software]]
[[Category:Software]]

Latest revision as of 05:56, 16 November 2026

ForgeFed and federated code forges describe a way for separate code hosting sites to work together, so that a person registered on one forge can open an issue, star a project or submit a merge request on another without creating an account there. ForgeFed is the protocol that defines those exchanges, and Forgejo, the software behind the nonprofit Codeberg, is the best known forge working to implement it.[1][2] Federation spreads the social layer of software development across many independent servers, which makes it a real but partial answer to dependence on a single platform.

Why federation matters for code

On 23 October 2020 the Recording Industry Association of America sent GitHub a takedown notice under the Digital Millennium Copyright Act targeting youtube-dl, a popular video download tool, and GitHub disabled the repository.[3] GitHub reinstated it on 16 November 2020 after receiving new information, and among its policy changes it promised that owners of disabled repositories would be able to export their issues and pull requests where legally possible.[4]

That promise points to a structural fact. Git is distributed, so every clone of youtube-dl still held the full code history. The issues, reviews and discussion around that code, however, lived only on the platform. Codeberg makes a similar argument in its mission statement: millions of volunteers produce free software that ends up hosted on closed commercial platforms, and it cites the fate of SourceForge as a warning.[2]

How ForgeFed works

ForgeFed is an extension of ActivityPub, the protocol that the World Wide Web Consortium published as a Recommendation on 23 January 2018 and that underlies the fediverse.[5] In ActivityPub every actor has an inbox for receiving messages and an outbox for sending them. ForgeFed extends that idea so that repositories and issue trackers have inboxes too. The project compares it to email, except that the messages are structured JSON objects instead of free text.[1]

The specification sorts objects into activities, actors, child objects and global helpers. Actors such as repositories host their child objects, such as tickets, on their own server. To open an issue on a remote project, a contributor sends an Offer activity containing a Ticket to the project's tracker, and the tracker decides whether to accept it and assign it an address.[6] The specification also defines following, starring, remote pushes, forks and migrations, and the full life of issues and merge requests, from opening and assigning to applying patches and reviewing them.[6]

Vervis is the reference implementation, used as a demonstration platform for testing the protocol. The ForgeFed site lists Forgejo as implementing federation and notes that a ForgeFed plugin for the Pagure forge is unmaintained.[1]

Where Forgejo stands

Codeberg e.V. is a registered nonprofit association in Berlin whose members elect its board. Its site runs Forgejo, a hard fork of Gitea that Codeberg has backed as an umbrella organization since 2022.[2]

Forgejo's first federated feature, the federated star, was merged on 6 June 2024. When a mirror declares that it follows its origin repository, stars given on the mirror are passed along to the origin.[7] The project's federation roadmap marks the star as done; lists unstarring, following user activity and repository search as work in progress; and places federated comments, discussions and pull requests further out.[8]

Federation is disabled by default. In September 2026 a security report described how Forgejo's inbox handlers accepted the actor named in a message body without checking that it matched the key that signed the request, which allowed forged stars and follows on instances with federation turned on. In the discussion that followed, stricter signature checks were proposed as a mitigation.[9]

What federation does not solve

Federation moves messages between servers, but it does not replicate or preserve them. Under ForgeFed an actor hosts its own child objects, so a project's issues still live on its home instance.[6] If that instance shuts down without a mirror, its history goes with it, and every instance remains a server that someone must fund and maintain.

Discovery is also limited. Forgejo's roadmap says plainly that federated repository search makes no claim to completeness and can only find repositories that are somehow connected to the instance doing the search.[8] Trust is harder too, since each server must judge activity sent by strangers, as the 2026 security report showed.[9]

Other projects take a different path. Radicle is a peer-to-peer forge in which repositories are replicated across peers, and issues, discussions and patches are stored as signed Git objects instead of being hosted by one server.[10] Pairing federation with a permanent archive is another option, explored in Permanent wiki and Git forges on AO.

Practical steps today

Projects that want less platform risk can act now. They can host on Codeberg or another Forgejo instance, keep mirrors on more than one forge, export issues on a schedule, and keep federation for test instances until it matures. Developers interested in the protocol can read the ForgeFed specification and try Vervis, and the Forgejo federation repository publishes its architecture and threat analysis openly for review.

  • Why did the youtube-dl code survive its takedown more easily than its issues and discussions?
  • How does modeling a repository as an actor with an inbox change what a code forge can do?
  • What are the trade-offs between federation, where each server hosts its own data, and peer-to-peer replication, where many peers hold copies?
  • How should a forge decide whether to trust activity sent from an unknown server?
  • Why might a federated star be a sensible first feature, and what does it reveal about building federation in small steps?
  • What would a fair moderation policy look like for issues opened from other instances?
  • Design a backup routine that would let a small open source project survive the loss of its forge.
  • How could federated forges and a permanent storage network divide the work of live collaboration and long-term preservation?

Readings from Wikipedia

See also

References