I use Jerboa and have already blocked the @lemmy.ml instance. There were calls to make that a thing with lent itself but I don’t think it ever happened.
There were also suggestions to do more of the defederstions in a “soft” way, by means of adding the instance to the block list of any user on the instance that wants to defederate it. Reversible by any user that wants full access with their main user.
From what little I understand about how Lemmy works and what the goals of the Fediverse are, this sounded like a much better way to do things.
Lemmy’s options for blocking and restricting are too limited, and it’s also a bummer there’s not an option for providing a reason for a block or restriction in the federated instances view. I think it all ties into Lemmy’s issue with “moderating tools are not an emphasis”
I used to be hopeful for Lemmy.world. that time has passed me by. Now they’re in the good riddance pile with sh.itjust.works. I’ve come to respect the beehaw admins the more time passes and the more it becomes obvious that was the move. Those instances don’t take moderation serious, and as a result they’re festering danger zones. You get a lot of good takes from Lemmy.world and sh.itjust.works users who don’t realize instance choice says something about you, but the overall tone of those two instances and Lemm.ee is not an overall tone I’m interested in experiencing as my general instances
If you make the platform, you can influence it through design decisions. It’s far more subtle than what spez did, but it’s still an effective method of control.
![[Transphobia Warning] Nutomic’s Stance on Transgender People](https://lemmy.ca/pictrs/image/e65d59a4-e335-42e1-88e3-f30708116c5b.jpeg){kind=link}
Lemmy lead dev
Too bad the LW admins are too busy sucking off the .ml admins to defederate from them.
I use Jerboa and have already blocked the @lemmy.ml instance. There were calls to make that a thing with lent itself but I don’t think it ever happened.
There were also suggestions to do more of the defederstions in a “soft” way, by means of adding the instance to the block list of any user on the instance that wants to defederate it. Reversible by any user that wants full access with their main user.
From what little I understand about how Lemmy works and what the goals of the Fediverse are, this sounded like a much better way to do things.
Lemmy’s options for blocking and restricting are too limited, and it’s also a bummer there’s not an option for providing a reason for a block or restriction in the federated instances view. I think it all ties into Lemmy’s issue with “moderating tools are not an emphasis”
I used to be hopeful for Lemmy.world. that time has passed me by. Now they’re in the good riddance pile with sh.itjust.works. I’ve come to respect the beehaw admins the more time passes and the more it becomes obvious that was the move. Those instances don’t take moderation serious, and as a result they’re festering danger zones. You get a lot of good takes from Lemmy.world and sh.itjust.works users who don’t realize instance choice says something about you, but the overall tone of those two instances and Lemm.ee is not an overall tone I’m interested in experiencing as my general instances
I’m sorry if I misunderstand, but are you saying a good instance heavily engages in tone policing?
If I’m not misunderstanding, I hope you realize that would imply you only want to ever read a word from like the gentlest 2‰ of humanity.
Is it a pre-requisite to be a smug douche if you’re going to run a social media platform now?
Man… I miss Tom.
He develops it, doesn’t run it
If you make the platform, you can influence it through design decisions. It’s far more subtle than what spez did, but it’s still an effective method of control.
If they do, it gets called out, like the slur filter from a while ago
Forks can and will exist though, so it’s not all bad
I’m looking forward to mbin, Sublinks, and piefed being primetime ready