DigitalJacobin

Feel how you want, but Spotify has a very clear policy on hateful content. And sure, maybe you won't listen to it, but do you know who will? Bigoted psychos that will go out and commit a hate crime. Allowing content like this on a popular platform will lead to hate crimes. There is nothing wrong with private platforms choosing to not platform certain kinds of content and it is entirely within their right.

Spotify has the right to deplatfom hateful content and doing so is the ethical thing to do.

The act of book banning itself isn't the real issue. The issue is the homophobia/transphobia motivating the conservative book banning.

We used to support social mobility

When? Under slavery? Under Jim Crow? Under neoliberalism/Reagan?

and home ownership

Maybe to get settlers to move west for manifest destiny.

There are many, many good reasons to not use Brave. Being spyware is not one of those.

Boycott Brave for real reasons like their CEO and owner being a raging anti-gay reactionary or because of their cryptocurrency bs.

Unfortunately, adoption has been slow and Alliance for Open Media are pushing back somewhat (especially Google^1, who leads the group) in favor of their inferior .avif format.

However, getting people used to double extensions is one quick way of increasing the success rate of attacks such as the infamous “.pdf.exe” invoice from an email attachment.

Very good point. Though, i would argue that this would be much less of a problem if Windows stopped sometimes hiding file extensions.

I can’t see how Windows’ convention is worse

I don't believe what you're referring to is really a Windows versus Linux/Unix thing.

If I zip a file, it doesn’t matter what it was in a previous life, it’s now a zip - this is also how Unix deals with many filetypes, I’ve never seen a .h264.mp4 file, even though the .mp4 container can actually represent different types of encoding.

I disagree, but i do get what you're saying here. I don't think that example really works though, because a .mp4 file isn't derived from a .h264 file. A .mp4 is a container that may include h264-encoded video, but it may also have a channel with Opus-encoded audio or something. It's apples and oranges.

Also, even though there shouldn't be any technical issues with this on Windows, you can still use a typical short filename suffix if you wish, though i would argue that using the long filename suffix is more expressive. From "tar (computing)" on Wikipedia:

I get the frustration, but Windows is the one that strayed from convention/standard.

Also, i should've asked this earlier, but doesn't Windows also only look at the characters following the last dot in the filename when determining the file type? If so, then this should be fine for Windows, since there's only one canonical file extension at a time, right?

True, but it offered a much more secure alternative to opening up PDFs locally.

What's messed up is that, technically, we do. Originally, OpenDocument was the ISO standard document format. But then, baffling everyone, Microsoft got the ISO to also have .docx as an ISO standard. So now we have 2 competing document standards, the second of which is simply worse.