FEP-fc48: Generic ActivityPub server
This is a discussion thread for FEP-fc48: Generic ActivityPub server.
Generic ActivityPub server is a server that implements standard ActivityPub client API or FEP-ae97 client API, and can process any activity (including activities those behavior is not defined in the ActivityPub specification).
Codeberg.orgfep/fep/fc48/fep-fc48.md at mainfep - Fediverse Enhancement Proposals
Is there more than the list of 5 basic activities that can be considered generic, I wonder? Perhaps it might make sense to describe what a generic server supports, in the form of Use Cases, in a similar way as the motivational use cases in the ActivityStreams vocubulary spec. Then for each use case a consistent pattern can be specified that MUST be implemented (either refer to AP spec if robustly defined there and/or add additional info on format, behavior, msg exchange).
Replying to @aschrijver@socialhub.activitypub.rocks
Adding examples: https://codeberg.org/fediverse/fep/pulls/909/files
I think Follow-Accept could be broken down into Create(Relationship) and Add activities.
Codeberg.orgfepFediverse Enhancement Proposals