Embedded portable device with a teeny ARM processor. Sadly, no room for linux anything or even an RTC. Every time it connected to a phone, the phone would set its clock so the timestamps were somewhat close to being accurate.
However, if you swapped out the AAA battery and DIDN’T connect it to the phone at least once, all your subsequent readings would go back to zero epoch and would be forgotten 🤷🏻♂️
Good times.
Worked on a project where devices just magically froze, but only during the month of February!
Turned out the people who had written the firmware had decided to do their own time math to save space and had put in an exception in the code for leap year values. Except instead of February 29th, it kicked in for the whole month. And the math was wrong so you ended up with negative values.
The product was due for launch in March of that year and was headed to manufacturing. It was by sheer luck that someone ran a test on February 1st and caught the problem.
Don’t mess with time in code, kids.
The Fediverse experience starts with an unanswerable question: what server do you want to be on?
Most people will not have any way to answer that without knowing what the downstream impact will be. Mastodon people are working on smoothing that down, but it’s still a pretty fraught question. And if half a given community ends up on one server and half on another, they get fragmented and conversations and followers fizzle out.
Bluesky wants to tell people they’re not a single-node lock-in to avoid the Twitter effect, but it turns out that’s their key advantage.
The only thing that will guarantee they don’t end up like Twitter is if they revamp their corporate governance mechanisms, but they had to take VC money and haven’t come up with a long-term revenue model, so it’s not clear how they can avoid it.