It's a mild pain and definitely not what we were promised, but I guess that's the only way federation can really work in practice (especially considering when an instance is blocked user on the blocker side just continue to see it frozen in time, with no warning as to what's going on)

[–] somethingchameleon@lemmy.ca 5 points 8 months ago (5 children)

I think a solution would be to have instances without communities.

It sucks, but I'm really trying to find instances with the most federation. I'd rather censor things myself than to have some useful idiot do it for me.

"Instance A blocked instance B, so now we have to use instance C to communicate with both." Seems kind of roundabout, which is why I'm looking for the 'ever-C' instance that federates with the most.

[–] Croquette@sh.itjust.works 2 points 8 months ago (1 children)

The issue is that depending on where the Instance is located can mean that the person is liable for the content on their instance, or at least some corps will try to take them to court over that.

It would be really nice to have something you've described, but then who hosts the community and becomes liable?

[–] somethingchameleon@lemmy.ca 0 points 8 months ago

Someone's always going to be liable, that's unavoidable.

I'm just spitballing ideas for how we can always connect to the servers we want to.

@Mic_Check_One_Two@reddthat.com hit the nail on the head. Self-hosting would be the end goal, but it's too much of a hassle for most people to go through.

So a few servers that exist solely to connect with the fediverse would be ideal for those people.

load more comments (3 replies)

load more comments (10 replies)