Sam A.

But without Play Protect (unless you sideload gApps).

Yes, I know, but how do you know that it doesn’t accidentally generate a face that’s identical to an existing person’s face? After all, it’s trained on images of humans.

How can we be sure that that person actually does not exist?

Not really without knowing which instance you’re talking about, but one guess is that you might be following a hashtag that has become more actively used.

I would not do that. The whole idea behind Tor Browser is to make users look similar. By using a custom DNS provider you stand out from the crowd, thus making yourself more unique/identifiable. A website may not be able to see who you are, but it’s gonna have a way easier time seeing that you’re the same person visiting as the person who was there yesterday.

I use Brave browser, my SearXNG instance works fine. Feel free to try it out: https://search.sapti.me/

If it doesn’t work, it might be something with your browser.

IVPN, Mullvad and Proton are some good ones.

Joplin synced to a self-hosted sync server with E2EE on, that’s my setup. Works great.

To be fair to Proton, it’s not necessarily them who’s blocking your emails. In my case, I’m able to send emails to fx. an @hotmail.com address, but not other domains. And from the error messages I get (though I don’t use Proton), it looks like it’s the receiving mail server that’s blocking my incoming mail, not my own server blocking my outgoing mails.

Thanks for replying, I ended up with Simply.com, a Danish provider (I live in Denmark). They didn’t want any KYC besides the usual you give when paying with a credit card, full name, address, email, phone. It’s a .me domain, so maybe that’s why.

My domain is still being transferred, so I’m crossing my fingers, but it’s a quite big provider, so I’m not really worried.

May I ask what domain registrar you switched to? I’m having the exact same issue, albeit not with Proton but another email provider.

Not that I’m gonna discuss your personal opinion, but what do you mean specifically by “ungoogle-able phone”?

Perhaps you could also print an encrypted version of your Bitwarden TOTP secret on a QR code and bring it with you in your luggage?

So, encrypt the secret with a passphrase you can remember, encode the entire thing in a QR code and print it on a piece of paper. Easy.

So your password manager uses your phone as 2FA, and the credentials inside your password manager also use your phone as 2FA? Hmmm…

So essentially, you can’t bring your phone, that’s the main issue. Does your authenticator on your phone support exporting a backup? Then store that in your password manager if that’s possible and set up an alternative 2FA for your password manager (SMS on the burner phone number perhaps or a security key). Then when you arrive, reinstall the authenticator on your burner phone and import the backup.