nitori

nitori wrote

Many browser developer tools allow viewing a page’s media; for example, the Network Inspector allows rendering the body of an individual request. A request for an image inside a spoiler should not unnecessarily bypass this. Browsers with such features shouldn’t ship spoiler support until a developer-tools toggle for “show spoiler contents” is ready. Should this also apply to spoiler text?

I think if a user is going to inspect element a webpage, they kinda have already waived their right to not get so surprised by secrets. This just seems like more unnecessary complexity for browsers for little gain.

2

nitori wrote

Reply to comment by nitori in jstpost breakdown: 2 GETs, by twovests

Alright just setup a HTTP 307 web forward in my nginx and pointed to my own IP in dnsmasq lol

(Realized I can't do CNAME or manually putting jstpst's IP into hosts because that will break TLS lol)

1