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.

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.