Fedify: an ActivityPub server framework
Once the next version of #Fedify, v1.0.0, is released, the API will be stabilized. Are there any features you'd like to see before the API is stabilized?
Once the next version of #Fedify, v1.0.0, is released, the API will be stabilized. Are there any features you'd like to see before the API is stabilized?
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
@fedify dual node dispatchers so we can run one for actors/users and one for podcasts. We are currently forced to run two servers/domains
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
@fedify what are your thoughts on the client-server part of the protocol?
I get from the name alone that fedify is more oriented on the server-server side (i.e. federation). Vocabulary implementation & the rest of utility features would probably make it relatively easy to implement client-server stuff. But it would be nice to have it fully integrated, with something like outbox listeners on the federation object.