The first beta of #Mastodon 4.2.0 is now available for testing! There are too many improvements to count. See the extensive changelog and upgrade instructions here:

https://github.com/mastodon/mastodon/releases/tag/v4.2.0-beta1

Release v4.2.0-beta1 路 mastodon/mastodon

鈿狅笍 This is a beta release! This is primarily aimed at server administrators who are willing to report issues, and may be less reliable than stable releases, although it is still tested on mastodon....

GitHub

@MastodonEngineering

Coming soon in #Mastodon v4.2.0:

馃憖 3rd-party JavaScript spyware loaded without users' consent.

#MastoAdmin #privacy #SurveillanceCapitalism

https://github.com/mastodon/mastodon/pull/25019

Add optional hCaptcha support by ClearlyClaire 路 Pull Request #25019 路 mastodon/mastodon

Add optional hCaptcha support based on glitch-soc#1665 and glitch-soc#1667, largely rewriting prior work at glitch-soc#1323 Whenever the environment variables HCAPTCHA_SECRET_KEY and HCAPTCHA_SITE_...

GitHub
@downey @MastodonEngineering I said, they don't really care about us anymore.
@downey @MastodonEngineering but it's true we could argue about DeepL translation feature too, if we take this as we take it.
@gmate8 Somewhat. We use a self-hosted LibreTranslate but AFAIK content is only sent to the translation server when the user clicks the "Translate" link right? At least there is a bit of user autonomy there, as opposed to this new captcha that records PII automatically without warning or affirmative steps by users.
@downey @gmate8 Not really in my opinion, the user who write something is not the one who'll press the translate button, you can't control if and when someone will send your stuff to deepl.