something something FEP about a "real time inbox" that signals that the actor should process this activity quickly?
-
something something FEP about a "real time inbox" that signals that the actor should process this activity quickly? could be useful for inserting into some other queue? perhaps this could also be a batched inbox e.g. N number of activities can be delivered at once, like Matrix EDUs (iirc)?
do either of these concepts already exist as feps?
-
something something FEP about a "real time inbox" that signals that the actor should process this activity quickly? could be useful for inserting into some other queue? perhaps this could also be a batched inbox e.g. N number of activities can be delivered at once, like Matrix EDUs (iirc)?
do either of these concepts already exist as feps?
@maddyunderstars don't think they do but batching is really useful even outside realtime use
multibox can TECHNICALLY do batching due to the json-ld quirk of everything being an array (so, send multiple activities as an array ofas:object). no clue if anybody implements it but it should be Technically Spec Compliant -
@maddyunderstars don't think they do but batching is really useful even outside realtime use
multibox can TECHNICALLY do batching due to the json-ld quirk of everything being an array (so, send multiple activities as an array ofas:object). no clue if anybody implements it but it should be Technically Spec Compliant@maddyunderstarswhere the object is at least one activity to be delivered
the "at least" seems to imply batching is indeed a valid use case -
@maddyunderstars
where the object is at least one activity to be delivered
the "at least" seems to imply batching is indeed a valid use case@maddyunderstars though. uh. i think you lose ordering here because json-ld arrays are technically sets and not lists if not explicitly declared as such. you'll want to have timestamps on each activity and re-order them during processing -
something something FEP about a "real time inbox" that signals that the actor should process this activity quickly? could be useful for inserting into some other queue? perhaps this could also be a batched inbox e.g. N number of activities can be delivered at once, like Matrix EDUs (iirc)?
do either of these concepts already exist as feps?
- FEP-0499: Delivering to multiple inboxes with a multibox endpoint (not about batching but could be repurposed for that)
- FEP-1a11: Send Announces Containing Many Activities (batching for FEP-1b12 applications)
- FEP-3ab2: ActivityPub Event Streaming API (this is for clients but might contain some interesting ideas)
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login