Spzi

can you imagine having to check 500+ servers to see the blocklist every single time someone adds a comment?

Defederation happens much less often than new comments are posted. The visibility information is also the same for all comments, posts and communities on one instance.

So the check would not have to happen in real time for each comment. It can probably be done once per hour/day for the whole instance as a low priority task.

I like the idea of a visibility indicator.

Yea, it’s going to be a problem if a lot of large instances start defederizing from each other. People aren’t going to want to have 4 different accounts to interact with communities they were contributing to before they defederized.

So instances with the policy to not defederate anybody (or other, clear and rather strictly open policies) become more attractive. Eventually, people who value open access will live on instances catered to that need.

The need for moving due to defederation or the need to have multiple accounts is only a thing during a transitional phase, I suppose.

The idea is that every instance is basically responsible for their own users.

It's correct what you say, but the idea bugs me the more I understand it.

It feels like guilt by association. The actual cause is the behaviour of specific, individual users but the repercussions are equally felt by other users from the same instance. These other users can have nothing in common with the causing users, or might have even opposed them in their wrongdoings.

There is also a level between users and instances; communities. Maybe the problem was with one specific community, yet all other communities who happen to live on the same instance feel the same consequences.

Defederating individual communities would feel better for me, but ultimately I think a problem caused by individuals should be solved with these individuals, not with groups which are more or less meaningfully associated with those individuals.

What interests me is that there is still a gaming@beehaw.org community on lemmy.world. Locals can post there, see new stuff, etc. It’s not “dead.” Maybe no alternative will rise because no one notices.

You could just as well create gaming@lemmy.world, to be able to interact with lemmys from other instances again.

After the moment of defederation, you will not get anything new in communities coming from beehaw except posts and comments made by users of your home instance.

So you can still see old posts and comments of beehaw users, but everything new will have to come from your home instance exclusively. You won't see new posts or comments made by users from beehaw or any other instance in communities originating from beehaw.

It's not exactly like that, but has similarities.

The differences are, you can still use lemmy as a platform while being completely isolated from a spez you don't like. Or choose to use an account in another instance which is federated to everything, or even both.

In a centralized system like reddit one group can decide for all others. Here, no one can decide for all others. That includes you cannot decide how others should or should not defederate.

Yes, I think that's what they tried to explain. If you do not unsubscribe from a community on an instance which has defederated your instance, you will only ever meet lemmys from your home instance in this community. This probably gets stale rather quickly, hence the recommendation to unsubscribe.

If you want to interact with lemmys from other instances, unsubscribe from communities from instances which defederated your instance.

Let me see if there’s a better way.

I'm also searching and gathering, let's share! Also tagging @Homo_Stupidus@lemmy.world

https://github.com/maltfield/awesome-lemmy-instances#all-lemmy-instances

3rd colum from the right (BI) shows the number of instances blocked from this instance. It does not tell you which instances are blocked specifically, but gives a rough idea with an overview.

https://lemmymap.feddit.de/

Bottom left you can check 'blocked' and see a visual graph of red defederations. This view becomes increasingly unusable as lemmy grows, and already takes some time to load.

All that being said, the main complaint I’ve noticed (and I think is valid and it often gets dismissed) - to sign up users are given a choice (which server to join), and to make an informed choice there’s a minimum of a few pages of required reading

It definitely matters, and the way you’re presented this choice is pretty overwhelming

I’m working on a Lemmy client, and my thought is this - break up the options. Give users a choice of 3-5 options with a “next” button and a search option.

I would even go further and allow a "don't care" option which randomly assigns new users to an instance with auto accept. Even make this the default.

Those who want can have the option to get into the details and make an individual decision.

I’d love a setting that would let me hide all posts that I’ve upvoted, or hide all posts that I’ve read (clicked). Also the ability to manually hide a post from the main list view (get rid of something without having to upvoted or click on/into).

Me too!

When you defederate a server you can’t see their users

What are the implications for triangle constellations? Instances A, B and C.

A defederates B. Users from both A and B submit comments in a post in a community on C.

Do users from A and B get different views of the comment section on C? Or can they still meet and engage with each other on this neutral ground?

Just adding for those who haven't found them yet:

• !Duolingo@lemmy.ml
• !Duolingo@lemmy.world