Whatever happens on my browser is client side, which is hardware and software I own. I can make what I own do what I want. It's a right.
It's like Google saying that I can't skim a magazine in my home, and that I must read the ads. Google can do what they want server-side, and I'll do what I want client-side.
Hey thanks! That's my favorite one! Congratulations!
Your 150 supports WristApps, which are little 6805 binaries that get uploaded into ~780 KiB storage over the Datalink connection! It's tiiiiiny, but enough to have programs for useful things like countdown timers, small games, etc. I'm kinda thinking of making a collection of links to WristApps somewhere to keep these things from getting lost to time.
For the Notebook Adapter emulator, the RPi Picos should work great, too! Adjust the GPIO pin to the onboard LED, and it should just work! The whole thing is mostly just passing serial data around, making an LED light up, and sleep statements :)
I noticed that the Datalink 50 and 70 watches (along with other protocol 1 devices) are very finicky, yeah. The Datalink 150 and 150s is much better, although not perfect. The success of the transfer needs a bright CRT monitor, and your room should ideally be free of flashing devices, like florescent bulbs and some LED bulbs.
My Notebook Adapter emulator, with a bright white LED attached, is a significant improvement. It can sync a Datalink 150 watch several feet away! In fact, the light is so bright, that if you hold it too close to the watch, it'll saturate the optical sensor and cause transfer errors simply due to its brightness. If you point the LED sideways, this fixes this issue and makes transfers work just about every time. Check it out:
Yeah it's an interesting project, but it looks bad with the printed case and exposed tact switches, and seems to have little functionality.