Use NextDNS with this guide:
https://github.com/yokoffing/NextDNS-Config
Haven’t had anything broken :)
Use NextDNS with this guide:
https://github.com/yokoffing/NextDNS-Config
Haven’t had anything broken :)
Data privacy is a good thing, but user awareness is far more important. People are always the weakest link when it comes to privacy & security.
I’m glad more and more people are getting educated with all the resources that we have today and I like how Apple makes it easy to turn it on when users are educated enough. But they do need to be mindful of what they’re storing, the consequences (if they forgot they password), and what does E2EE protect them from.
Probably people in Korea or even nProtect themselves.
That said, fixing a bug related to software incompatibility with Wine might also benefit other applications (since Wine may behave as “expected” as it runs on Windows). This is why they even tested Audacity to run on Wine even that a native Linux version is available.
I use NextDNS and I do have a subscription, currently using it on my router via DNS over HTTPS.
It is an excellent service (like a Pi-Hole on cloud) and I like how it does things like logging and analytics.
For using it in iOS you shouldn’t need to use the app, just install a (signed) profile via apple.nextdns.io and it will be configured natively (this is Apple’s approved way to use 3rd party private DNS).
I use this profile method and just made an exception to my home & work wifi network but will always use it otherwise (on mobile network or any other wifi networks)
Man that looks sleek. I can’t wait for this update to roll out.
Debian usually backports security fixes to older versions, so you may wanna check to Debian if they have an updated version of the package with the security fix.
This can be done by taking the CVE number related to this vulnerability and look at the package changelog.
There is even a tool to convert Docker Run commands to a Docker Compose file :)
Such as this one hosted by Opnxng:
https://it.opnxng.com/docker-run-to-docker-compose-converter
They do, the author just recently started working on it again and welcoming contributions :)
I think Cloudflare DNS works too and it’s free.
I agree. This requires the user to actually save the attacker phone number as contact in order for this the IP address to “leak”
There’s still a chance that your contacts would have been hacked, and one could be vulnerable. But it all comes back to your risk profile. If you require hiding your IP address, you should turn this off or even use a VPN for all your traffic.
As most have pointed, the “always 2x” rule doesn’t have that much of relevance in 2023 as most computers now has more than 4GB of RAM. I would only use that much of a swap when using a low hardware.
For desktop, I would never go swapless, though. In the event of memory pressure, swap would still help in that situation so that OOM Killer do not kick off and unintentionally kill my working process. Plus it helps that Linux can move the least used data to the swap and use the RAM for filesystem cache.
So my rule of thumb, for desktop: If RAM < 8GB: Swap == 2x RAM If RAM => 8GB: Swap == 1x RAM
For servers, I think it depends on the workload. I keep a small amount, like probably 50% of RAM or less. But for stuff like Redis, it doesn’t make sense to have swap. You want to ensure that everything is in the memory.
They do encryption at rest too. Really good notes app and it’s cross platform too. Only missing a “web” client for when you want to access your notes on a computer without Joplin installed (but that defeats the purpose of the E2EE IMO)