• 1 Post
  • 35 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle
  • 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.










  • 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.




  • Not really. The real life thing is carefully guided process with serious obligations in which the professionally trained and educated judge is still the main arbiter. The jury is segmented to a very specific part of the process with a clear protocol for a reason.

    What you’re asking for is giving every Xth rando a police badge because law enforcement is understaffed.




  • 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.