ROJER
Mastodon EngineeringThe 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
Senhor Schlauschlau 🪐
Evv1L 
@MastodonEngineering hehe nice number
El Stevo
Giovanni Crisalfi@MastodonEngineering line in threads! Lovely
tshepang@gicrisf @MastodonEngineering is this similar to #phanpy, where it is easy to see complex conversation flow
Arataka
El Duvelle@MastodonEngineering
Nice! Of those I understand I spotted some cool new features:
- “Add support for importing lists” !!!
- “Add lines to threads in web UI” I thought it already had that?
- “Add new onboarding flow to web UI”
- “Change reblogs to be excluded from "Posts and replies" tab in web UI” that would be nice
- “Change account search to match by text when opted-in” I wonder if that means full text instead of only hashtag search?? That would be big!Also:
- “Change 'favourite' to 'favorite' for American English “ oh no!
Michael Downey 🧢Coming soon in #Mastodon v4.2.0:
👀 3rd-party JavaScript spyware loaded without users' consent.
Nordnick 🌐@[email protected] @[email protected]
Looks like this is a privacy issue and it may not even be legal... right?
Looks like this is a privacy issue and it may not even be legal... right?
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!
KuJoe 💞@downey so this is required now? I thought the PR said optional? Why did this change?
lalalala sombra@downey @MastodonEngineering I thought hCaptcha was the good one. Disappointing.
Adblockers will always be a necessity.
Robin Syl 🌸
mirabilos@lasombra @downey @MastodonEngineering no, they (Cloudflare/hCaptcha) are really really bad. I contacted them on behalf of several blind #lynx users and they refused to even understand the problem.
🍉 max frühschütz – нет войне@downey @MastodonEngineering weird that they went for a proprietary solution instead of something like mosparo
GMate8@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 LibreTranslate's cool, wish it was available in hu
But even lingva could be an option somewhat
But even lingva could be an option somewhat
Zii0
Рой Клꙮунов
@aka_dude Users can't set that, but thanks for misrepresenting my comment.
This account is inactive!@downey @MastodonEngineering oh Jesus, is that real?! That sucks, but sadly that's true 😔
Opalium@downey @MastodonEngineering
I wonder: would informing or otherwise notifying the user that the sign up process includes a third-party captcha - before even signing up - be a reasonable compromise here? This way, they can choose a different instance should they wish to avoid the captcha.
I wonder: would informing or otherwise notifying the user that the sign up process includes a third-party captcha - before even signing up - be a reasonable compromise here? This way, they can choose a different instance should they wish to avoid the captcha.
@opalium Yes, consent is what was raised in May and ignored by the devs since then.
@downey @MastodonEngineering to add insult to injury, hCaptcha/Cloudflare actively refuse to support a11y, e.g. for lynx users. They ought to be boycotted, even if GDPR etc. weren’t an issue already.
@downey @MastodonEngineering not that it matters much for your instance, since
floss.social already violates the GDPR by illegally loading content from shields.io and masto.host without obtaining prior user consent…
waldi@downey My instance delivers right now: "content-security-policy: script-src 'self' https://chaos.social 'wasm-unsafe-eval'". This was not changed, visibly, in this commit. How does it load that 3rd-party stuff?
@MastodonEngineering what does this mean exactly? Do I need to make changes to my Streaming servers to make them work or do I need to drop down to one server?
"Drops built-in clustering support from the streaming server"
Chris ElyYay! Useful lists are closer:
- Add exclusive lists
- Add support for importing lists
- Add ability to include accounts with pending follow requests in lists
80columnsExclusive lists sounds like the feature I was missing! With that, I'll probably start using lists for real. Yay!
mem_somerville@MastodonEngineering I had a weird thing happen today and I can't get rid of it. At the top of my caturday column I have an offer to follow this hashtag. I don't want to follow it, I want it to just flow into this column.
But I can't get rid of the header thing.
Does anyone know how to remove it? Or should I report that somewhere?
Five Element Ninja@mem_somerville @MastodonEngineering As far as I can tell there's no option to remove it. However, I was able to remove them using uBlock Origin's element zapper. Now my columns are back to normal. If you use something like Tampermonkey or Stylish, you can target those headers via the class .hashtag-header. Not ideal, but it works.
Caroline Bell 
morph@MastodonEngineering Add Exclusive Lists 👍
Astro@MastodonEngineering 420 lets gooo
Andrew@MastodonEngineering omg that’s the weed number
nicki xaphania mouse 🐁
spv
Thaddaeus@MastodonEngineering Exclusive lists 😍
Ividapp Avidapp എല്ലായിടത്തും!@MastodonEngineering Dear Sir, Kindly provide push notification feature without depending on #Google play service for #degoogled phones 😌 #mastodon #fediverse
Agree
Unnecessary..It's working good
Poll ended at .
Solarbird 
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.
Erotic Mythology 🌹@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?
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?
@AimeeMaroux @MastodonEngineering They're calling it "scraping" which is... what they're calling it. >:/
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.
Wohao_Gaster 
@MastodonEngineering Haha funny number 420
Caleb@MastodonEngineering
Blaze your Glory!
Blaze your Glory!
joene 🏴@MastodonEngineering As also mentioned on GitHub:
- Please consider to change the text 'Live feeds' to 'Public timelines'. It much better describes where it's about and existing users will not complain about missing functionality. https://github.com/mastodon/mastodon/pull/25641#issuecomment-1670069276
- Please remove the new legal report category feature or at least give server owners the option to disable it. https://github.com/mastodon/mastodon/pull/23941#issuecomment-1670007258
Change local and federated timeline to be tabs of a single “Live feeds” column by ClearlyClaire · Pull Request #25641 · mastodon/mastodon
This: split /public/remote out of /public adds a new column to handle all routes under /public, with a tab selector to switch between Local/Remote/All merges the “Local” and “Federated” links in t...
YoYunix@MastodonEngineering oh nooooo......that again user's #privacy !
ElephantidaeI 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 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.
Seg@MastodonEngineering ahahah, alriiiiight