Ebby

I was also leaning towards Garmin, but the price and style kept me with Fitbit for now. I really wanted to jump ship recently though.

As a longtime Fitbit user, the writing is on the wall. The Google buyout has been horrible, features disappearing, support sucking, no more web dashboard, payment issues, calorie goals no longer customizable, etc.

They bought the company for user data and patents. Merge what they want into their watches and discontinue the rest. Absolutely minimize maintenance costs by dropping features and firing employees. They'll keep the Fitbit name, maybe roll that into a watch sub-series, but the buyout was definitely a gut-and-dump deal.

Too bad the antitrust suit won't save what used to be a great product and company in time.

Whoa! Really! That would be awesome. I couldn't find it at all last time I had it out. Interesting it would use govee though. Is there something special I'd have to do to set that up?

Yup! I have the stuff, just haven't gotten around to flashing one yet. Working on a wind meter at the moment.

The original models will. While Home assistant has an Anova integration, it is cloud dependent and it's the cloud that will discontinue support. As I understand it.

Local control uses a Bluetooth bridge which I guess is my next project.

It's kinda nice to just search what you are making, click cook, and all the settings are preloaded and the device starts. The manual interface is clunky.

I looked into that and you need to build a Bluetooth bridge out of a ESP32. Pretty easy once you have the dev platform set up, but not for your average Joe.

There is an anova integration, but depends on their cloud service. When they stop supporting old devices, they will no longer function.

That's what I understand anyway.

Yeah, came here to say this too.

The title is false. That's not what is happening.

Live-action Bojack Horseman can f riiiiiiight off!

Shudder

Great image.

Wow, you just reminded me of a data use policy I wrote up when I was young and sent a data broker after a security breach!

They laughed at me.

You and I think alike here.

Alrighty, brainstorming time people. If you could write some practical laws, what protections do we need to stop these from happening.

I'm thinking 3 categories: Reporting, oversight, and accountability.

Reporting: all entities holding personally identifiable information (PII) must reach out once every 12 months. This hopefully unveils seedy brokers relying on obscurity. Maybe a policy to postpone notification up to 5 years (something like that) may be available as opt-in.

Oversight: targets of PII have oversight of what is collected/used. Sensitive information may be purged permanently upon request.

Accountability: set minimum fines for types of data stored. This monetary risk can then be calculated and factored into business operations. Unnecessary data would be a liability and worth purging.

1. data stays local for the most part. Every file you send to the cloud becomes property of the cloud. Yeah, you get access, but so does the hosting provider, their 3rd party resources, and typical government compliances. Hard drives are cheap and fast enough.

2. not quite answering this right, but I very much enjoy learning and evolving. But technology changes and sometimes implementing new software like caddy/traefik on existing setups is a PITA! I suppose if I went back in time, I would tell myself to do it the hard way and save a headache later. I wouldn't have listened to me though.

3. Portainer is so nice, but has quirks. It's no replacement for the command line, but wow, does it save time. The console is nerdy, but when time is on the line, find a good GUI.