I think it is a bad idea for instance admins (fediverse) to ban entire instances. Unless there is a very very very serious motive behind it. And make it public when you do. Because this will cut ties with those instances and the users from your own instance will be unable to reach anyone from those banned instances. This is a dangerous game that many on the fediverse are playing. They seem to not grasp the consequences.
If we ever ban any instance then we will first announce it to all of our users, and then make it public. But unless there is severe spam flooding our servers, I do not see a reason to do that.
Users can block other users and for some federated networks they can block entire instances. Let the users decide! Not a handful of "admins". #tromlive
If we ever ban any instance then we will first announce it to all of our users, and then make it public. But unless there is severe spam flooding our servers, I do not see a reason to do that.
Users can block other users and for some federated networks they can block entire instances. Let the users decide! Not a handful of "admins". #tromlive
6 people like this
6 people reshared this
Jeena
•Tio
Rokosun
•That's much better than how its on mastodon π
@jeena
Jeena
•What I tried to say was that it's easier for an admin because they don't have a discovery page which shows stuff from other instances, therefor no real need to block instances nor to follow instances as an admin.
But if you're not admin and the admin blocks stuff it's not nice. At least you can move to a different instance.
Rokosun
•BTW, mastodon has global timeline instead of the discovery page on peertube, so don't they both have this issue ?
@tio
Jeena
•Jeena
•Rokosun
•@tio
Tio
Rokosun likes this.
Tio
:debian: πππππ :fedora:
•Rokosun
•@tio
Mastodon
Mastodon hosted on mastodon.socialTio likes this.
Tio
Tio
LPS likes this.
LPS
•@futureisfoss@selea
Rokosun
•@tio@selea
Rokosun
•Tio likes this.