Not really. IMO, the determining factor for this is how “sticky” a given service is.

Leta is a public search engine that you don’t have to pay for their VPN to use, and switching search engines is quite trivial, making this a very easy switch in the event that either service is unsatisfactory.

That said, I have no idea why anyone would want Google search results in 2025 because their search engine is terrible, but more power to anyone that does.

Well, hopefully the get on that. They have to realize that a large portion of their target demographic (people fed up with garbage search) also rightly don’t want their search histories tied to their real identities.

What does this actually do? Is it possible to use Kagi without providing them personal information to create your account yet?

WASM is a better way to run code client-side, and has the benefit of not being a terribly slow, untyped mess 😌

W. JavaScript was a mistake.

Shouldn’t we also have the opposite list; a sort of name and shame or if you use these banks, you’re screwed list?

In part, because it can be more conclusive to take a bank that has consciously made the decision to block access, rather than having a list of banks that maybe just haven’t gotten around to it yet.

Is it? The FTL is restrictive about who is allowed to redistribute and modify anything covered by it. Is this data covered under a different license?

FYI: the people in here recommending the open source competitors for Yubico aren’t mentioning one thing: YubiKeys, being proprietary, support a proprietary protocol called Yubico OTP in addition to the FIDO authentication protocol that the open source competitors can do.

The reason this matters is that some applications, like the Linux Bitwarden desktop app (there are others, but this is one that I’ve had to deal with), don’t support FIDO authentication, but do support Yubico OTP. This means that, for those apps, the open source keys wouldn’t be a valid authentication method.

Granted, the number of applications like this are small, and probably grows smaller by the day, but it’s an important distinction to be aware of.

This must be a joke response…

Yes. The US is also authoritarian. Yes, there is a clear media bias when it comes to the headlines that western media outlets are willing to run. In particular, paining non-western countries as more authoritarian than the US (which is sometimes true).

It’s valuable to point this out. Dog knows the shitty media bias bots used in other communities won’t.

However, the overall tone of your comment seems to suggest that it’s okay for non-western governments to do authoritarian bullshit, just because the US does. I trust that wasn’t the point of your comment, but I assume that’s why some may not take kindly to it.

For what it’s worth: my instance disables down votes, so I literally can’t down vote posts I disagree with.

Google has a disproportionate and overwhelming say in AOSP. What do you think Lineage OS is based on?

When Google makes API changes to Android, it hurts AOSP too. Can the devs try to maintain the legacy API on their own? Sure, but it’s extra effort, so it’s usually not something you can count on.

https://github.com/fathyb/carbonyl

This is more usable than browsh, in my experience, but has the very unfortunate downside of being based on Chromium (🤢)

KeePaasium is what you use for Apple devices (macOS and iOS. Unfortunately, it’s a paid app, but you can enroll in the beta program to get it for free.

In what way? I thought it was just an alternative client for Signal.

If you use GNOME or KDE, check out https://github.com/quexten/goldwarden.

Lobby your government to nationalize it. Anything that important can’t be left to private industry.

There are suitable alternatives listed in other comments, but it is worth noting that none of them will support the proprietary YubiKey authentication protocol.

This isn’t a big deal if all of the applications you want to use it with support FIDO2/WebAuthn authentication, but YubiKeys support both.

This is the correct answer.

FYI: Bitwarden has integrations for SimpleLogin, Addy.io, FastMail, etc. for their username generator, so you can easily generate aliases for every site, regardless of what alias provider you use.

The person you are talking to also believes the narratives that Russia spins about their invasion into Ukraine, so the don’t have very sound epistemology to begin with, unfortunately.

You say that as if companies haven’t been imposing greedflation/shitflation on everyone for many years.

Voting with your wallet isn’t an effective means by which to motivate a company to do anything. You’re just a drop in the bucket, so your distaste for a company will never influence their behavior. You know what does? Shareholders.

Thankfully, Proton is moving away from that harmful influence by becoming a non-profit, so that will be less of an issue for them and they can focus on delivering services that users actually want instead of shoveling in anti-features and forcing arbitrary price-hikes on their customers like most for-profit companies do.

Is there a guide for how to do this in a more declarative fashion?

FYI: this is another FUTO app that uses their proprietary “FTL” license, so it’s not open source.

Unregistered HyperCam 2

Proper desktop autotype for Linux and an SSH agent mode.

I agree with doing this, but the main drawback is that you can’t easily check all of your unique aliases in HaveIBeenPwned without scripting something and paying for API access.

I have hundreds of unique aliases for my accounts, but no simple way to see when/if the services that use them are breached.

You can root on GrapheneOS. You do it exactly the same way you’d do it for the stock Google ROM:

1. Have an unlocked bootloader. Yes, this means that it “”“defeats the purpose of GrapheneOS”“”, if the purpose of GrapheneOS isn’t for you to avoid Google’s privacy nightmare. I use GrapheneOS for privacy moreso than security, and not being able to block ads properly is irritating.
2. Install the Magisk app.
3. Extract the boot.img from the GrapheneOS image and patch within Magisk.
4. Flash the patched boot image in the bootloader.

The main annoyance with this is that you’ll have to do that dance every month when a security patch gets released, but for me, it’s better than vomiting from exposure to ads on mobile.