Yeah, that’s why I love that fact too. Sending a rocket into space and landing on a tiny ball of rock was literally easier than pretending to do it.

Actually, the moon landing was faked but for realism purposes they filmed it on location.

Nah, the technology to fake the moon landing straight up didn’t exist in the 60s. There’s a really good video on youtube that goes over it but I can’t seem to find it right now. But basically, even though there were some nice techniques to make special effects for movies, they wouldn’t have worked for faking an actual moon landing.

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.

You can actually see it in modern times. The Himba tribe in Africa doesn’t have a concept of the colour blue. There’s not even a word for it, as far as they’re concerned blue is just a shade of green. To us it seems obvious, the sky is blue and the plants are green but to them it’s all different shades of green. It’s not a genetic thing, they’re seeing the exact same colours as anybody else, their culture just doesn’t distinguish between the two colours.

They can ban the mods but if /r/interestingasfuck can’t find new mods for 22 days and counting then /r/dndmemes will probably stay empty for even longer.

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.

I haven’t researched it at all but I’d be very surprised if you needed anything more than a domain name (basically free as long as you don’t go for a common TLD) and somewhere to host it (literally free if you do it on a home PC but that comes with other issues). Cloudflare and extra security are nice but aren’t necessary for something like this.

Multi-threaded programming is hard. You can’t just write some code and expect it to work across 4 cores, you need to know what to parallelise and how to do it. If you think normal bugs are hard to fix, just wait until you have a calculation that gives a different answer each time you run it thanks to race conditions.