niplav @niplav@schelling.pt

in other news, /r/linuxmasterrace is still going strong

unkillable

> SAP

ah yes, now I know why you could power a fountain with my blood pressure

oh boy i do love dealing with university software infrastructure

I'm only paying lisp service to John McCarthy

guy who, when he hears someone mention SARS, thinks of deep Q-learning

“I wouldn't trust her—I heard she's antisemiotic”

why is https://www.gwern.net/Embryo-selection also tagged “anime”? Gwern, do you want to tell us something?

the infinitely abundant patience of the early lw commentariat

i imagine that arriving at vibecamp, the first thing you hear from afar is a chant: “Hot Moloch! Hot Moloch!”

concept: schelling.pt meetup at 0°N 0°E (Null Island)

with boats

but maybe there's some obscure way to route around those concerns?

but in that case, I'd worry about bugs in the obscure implementation of that feature.

how do whatsapp/signal/telegram desktop clients work? you'd basically either need to transfer the private key (in which case the encryption isn't e2e anymore?), or generate new keys for every device.

we can't do it with cookies holding the private keys, since many people block cookie usage & cookies are readable by anyone. we'd need to have local storage that the server authenticates for, otherwise any server would be able to read out the private key from storage via js & send it to the attacking server…

as far as i can see, client-side e2e encryption in the browser requires *a bunch* of changes to browser tech?