I was changing the way I internally date files for my website… (file-wise, dates are still rendered out YYYY-MM-DD style and Month, DD YYYY – HH:MM AM Z in text to reflect me currently living in the States) and…
I really wish Swatch Time, or, at least a metric time based in 1000, took off.- A time-of-day measurement with one unit of measurement that stays the same is really attractive for filenaming. The beat time "960" suffixed onto a filename, looks, and makes sense as, Nine-Hundred and Sixty. It makes sense as 96% of a day. Even if it's a Swiss person's day and not mine.
- Comparatively, when I suffix files with "140840" it looks like One-Hundred-and-Fourty-Thousand Eight-Hundred and Fourty, even though it means 14:08:40.
I reckon it wasn't marketed very well, and, making the meridian in Switzerland all because it's the Swiss watch company didn't really help with adoption. I think if the concept was introduced with both local and internet beats, as in, "how far out of 1000 are you in a day YOUR timezone? That's your Local Beat." and "also Switzerland is now the internet timezone of the world! That is the standard beat. :3" It woulda prolly seen more adoption.
I am currently suffixing YYYYMMDD changelog and microblog files in my website source repository with their official, HikaTamika™-coined Local Beats, as they make more sense to me than a -HHMMSS suffix.
Edit: (Thought of more!)
All that to say, I think where Swatch Internet Time, or rather, Swatch Beats fumbled with regard to cultural adoption, was the focus on trying to be/replace UTC as the base time
zone. UTC is UTC. UTC is good. I like UTC, even though its influence has colonialism to thank.
To me, where beats really shines is the
units!! Not the starting point/timezone!