esoteric_programmer@social.stealthy.club respectfully there is no other way to get an Article object ingested by Mastodon without being munged without shoving it all into summary.

Summary should contain a truncation probably, but other than that it's GtS that is "doing it wrong".

@julian if we weren't constrained by what mastodon does or it implemented the article activity type properly, would this still be done the same way? yeah, I suppose technically gts is wrong for not implementing the mastodon behaviour as well because it's nonstandard, same as they mandate authorised fetch like functionality for everything that federates with gts, but yet they support some other nonstandard things themselves, which exist only because mastodon does it this way, so they're kinda inconsistent there. I wish more servers would implement the client-server part of the activity pub protocol for example, but that too is blocked because everyone making clients for the fedi targets the mastodon API from what I know, so yeah, sad indeed.
Btw, other threadiverse platforms, like lemmy and py-fed, don't have this issue on my end, where I could follow them because they support authorised fetch that is. I wonder how do they do it? or...hmm, maybe they don't work properly on mastodon while they do on gts?

esoteric_programmer@social.stealthy.club I'm sorry I got a bit salty about it.

Basically if Mastodon were not in the equation we would send an Article with a name and no summary at all. Threadiverse implementations handle that perfectly already.

GtS actually did implement the Mastodon behaviour! Content warnings were their thing (afaik), done by adopting summary as the CW. GtS followed suit but applied this to all objects, not just notes. So in this case GtS went a bit further is all.

@julian ahh, gotcha. And what would happen now if you didn't include summary at all?

esoteric_programmer@social.stealthy.club Mastodon would show the title and URL, and the content would be excised out.

Which I suppose is so fine insofar that sometimes long form content is best read on the originating site, but end users want their content read natively on Mastodon

@julian and gts would do the same, right?

esoteric_programmer@social.stealthy.club actually I'm not sure how GtS would handle it!

@julian So in other words, if an Article-type object has a summary, Mastodon discards the title, shows the summary and links to the original, and if it doesn't have a summary, Mastodon shows the title and links to the original?

Its "traditional" behaviour since ca. 2017 was that it either showed the title and the link or, in the absence of a title, only the link with zero context, and when there was a summary, it used the summary as a content warning.

I'm still not sure whether Mastodon is limited by all interfaces available for it only being geared towards old-school plain-text microblogging and incapable of handling fully formatted HTML content, or rather by the devs' stubborn unwillingness to let anything in that's too much not old-school plain-text microblogging.

@julian @esoteric_programmer It will probably display content without title.

jupiter_rowland@hub.netzgemeinde.eu Mastodon shows the title, summary, and adds a link.

It's as good as it'll get and quite a ways from where it used to be.