Roughly speaking our grassroots commons faces 3 challenges..

1. Tyranny of small decisions. Uncoordinated action makes it impossible to collaborate at scale

2. Herding of cats. Attempts to govern fiercely independent autonomous people doomed to fail

3. Tragedy of the commons. Unsustainable imbalance between value extraction and delivery

What ailed @forgefed for a long time is that everyone is interested for #ForgeFed to become the real deal, yet no one was working on it, no feedback.

@nlnet

I consider the #FEP process as a "best-we-can-manage" at the moment. There is room for a ton of improvement in the grassroots standardization process. What I would be much in favor of is to see more organization around specific themes.

The FEP is nice but it is a random collection of bits and pieces collected as best-practices from across the ecosystem.

Examples of where decentralized ecosystems focus on specific use cases or verticles are #ForgeFed, Podcasting, and Forums.

See also this topic on #SocialHub#ActivityPub dev community, with links to various #ForgeFed related issue trackers to participate in:

https://socialhub.activitypub.rocks/t/call-for-action-help-draw-attention-to-forgefed/5480

@forgefed @nlnet

@forgefed @nlnet

The attention to #ForgeFed has likely led to the following #HackerNews submission being discussed on the front page:

https://news.ycombinator.com/item?id=44873341#44896900

cc @forgejo @Codeberg bunch of discussion mentioning you there.

The https://forgefed.org developers are extending the specs, and asking for feedback in the issue trackers on #Codeberg, but none is forthcoming.

As a result large crowds root for @forgefed #forge federation to come along, but it will not happen anytime soon at the current pace.

@nlnet through #NGI0 provide funding to #ForgeFed, #Vervis, #Anvil, and also #Forgejo and these people are bravely forging ahead. More community help is needed though.

Same is true for #Gitlab's federation efforts.

@forgefed @nlnet

The attention to #ForgeFed has likely led to the following #HackerNews submission being discussed on the front page:

https://news.ycombinator.com/item?id=44873341#44896900

cc @forgejo @Codeberg bunch of discussion mentioning you there.

@forgefed can do with some help.

Please refer to my Call to Fediverse, regarding #ForgeFed and #ActivityPub #ForgeFederation status in general.

https://social.coop/@smallcircles/115014396440943917

Now #Codeberg and #Forgejo are among the first forge projects that consider implementing #ForgeFed. They are already busy implementing basic #ActivityPub support at this moment.

See: https://codeberg.org/forgejo-contrib/federation

#Codeberg is a developer platform based on the #Forgejo code forge software.

#ForgeFed is a protocol specification, an extension of #ActivityPub.

Any #forge can implement ForgeFed and become part of the #fediverse, as it were. This allows devs to interact with projects on remote forge servers as if they were part of their local hub. They can create issues, discuss them, create PR's, define teams.

The social network #Github provides to discover #FOSS projects is now federated.

I posted a call today for devs to give #forgefed due attention. There is a bit of a tragedy in that the @forgefed team is working on the specs, everyone very excited about the prospect of full forge federation, yet no one is implementing forgefed nor providing good input and feedback to mature the specs. The forgefed folks still have some @nlnet funding via #NGI0 but if that runs out it is unsure whether they can support implementers when time comes.

https://social.coop/@smallcircles/115014396440943917

See also this topic on #SocialHub#ActivityPub dev community, with links to various #ForgeFed related issue trackers to participate in:

https://socialhub.activitypub.rocks/t/call-for-action-help-draw-attention-to-forgefed/5480

@forgefed @nlnet

The https://forgefed.org developers are extending the specs, and asking for feedback in the issue trackers on #Codeberg, but none is forthcoming.

As a result large crowds root for @forgefed #forge federation to come along, but it will not happen anytime soon at the current pace.

@nlnet through #NGI0 provide funding to #ForgeFed, #Vervis, #Anvil, and also #Forgejo and these people are bravely forging ahead. More community help is needed though.

Same is true for #Gitlab's federation efforts.

Roughly speaking our grassroots commons faces 3 challenges..

1. Tyranny of small decisions. Uncoordinated action makes it impossible to collaborate at scale

2. Herding of cats. Attempts to govern fiercely independent autonomous people doomed to fail

3. Tragedy of the commons. Unsustainable imbalance between value extraction and delivery

What ailed @forgefed for a long time is that everyone is interested for #ForgeFed to become the real deal, yet no one was working on it, no feedback.

@nlnet

Just hearing the word/name "ForgeFed" lights me up with hope.

I don't know what it is but I imagine and hope it is a federated/ActivityPub git instance or something...

Gonna check it out!

#ForgeFed

okies, decided, today's the day... gonna start moving my repositories to codeberg... notabug.org's too consistently inconsistently available. n_n a little sad. mmmmmmuch fondness for notabug.org. ... i wonder, if i leave the repository off the end of the url in codeberg's migration tool... does it allow migrating everything in one go? :3

or should i skip codeberg, and go full forgejo? :)

#git #githosting #gitforge #notabug#codeberg #forgejo #forgefed

okies, decided, today's the day... gonna start moving my repositories to codeberg... notabug.org's too consistently inconsistently available. n_n a little sad. mmmmmmuch fondness for notabug.org. ... i wonder, if i leave the repository off the end of the url in codeberg's migration tool... does it allow migrating everything in one go? :3

or should i skip codeberg, and go full forgejo? :)

#git #githosting #gitforge #notabug#codeberg #forgejo #forgefed

Crisis averted, #GitLab reopened the epic on #ActivityPub / #ForgeFed implementation. 😊

They made it clear, though, that they're not going to do it themselves in any foreseeable future, their "current focus isn't in this area", so it's up to the community to implement it. As I mentioned in the issue, I won't be able to come back to it until I'm done bootstraping the business I'm working on, so anyone who wants to see it done faster should feel free to jump in.

https://gitlab.com/groups/gitlab-org/-/epics/11247#note_2603598572