Comment on Dark patterns killed my wife’s Windows 11 installation – OSnews
Catnipchewer@lemmy.world 22 hours ago
Linux is waiting patiently for that woman
Comment on Dark patterns killed my wife’s Windows 11 installation – OSnews
Catnipchewer@lemmy.world 22 hours ago
Linux is waiting patiently for that woman
stardreamer@lemmy.blahaj.zone 19 hours ago
Devil’s advocate here: switching to Linux wouldn’t help here.
I recently had to set up a public web server for a org that I belonged to. The idea was that I would set everything up in the most secure and unbreakable way I can think of, write documentation on how to do everything, transfer ownership of all the “break glass” credentials and lock my own account once I’m done.
This turned out to be a huge mistake. What was supposed to be some free work for a hobby group turned into a massive pain every day at 3-4am (due to time zone differences)
The person in charge of managing access control couldn’t figure out how wg-easy works. She managed to give her own credentials to EVERYONE who needed access, which obviously didn’t work due to IP conflicts. When pointed out, she modified the IP in every config file, which of course, still didn’t work. It took forever to tell her NOT to share credentials and create new peers for each user.
The biggest problem is some how NOT windows or mac users. There is a single Linux user that is causing the most headaches. When I set up wireguard, I tested on both Linux and Windows, with Linux being what I used. I ran into some minor hiccups with getting split dns to work correctly, but it was relatively easy to fix in Network Manager. I assumed if there are other Linux users they would be able to fix it themselves. Obviously I was wrong.
Said person had DoH enabled in their browser that they didn’t know how to disable, running varieties of “I don’t know” for their network stack, DNS resolver, etc. almost every question for dig, cat /etc/resolv.conf descended into “what’s that?” or completely incorrect commands (e.g. resolving a http url in dig). I could not figure out what the person was running, the person themselves had no idea what was running (I think it was systemd-resolvd, but I still don’t know as of now). Eventually, after 3 workdays of trying to help fix this at 3-4am, I gave up. I can’t help with a personal device belonging to somebody that has no idea what they’re doing.
As for why I’m mentioning this story: switching to Linux wouldn’t help this lady with her problem. There are similar issues on linux that would prevent a login or a graphical session (there was an old work machine that ran VLC, where VLC threw GBs worth of QT errors, eventually causing systemd to crash on reboot when the drive was full). The problem here isn’t just the system, it’s the user. If the general mindset is “I don’t know what’s wrong with no details”, there’s no savings the user from technical problems.
Muffindrake@lemmy.world 8 hours ago
Oh yeah, starting your post with
The missing undertone here, which is present in about every issue involving Windows 11 ever since it was released, is the corporate enshittification, the unerring fatigue of normal users of avoidance to
We have been conditioned to view people that criticize the corporatism in this Western society with the same lens as we used to conspiracy theorists. You need to call this out as propaganda wherever you see it. The people who cannot describe the price of a supermarket banana or bread are not your friends.
Look at it this way: A normal dude with bad hair and questionable social intelligence isn’t getting up in the morning and deciding to fuck with a million or more users by making their computers unbootable. There is only good intentions. Sometimes the Lennart Poetterings fuck up - but we will send three long-haired dudes with funny glasses to your place to fix your tank for free, as you did.
Whereas with Shitmicro Operating System, they have continually demonstrated that they’re here to sell you ads and make everything so much shittier like you would not have believed twenty years ago.
stardreamer@lemmy.blahaj.zone 5 hours ago
That was the context. The problem wa connecting to Wireshark, which more and more people are doing thanks to general awareness of VPNs.
Huh? Where in my post did I defend MS? I was there when Balmer and crew decided to sue anyone with a pulse for using Linux. I was there when the Cathedral acquired the Bazaar (and I deleted my account for it), and I am still here using Linux and BSD for every single machine I own with the exception of one. I still hold a grudge against Mr. Bill “Jump on a roller to show how fit you are” Gates, and I refuse to purchase anything from their game catalog since 2011. Hopefully with this context, you would no longer misconstrue my point as “defending Microsoft”.
Alas, normal users care about neither. The computer is just a tool that allows them to do work which allows them to put food on the table. If your assistance is just “boo hoo use Linux”. That’s not productive to them nor us.
Case in video game modding: 1. GShade, where the developer deliberately made people’s game segfault if compiled on their own after an update 2. MultiMC, where the developer personally threatened to sue for trademark violation after packaging the application for a Linux distro 3. Bukkit, where one dev decided to DMCA and take down all instances of the project.
Outside of video games: the entire university of Maryland, which attempt to inject backdoors into the Linux kernel that was not caught until they published a paper.
Also, regardless of intentions, if the damage is done, the harm is done. If a suitcase falls from an airplane and kills me tomorrow, I wouldn’t care whether it was intentional or not. I would be dead.
corsicanguppy@lemmy.ca 4 hours ago
Dude. That guy has single-handedly ruined two decades of bulletproof, fast, reliable booting. I can’t wait until we all wise up and it’s more than PCLinuxOS that avoids this mess. It’s a metastatic kudzu/poison-ivy hybrid with a taste for flesh.
corsicanguppy@lemmy.ca 4 hours ago
If you’re pushing kubes onto a normie or a noob, the fault’s partially yours. Single-box apache, maybe samba xor git, depending on the workflow, and some audio hints in /etc/profile.d to remind them how to restart various pieces if they can putty in.