1142
What a joke, can't believe people still voluntarily use this OS
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Jan 2026
1142 points (97.2% liked)
Programmer Humor
29845 readers
252 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
I understand the mechanism, and why it is important.
I don't understand why the error message from the store was nothing more than an error code, and why the MSKB for that code had absolutely no mention of a failed ssl negotiation as a possible cause.
Time->TLS errors aren't handled well anywhere.
As critical as they are to 2fa and TLS, you'd think every OS out there would poke around a few time servers and scream bloody murder if the time was off.
Honestly, I think we, as a society, have leaned a little too hard into time as a precise critical failure point. It's fine for things like GPS that actually require it. but our clocks don't need to be precisely the same to tell how recent a request and response are and we can certainly make better hashing algos
wget will give you a sniff of what the problem is. Microsoft Store will not.
I don't NEED an application to necessarily pinpoint the error. Just even a rough direction. Any browser will explicitly tell you if there is a cert issue. That's more than enough to go on.