• 0 Posts
  • 100 Comments
Joined 1 year ago
cake
Cake day: August 21st, 2023

help-circle
  • Why? I think there’s a decent chance they don’t survive this - at least their commercial airplanes. I won’t fly on a Boeing any time soon, if ever. It will take years to get back to a safety culture and there are tons of shit planes manufactured in the past several years that will be in service for decades.

    If I was a pilot, I wouldn’t want to fly one either. They just had another incident where a pilot says the gauges went blank and he lost control. If a pilot union starts pushing back, it’s game over.

    Would you fly on one of their planes?









  • Do what you feel you need to do. Beehaw was my first Lemmy instance, although I have since left. What I initially liked about it was that there was active moderation and the admins seemed to do a good job keeping things running. It was a chill place that didn’t really appeal to the more toxic types you run into on the internet. It was like a friendly little bubble and a good home base in the fediverse.

    While I appreciated that toxic instances were blocked, I felt blocking instances simply because they didn’t have great moderation was a little too much. It meant I was missing out on a lot of good content too. I understand the decision but I realized then that the original Beehaw community was more content to be insulated than I was. For a lot of people there, it was more important to have their own tight community than to be part of the fediverse. There’s no hard feelings about it. I enjoyed my time on Beehaw and contributed to server costs. I found another good instance that’s better federated and manages not to have a bunch of nazi and racist garbage so it’s all good.

    These conversations have been brewing for a while at Beehaw. I would imagine a lot of the people who don’t especially like the insulated approach have moved on to other instances or created alt accounts for when they want to interact with the larger fediverse.

    I don’t think anyone will miss anything if Beehaw migrates to a non-federated platform.


  • Not necessarily. You probably want to optimize the kernel and a few packages. Then there are some apps where you want to build them with specific features. Then there’s a bunch of stuff that takes forever to build where a binary would be convenient. Flags and optimizations aren’t that important for KDE frameworks or Firefox.

    Offering binaries is a really nice middle ground. Gentoo makes it so easy to build custom packages from source but it’s always been all or nothing. I don’t want to wait 2-3 hours building updated libraries or Firefox every time there’s a patch.

    Personally, I would be interested in a distro that had binary packages, easy builds like Gentoo and something like Arch’s AUR.





  • Yeah, it works fine. You might want to tinker with the packages as others have suggested but it’s exactly what you expect from Fedora. The only difference is it’s Plasma instead of GNOME.

    I had the same experience with GNOME on the family computer. I had to add extensions to make it more accessible. Then when they auto update you get dumped into vanilla GNOME until you log out and back in to re-enable extensions. I would get called over every time that happened. I switched it to Plasma and everyone is happy.

    One thing worth pointing out is the dash to dock/panel, just perfection and appindicator GNOME extensions are all in the Fedora repository. When you install them from there, you don’t get that janky behavior during updates where you have to re-enable them. Those extensions go a long way towards making GNOME more accessible to users coming from Windows or Mac. Default GNOME is great if you use keyboard shortcuts but it’s not very intuitive when you’re starting out.


  • Joker@discuss.tchncs.detoLinux@lemmy.mlFlatpack, appimage, snaps..
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    8 months ago

    It’s been that way since the dawn of computing. Developers will push hardware to its limits and the hardware people will keep making a faster chip. A lot of software was laggy as hell back in the day. Not to mention, it didn’t have any features compared to the stuff now. Plus our shit would crash all the time and take down the whole PC. Sure, you run across some shockingly fast and good apps but those have always been few and far between.





  • In all fairness, 13 days is a fairly quick turnaround for patching in the enterprise. The breach was only 6 days after disclosure. They were almost certainly in the planning stages already when this happened.

    I used to be the head of IT in a large organization that worked with clients in highly regulated sectors. They all performed regular audits of our security posture. Across the board, they expected a 30 day patch policy. For high profile vulnerabilities like this one, they would often send an alert and expected imminent action within a commercially reasonable time frame. We would get it done anywhere from 24 hours to days later depending on the situation and whether there were complications. It was usually easy for us because we were patching every device and application on the network every couple weeks anyway. A hotfix is much easier to deploy when everything is up to date already and there are no prerequisite service packs. We knew we were much faster than most and it took a lot of work to get there. Thirteen days is a little slow for a 0-day by our standards but nowhere near unreasonable.

    The reality is many enterprises don’t patch at all or don’t do it completely. They may patch servers but not workstations. They may patch the OS but not the applications. It’s common to find EOL software in critical areas. A friend of mine did some work for a railroad company that had XP machines controlling the track switches. There are typically glaring holes throughout the company when it comes to security. Most breaches go unreported.

    Look, I hate Comcast as much as anyone. They suck. But taking 13 days to patch isn’t unreasonable. Instead, people should be asking why there weren’t other security layers in place to mitigate the vulnerability.