Forgejo v10.0 is available
Forgejo v10.0 is available
6 comments
-
No mention of federation 😢 It must be a very boring or difficult topic to work on.
-
Federation of a forge has all the downsides of Lemmy federation multiplied - the implication is that I could issue a remote PR or a remote Issue (whatever) against a project with ill intent (trolls, spammers, whatever) instead of having a local account on that forge. sounds cool but...
...now besides only your own forge instance users, you now have to deal with "the whole world" being able to shit on your Git projects if they want to do so, until their bad-actor federated forge instance gets blocked. This is all beside the technical problems of how to integrate remote users into your workflows.
Forge federation has (to me) a large "social spam" problem of negatives to solve first. $0.02
-
Hmm... mailinglists should have the same problem, shouldn't they? Or are they maybe just so unpopular that they don't?
-
-
The whole reason I follow Forgejo is the thing they don't seem to progress on: federation.
We either need to accept mail based patches again and teach a wide audience how to work with that or we need a federated forge.
When federation gets picked up it will be a major boost for Forgejo and the FOSS community.
-
Mail based patches really are ancient tech. Only the minority will accept that workflow unless a beautiful UI is put on top of it.
If I had time and willingness to write Go, I'd participate in Forgejo. @forgejo@floss.social if you have a way to donate directly to federation development, I'd put money to that.
-
-
-
Is forgejo better than gitea?
6 comments