Before Arch that role belonged to Gentoo.

To add, before the change the Gentoo wiki was a top resource when it came to Linux questions. Even if you didn’t use Gentoo you could find detailed information on how various parts of Linux worked.

One day the Gentoo wiki died. It got temporary mirrors quickly, but it took a long time to get up and working again. This left a huge opening for another wiki, the Arch wiki, to become the new top resource.

I suspect, for a number of reasons, Arch was always going to replace Gentoo as the “True Linux Explorer”, but the wiki outage accelerated it.

I completely forgot that existed! Double checking the technical article they do correctly label it as a browser in their testing matrix/grid.

I just got confused by the clear “Brave browser” call out. When I hear DuckDuckGo I definitely don’t think browser.

Good catch!

You’re not affected if (and only if)

You always used the Brave browser or the DuckDuckGo search engine on mobile

I found that odd, but reading the more technical write up (linked in the article) it seems Brave blocks localhost communication.

The Chrome proposal references a single use case. I’ve never seen a website that sets up my local devices, but is this a new thing?

Why did localhost not get blocked earlier? This seems like a huge hole browsers have ignored for years.

Also the DuckDuckGo exception doesn’t make sense to me. Does DuckDuckGo have Facebook trackers on it to begin with? Whatever site DuckDuckGo sends you to, if they have the trackers, you’ll get tracked.

Linux has two ways of drawing pictures, the old way (Xorg) and the new way (Wayland).

The old way is like a giant box of crayons with the crayon sharpener built in. The box is all marked up, the sharpener is full of gunk, and a few crayons are melted together. Nobody really wants to touch the old box of crayons, although it does work for the most part, it’s a familiar box.

The new way is like a smaller box of crayons. The clean sharpener isn’t built in but it is available nearby, although some people say it doesn’t work as good. A few crayons are missing, but are available in most cases, they’re just not in the box. Most people are working to improve the new box.

If you’re using Linux, the new box of crayons is generally the better choice. It’s ok to stop using the old box.

Lex Luthor.

Sure, he wants to kill Superman, that’s not the best political stance, but other than that he’ll basically just focus on fixing everything else that slows society down in order to have a society that’s better at killing Superman.

Plus it’s not like he’s successful at killing Superman. So really it’s a win-win.

Knoppix. I didn’t see it listed yet so I had to chime in.

I saw it and was confused that computers could run something that wasn’t Windows and wasn’t Mac. Then I was handed a Knoppix LiveCD and suddenly MY computer was Linux. Absolutely blew my mind.

I then explored Mandrake (now Mandrivia?) for a while but it never really stuck.

A few years later Ubuntu was handing out LivdCDs to everyone running Warty Warthog and soon after window managers started to use Beryl (?) which let you have a fancy cube desktop. Absolutely pointless but that’s how it all started.

I love pineapple and really strongly dislike it on pizza. The only time I’ve had “acceptable” pineapple on pizza is when it was chopped up really tiny and I could barely taste it.

My problem with pineapple on pizza is,

• Hot/warm pineapple is gross.
• Pineapple makes the pizza watery.
• Pineapple adds a sweetness that a pizza just doesn’t need. It detracts from other flavors.
• Again hot/warm pineapple tastes gross.

Just trusting them to pay you out of their own pocket?

Assuming US, it actually depends on the state (may be all states, but I can only speak of those I’ve lived in). The law is that the money must go into a separate interest bearing account and that is the money that is to be returned. So the money isn’t supposed be their own pocket.

As you mentioned elsewhere it’s encrypted.

Take a look at /etc/crypttab and creating and adding a key file that can unlock the drive.

Essentially your additional SSD will have both a password and a file containing a password that can unlock the drive. When you unlock your root filesystem (I’m guessing at boot) it will then have the key file that can unlock the SSD.

Something like cryptsetup luksAddKey /dev/pathtossd --new-keyfile /etc/newpassword

Systemd might make this easier to setup nowadays.

Edit: Also, yes, the password to unlock your SSD is just sitting in a file in your root drive. Be sure to restrict it to only be readable by root.

Oh I completely agree. There is a reason it took me a while and careful observation before I figured it out.

I assume it’s part of, or started as, a little password dance. Something like, “abc123DEF”.

Or maybe it just comes from the idea that only a single key can be pressed at a time?

Either way I completely agree, insane.

I agree, but it’s more common than you’d think.

I used to work at an organization that used Chromebooks, which replaces the caps lock key with a search key (same shape, different behaviour). I was surprised at the number of people who struggled with their passwords because they would hit the “search” key, enter a single letter, and then hit “search” again. It took me a little while to figure it out because… Who does that?