Post #1753554
2026-04-27 18:23 UTC
Stubbed my toe on "JavaScript can't do SHA-256 if your web app wasn't served over SSL" and apparently this is a known rabbit hole, holy shit: https://github.com/w3c/webcrypto/issues/28
I would like to understand the thought process of someone who imagines any outcome other than people rolling their own crypto for locally served web apps
Replies (3)
-
@whitequark@social.treehouse.systems 2026-04-27 18:26
@swetland @wren6991 anything else can be enabled with a command-line flag or enterprise policy, but yeah
-
@wren6991@types.pl 2026-04-27 18:44
@swetland @whitequark Yeah, I hate to say this but I'm gaining new appreciation for Electron, Tauri etc. "It works on my localhost dev setup." "Then we'll *ship* your localhost dev setup."
-
@lanodan@queer.hacktivis.me 2026-04-27 20:09
@wren6991 I could maybe get making sure there's no https downgrade (say first-party is https but cdn is http), and that having an effect on *encryption* but SHA-256 is a hash, it doesn't matters.