I know I've criticized GnuPG, but it's a critical part of our software ecosystem. They're running out of money. https://www.gnupg.org/donate/index.html …
-
-
Replying to @matthew_d_green
Reporters in the tech area: there's a good piece on how random ICOs are raising millions and essential security projects are starving.
7 replies 48 retweets 95 likes -
Replying to @matthew_d_green
I always think about how the NTP guy has struggled to pay rent despite how literally everyone relies on NTP
2 replies 1 retweet 6 likes -
Replying to @antumbral @matthew_d_green
I occasionally see blog posts about Google or somesuch coming up with an improvement on NTP but they can't spare couch change for him?
1 reply 1 retweet 3 likes -
Replying to @antumbral @matthew_d_green
Upstream NTP is largely responsible for why leap seconds break everything. Google fixed that.
1 reply 0 retweets 1 like -
Replying to @RichFelker
Couldn't they have fixed upstream? They apparently sponsored it in the past.
2 replies 0 retweets 2 likes -
Replying to @antumbral
No, because upstream is doing "the right thing" except that it's horribly wrong for the real world. :-)
1 reply 0 retweets 0 likes -
Replying to @RichFelker @antumbral
That's plainly false. Just because computer scientists and programmers couldn't be bothered with leap seconds doesn't mean they don't exist.
2 replies 0 retweets 0 likes -
If you need a clock that doesn't involve them, great! But don't call it UTC or pretend that it's ok for the length of a second to vary.
1 reply 0 retweets 0 likes -
The right fix would be to standardize a map between "smooth time" and UTC and track them both. Google's fix is a practical hack, but a hack.
1 reply 0 retweets 0 likes
Google's fix is one proposed map. I don't really care which map we use as long as there's one with sufficient traction.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.