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:
Well the devs aren't known for pausing anything to deal with objections or concerns ... so, screw the privacy rights violations for users and legal problems for admins!
@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.
@MastodonEngineering honestly don't see how killing off relay.fedi.buzz is an improvement....🤦🏻♂️killing usability of your platform for small #instance#mastoadmin.....yikes.
@MastodonEngineering
One improvement I think would be good for better automated post deletion on #mastodon is the exception on reply posts and replied posts so we don't unilaterally break conversations. Currently the exceptions based on interaction are only for favourited and boosted posts.
@MastodonEngineering This release will break relay.fedi.buzz, a great service by @astro. It worsens UX for Users on smaller instances, defeating the purpose of federation by making it less attractive.
I was so happy when you announced that there would be a separate account for posting developer news that ordinary followers of the @Mastodon would not need to know. But then what is the point, @Mastodon, if you then just boost the posts only server admins need to know about?
Any way, as always, thanks to all the folks dedicated to improving Mastodon!!!
@MastodonEngineering no one is talking about how there is no actual features added. Badges aren’t a thing people want. People want actual new things into mastodon, a better way to talk to other servers, better ways to not missclick when using mobile phones because you guys put the sidebar on the right side, etc. NEW FEATURES.
Breaking relay.fedi.buzz - particularly with ZERO notice - is a crushing negative for hashtag games and follows on small instances. Ad hoc group activities like monsterdon and tcmparty and hashtaggames itself are largely possible on small instances because of hashtag relay services like fedi.buzz, and whole-instance relaying is not a solution for us.
(Imagine small instances trying to relay all of mastodon.social, come on. No.)
It’s also prohibitive against other uses on small instances like emergency tracking. If you want to try to do that, you’d better be on a big instance like mastodon.social.
This is a massive kneecapping and it’s going out without consideration or notice.
@moira@MastodonEngineering Oh no, that sucks! 😨
I recommended fedi.buzz in my guide to Mastodon, especially for niche creators and people on smaller instances.
I'm assuming it's a measure against crawling?
But yeah, it makes things much harder for creatives, it's breaking up small communities, it's making small instances much less able to participate in the ways I described. (Unless and until fedi.buzz implements around it, of course, which they could do various ways and pretty certainly will. And those ways aren't better.)
I have suggested that it should be left up until there is a replacement tool for this critical small-instance functionality, but I kind of doubt they're going to do that. I also suggested only exposing posts with hashtags, as hashtagged posts are clearly intended to be discovered, and this is discovery. So.
Add comment