<?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[#Mastodon&#x27;s #ActivityPub inbox treats object types in tiers.]]></title><description><![CDATA[<p dir="auto">#Mastodon's #ActivityPub inbox treats object types in tiers. <code>Note</code> and <code>Question</code> are supported directly. A second tier, <code>Article</code>, <code>Page</code>, <code>Image</code>, <code>Audio</code>, <code>Video</code>, and <code>Event</code>, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as <code>Note</code> regardless of what the object actually is.</p>
<p dir="auto"><a href="https://github.com/mastodon/mastodon/issues/24079" target="_blank" rel="noopener noreferrer">mastodon/mastodon#24079</a> asks for content to show up whenever it's present and the <code>mediaType</code> is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.</p>
<p dir="auto">Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.</p>
<p dir="auto">If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.</p>
<p dir="auto">#fedidev #fediverse</p>
]]></description><link>https://forum.pierobosio.it/topic/8dab8074-1c72-4bbf-acd6-8d97ba5fd539/mastodon-s-activitypub-inbox-treats-object-types-in-tiers.</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Jul 2026 18:04:37 GMT</lastBuildDate><atom:link href="https://forum.pierobosio.it/topic/8dab8074-1c72-4bbf-acd6-8d97ba5fd539.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 10 Jul 2026 10:34:05 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to #Mastodon&#x27;s #ActivityPub inbox treats object types in tiers. on Fri, 10 Jul 2026 11:23:09 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/smallcircles%40social.coop" aria-label="Profile: smallcircles@social.coop">@<bdi>smallcircles@social.coop</bdi></a> Fair, and I'll be honest, I haven't read the linked post yet, it's a long one and I want to give it a proper read rather than skim it.</p>
<p dir="auto">I'd like to be more involved in the standardization side of this too. Language is a real hurdle for me there, participating in that kind of discussion in a second language is harder than it looks, so bear with me if I'm slower to engage than I'd like. That said, writing this case up as a FEP seems worth trying, and I might take a shot at it.</p>
]]></description><link>https://forum.pierobosio.it/post/https://hollo.social/@hongminhee/019f4bc4-6281-735d-8834-19f5704c0bdb</link><guid isPermaLink="true">https://forum.pierobosio.it/post/https://hollo.social/@hongminhee/019f4bc4-6281-735d-8834-19f5704c0bdb</guid><dc:creator><![CDATA[hongminhee@hollo.social]]></dc:creator><pubDate>Fri, 10 Jul 2026 11:23:09 GMT</pubDate></item><item><title><![CDATA[Reply to #Mastodon&#x27;s #ActivityPub inbox treats object types in tiers. on Fri, 10 Jul 2026 11:15:40 GMT]]></title><description><![CDATA[<p><span><a href="/user/hongminhee%40hollo.social">@<span>hongminhee</span></a></span> </p><p>&gt; If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.</p><p>Which is, umm.. *far* from ideal. In my long screed about the state of the fediverse my main plea was for the ecosystem of fedi devs caring collectively about the open and grassroots standardization processes. That way, after some time you get a standardization process that can 'stand on its own' i.e. make decisions on the best direction for the future, instead of always relying on the elephant in the room for any progress. There would be an incentive to follow this standardization process, which will never arise otherwise, and things remain "everyone together, alone".</p><p><a href="https://coding.social/blog/grassroots-evolution/" rel="nofollow noopener"><span>https://</span><span>coding.social/blog/grassroots-</span><span>evolution/</span></a></p>]]></description><link>https://forum.pierobosio.it/post/https://social.coop/users/smallcircles/statuses/116895392776495473</link><guid isPermaLink="true">https://forum.pierobosio.it/post/https://social.coop/users/smallcircles/statuses/116895392776495473</guid><dc:creator><![CDATA[smallcircles@social.coop]]></dc:creator><pubDate>Fri, 10 Jul 2026 11:15:40 GMT</pubDate></item></channel></rss>