I've seen the raw HTML for some #piefed post content showing in the spoilerText field on some platforms via the mastodon api, including #gotosocial, #neodb (takahe/incarnator) and I think #pleroma. My current kludge is to check the spoilerText for html tags (specifically, a beginning <p>).
Discussion
Loading...
@fedicat Ooo, that doesn't sound ideal. Mastodon doesn't have that problem, does it?
Any opinions on which platform needs to change what?
(I'm the lead PieFed developer)
@rimu it’s fine on mastodon but has varying results on all the other mastodon api platforms I tried, attached are screenshots from my app on gotosocial, neodb, pleroma, and sharkey, but I duplicated with plfe and phanpy before. In the screenshots I’m truncating the spoilers and running them through an html converter but gotosocial seems to turn it into plain text and also sets the sensitive flag. But I notice posts in the last week look OK, maybe something changed?
4 media
@fedicat No, nothing changed at our end.
In AP, the 'summary' field has different meanings depending on the type of the Activity. For a Note, it's a content warning. But for all other types, it's just a summary in the more usual sense.
https://github.com/mastodon/mastodon/issues/8609
I think.
Still, I had a dig through the PieFed code and found a place where a summary is being added to a Page activity. This is of no use to PieFed and could possibly be 'confusing' other systems so I've removed it.
Thanks!
@rimu oh cool, that's interesting to know!
