Skip Navigation

Posts
0
Comments
36
Joined
1 yr. ago

  • Nevermimd that signal's centralisation makes it vulnerable to this kind of outage, and that was a conscious design decision. So nobody should be surprise this has happened.

  • For fuck's sake, why can't we have nice things?

  • I give them less than a year to turn sour and start "pivoting to a new strategy"

  • To be exact, they are empowering Microsoft future. This is because of the absolute insane amount of money they are pumping into LLMs while still not finding a business case for them.

  • I know, yes. But I'm talking about virtualization, not containerizarion

  • Personally, I want to properly isolate the services with virtualization. The main reason is I expose some of the services online, and I don't t want to only rely on keeping all software up-to-date at all times. This allows me to limit the damage if one of the services is compromised.

    I wouldn't use MacOS as the virtualization platform, and instead use something else, like BSD, Linux, or xen-based for my servers

  • Sounds like my next phone won't use Android then, and I'll tell everybody to avoid it. If only Linux mobile was in a hood place :(

  • Sorry, I made a typo, I meant drives, not drivers.

    Firmware is software embedded in the SSDs, and Windows has no control over them. Microsoft can't fix this and the SSD manufacturers here are at fault.

    Do note that I escaped Windows in 2017, and wouldn't like to go back to it because of how nauseatingly user-hostile it is.

  • Eh... Reading the article it's clear what's causing this are faulty SSD drives. Windows might stress their crappy firmware, but the fault lies on the hardware.

  • Isn't that the bare minimum mandated by the EU?

  • It didn't get review-bombed. It got negative reviews after the last update because people don't like it.

    Personally I bought it and don't like it: it's an awkward mix between diablo-likes and souls-like, while not reaching the heights of either, it also has its own unresolved issues, like lack of descriptions for weapons or abilities. This might have been fine on the first release of the early access, but we're almost a year in and people expect initial 8ssues to be fixed.

  • Xcp-ng might have the edge against bare metal because Windows uses virtualization by default uses Virtualization-Based Security (VBS). Under xcp-ng it can't use that since nested virtualization can't be enabled.

    Disclaimer: I'm a maintainer of the control plane used by xcp-ng

  • But the individual network packets are usually at most 1500 byes long, and applications encrypt the content. Hashing doesn't prevent jack squat. It's more likely to be DNS + IP blocks