RE: https://wspanialy.eu/@PanNindyk/116786116739369324
It works! But seems not federated 🤔📩
Hat tip to @LukaszHorodecki @PanNindyk
*emerges from Brandity Brand™®️ cocoon*
I roleplay a space sorceress in the #MastoDev hashtag now
I don't usually encourage linking to Phanpy (it's not supposed to be a shareable permalink) but here's a preview of @stefan 's collections https://dev.phanpy.social/#/stefanbohacek.online/a/109694346929844617/c (should work when not logged in too).
The CSS workaround to replace the 'Hide' text with '⛛' in the top right corner of media, didn't work anymore. This is especially important for languages with a longer translation of that word, like 'Ausblenden'. I had to hack the code to make it work again.
I can make a pull request upstream, but it will probably not be accepted I'm afraid. Here is the related issue: https://github.com/mastodon/mastodon/issues/32341
This is only for the web-app. You have to refresh your browser tab to see it.
For those using masto.js 💁♂️ https://github.com/neet/masto.js/issues/1424
We need reply controls in mainline masto like yesterday. Of course technically its always possible for people on a malicious instance to evade them, but that is not a counterargument to having them work on the overwhelming majority of well behaved instances where the people we actually talk to are.
We already have the mechanism in mainline masto: reply collection enumeration - if person on instance A receives a malicious reply from person on instance B that is propagated to instance C, when instance C displays the thread, it refreshes the replies collection, sees a tombstone for the malicious reply, and does not display it in the thread.
We already have notification filters and a whole ui built for that. Reply controls could just be another tab on the same menu with the same controls.
You can't stop people from posting whatever, but you should be able to control whether someone uses your posts as a platform to harass you and the people around you.