Post
Building an implementation from the ground up with the goal of unleashing the client-server api.
This issue asks whether ActivityPub API be a complete replacement for a server's existing API
https://github.com/swicg/activitypub-api/issues/19
I’m wondering how far I can go without having to define ANY custom APIs.
For example, moderating local users: I could send activities to the application actor, with a Move activity with the target-actor as object from an Active to a Suspended collection
Obviously there are implementation details to work through with roles and permissions and such.
If I’ve learned anything from this space over the years it’s that moderation is critical to any social software.
So to me, any aspect of the software which deals with social, should be manageable from the ActivityPub API.
@django in the link aggregator I developed on top of GoActivityPub I have Flag/Block and Ignore activities by actors automatically be CCed to the moderator team - and they appear in an open anonymized moderation log.
Moderators can then do things to the actors/objects that were flagged.
It's not allowing for a lot of moderation nuance, but it's all done only with vanilla ActivityPub vocabulary.
@mariusor neat, so server side the moderator team exists as a collection of users?
A space for Bonfire maintainers and contributors to communicate
