This is a big problem. It creates the illusion that /c/cats on one particular instance is the real /c/cats.
This is the root of re-centralization and it must be pulled out.
This is a big problem. It creates the illusion that /c/cats on one particular instance is the real /c/cats.
This is the root of re-centralization and it must be pulled out.
Stop saying “it doesn’t matter”. Like right now, a member of lemmy.world who was participating in an instance on beehaw.org would vehemently disagree that it doesn’t matter what instance one is on.
And besides that, instances disagree on moderation/culture, so the same community on different instances can be very different on 2 servers, that will stay even after a “winner” community emerges.
+1 The provider you choose has complete control of your account. You only have access when their server is up. They control updates.
If they don’t have good backups you could lose everything. It may be unpopular but I think most would be wise to pick one of the already established major instances.
I actually think it’s best to host it yourself, which is what I plan to do after 0.18 releases ;) But obviously that neither scales nor is something the majority is interested in ;)
My current main instance was picked because they a) were not one of the biggest, but b) still seemed competent (they host a lot of different federated services)
There is no ‘real’ cats. That’s part of the point.
I think this is incorrect - federation depends on a “true” version. A community is tied to an instance, that’s where the true version is. When you’re logged into another instance and you comment in that community, your comment gets copied to the true version, as do comments from other federated instances, and all of them get copied from the true version to a version on yours.
When one instance defederates with another, that copying stops happening. If a copy of that thread is still on your instance, and you comment on it, your comment won’t get copied to the true version, so it also won’t get copied to other instances; only users on your instance will see it.
That’s my understanding, but I’ve only been here a few weeks.
That is essentially what happens and it’s a technical issue, not a philosophical one. If one instance is denied posting to another, the user should be notified at some point about that. There are a lot of silent errors right now with the setup. If you disable signups for example, users can still try but never see that it will never work.
there are alive cats and dead cats at the same time.
However, that also adds confusion for someone trying to figure out whether or not to use the service in the first place.
So they need to choose an instance. How do they pick an instance? There’s all this talk about defederation and all of that, so do they need to do a bunch of research to figure out who is where, to register? Oh wait, one of the big instances aren’t taking signups, and another is restricted, based on application.
That’s a lot of legwork for someone who is used to being able to go to “lemmy.social.network”, register, and just go. You don’t have to research Twitter or Reddit ahead of time, to figure out if you ended up in a server-region that was locked out from the others with seemingly no explanation or warning, or suddenly lose access because of some kind of operator issue with some other server.
Yes. The UX of Lemmy is currently extremely early adopter state. kBin is early alpha, Lemmy is probably late-alpha. Neither are close to any state where they could get mainstream adoption. Part of that is inherent to federation, part of it is simply how early the projects are.
There’s not even a consensus what lemmy is yet, two big opposite camps are “federation is a bonus, but essentially every instance is for themselves”, the other extreme is like OP “any instance that blocks another is not part of the fediverse any more”.
Beehaw is not federated, it functionally has ceased to exist.
There will not be a winner instance.
If all of the Lemmy federation cannot be read from any random instance, then it already is a failed experiment.
Not 1% of1% of1% of 1% cares what the instance name is or what their rules are. I am probably still missing many orders of magnitude.
The beehaw controversy is obvious. You don’t need to know the specific. I don’t know them and I don’t care about them nor what their story is.
The lesson is clear, tyrannical instance owners exists, and they will leverage your participation against you and cut your relationship.
There exists poisonous instances on Lemmy and they must be disempowered. Instances must be nothing more than portals to the whole. They must have no power.
Beehaw is defederated from two major popular instances and in talks with the admins of those instances about the path for refederation. I’m looking at this post from beehaw. You are taking an event, recasting it as something it isn’t, and trying to use that as evidence of a point. And in fact, you seem to be suggesting that instances that aren’t moderated how you want should be defederated. Which. Yes. That’s. That’s the point. That’s what Beehaw did. And they’re even communicating about how to move forwars
Dude, it’s obvious you don’t understand how lemmy or the fediverse works. You need to read more and maybe ask questions to clear up your misunderstanding before you go around making grand pronouncements about how lemmy should be run. A little bit of humility goes a long way.
Utter bullshit.
https://beehaw.org/instances
You can scroll to the bottom and see it’s only defederated from a handful of instances.
Furthermore these is no fucking Lemmy federation. Lemmy is one part of accessing the Fediverse. Ironic that someone worried one instance might get all the credit has no problem giving it all to one platform.
Honestly I’m not far off thinking removing any Lemmy instance at all is the best bet, Lemtards are getting annoying.
Oh, you are one of those people who know everything better than everyone else. You should have started with that.
Beehaw just defederated to get things under control, for the sake of their users.