<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[something something FEP about a "real time inbox" that signals that the actor should process this activity quickly?]]></title><description><![CDATA[<p>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)?</p><p>do either of these concepts already exist as feps?</p><p><a href="https://aus.social/tags/activitypub" rel="tag">#<span>activitypub</span></a> <a href="https://aus.social/tags/fedidev" rel="tag">#<span>fedidev</span></a> <a href="https://aus.social/tags/FEP" rel="tag">#<span>FEP</span></a></p>]]></description><link>https://fedi.wiki/topic/8a1d0edb-ea28-4db1-8c23-2753142804da/something-something-fep-about-a-real-time-inbox-that-signals-that-the-actor-should-process-this-activity-quickly</link><generator>RSS for Node</generator><lastBuildDate>Tue, 25 Aug 2026 08:25:07 GMT</lastBuildDate><atom:link href="https://fedi.wiki/topic/8a1d0edb-ea28-4db1-8c23-2753142804da.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 20 Aug 2026 12:07:20 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to something something FEP about a "real time inbox" that signals that the actor should process this activity quickly? on Thu, 20 Aug 2026 12:33:09 GMT]]></title><description><![CDATA[<p><span><a href="https://aus.social/@maddyunderstars" rel="noopener">@maddyunderstars</a></span></p><p>- <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/0499/fep-0499.md" rel="noopener">FEP-0499: Delivering to multiple inboxes with a multibox endpoint</a> (not about batching but could be repurposed for that)<br />- <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/1a11/fep-1a11.md" rel="noopener">FEP-1a11: Send Announces Containing Many Activities</a> (batching for FEP-1b12 applications)<br />- <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/3ab2/fep-3ab2.md" rel="noopener">FEP-3ab2: ActivityPub Event Streaming API</a> (this is for clients but might contain some interesting ideas)</p>]]></description><link>https://fedi.wiki/post/https://mitra.social/objects/01a01f29-3713-7470-a060-180524162089</link><guid isPermaLink="true">https://fedi.wiki/post/https://mitra.social/objects/01a01f29-3713-7470-a060-180524162089</guid><dc:creator><![CDATA[silverpill@mitra.social]]></dc:creator><pubDate>Thu, 20 Aug 2026 12:33:09 GMT</pubDate></item><item><title><![CDATA[Reply to something something FEP about a "real time inbox" that signals that the actor should process this activity quickly? on Thu, 20 Aug 2026 12:12:20 GMT]]></title><description><![CDATA[<div><span><a href="https://aus.social/@maddyunderstars"><span>@maddyunderstars</span></a></span><span> 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</span></div>]]></description><link>https://fedi.wiki/post/https://not-brain.d.on-t.work/notes/aq51olulggzqny6y</link><guid isPermaLink="true">https://fedi.wiki/post/https://not-brain.d.on-t.work/notes/aq51olulggzqny6y</guid><dc:creator><![CDATA[kopper@not-brain.d.on-t.work]]></dc:creator><pubDate>Thu, 20 Aug 2026 12:12:20 GMT</pubDate></item><item><title><![CDATA[Reply to something something FEP about a "real time inbox" that signals that the actor should process this activity quickly? on Thu, 20 Aug 2026 12:10:21 GMT]]></title><description><![CDATA[<div><span><a href="https://aus.social/@maddyunderstars"><span>@maddyunderstars</span></a></span><span> <br /></span><blockquote><span>where the object is at least one activity to be delivered</span></blockquote><span>the "at least" seems to imply batching is indeed a valid use case</span></div>]]></description><link>https://fedi.wiki/post/https://not-brain.d.on-t.work/notes/aq51m20s95e7nwk7</link><guid isPermaLink="true">https://fedi.wiki/post/https://not-brain.d.on-t.work/notes/aq51m20s95e7nwk7</guid><dc:creator><![CDATA[kopper@not-brain.d.on-t.work]]></dc:creator><pubDate>Thu, 20 Aug 2026 12:10:21 GMT</pubDate></item><item><title><![CDATA[Reply to something something FEP about a "real time inbox" that signals that the actor should process this activity quickly? on Thu, 20 Aug 2026 12:09:47 GMT]]></title><description><![CDATA[<div><span><a href="https://aus.social/@maddyunderstars"><span>@maddyunderstars</span></a></span><span> don't think they do but batching is really useful even outside realtime use<br /><br /></span><a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/0499/fep-0499.md">multibox</a><span> can TECHNICALLY do batching due to the json-ld quirk of everything being an array (so, send multiple activities as an array of </span><code>as:object</code><span>). no clue if anybody implements it but it should be Technically Spec Compliant</span></div>]]></description><link>https://fedi.wiki/post/https://not-brain.d.on-t.work/notes/aq51lc2pce13aym3</link><guid isPermaLink="true">https://fedi.wiki/post/https://not-brain.d.on-t.work/notes/aq51lc2pce13aym3</guid><dc:creator><![CDATA[kopper@not-brain.d.on-t.work]]></dc:creator><pubDate>Thu, 20 Aug 2026 12:09:47 GMT</pubDate></item></channel></rss>