Conversation
Notices
-
Embed this notice
it seemed clear to me that Accept/Reject are meant to be human-created activities in AP
- kaia likes this.
-
Embed this notice
they all are, they shouldn't be repurposed for managing collection or conversation state, that will turn into a mess fast
-
Embed this notice
I am also thinking that overloading the verbs for multiple things that can only be matched by resolving the referenced object will make filtering more expensive.
-
Embed this notice
@i it's sort of funny how collection-oriented activitypub is yet they're almost unused except for inbox and outbox (because there's no defined rule for synchronizing collections across servers because that is a hard problem)
-
Embed this notice
@sun but it would be more fun if people were allowed to manage their own collections
-
Embed this notice
@i split horizon since everybody can see different activities, also they can be deleted.
-
Embed this notice
@sun you could federate the entire network off a single iteratable public /outbox, first and since is all you need
-
Embed this notice
@sun Specially as like… there's Add/Remove?