Hopefully the custom elements / shadow DOM specs will improve, though, because it's useful to have a standard around these things. E.g. some folks really prefer to stick to a standard rather than a framework which may change in 6 months. That's the other valid use case I see.
It's interesting news that JSON.parse no longer throws a stack overflow exception in V8 when the JSON is too deeply recursive: https://v8.dev/blog/v8-release-76
Keys to Accessible Web Typography: 1. base font size in relative units 2. colour & contrast 3. Legible fonts with "Milimeter" test (I also use the a1iIlL0o test) 4. paragraphs shapes, line length and line height 5. semantics & heading levels for hiearchy
I'm afraid that a moderation API alone would not be enough of a measure against spammers. It presumes that automod applications will be developed, that admins will know about them, and that admins will set them up. Which would require self-hosting because automod-as-a-service would have awful privacy implications.
That's a shame though because experimentation over a moderation API would be more effective than a centrally designed upstream solution.
@v0idifier I dunno. I realize there's an API, and originally I supported it, but given the recent spambot wave I'm starting to wonder. Maybe the API itself could include the question/answer.
Long-term I would love to see Mastodon include some kind of variation on the captchas described here: https://kevv.net/you-probably-dont-need-recaptcha/. I.e. individual admins could configure a custom question like "what color is the sky" or maybe a community-specific question like "speak friend and enter."
Assuming every instance chooses a different question and they're not too obvious, it would at least make it harder to build spambots that mass-register on different instances.
It seems toot.cafe has been mercifully free of the recent spambot wave. (As in, they haven't made any accounts here.) Is it only happening on instances with open registration? toot.cafe is closed but has an open invite link instead; a pretty blunt anti-spam tool, but perhaps it's working. #MastoAdmins
I just want to thank all the mods at mastodon.technology (@bclindner@danielhglus@fuzzface) for their work handling reports on the instance, and especially this week with the wave of spam we're seeing on the fediverse.
An extra-special thanks to @bclindner for building tools to automate moderator responses to these spammers, and for open-sourcing those tools to help other admins: https://github.com/bclindner/ivory/