This branch currently adds support for a content advisory (or something). It can submit statuses with content warnings and addresses #69 (closed) . Mastofe current respects them and pleroma-fe displays them like they normally are.
There are a few things that need to happen though:
One kind of weird thing I noticed is that pleroma stores summaries, but mastofe/common API expects spoiler_text. If need be, I can change the frontend code to talk about summaries for consistency, but I think this will then require a change to pleroma to handle that translation in Common API.
Is it abusing the twitter API that I added this extra form field? I wasn't sure how else to do it.