I actually like the CMF watch for a bunch of reasons, but I would not have bought it if I’d realized that you need to sign into a web service via an app to change a bunch of the settings, including the time. Because now that service is broken and my watch is running an hour off because of a json parsing error.
There are two different tables in this database about menstruation, including a notably menacing 'menstruationID' field. The Nothing documentation doesn't admit their existence.
Apropos of nothing the best time to start listening to @evacide is twenty years ago; the second best time is now.
A personal hobbyhorse of mine is that not enough people understand that systems internals are a pageant and that the perceived trustworthiness of a system is a different job that's only loosely related to any functional guarantees the code provides. The difference between a DB table called BitchAssWankleDonk and one called "userAcctState" might be a sed one-liner but it's also the difference between a team that dgaf what anyone finding the BitchAssWankleDonk table might think and one that does.
Incidentally: Y'all, the sqlitebrowser tool is really fantastic? If you've ever thought, I wonder what's in there really, this tool lowers the complexity bar for exploring databases as low as I've ever seen it. It's great.
Well, what I've learned so far is that the original application for CMF watches is broken and deprecated, so I'm supposed to use their new NothingX app which I need to use/dissect to obtain the token that will let me switch GadgetBridge, whose documentation and processes for this watch are now outdated, which has led me where I am now, which is "I am currently dissecting the internal database of an Android app so that I can set the time on my watch", here in the best of all possible futures.