I think it’s both. Instead of trying to update the codebase with one new database attributes for each conceivable way to tag content, you simply put in facilities to abstract that - “show only posts with tag foobar”, “hide all posts with tag foobar”.

Having gone through the code a bit, the NSFW handling looks very baked in, so it’s not a small ask. The smart approach would be to add an arbitrary tag system and handle it that way.

Their stance is that you personally are banned for life from subs regardless of which account. Would be a real shame if your IP got changed between accounts, your cookies and local storage got cleared, and you never mentioned the old account again. You could accidentally post in a sub you got banned from, and they wouldn’t be able to helpfully re-ban you from the sub!

If you were still trying to spend time on reddit in the first place at least.

I’ve done it a fair bit and it’s actually pretty painless. If you know how to use vim you save a ton of keystrokes, which makes a big difference on mobile.

…ssh and vim?

They’re both very complex so it’s understandable people would have different experiences. In general I’ve found GCP fairly straightforward, with shitty documentation, generally good support of fundamentals, great k8s support, good prices, fairly modern APIs, and relatively low feature coverage. AWS more built out, awful & totally inconsistent UI, better feature coverage, higher prices, and some pretty janky XML APIs if memory serves.

Honestly, it’s not as bad as AWS or Azure. Plus if you use k8s it’s first-in-class support, since Google came up with k8s. There is a fairly steep learning curve though.

If you’re deploying anything in cloud infra you need to make sure it’s portable between providers. Vendor lock-in is a big avoidable no-no.

All I know is I’m already sick of this anti-FOSS users narrative.