ulhar4409right now i'm thinking of putting any CWs in the Summary field, in the hopes that feed readers prioritize that before showing the Content, but i'm not sure if that's appropriate or not
gRegorulhar4409, personally I'd avoid that further misuse of the summary element, though I know it might be a lost cause with Mastodon's use like that
gRegorperhaps for sensitive posts you could only include the intro and content warning, then they click through to the original to read the whole thing
[tantek]Mastodon is overloading "summary" in ActivityStreams which is quite different from RSS. Based on the poor experience with interop there, and RSS implementations are a lot better established, so I suspect that such overloading in RSS will look broken
Loqicontent warning is a feature of a post create UI where an author can hide some or all of the primary content of a post due to concerns about negative impacts of the content upon viewers, and typically provide a text warning (eponymously named) with the nature of the concerns, which is initially displayed instead of the post content https://indieweb.org/cw
ulhar4409now i'm randomly wondering if anyone's made a service/system to translate Mastodon api calls into Micro[ps]ub calls... the end result being that any Mastodon client could potentially be used as a Micro[ps]ub client
[aciccarello]Yeah, that's an interesting idea. There would probably be some gaps in supported features but would be cool to see the base functionality working.