Will lemmy.world be defederating from beehaw.org now? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by DudePluto@lemmy.world to c/lemmyworld@lemmy.world

44 comments fedilink hide all child comments

First of all, let me say that while the admins can do what they want, I think it's pretty unfortunate that beehaw is defederating from .world and shitjustworks. I don't want to see the fediverse fracture, I want it to encourage conversation with others.

But, beehaw has done what they've done. And I must say it's annoying to be able to see their posts and comments and not engage with them. Plus, I could see their large, still visible communities taking away from ours without people realizing their own posts and comments aren't working.

So will .world be defederating from beehaw? I don't have a horse in the race, I'm jw

you are viewing a single comment's thread
view the rest of the comments

[-] howdy@thesimplecorner.org 25 points 1 year ago

Yeah one way federation while still providing content doesn't feel too good. Defederate would make sense. Purge Beehaws content from the database (admins can do that directly with the postgres I assume). If they decide to open up in the future then just refederate. Will be all good. Beehaw is trying to have a specific style of community so they are doing what is best for them. That's the flexibility of this framework.

[-] DocMcStuffin@lemmy.world 29 points 1 year ago

We're seeing the pains of the sudden and quick growth in lemmy from rexxitors (which I am one). It's exposing the current limitations of the software. Basically defederation between 2 instances should be more transparent. Like it should be a banner on the local instance when you're in one of their communities or posts. I only found out from a post in another community.

I personally am not going to get bent out of shape about it. New communities can pop up to take their place. Better mod tools can be developed to help. The lemmy software will improve over time.

[-] sethboy66@kbin.social 4 points 1 year ago* (last edited 1 year ago)

It's not really a limitation of the software, it's all up to each instance to decided how they handle things. Instance admins can code in a banner as you describe and they can make defederation transparent such as how Beehaw lists all linked and blocked instances. Every instance can do this, they just have to choose to implement it.

[-] DocMcStuffin@lemmy.world 5 points 1 year ago

Beehaw didn't come up with /instances. That's builtin to all Lemmy instance. It's part of the Lemmy source code. Designed, written, and tested by the Lemmy devs. It's part of their design for transparency.

Instance operators aren't software engineers. I have no doubt some are, and I have no doubt most are not. I also doubt that most are familiar with rust, typescript, postgres in addition to the Lemmy API along with ActivityPub. I'm sure the average admin can "code in" a banner involving some or all of that just like the average person can rebuild an engine, install custom shocks, and weld together a roll cage. But let's say they do "code in" a banner that only displays itself depending on federation status. Now they have a separate patch set that has to be maintained and tested with each update to Lemmy. And published too because Lemmy is licensed under the AGPL.

So yes, this very much is a limitation of the software. The user should be informed, "you can't comment or interact with this other instance." Was this an oversight of the devs? I would say no. As a software engineer there are some things you don't even think of as problems until they pop up as problems. It's part of the engineering process and evolution of a code base.

And my intention from this long winded comment isn't to rip your head off. Even if I come off like that sometimes 🙃. It's me speaking from my knowledge and experience as an engineer.

[-] jcg@halubilo.social 3 points 1 year ago* (last edited 1 year ago)

To be fair, setting up an instance with your own patch is how improvements are made in the first place. Only a day after I set up my own instance, I forked the repo and started tinkering. Same case with lemm.ee. I'm a software engineer by profession but this is the first time I've touched Rust and inferno (I use typescript but with React/NextJS, inferno is new to me and pretty interesting). What's funny to me is that lemmynsfw.com was the first highly populated instance I saw which is actually running their own patch. But hey, porn has always had a heavy hand in driving tech. Half of the best features of YT were ripped right out of PornHub.

Mind you, while lemmy-ui will probably be easy to pick up for most frontend devs working with a modern tech stack, I'm sure the main Lemmy repo will drive a lot of devs away just because it's in Rust. But I can see why it's like that. Lemmy is barely a blip in terms of CPU and RAM. The big factor for most instances is really just going to be storage space.

[-] DocMcStuffin@lemmy.world 2 points 1 year ago

That's true. This is one of those things where they would probably accept a pull request. Assuming it's just a ui fix.

Someone already opened an issue on it.

[-] howdy@thesimplecorner.org 3 points 1 year ago

Yup. I saw the announcement post when it came out. Agreed, literally no reason to get mad. Always another server to jump on. Again, that's a perk.

[-] wabafee@lemmy.world 15 points 1 year ago

To be fair I don't mind that .world should just keep federate it may be one way but content is content some people just lurk anyway. Its probably what makes .world attractive aside from no requirement in registration.

[-] howdy@thesimplecorner.org 3 points 1 year ago

It is an interesting conundrum. I feel it's a catch 22. Some people will be upset, some won't.

[-] Action_Bastid@lemmy.world 20 points 1 year ago

I think someone else hit it on the head with the suggestion that there should be some sort of warning that the community is essentially view only and cannot be interacted with. If it has that, then everything should be good.

[-] FaceDeer@kbin.social 10 points 1 year ago

Maybe a solution would be a user preference, "hide content from defederated instances". I know I would be very annoyed to keep seeing threads that I couldn't post in, the whole point of a site like this for me is user interaction.