Wobbly clock
somethingorotherwhatever.com
somethingorotherwhatever.com
I always thought that was a brilliant way to keep mechanical clocks in sync. And the system had been there since the 1970s, so it was well before digital clocks were feasible for a school.
In contrast, I'll sometimes now walk into a lobby or reception area of a business where they will have like five different analog clocks on the wall representing NY, Paris, London, etc, (trying to look "international" I guess) and the minute hands are out of sync. Kind of sad in 2023. :-)
When Daylight Savings Time began, I sauntered in about 9am and my coworkers were filtering in too. The morning guy, "Matt" had been there since about 6am and he had changed the clocks. So my other coworker, "Jason" congratulated Matt for setting all the clocks correctly and then he asked him, "so did you do it by setting all four clocks ahead one hour, or did you move them all to the left and then move the Pacific clock to the Eastern position?" Facepalm!
That might be a good job interview question, or it would have been if manual, analog clocks were still a thing.
In Germany (and in neighboring countries), radio-controlled clocks are quite common for this purpose, listening to DCF77 near Frankfurt [1].
Long wave seems to work a bit better than the L-band for indoor propagation, and it probably also helps that the transmit power is three orders of magnitude higher.
I'm not sure if the US has an analogous service – there's WWV and WWVH, but they are shortwave transmitters, and I don't know if wall clock or even wristwatch size receivers are possible for that.
It does. Small WWVB clocks that self set are quite common.
It makes sense that a company might make those, if they also make the NTP servers that those clients might be connected to.
Good stuff. I'm planning on buying some for the house.
(Sorry for the deprecated master/slave terminology, it's unfortunately what they used at the time)
The clocks could even be set for Daylight time centrally, so I assume it had a way to send a signal that triggered a motor to move the hour hand faster.
I've always found the clock faces more fascinating than the mechanisms driving the hands around. I'm easily distracted. My CodePen kaleidoscope clock's here: https://codepen.io/kaliedarik/full/vYLaOxK
This clock solves that problem.
Anyone know if I can get this as an Apple Watch face?
Currently, 3rd parties can't create custom Apple Watch faces.
It seems to be part of Apple's strategy, to focus on Out Of The Box experience, not on user configuration. And to the greater point? To make profit. The perfect product is not the point, nor is the perfectly satisfied customer.
While I fully believe that Apple should open up to third-party faces, I am quite content with the customization options that they offer now.
As for the reasons why they don't, my speculation is the following (I'm not defending them): They are worried about custom watch faces that might perform poorly or draw too much battery. Watch is a challenging platform to develop for as watchOS is very protective of its resources and won't hesitate to kill your app. But Apple probably doesn't want to kill the watch face and at the same time doesn't trust the developers to develop their watch faces to Apple's standard.
I've never seen one worn in real life.
Personally, they're a less cool version of an 80s swatch.
The point of a smart phone is not ringtones. The point of a smart phone is not even being a phone anymore. It's everything else you do with it.
The point of a smart watch is not cool watch faces.
You want skins/customization, which is fair. But you have to admit it's not core functionality.
In English! In Dutch this would actually create a problem, as when it is 3:45 we say it is "15 before 4". I noticed that I actually struggled to interpret the wobbly clock when it was close to changing the hour.
I always think that the prevelance of saying "three forty-five" is a result of digital watches.
I taught my kids similarly. Starting with the hours, and then "half past" and then "quarter to" and "quarter past."
Only after all that was second-nature did I even explain to them the idea of 60 minutes.
I mean, analog watchfaces are bad at telling precise time - it's just that there wasn't anything better until quite recently (and people are typically fine with 5-minute precision). They're great for conceptualizing time intervals (easy to mentally picture a pie chart), but I strongly suspect most people when asked "when is the next meeting?" are reading time then doing the arithmetic rather than reading the interval directly.
I could be wrong, of course.
Also, it's a great way to teach kids multiples of five and fractions. :)
The Babylonians were masters of division-based math, when the purpose was to divide things up into equal parts.
Started to fade from fashion when economics became about making things grow (increase the pie) rather than divide what they had (slice the pie).
If you grew up reading analog time, these aren't at all hard to read, even to the minute. Really, it's not an affectation, I would find a mark-less analog watch faster to grok than a digital watch. Most people who grew up on analog watches will similar have no problem with them.
The only kinds of watches that are more about "rough" time are ones without marks and without a minute hand. Those I can only read to about 15 minutes.
For example, 189/304 vs [####__]; the latter is probably faster to process.
Also, not related to clocks, but analog gauges in particular: a number lacks an important vector of information: rate of change.
[1] https://books.google.nl/books?id=nrtUgKzFhJ4C&pg=SA7-PA16&lp...
For the progress bars (or, say, tank level gauges) it totally makes sense - I like them the same way you've presented, it's easier to ingest [####__] (or, better, [####__]62%, so it can be also spelled out if someone's asking) than 189/304.
Linked book doesn't open for me, but I agree that this also applies to various instruments, especially in aviation, where IFR is of extreme importance. Though for a car I've picked mine specifically based on having a clear large digital speedometer (because unlike on an aircraft, cars 101% rely on seeing outside) and I'm always interested in speedometer reading for answering "how fast I'm going, exactly?" (speed limit comparison is a no-brainer, and with a precise reading I can maintain speed at +/-1mph of the desired target, which is impossible with an analog speedometer) rather than "am I slowing down or speeding up?" (I see this already).
But watches - when using for telling time - aren't really gauges, are they? Analog watchfaces can be (and are, by some) used as a gauge when measuring time intervals ("how long had passed", "how much time left"?), but again, like I wrote, I suspect that most people read the time then do the arithmetic rather than imagining a pie chart.
depends how the person was trained, my friend.
I have this suspicion based on a few anecdotal data points plus the fact that digital watchfaces are becoming more and more common (phones and computers specifically), and people love to do things in an uniform manner.
But I'm very biased here (and thus could be wrong), because I strongly dislike classic analog watchfaces. I'm certainly for novel approaches - I do like Apple Watch's "Solar" watchface (the digital version), as it has a digital reading centered in essentially a gauge that shows the Sun's motion, allowing to see the time relative to the daylight. Similarly, I enjoy calendar and weather widgets that show the day as a timeline, so I can see how events or weather conditions approach. But I'm always asking myself "what time is it now?" first (and "ok, how long until...?" only comes after, even if it was the original intent) - it was my mental model for as long as I remember myself - so I strongly prefer digital 24-hour displays.
That’s an excellent analogy. If digital were as quick to process, we would simply have data tables everywhere and no need for data charts.
However the minute hand only moving every 5min isn't great.
Edit: here's a video of it running (somehow the seconds hand runs backwards)
> This clock is inspired by a post by ILAMtitan on the 43oh.com forums, which was in turn inspired by Vetinari's clock from the Discworld series of novels. Although the movement of the second hand is quite erratic, it ticks exactly 32 times in 32 seconds, and so keeps quite accurate time overall. The clock started life as a cheap $3 clock from KMart. It's mechanism was kept, but the driver circuit was removed and replaced with an MSP430 microcontroller. ILAMtitan's code is designed to ensure that every 32 seconds it will tick 32 times, but the exact timing of those 32 ticks is variable. There can be as little as 1/4 second between ticks or as much as 24 seconds. Overall though it will keep quite accurate time.
I will have to buy some cheap clocks and start tinkering.
I am a fellow juggler, and used to run the Internet Juggling Database. We also very briefly bumped into each other in a corridor at Leeds Uni Physics department about 25 years ago ;-)
You don't have contact details in your profile, but feel free to email me. I travel a lot and can put you in my geographical address book so that if I come within reach we can get a coffee.
Cheers!
More, I created a system wherein people can register, and then whenever someone is travelling they can tell the system and it automatically emails everyone they know who is close to the destination.
I'm the only one who uses it, although there are a few hundred people on it, so I basically just use it as my geographical address book.
I also put landmarks, museums, and other places I might like to visit. When I tell it where I'm going it then sends me email to remind me of them.
It's online (but registration is invite only, let me know if you want to play with it) over at https://scoutmaps.io/ – at one point I was going to attempt to commercialize it, but eventually decided I liked it better as hobby software so that I can write features that better serve my current userbase of one :)
He has a great writeup about it here: https://medium.com/the-outtake/the-clock-85e8e3a50e4b
[0] https://developer.apple.com/library/archive/documentation/Au...
But the way the minute hand stays pointing to a multiple-of-five-minutes until it Boings! to the next increment is disconcerting.
It looks like it's slow all the time. E.g. 10:29 looks like 10:25 which is more than enough error to look wrong.
Maybe I'd learn to read the bent-hand deflection after a while. But I guess I prefer the clock I have that just points to the right minute all the time.
Yeah, it would be a bit more satisfying if the end moves discontinuously (as it does now) but the stem moved continuously.
Still very nice as it is though.
This links to a Twitter thread: https://twitter.com/christianp/status/1250454284581457923
Which has at least one other interesting clock idea, this one with floppier hands: https://twitter.com/kangaroophysics/status/12508031830451814...
Edit: D'aww. Hug of death.
i feel like i am really missing out on something here
5:46 -> "Five and and bit tense 45"
5:48 -> "Five and 45 tense"
5:49 -> "Five and very tense 45" or "Five and loose 50?" ?
But I like it :D
Four past a quarter to six. As I'm posting this, it is 12 past half til 6 (Eastern).
The seems to have something that stops the end of it moving on until enough tension has built up to side underneath it. That much is fair enough. But then that same thing stopping the end would also prevent the same satisfying wiggle when it gets to the next position because it overshoots immediately.
The only thing I can think of is that the restraining pins move in and out is the clock have at just the right time but that would be quite a fiddly implementation and probably affect the visuals
As an aside, I'm not sure that doing this for the hour hand is a "good" idea. The difference between 10:00 am and 11:00 am is significant and needing to check how much the bend is doesn't "feel" right.
(late edit thought) If we're getting to the "this is controlled by some other system that doesn't need to be purely mechanical", having an electromagnet on at the right spot that then toggles off at one 5m increment and on at the next so that there's only one magnet active at a time could reduce possible issues of having the wiggle/snap attach to the wrong magnet.
Currently on exhibit at Chicago MCA - https://visit.mcachicago.org/exhibitions/gregory-bae/
It's possible that I've got the wrong mental model for how that would work.
Not a clock, but I was messing with soft body physics and ended up with this thing this weekend: https://mrrr.vercel.app [1]
Consider a v2 where the hands are physically simulated al dente spaghetti.
[1] (I ended up making a classic frame-by-frame animation though: http://mrr.sonnet.io - pitching it as an "AI-powered MRR optimiser" on LN)
Does that answer your question? I don't know what I can do that you couldn't do for yourself, so maybe I'm not understanding your question.
Alas, there's no sabo-tabby.
(If I blink I will get distracted!)
Funny how little art projects like this are so intriguing.
Thanks for sharing it!
Thought it would be a little bit bigger than that.
I'm getting the author to move it.
Stand by ...
OK, here:
Agreed that it's probably glitch.me pushing people to a paid option, but there's no real problem with that ... they are a business providing a service.
We do have some default protections in place to prevent (even accidentally) problematic projects from taking too many shared resources.
We've temporarily removed those barriers for this project since it was getting such a big hug. It should stay up and be Remixable now.
disclaimer: I'm on the engineering team at Glitch.
like, an old netbook could serve up all those requests in 100 milliseconds with apache
on a 9600 baud modem (5 kilobytes 300_000 times an hour is under 4 kilobits per second)
are you hosting glitch.me on an amiga 500 on dialup in zimbabwe or something
by contrast the 512 megabytes of ram is about a 64th of a laptop and the 712 megabytes of disk is about a thousandth of a laptop
this results in absurd situations like this one, where a purely static web app collapsed under a load you could literally handle on a commodore 64 on dialup
well, i guess with tls you might need a 25-MHz 386 on dialup
worth noting that anyone can remix the project :) https://glitch.com/edit/#!/wobble-clock