Probably a good time to mention that the next version of Mastodon will finally make account suspensions reversible (with a separate option to delete data when needed). Been working on that for a few weeks (among other things)
I knew this reminded me of something, I looked it up and similar things have happened to at least one podcast app in the past. Eventually Google admitted there was no violation but only after the story gained publicity.
I was notified that @tateisu's Mastodon app "Subway Tooter" has received a warning from the Google Play Store citing user-generated content that "incites discrimination".
A Mastodon app does not host or promote any content. The user types the address to connect to. The responsibility of moderating resides with that server. So unless Google is going to drop Chrome, Firefox and Opera from its platform, this is completely out of line.
MDN doesn't say this, do Access-Control-Allow-Methods and Access-Control-Allow-Headers have defaults if you don't return those headers? I.e. would it be sufficient to just have Access-Control-Allow-Origin for static files to be served?
Sometimes I think what could I have done differently to make better use of the opportunities given by Mastodon being in the spotlight in the past. Like I imagine if Mastodon as it is in 3.2.0 was available during April 2017, a lot more people who checked it out would have stayed permanently, probably. It’s kind of frustrating to think about, really.