I think point number three is likely what Deckwise is getting at. Every distro is stable when you don’t update it. I generally measure the stability of a distro on the ability to blindly update without taking out something mission critical.

The benefit of passkeys over passwords is that they’re phishing resistant and use strong encryption. They’re effectively an iteration on yubikeys meaning you can have as many (or as few) passkeys associated with a given login as you’d like. So, you can easily prevent there being a single point of failure in the system.

Passkeys are tied to accounts and devices and those devices are the only devices used for authentication. This means you can access your account form a public device without that device ever knowing your credentials provided you and your secure device are physically present so it avoids the whole keylogger issue.

I think you may be mistaken, friend. The USB 3.0 controller is part of the A17 Pro SoC. It was specifically called out during the keynote when discussing the A17 Pro. You can read about it here too: https://www.tomshardware.com/news/apple-a17-pro-3nm-iphone-15-pro

It’s clickbait because they’re using last years chip like they always do. It’s not out of spite. The usb controller on the A16 Bionic does not support USB 3.0 because lightning never needed it. The A17 Pro in the pro models has an updated USB controller.

Optical cameras alone have issues as well that can’t be handled though. It’s the combination of the two along with other things like ultrasonic sensors that makes them safe. More sensors in general are better because they reduce the computational burden and provide redundancy - even if that redundancy is to safely stop.

Cost is certainly an issue, but on $40k+ vehicles it’s cheap enough for other EV makes to include it in the cost. Volvo for instance is using Luminars version at a cost of about $500 (https://www.wired.com/story/sleeker-lidar-moves-volvo-closer-selling-self-driving-car/).

Image processing is expensive even with dedicated hardware and LiDAR provides enough extra information to avoid needing to make make certain calculations off of images alone (like deltas between image series to calculate distance). Those calculations are further amplified by conditions where images alone don’t provide enough information - similar to how there are conditions where the LiDAR data alone wouldn’t be sufficient.

Just commenting to say I thoroughly enjoy your choice of username. Loved that little joke.

I remember printing out the Gentoo installation manual in the compsci lab way back in 2004. It was my first Linux distro and have fond memories of tinkering around on it. I remember leaving it a few years later for a cool new distro that was on the rise called Ubuntu. I still think portage is one of the better approaches to package management though.

These plaintiffs would be better off sueing the companies of these websites for ignoring privacy laws and continuing to add tracking scripts to their sites.

That’s precisely what these people are doing. They’re not suing Google because Chrome doesn’t prevent these sites from building profiles and tracking users even while in Incognito Mode, but because Google themselves are engaging in such privacy invasive tactics.

We’ve been getting pelted hard in the states. Just had one hammer a town to the south before it was hit by a tornado.

I think it comes down to what you want to do with these things. You’re just getting into home automation, so I would plan on whatever choice you make now not being a reflection of where you end up on your journey.

The kasa devices don’t have great open firmware support but do offer a low level api for integration into things like home assistant. I’d personally lean towards it, but that’s mostly because I deal with software for a living and feel I can get enough value out of how it integrates with things in both the tinker space and out of the box.

If you’re more interested in tinkering at the firmware lev though it looks like the sonoff is the one to get. They’re ultimately just a plug you can turn on/off and monitor the energy usage with so however you end up tinkering, it’s a gateway into the larger home automation.

Absolutely, though it’s one of the main communication protocols, so I would imagine their numbers to increase. It seems like the HomeKit specific vendors like Eve have gone all in on it in preparation for Matter.

I mean, the obvious thing here is that “it just works” compared to flashing (and knowing how to flash) custom firmware onto devices. In my mind there are two big things that Matter has going for it:

1. Local-only support. If a device supports Matter it needs to be fully controllable locally per the specification.
2. Thread support. All the perks of zigbee and z-wave with the benefits of a much more reliable and robust network thanks to its mesh design. Every Matter device can act as a relay for any other Matter device. The only thing that needs to talk to anything over the LAN (or internet) is a border router.

Those two things aside, Matter is open source. It was formerly ProjectCHIP. So, if the device has the correct hardware to support Matter (not all current IoT devices have the necessary hardware) in theory open source firmware for those devices should be easier to develop.

I don’t believe they’re insinuating that you were the one that created the mistake. Rather, that you seem to be knowledgeable of the specific problem and may be the one most capable of fixing it. The two line fix may be obvious to you, but may not to the main Lemmy devs. Until phriskey got involved, a lot of db tuning was being avoided (they’re responsible for most of the big db improvements this version).