Gregory's Servershitpost of course but i am once again thinking about the muddiness of treating activities as commands or as remote procedure calls, instead of treating them as purely notifications. i mean really they're just a series of statements. bit weird to go attach behaviors to them. it's the kind of thing that makes me make jokes about the activitypub vm or programming language
|
6 comments
 @dmitri no, i'd rather we were explicit about defining an actual "protocol" such that i can tell ahead-of-time if the actor i'm sending an activity to is going to do anything with that activity. basically, are they going to interpret my notification as a command? that's kind of important to know!  @dmitri like, look at Create Note. if i want that to just be a notification, i'm going to be very upset when someone takes that as a command to Create an identical Note in their database. Taking it one step further: if Nextcloud generated a Create Document, and sent it as a notification, then some other system saw that as a command to Create the same Document... see how messy it gets? @dmitri throw in some state desync (blocks, failed deliveries, silent actions, etc.) and you're going to have some real "fun" dealing with that mess. |
@trwnh one, LOL true. But also.. I dont know if it's that muddy. Distributed event logs is a really common pattern for federated or p2p distributed systems. Like.. would you rather it was direct RPC calls?