• 1 Post
  • 272 Comments
Joined 2 years ago
cake
Cake day: January 1st, 2024

help-circle


  • Gave it a quick shot right now, and gonna be honest - while the premise seems nice, the sample project is very transparently AI slop generated with a prompt that, I can only assume, included an instruction like “for every sentence that doesn’t include a whimsical quip, I’m gonna kill a kitten”. It is absolutely grating to read. I don’t care if you do that in your marketing copy, but keep that shit out of technical documentation, it’s annoying, it’s distracting, and it’s turning me off the entire project. Like wtf is this:



  • Also raufgeklickt, dahinter die perfekt nachgebaute SIMon-Mobile-Anmeldeseite. Meine Anmeldedaten eingegeben.

    Weil es bisher in den Kommentaren noch nicht erwähnt wurde, aber es einer der wichtigsten Schutzmechanismen gegen sowas ist: Jeder, absolut jeder, sollte konsequent einen Passwort-Manager mit Autofill benutzen, und dann sehr, sehr skeptisch werden wenn Autofill mal nicht funktioniert - normalerweise bedeutet das, dass man gerade nicht auf der Seite ist, auf der man glaubt zu sein.

    Passwort-Manager sind wirklich in jeglicher Hinsicht win-win ohne Kompromisse - sich irgendwo anzumelden wird einfacher und sicherer, gleichzeitig. Man muss sich nur noch ein einziges Passwort merken und von Hand eingeben, alles andere macht der Passwort-Manager für dich, und sorgt ergänzend auch noch dafür dass du überall unterschiedliche und sichere Passwörter benutzt.






  • I agree they probably should’ve addressed that in the main post, but at least it’s in the caveats below:

    Fine, maybe country first. The purists in the comments are technically correct — postal codes aren’t globally unique. You could do country first (pre-filled via IP), then postal code, then let the magic happen. The point was never “skip the country field.” The point is: stop making me type things you already know.



  • I mean I get your point, but it seems like at the current point in time, “Gaming” distros also happen to be the distros that produce the least amount of weird issues and headaches for someone new to Linux, especially if you’re on Nvidia. Bazzite in particular has been incredibly smooth sailing in a way I’ve seen no other distro achieve so far. And it does have a non-Gaming sibling distro if you don’t want that stuff.




  • if you run into any weird edge case issues it’s much more likely that someone else has already been there and discovered solutions

    While that is true, the amount of those weird edge cases that you’ll get varies wildly between distros. In my experience so far on a somewhat comparable rig to OP, Bazzite has been the only one that actually just worked out of the box and had not a single hickup, while any other distro I’ve tried (Pop, Fedora and Arch) all had several issues that required troubleshooting.

    So, I guess, for someone willing to actually understand Linux, learn, and troubleshoot issues themselves, your advice is the way to go, but for the relative who wants their system to just work and would call me anyway at any sign of trouble, I’m recommending Bazzite (or Aurora, I guess) all the way





  • And everytime you send another verification request the previous one will get invalidated immediately and you need to wait until they verify the new one.

    That’s not been my experience. I signed up yesterday, requested a new verification email after the first one didn’t arrive for ten minutes, only then read about the issues they’re having and decide to wait. A few hours later a verification email arrives, that just works, and I start setting up my server. Even more hours later the second verification email arrives.

    I mean, I guess it could’ve been the case that the first email I got was from the second verification attempt, and the second email was from the first one which was invalidated, but idk about that


  • So root still has write access to the system then

    No, not while the system is running. The base-layer of the OS is fully read-only.

    An update doesn’t write to the existing system, it creates a new one that will be switched to on next reboot. So the current system is not actually changed, hence the term immutability. This has two benefits:

    • atomic updates: either the upgrade is successful and you switch over to the new system, or it isn’t and you stay on the untouched current system. There’s no way to end up in a broken OS because an upgrade went sideways.
    • rollback: the old version stays untouched on disk, so even if the upgrade was successful but something still turns out to be broken after you boot into it, you can just switch back to the old, known-working system