n.s.

i went into close-to-hardware programming as my job to avoid dealing with SSL. i am currently learning SSL because hardware demands it now. weee!!

The thing I really dislike about SSL is that all the people working on it are like "okay, that's how it'll work for big sites connected to the internet as a whole, and... we're done."

Why is there still no good story for IOT devices that don't phone home, but just exist on the local network? Why can I not tell my phone "okay, on this wifi network, accept this root cert. for local devices and hostnames that end in .myfriendshouse.home"? Instead, I have to basically root my phone so that from them on it always displays "this network may be monitored", because that's how signing certs work: it doesn't make sense to support local, limited signing certs on the big Internet, so they're an obscure corner of the spec. that might or might not work on your device. (Also, my friend's signing certs has to have been built with those restrictions attached to the cert, because letting the end user control where certain root certs apply doesn't make sense on the big Internet)

Why is running a thing that makes SSL certs for my home network hundreds of times more difficult than running a thing that hands out local DNS names? I'm even running an IMAP and SMTP server, and they're much easier to manage (except for the fact that their certs are multiple years expired because dealing with that is the hard part).

the more you're getting into web, the more you realise that almost all standards and technologies fucking suck

goddamn preflight requests, CORS, consistent cross-browser CSS, fonts rendering on different browsers, HTML semantics (the divs hell you know?), SSL, javascript and other terrible bullshit

i currently work on a complex project in a team and do that crappy frontend stuff... this is what we call "геморрой" in russian

messing up with maths and computer vision is much fun :)