Gitea federation task list #3
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is a detailed task list of things that need to be accomplished for Gitea federation.
For Gitea 1.18, I think we should aim to at least get the federated features of following, starring, issues and comments, and pull requests merged, as well as a UI for them.
User keypairs
This is done.
Discovery
This is done.
Actors
This is almost done.
ForgeFed
go-ap
We need to add ForgeFed types to go-ap. Mastodon discussion, mailing list discussion, current code
Sending/receiving activities
This is almost done.
To
field which is a bad hack)attributedTo
matches HTTP signature.Database representation of remote data
User eXperience and User Interface
See #8 for discussions
authorize_interaction?uri=
page (like Mastodon)Serving/fetching ActivityStreams
Remote interactions
Migrations
See #9
Interoperability
Testing
Documentation
Moderation
See #10
Gitea federation statusto Are we federated yet?Are we federated yet?to Gitea federation task listHosting two servers will need a redesign of the integrations tests(and a lot of Gitea's core design), so that should be a nuclear option. What about creating a "reference-design" server, which is just a stub of the federation capabilities(it doesn't need to do any processing)
That's one possible idea, since it's actually really easy to implement a basic AP server (for instance, https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/) since you only need to serve an actor object and a Webfinger endpoint.
Another idea could be to federate Gitea with itself.