5 ms·

>- allow communities to manage themselves in a decentralized manner, without any San Fransisco-based big-tech company imposing their CoC, ToS or view of "divers

>- allow communities to manage themselves in a decentralized manner, without any San Fransisco-based big-tech company imposing their CoC, ToS or view of "diversity" upon them. the main matrix homeserver blocks you from federating with them if you violate their CoC and kicks all matrix users from your room

dane-pgp 5y ago
What is the user experience like when that happens? If you use the main Matrix homeserver and you're in a room hosted on another server when this happens, does your client show a helpful message like: "Sorry, you're not allowed to be in this room any more, because the people hosting the room committed the following thoughtcrime: $REASON"? I worry that it will instead just look like some generic network error message, with the remote server being tacitly deemed an un-place full of unpersons. Down the memoryhole it goes.
- DoItToMe81 5y ago
  It gives you a generic error message and doesn't describe the block. And it happens quite frequently, whoever administrates the Matrix main homeserver is very ban happy.
Macha 5y ago
And so users can move to another homeserver with different standards, or run their own. This isn't possible if Discord or Skype or Telegram block your users.
scarygliders 5y ago
> the main matrix homeserver blocks you from federating with them if you violate their CoC and kicks all matrix users from your room In my opinion that doesn't really matter. matrix.org is "just another homeserver" - it just happens to be one with a large amount of Spaces and rooms, and thankfully federation doesn't orbit around matrix.org nor does it depend on that. There are plenty of other homeservers which federate with each other quite happily. I've seen some rooms which have a policy of not allowing users with a matrix.org account, because they disagree with the matrix.org CoC/policies/actions, and that's also fine, because the nature of the matrix protocol allows that freedom. If a person wishes to stick with matrix.org, well, they have that choice. If a person has a homeserver which gets booted from federating with matrix.org, that's also fine - the problem will eventually be routed around by federating with plenty of other homeservers. This happens already.

dane-pgp 5y ago

What is the user experience like when that happens? If you use the main Matrix homeserver and you're in a room hosted on another server when this happens, does your client show a helpful message like: "Sorry, you're not allowed to be in this room any more, because the people hosting the room committed the following thoughtcrime: $REASON"? I worry that it will instead just look like some generic network error message, with the remote server being tacitly deemed an un-place full of unpersons. Down the memoryhole it goes.

DoItToMe81 5y ago
It gives you a generic error message and doesn't describe the block. And it happens quite frequently, whoever administrates the Matrix main homeserver is very ban happy.

Macha 5y ago

And so users can move to another homeserver with different standards, or run their own. This isn't possible if Discord or Skype or Telegram block your users.

scarygliders 5y ago

> the main matrix homeserver blocks you from federating with them if you violate their CoC and kicks all matrix users from your room In my opinion that doesn't really matter. matrix.org is "just another homeserver" - it just happens to be one with a large amount of Spaces and rooms, and thankfully federation doesn't orbit around matrix.org nor does it depend on that. There are plenty of other homeservers which federate with each other quite happily. I've seen some rooms which have a policy of not allowing users with a matrix.org account, because they disagree with the matrix.org CoC/policies/actions, and that's also fine, because the nature of the matrix protocol allows that freedom. If a person wishes to stick with matrix.org, well, they have that choice. If a person has a homeserver which gets booted from federating with matrix.org, that's also fine - the problem will eventually be routed around by federating with plenty of other homeservers. This happens already.