@devnull@article_interop@pfefferle it comes from a time when the network looked a lot different, but now that Mastodon caved into the demand of showing long posts and just adding a Show More button there really isn't any reason for them to not support articles...
@liaizon@article_interop@pfefferle my understanding is that if Mastodon doesn't recognize the type it just falls back to showing title and url, which is a sane default. Not everything is meant to be parsed like a note.
So I get their direction here, but the knock-on effect on other implementors is signalling that some additional thought is required here.
@devnull@article_interop@pfefferle I don't really care how its done personally, I just want to see it done because the way it is currently is super silly and quite frustrating for the actual user. I do not personally think the semantic difference between 'as:Note', 'as:Page' or 'as:Article' is the heart of the issue here. We just have to come to some active conclusion and make it happen...
@liaizon as you alluded to in your reply, WP gets around this by assuming type as:Note which I disagree with from a protocol fragmentation standpoint. It implicitly acknowledges Mastodon as the dominant #ActivityPub player with clout to change the behaviour of others, and I stand against it.
#nodebb will send type as:Page (like #lemmy and #kbin), and we will work with @article_interop (and hopefully @pfefferle) to encourage Mastodon to handle it properly by modelling the appropriate behaviour.
Has anyone patched either Mastodon or Lemmy so that Lemmy's posts display the whole article in your Mastodon feed yet? At this point it seems like it might be as "simple" as changing the post type from "article" to "note" since Mastodon is now able to display a good amount of formatting and stuff inline #fediverse#ActivityPub