cross-posted from: https://lemmy.ml/post/315953
- Mastodon post where they manage to follow a their gitea account: https://social.exozy.me/@ta180m/108472185098129371
- Gitea federation task list #3 - https://gitea.com/Ta180m/gitea/issues/3
- the gitea fork that develops this: https://gitea.com/Ta180m/gitea
Verry nice, Luke the idea
Hmm, wouldn’t it make more sense to first implement federation between Gitea instances? I see little point in following an Gitea account from Mastodon and the PRs and issues would probably get spammy really fast.
In some way, I do enjoy the barrier of entry to issue trackers, so long as other people who have complaints actually get their complaints properly added to the tracker by someone able to. Using a microblogging platform to add issue reports feels like it would become low-effort and spammy.
Federation between instances sounds useful, so that I don’t need accounts on multiple Gitea self-host instances (I’m already on two) and to give exposure to more projects. A project gets the benefit of ultimate control over their code base self-hosting, without the isolation of self-hosting.
