A link to the official notice: https://support.ecobee.com/s/articles/Connectivity-and-Support-for-Legacy-Products
(It was the first link in the article, good job The Verge)
It is also nice that these just degrade to regular thermostats. It isn't like they are completely stopping working. It would be nice if you could swap out the API, or they keep the API running longer (how much work can maintaining it be?). But this sounds like a pretty graceful degradation.
It would be nice to have these speak some common Zigbee protocol or similar. But this isn't the worst behaviour I have seen from companies.
It happened: https://discourse.nixos.org/t/nixos-foundation-board-giving-power-to-the-community/44552 Lemmy post
We'll see exactly what this means. But I would love if it means that the project manages to continue without the huge amount of confusion and disruption that would come from forks fighting for becoming the canonical source.
I just got a Lenovo Yoga 9i and am pretty happy with it. It has a really nice display and wanted to experiment with a convertible as I occasionally wished I had a tablet but wouldn't use it enough to justify it. Having a laptop that can double as a tablet was attractive.
Random notes:
- Fingerprint reader doesn't work.
- There is a sysfs file to set an 80% charging limit which is nice.
- WiFi often seems slow and the signal strength is reported as low. I suspect this is poor AP selection as it seems to connect to a further AP in my house rather than the closer one.
Or use a browser extension to implement your preferences rather than push them onto others in a way that makes it harder for them to implement theirs.
If an article links to medium.com my redirects kick in, my link flagging kicks in and everything else. If everyone uses some different service to "fix" medium I am stuck with what they like. There is valuable to keeping the canonical URL.
I would also love to see domain blocks as a user preference in Lemmy. Just hide these sites that I don't like.
the whole security model of sudo makes no sense
I think that is a bit strong. Sure, you aren't gaining much protection if you just allow sudo -su root but there are a lot of valid use cases.
- Logging.
- A bit of an "explicit" check to keep you from doing something stupid without thinking.
- You can configure sudo to only allow specific commands from different users. (Maybe a trusted friend should have permission to reboot your Minecraft server but nothing else)
If you haven't used any configuration management before it would definitely be valuable to learn.
However I would also recommend trying Nix and NixOS. The provide much better reproducibility. For example using Ansible-like tools I would always have issues where I create a file, then remove the code to create the file but the file still exists or the server is still running. I wrote a post going into more detail about the difference a while ago https://kevincox.ca/2015/12/13/nixos-managed-system/. However this is more involved. If you already have a running server it will be a big shift, instead of just slowly starting to manage things via Ansible.
But I would definitely consider using something. Having configuration managed and versioned with history is super valuable.
Reading feeds.
Mostly blogs and videos. Some comics. Some odds and ends like notifications for various things.
If they can shove ads into the GMail UI I'm sure they could have found a place to put them in Google Reader.
I just use snapshots for taking backups. This ensures that I get a consistent state when the backup occurs. It seems to work well for that.
Video serving is a very sequential workload so hard drives will be more than sufficient and you can typically get storage at a lower price.
SSD may give you slightly faster start and seeking but it is unlikely to be noticeable.
Also https://archive.org/details/yuzu-windows-msvc-20240304-537296095_20240305_1340 AKA magnet:?xt=urn:btih:13001f9414da4cf238d0370fea54f5668406107a&dn=yuzu-windows-msvc-20240304-537296095_20240305_1340&tr=http%3A%2F%2Fbt1.archive.org%3A6969%2Fannounce&tr=http%3A%2F%2Fbt2.archive.org%3A6969%2Fannounce&ws=http://ia600207.us.archive.org/22/items/&ws=http://ia800207.us.archive.org/22/items/&ws=https://archive.org/download/