Poor license choice. If you really want to enforce it, don’t rely on MIT.

Yup, I think this is the root cause for Mozilla’s inevitable failure: the wrong management for the job.

Agreed. It is very powerful but the interface has a long way ahead to be user friendly. Still, it is worth the effort if you really care about sticking to linux.

As a person who experienced the customer support regrading preorders I can confirm this firm is extremly sketchy.

If you like what NOYB is doing: they are accepting donations.

There is indeed a big difference between requiring a specific password vs. requiring a specific device or software to be able to use the service. Keep in mind that big tech can very conveniently leverage this technology to lock you in. For example think about Apple, Google and Microsoft requiring you to use passkeys, and then later require you to use your certified phone and app. Most people will not be able to “go elsewhere”.

You seem to be falling for what the author was writing about. Only because you could technically try to use keepassxc to store passkeys, that does not mean that it will work. You see passkeys were build in a way the service you’re trying to login to can decide if they accept your keepassxc for passkey storage or not. It looks like you are in control when you are actually not.

Correct, I use Kast on the desktop, works nicely

If you’ve got a nextcloud somewhere, you already have everything you need running. Install required extension and login in antenna pod. Works nicely, can recommend it.

Just don’t use flatpaks. Let your distribution handle updates like it is supposed to do.

I would contradict you. The internet is not overreacting, Mozilla and parts of its community try to downplay the issue at hand.

Hopefully the court was clever enought to specify that the side loading must not be more difficult than installing via the store. Apple will for sure make it as complicated and user hostile as possible so they fulfill the ruling without having any practical impact.

Finally some good news

Kudos to Niccolò for openly speaking about his mistake of incorrectly stating his video was not sponsored. However I think he made a second mistake which is more serve. As a content creator he must pay more attention to what companies he’s accepting sponsorship from. Given the track record of malibal, this should have been a red flag in the first place.

Learned something new. Thank you!

I also use openScale from F-Droid, in combination with this Bluetooth scale:

https://sanitas-online.de/de/p/sbf-70-bluetooth-glas-diagnosewaage/

Signal forks can have unexpected behaviours like retaining deleted messages and also they don’t get updated at the same rate that Signal get updated.

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.

Every couple of years I hear a story about hackers disturbing signal with backdoors, which would be impossible or very hard to be done If they blocked third party clients. (Ex: 1)

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.

The amount of people who use third party Signal clients are very few anyway.

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.

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.

Here a a few things that I miss from OsmAnd:

• adding more than a handful of routing points is tedious
• you cannot plan partially or fully independent from existing roads
• no way to save and restore a planned trip
• no overlays for hill shading or incline visualization. Very useful for assessing the effort of a route.
• no public transport support. Very useful for planning a trip with transitions.
• no rain radar
• satellite view