Mastodon and non-Note types

julian

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:

The experience is degraded vs as:Note
name is read and prepended to the rendered content
url is read and appended to the rendered content

Noting now that...

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

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?

Jupiter Rowland

@julian

Noting now that...
summary is NOT treated like it is for as:Note, where it acts like a content warning teaser

AFAIK, that's typical behaviour. Mastodon acted the same when Hubzilla sent Article-type objects. It doesn't seem to make much sense to hide the title and the link behind a content warning. Also, I guess the Mastodon devs were aware that whatever sends Article-type objects does not treat the summary as a content warning because only microblogging projects do.