@evan There was some discussion of this on SocialHub a while back: https://socialhub.activitypub.rocks/t/fep-proposal-c2s-websocket-endpoint/2955
Or you might have been aware of it already, in which case, sorry for the noise 
F
fentiger@mastodon.social
@fentiger@mastodon.social
Posts
-
Server-sent Events for the ActivityPub API -
#activitypub thonk: delivering to a Collection is nonsensical because a Collection could be an actor.@trwnh I've started wondering if it would make more sense for an activity addressed to a Collection to be delivered to that Collection's owning actor - which is then responsible for expanding the collection, if that's what makes sense.
My thinking was that this would allow the owner to define policies such as who's allowed to send to the collection - but it would also support your use case, by allowing the owner to treat Follow activities differently.
-
@helge @steve My largest #ActivityPub object is this one at 223858 bytes: https://kbin.social/m/fediverse/t/4331@helge @steve My largest #ActivityPub object is this one at 223858 bytes: https://kbin.social/m/fediverse/t/4331
It doesn't help that it's doubled up, with every link appearing first in "content" and then in "contentMap[en]". It's legitimate, though - it says a bit more than just "snausages".
There are quite a few at around 50K, too, mostly Lemmy's federated block messages.