You’d think so but colours are weird. Some of the ones we see aren’t ones that actually exist, they’re invented by our brains. Magenta for example doesn’t exist, there is no wavelength for it and because of the way our eyes detect light it should really be a shade of green. But our brain doesn’t like that and invents a brand new colour instead.

Tbf, that was wolf of wall street, it’s basically a three hour long line of cocaine.

It’s because it can cause confusion. The only difference between example.com/file.zip and example.com.file.zip is one uses a . and the other a / but both are valid domains. If somebody isn’t paying much attention or they don’t know much about domain names, they could click thinking to get a zip file from a legitimate site and end up going somewhere malicious instead. No other TLDs have this issue (well, I guess .com technically has it but who the hell is downloading and running com files these days) and they’re pretty much exclusively used for this reason so it’s a good idea to block them just to be safe.

Not really, it’s like hosting your own email server. Sounds great in theory and is a fun project but at the end of the day all you get is a vanity URL and a headache.

Plus, the more entwined threads is with the rest of the fediverse, the harder it’ll be for them to break off. Users will be following Mastodon accounts and posting in Lemmy communities and if Meta does something to break that, they’re the ones that’ll get the backlash, not the fediverse. We’ll just continue along as normal.

I mean, they can but it takes time to do that and until they do /r/pics is adhering to the letter of the law (or at least an interpretation of it) while spitting in the face of the spirit of the law.

Ah, no, swearing is allowed as long as it’s vulgarity, profanity is what requires an NSFW tag. It’s a very important distinction that the Reddit ToS accidentally makes.

So, in conclusion: Fuck -> No NSFW tag. Hell -> Yes NSFW tag.