mastodon

<p>re: better handling of non-notes by Mastodon</p><p>Toward the end of a day 2 FediForum session, <span class="h-card"><a href="https://mastodon.social/@pfefferle" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>pfefferle</span></a></span>, <span class="h-card"><a href="https://manton.org/activitypub/manton" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>manton</span></a></span>, and I sidetracked a bit and discussed once again the tendency for implementors to shift away from more suitable ActivityStreams Activities to as:Note.</p><p>Specifically, it was the demo/session by <span class="h-card"><a href="https://podcastindex.social/@samsethi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>samsethi</span></a></span> re: TrueFans. Instead of federating out an as:Listen, they send as:Note, and it&#x27;s a fairly safe bet that this is because the content cannot be richly represented in Mastodon. The same story played out with Mattias and the WordPress plugin, and myself with NodeBB.</p><p>Secondly, back in March/April and again in May, <span class="h-card"><a href="https://oisaur.com/@renchap" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>renchap</span></a></span> <a href="https://github.com/mastodon/mastodon/issues/29981#issuecomment-2110758130" rel="nofollow">mentioned that resolving this was of some interest to the Mastodon team</a>:</p><p><p>We will work on improving the display of non-Note content in the next Mastodon version</p></p><p>To be clear, getting Mastodon to suitably process as:Article/as:Listen/as:Offer or any number of other activities is not what the ForumWG wants to accomplish. It&#x27;s not up to Mastodon to adapt to the variety of content on the fediverse, but rather that its fallback handling needs to improve just enough so that its baseline rendering is acceptable to more implementors and their users.</p><p>As concise and actionable as I can make it:</p><p>Mastodon allows a subset of HTML for as:Note. This subset is good enough, but content in non-notes has all html stripped. Keep consistency here and allow the same subset of HTML.<br>Non-note content is truncated. This is no longer necessary due to the addition of the expand button. The wonderful thing is this standardization of behaviour actually simplifies Mastodon code.<br>Instead of appending the object URL to the status content, promote the &quot;Open Original Page&quot; button out of the overflow menu. It&#x27;s more than okay to defer to the original site vis-a-vis presentation and allow the user a smooth exit if desired (target=&quot;_top&quot; would be okay too if you&#x27;re worried!)</p><p>That&#x27;s it.</p><p>You could even skip the third point, but even with 1 and 2 achieved this would sufficiently raise the baseline behaviour just enough that I would immediately update NodeBB to send as:Article for new topics, and I am certain <span class="h-card"><a href="https://mastodon.social/@pfefferle" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>pfefferle</span></a></span> would adjust his defaults as well.</p><p>Lastly, <span class="h-card"><a href="https://oisaur.com/@renchap" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>renchap</span></a></span>, I&#x27;m sure I can speak for everyone at FediForum when I say that it was wonderful to see representatives from Mastodon (that of course includes <span class="h-card"><a href="https://macaw.social/@andypiper" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>andypiper</span></a></span> as well) in attendance. It means a lot to me personally that you were there, and sends a signal that Mastodon continues to desire broader inter-compatibility.</p>