site banner

Culture War Roundup for the week of August 24, 2026

This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.

Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.

We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:

  • Shaming.

  • Attempting to 'build consensus' or enforce ideological conformity.

  • Making sweeping generalizations to vilify a group you dislike.

  • Recruiting for a cause.

  • Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.

In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:

  • Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.

  • Be as precise and charitable as you can. Don't paraphrase unflatteringly.

  • Don't imply that someone said something they did not say, even if you think it follows from what they said.

  • Write like everyone is reading and you want them to be included in the discussion.

On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.

2
Jump in the discussion.

No email address required.

Maybe the web should be purely static again. Web 2.0 was a mistake.

I’m not exactly sure how you envision the blockchain helping, here.

There has to be a trusted cert. Just put it on the blockchain, same with domain ownership. When someone holds a domain on the blockchain they can issue a cert for it that lives on the blockchain too and is used for their https.

Blockchains provide low-trust secure public timestamping, which means they can confirm priority and therefore resolve double-spend disputes (which is how they enable cryptocurrency). The issue with certificates is whether the public key is correct in the first place, and blockchains don't provide any additional security beyond the key-signing process - fundamentally you can't trust that a public key is correct unless you trust the person who published it, or someone else who signed it.

If two certificates for the same person or entity with different public keys are published at roughly the same time, either both are valid (you can have multiple public keys) or one should explicitly revoke the other. There is no question of priority.

Shouldn't keys be self published? As in someone has a wallet, they can buy domain ownership on the blockchain, their wallet then publishes the correct key. It is verified by the fact that their wallet is the owner of the domain on the blockchain. Their wallet also sets the config.

Is what you want "the certificate shows this server verifiably is run by the owner of the domain (or an approved proxy)?" That's not all the current regime is doing: there is a nonzero amount of "and is an upright business interest" there that crypto has well-known issues with. How would you revoke or reject certs from malware hosts? Even if LetsEncrypt isn't checking site contents, the browser vendors are still doing so, functionally replicating the original centralized PKI complaints.

there is a nonzero amount of "and is an upright business interest" there that crypto has well-known issues with. How would you revoke or reject certs from malware hosts? Even if LetsEncrypt isn't checking site contents, the browser vendors are still doing so, functionally replicating the original centralized PKI complaints.

You are saying censorship is baked in to the system for safety reasons. The solution here is to make censorship opt-in instead of forced. Censorship companies can run a censorship server that I query if I'm so paranoid about malware websites having TLS certs. If you make it to where I have to obey the censorship authority no matter what, then they inevitably start exploiting their power to perform political censorship.

If you're that concerned about censorship, why use TLS at all? It makes sense if you're concerned about privacy -- assuming your counterparty's certs are actually secured -- but then you also want to make sure your counterparty is who they say they are so you don't leak messages to the wrong parties.

There is a very real privacy-censorship tradeoff here that is inherent in any indirect trust scheme: unless you're trading RSA keys out-of-band with your servers (not bad if you can), the PKI problem isn't really escapable. Web of trust never worked as an alternative. Any centralized solution there begets censorship.

All I need to do is confirm the counterparty is the owner of the domain, which they are on the blockchain under this scheme. It doesn't say whether they are good people or not.

How do you trust your counterparty to keep your conversation private without knowing they are who you think they are, and not a leaky proxy?

More comments