• 0 Posts
  • 75 Comments
Joined 2 years ago
cake
Cake day: July 24th, 2024

help-circle

  • Depends on what your using/how its set up.

    GNOMEs native password manager “Passwords and Keys” has the opportunity to store the Browsers Keyring. So if you store passwords in Firefox/Chrome they get stored in Passwords and Keys (and then auto gilled in the browser).

    KeePassXC has a Browser plugin, as long a your password databases is unlocked it will autofill inside the Browser.

    Its Linux, so there is not one solution and it won’t simply work across all apps.








  • OK. Finally got your point. That’s a fair argument and I guess one strategy to approach it that way.

    Though I do feel like the takeaway most people had from Linus’s failure is “If Linus can’t figure it out how can I ever?” So I would argue in that way the challenges sort of falsified the truth?

    But yeah got your point now, sorry for being slow.


  • Sorry I still feel like we have a misunderstanding here.

    I was saying that Linus is not an Average PC user so he would not simply click yes. I feel like you’re reasoning the other way round? I.e. an Average PC user would just click yes so Linus I not an averge PC user but that doesn’t make sense to me since he did simply click yes?

    I’m sorry I keep on about this and if I’m completely misunderstanding you I just wanna figure out what you mean



  • If you gave a scrolling wall of terminal text to the average PC user and then asked “yes or no”, they will just say “yes”.

    As much as Linus tries to claim it whenever he fucks up in Linux, he is NOT the average PC User. Yes he is a Windows power user foremost but a lot of knowledge and concepts translate broadly. For example: if you get a warning you have to read it before pressing yes like a monkey.

    I agree what happened to Linus should not have happened, but the fact that Linux distros just let you shoot yourself in the foot like that is part of the freedom Linux offers.
    “You wanna remove THAT? Sure go ahaead” in this case they even put in a “You sure you wann do that? This will break things”





  • The thing is … I kind of agree with both takes.

    I have been using Arch since ~2013 back when I still had time to mess around with it and learn the ins and outs, these days I work as a sysadmin so I want my systems at home to mostly “just work”, however Arch also is that Distro for me for the most part. Most of the times I actually encountered breaking changes it was because of my process not breeing quite refined. For example I didn’t regularly update my config files, so when there were changes in the PAM config syntax my login was borked, so now I check for .pacnew files on every update and sometimes I have to move over some changes. I also don’t update as often but just when I have a few minutes while I’m using my machines.

    So in short I consider Arch to be a valid option for a Stable Desktop OS (if you take some precautions and don’t mess with it too much).

    However for servers etc. I do usually go with Debian because the packages are usually simply a bit more matured and I do major version updates as you described (explicitly setting aside some time to possibly fix arising issues).