julian on Nostr: Just messing around to see what happens when you send Mastodon an as:Article. Hoping ...

Just messing around to see what happens when you send Mastodon an as:Article. Hoping to start a less informal discussion about it tomorrow/Monday.


As expected:



<li>The experience is degraded vs <code>as:Note</code></li>
<li><code>name</code> is read and prepended to the rendered content</li>
<li><code>url</code> is read and appended to the rendered content</li>

Noting now that...



<li><code>summary</code> is <strong>NOT</strong> treated like it is for <code>as:Note</code>, where it acts like a content warning teaser</li>
<li><code>summary</code> is read and displayed as-is in the rendered content</li>
<li><code>summary</code> is not parsed into HTML. All HTML tags are escaped.</li>

I also tested this by having activitypub.academy pull the note from NodeBB. Could be that service is running an older fork of Mastodon and summary parsing is different now.


Can anyone shed additional context?