The media in this post is not displayed to visitors. To view it, please go to the original post.

Yesterday, users of mstdn.social instance lost their connections to artists at mastodon.art instance ( src: framapiaf.org/@Curator@mastodo… ). I hope giving visibility to this issue will help them to restore the broken bridges.
in reply to :thonk:

@p Hehe, it's a sketch from 2019 and it's fun because I made my first real work of masonry last week, and if I had to redraw it, I would do it differently. Mortar paste can't be that sticky and solid. I was shocked to see how it was more like mud with sand in it, gluing nothing, and requiring casing for any volumes. So, I totally agree with your observations. 😺
in reply to ManicDee

@manicdee They are different, but I also mixed up the two instances at first so I think many will have the same feeling. Their naming really overlaps too much; it just sounds like one is the URL shortening of the second... I could disambiguate the two by their number of active users mainly:

- mstdn.social/explore (31K active users)

- mastodon.social/explore (220K active users)

in reply to David Revoy

to be honest, I think it is not ok to fully blocked an instance, since this is anti-fediverse. @Mastodon should remove “block a server” function, as this gives the admin the superpower over what the users on their server can see and interact. Simply silence a server from appearing in one server’s public timeline should be the ultimate solution. Every user/ resident in one server should have the freedom to choose what they can see.
in reply to Henry

@Henry there are instances that really everybody wants to block at a server level, because they aren't sending any kind of useful message but just plain, uncontroversially, spam.

Our instance only has less than 10 active users and no open registration, so we can afford do be very permissive, and we still have a blocklist that is mostly filled with those.

Then there are instances that have been created with the explicit intent to host people accounts dedicated to harass other people: one may prefer a place where these are blocked in advance or one where blocks only happen after the fact, but while under active attack you don't really want every user on a server to suffer from them either.

And then there is simply the fact that some user will want to manage their own block list, but others are much more happy knowing that an admin *they trust* has done most of the work.

The point is that the fediverse gives you the choice to be on a server where you trust the admin and like their policies, removing instance blocks from everybody (or enforcing them for everybody, if it was technically possible) would make it worse, not better.

Questo sito utilizza cookie per riconosce gli utenti loggati e quelli che tornano a visitare. Proseguendo la navigazione su questo sito, accetti l'utilizzo di questi cookie.