110
Update from Lemmy after the Reddit blackout
(join-lemmy.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Jun 2023
110 points (100.0% liked)
Technology
37705 readers
379 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Update 2: My conclusion
Update: So I dug around a little deeper, and found that
Update: More info about @dessalines@lemmy.ml
I don't agree with these views at all, but I don't agree with the view that no one should use lemmy because of the opinions of the developers. Its an open-source project, just don't use anything hosted by them. Like I don't support the US military, but that doesn't stop me from using the internet.
One sore point there is that the code comes by default with a donation link (the heart at the top) to join-lemmy.org. Even without the tankie issue it should rather go to a page local to the instance explaining donation options, and the default should be "The admin didn't set this up, if you urgently need to get rid of money here's a link to Doctors without Borders".
OTOH there's now a huge influx of people including tons of developers so I expect tankie influence to be drowned out sooner than later.
A bunch of developers isn't going to do anything though if they retain control over everything. I think after learning about this background, and their weird claims surrounding it yesterday, the path forward I would prefer is for a strong fork to emerge of the original code that instances deploy instead.
I prophesied that to happen back on reddit but with FLOSS development culture being as it is pre-emptive forking is kinda considered the same as a pre-emptive nuclear strike. It's just not done in polite company.
I'm about 100% that there's going to come a make-or break situation where, if the developers don't concede, there will be a fork, but it could also be that the devs are conscious enough of what's happening that they'll cave under the pressure and thus manage to retain some influence over the project.
Forking the project would beyond stupid, and to so blithely suggest it leads me to believe to you don't actually know much about that which you are discussing.