Yeah, it’s a bit of a conundrum. Lemmygrad is the most egregious part of it and easy to block thankfully.
But I agree with some of the other posters that lemmy.ml is still pretty bad in terms of what gets allowed and who gets modetated. Luckily, this still is not an unsolvable problem in a federated world. Of course lemmy.ml could also just be blocked, but many instances will probably be reluctant to do that, as it also hosts some of the bigger communities currently. But we can make an effort to prioritize non lemmy.ml communities over their counterpart, a different meme community over memes@lemmy.ml etc, and if consensus is strong enough and enough communities shift, lemmy.ml could theoretically find itself in a position where it will have to clean up their moderation practices or risk wider defederation.

No, the API isn’t ready yet. But that isn’t stopping some people
https://tech.lgbt/@hariette/110545151572492176

How does installing packages or configuring software work, if system files can’t be changed?

On reboot. You install your changes into a separate part of the filesystem that’s not running and then “switch parts” on next boot. Different distros do this differently. Vanilla OS has an AB system which basically works like Android does it, openSUSE uses btrfs snapshots and Fedora also uses btrfs I think but they got a more complex layering system on top.

I get that there’s a security benefit just in that malware can’t change system files – but that is achieved by proper permission management on traditional systems too.

Is it though? All it takes is a misconfiguration or exploit to bypass it, so having several layers of protection isn’t a bad thing and how any reasonably secure system works. And having parts of your system predetermined as read only is a comparably tough nut to crack.

Instead you left people who trusted you dangling, only sporadically feeding them promises you would never fulfill.

Now, you see, this is the part that I as an uninvolved observer who’s just now catching up on the happenings do not get. Promises that were never fullfilled?
How long has or hasn’t this actually been an issue? Because from what I can see looking at the codeberg commits, it seems like development stalled for how long, like a month or so?

I totally get not wanting to be left hanging and having some answers and pathway for how contributions can happen. But as you also agree on, I also get real life being more important and getting in the way sometimes. And in that sense, being out of it for a month or so does not exactly seem like an earth-shattering amount, even if it’s annoying when it happens to be the project lead and not much can happen.

I just can’t help but feel like all of this has been pretty impatient and premature, which also makes it hard for me to really understand the point of the fork, even if I can relate to the basic rationale behind it. But then again, I have no knowledge of the direct going ons and communications between the contributors and the events that led to this. So there might be a lot I’m just not getting.

Also, I’m not really sure what I’m supposed to take away from the whole 66/33 thing. Are SUSE or Canonical handling it notably differently? If they’ve concluded spending lots on PR will get them lots of costumers, making a shitton of money with 1/3 going to devs still might lead to more contributions than making a little ton of money with most going to devs.

Hobestly, I can respect that. They seem to be fairly open about the motivations of that decision and who it’s targeted it without devolving into vague fluffy corporate speech too much. You can sense the author was a bit pissed by the reactions.
And I do agree that many of the reactions to the news seemed overblown and I think the actions make sense from their point of view without being super shady, even if it still has some negative repercussions for the open source world as well.

Merge in what way? In terms of user interaction, they already are merged. Lemmy users can comment and make threads in kbin communities and vice versa.

And in terms of underlying codebase, there isn’t anything to merge. Lemmy and kbin are written in two very different programming languages. Trying to unify them would mean huge amounts of effort for no tangible gain.

I’d still rather see RedHat as one of the biggest kernel/linux contributors make that extra money than fucking Oracle, Amazon etc.

Also:

They sell ads first, IT second.

They sell ads? Source?

RedHat is probably the biggest Linux contributor across the whole ecosystem (for the kernel alone, only companies like Intel, Google or Huawei are sometimes bigger) and the average Linux Desktop user/hobbyist isn’t even their target demographic, so what money to possibly not throw at them are you even talking about? Are you currently paying money for a RedHat subscription?

Also spending money on marketing/ads isn’t the same as selling ads.

“I don’t really have anything to hide, but you never know whether the government might act authoritarian at some point. So best to be safe and use privacy tools.”

French police: “Hold my tear gas”