• 4 Posts
  • 46 Comments
Joined 8 months ago
cake
Cake day: July 26th, 2024

help-circle




  • The best path forward is that developers make their linux drivers before they release their hardware to the market. You know, like what they do for windows.

    There’s no silver bullet here. You have to wait for someone to reverse engineer the drivers if the developers of the hardware don’t care enough to supply even basic linux driver support. Either that or linux becomes so popular that it becomes senseless to ignore it (let’s be real though, MacOS is popular enough for this to be true and yet there’s still new hardware made that ignores that platform too.)








  • Sure.

    Valve’s operating system is read only and, when steam decides to update, any root level file changes will be lost between updates. This is partly good because the system will always be recoverable and update reliably, but comes with the downside that users have to take extra steps to install some base level packages (things like tailscale, syncthing etc. There’s always work arounds, but it’s not a guarantee that these work arounds will continue to work on new updates.)

    OSTree is also a read only file system utility that allows packages to be layered, so users can install their own packages. When the operating system updates, these packages are rebased and preserved on the next update so user level changes can be preserved.

    There’s more to this than that, but basically steam os is dependent on valve updating packages and generally leave all extensions either hand off or need to work around root filesystem. Ostree/silverblue/bazzite allow user modification by having a slightly more sophisticated updating process.





  • MoogleMaestro@lemmy.ziptoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    50
    arrow-down
    5
    ·
    3 months ago

    It’s very strange that you’ve made a post about bugs but chose not to list any of the bugs.

    Like, how can we make a recommendation if we don’t know what types of issues you’re running into? What type of hardware you have? What expectations you have?

    It just kind of screams of disgruntled user syndrome. These are community lead projects so, yes, they’ll have bugs. But if people never say what they are or what issues they had with what they used, the best the rest of us can do is just guess!




  • Calling the Scarlett Johansson lawsuit “Manufactured Drama” is certainly a take. A bad one, that is.

    Just like the lifting of a famous actress voice, one has to wonder how much LLMs are siphoning the intellectual property of the little-people of the open source world and willfully tossing the license and attribution clauses down the toilet. If they were willing to do it to a multi-million dollar actress, what makes people think that the intellectual property theft doesn’t go much further?

    Anyway, I think for this reason it’s actually really important to note that Junior Devs are much less likely to cause this type of issue for large companies. The question is whether the lawsuits from improper licensing cost more to settle than it costs to hire Junior devs, which brings us roughly to where the international outsourcing phenomenon brought us. At least, IMO.


  • Would love for you to describe exactly how it’s more complicated.

    “More” is relative, ofc, so YMMV on whether you agree with me or not on this.

    But the problem with pass key is that it has all of the downsides of 2FA still – you need to use a mobile device such as a cell phone, that cell phone must be connected to the internet and you often can’t register a single account to multiple devices (as in, there’s only ever 1 device that has passkey authorization.)

    This isn’t an issue with ssh keys, which is a superior design despite it not being native to the web browsing experience. SSH keys can be added or removed to an account for any number of devices as long as you have some kind of login access. You can generally use SSH keys on any device regardless of network connection. There’s no security flaws to SSH keys because the public key is all that is held by 3rd parties, and it’s up to the user in question to ensure they keep good control over their keys.

    Keys can be assigned to a password and don’t require you to use biometrics as the only authentication system.

    I feel like there’s probably more here, but all of this adds up to a more complicated experience IMO. But again, it’s all relative. If you only ever use password + 2fa, I will give them that it’s simpler than this (even though, from the backend side of things, it’s MUCH more complicated from what I hear.)