SoylentBob
On the downside the display is really bad and won't actually display anything at this point anymore, the watch is working fine though. Their app and synchronization process is also horrible. Synchronization is only triggered when you open the app, this process then takes what feels like ages to update the information in the app, and here comes the best part: You don't even get any valuable insights in your workout. Just some basic bar charts and sums.
I feel that a Watch like that still is a product I'd like to buy, but the Fossil experience imo wasn't good enough overall.
If you would rather put them in your cache, instead of not allowing to request them through your server, you are probably best off, by taking the lower TTL and using that as your initial TTL. E.g. this is how an authoritative Knot instance would handle differing TTLs in a DNSSEC signed zone.
> youre-going-to-wish-you-killed-me
Yeah that seems totally reasonable.
How does this compare to other community efforts, e.g. Zalandos Patroni project, aside from supporting more databases than just postgres?