I've been downloading my subscriptions and loading them into Plex. Plenty of room for improvement in that system, but I get a nostalgic hit of YouTube long ago. Man, it's fallen so far over the years.
Also related, I've hit 2.4TB of internet use for the first time last month doubling my previous record.
"As such, we’ve decided to waive our right to arbitration and have the matter proceed in court.”
Notice they still claim arbitration is their right, that the streaming agreement is still valid, but would rather appease the masses to mitigate bad publicity.
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.
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.
Renewables dipped below $0 for us in California too this year. Fortunately for the utilities, those savings don't get passed along to customers and I still paid $0.53 kW/h. /s
Don't take on all that guilt. There are things we can do to limit our data, but a lot, dare I say the majority, is scraped from sources beyond your control. You may have great practices and security, but others may not, and those weaknesses or business arrangements are vectors for breaches like these.
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.
Ebby @ Ebby @lemmy.ssba.com Posts 1Comments 608Joined 2 yr. ago
There are several out there using yt-dlp. Tube archivist, tube sync, etc. They are fairly straightforward to set up in docker if you use that.