Not in all situations. And in a way a user will not be aware of. The service or website can define what type of passkey is allowed (based in attestation). You may not be able to acutally use your “movable” keys because someone else decided so. You will not notice this until you actually face such a service. And when that happens, you can be sure that the average user will not understand what ia going on. Not all passkeys are equal, but that fact is hidden from the user.
In addition, Huawei now blocks sideloading Android apps to promote its ecosystem growth.
Well looks like I’m never going to get a device from this manufacturer then.
Sad to see Mozilla being managed into the ground, betraying their principles and selling their users.
That is not entirely correct. The reported found the app using permissions that are not covered by the manifest. It also found the app being capable to execute arbitrary code send by temu. So it cannot be clearly answered if the app can utilize these permissions or not. Obviously they would not ship such an exploit with the app directly.
“Could”. More likely it was closed loop. As I understand it this is an estimate, thus the word “could”. This has nothing to do with using closed or open look water cooling. Water isn’t single use, so even if true how does this big number matter.
The point they are trying to make is that fresh water is not a limitless resource and increasing usage has various impacts, for example on market prices.
The outdated network holding back housing is that it doesn’t go to the right places with the capacity needed for the houses. Not that OpenAIUK is consuming so much that there’s no power left. To use a simily, there’s plenty of water but the pipes aren’t in place.
The point being made is that resources are allocated to increase network capacity for hyped tech and not for current, more pressing needs.
This sadly is in line with Mozilla’s increasingly bad privacy defaults. Users who care have moved on to more reasonable configurd forks at this point (e.g. Librewolf).
There are ways to save messages before they are deleted even if the stock app is used. Do not ever rely on this feature to work in a “safe” way.
That is a problem the users who prefer 3rd party clients have to deal with. Obviously if you care enough to not use the official build, you of cause have to take care of using a trustworthy source. That is not “your problem” though.
That sounds a lot like “I don’t use it, so none else needs it either” argument. In my opinion, none of your arguments above are a good reason to combat 3rd party clients.