Any non-custodial wallet will work tbh. The best wallet would be a desktop one that is solely used for your chosen network and gives you total control over your funds, like Electrum (electrum.org) for bitcoin. Ideally it would also let you connect to your own node, although that could be used to trace transaction origins. Your wallet is only as private as you are :3
I recently moved all my personal accounts to a VPS instance. I decided on Mailu’s docker compose setup because of its ease of use and it has been working great so far.
I used Oracle’s free tier cloud (4 ARM vcpus and 24GB of memory) and email delivery instances so it’s worth a try, but any other cloud provider offer similar options.
I could have had an x86 server running with that much RAM
You only get that much memory with ARM. With x86 I think you only get 2 vcpus and 4GB of RAM. But for containers, if they run on ARM, it’s great. And Mailu has been running very smoothly so far.
As of downsides… well, it’s Oracle. But other than that, I actually find Oracle Cloud interface and offerings much more intuitive and straightforward than other big providers such as AWS or specially Azure, at least for non power users.
Using a public service like proton or firefox for that has the advantage of you blending in with the crowd, i.e. the service doesn’t know who the account belongs to whereas the service knows exactly that it belongs to you because only you have the top level domain.
In theory … in the real world it doesn’t matter too much because noone will hunt you down.
I guess that it’s no more of a hassle than using one email with your own top level domain.
The SimplyTranslate front end has many languages, translate engines selectable: Google | DeepL (Testing) | ICIBA | Reverso | LibreTranslate. Some instances are Tor-friendly, even onion. The project page seems to be codeberg.org/SimpleWeb/SimplyTranslate
Refusing to use Google is just common sense. LibreTranslate itself is decent (at least not Google), except a website hosting it may have some opaque JS or Google things (Font, Analytics, TagManagers, etc.)
Either way, translation can’t be super-private in general. For example, if you use it to write a private message or love letter in a foreign language… even including real names and physical addresses…
Also, metadata like “a Danish-speaker is reading this German text about X” can’t be hidden, and if the language pair is uncommon and/or if text to be translated is specialized (not generic), the engine provider may easily guess “this request and that request yesterday may be from the same user”, etc. if they want to. A sufficiently powerful “attacker” might de-anonymize you, helped by other info about you, already gathered. In practice, maybe not a big concern, if you’re just translating generic, non-sensitive text, not showing your real IP, and clearing cookies frequently.
privacyguides
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.