<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Online Privacy on What Just Happened NOW</title><link>https://wjhnow.com/tags/online-privacy/</link><description>Recent content in Online Privacy on What Just Happened NOW</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wjhnow.com/tags/online-privacy/index.xml" rel="self" type="application/rss+xml"/><item><title>Internet Users Are Shifting Towards Open-Source Tools. Does That Really Reclaim Their Digital Privacy?</title><link>https://wjhnow.com/p/open-source-tools-reclaim-digital-privacy/</link><pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate><guid>https://wjhnow.com/p/open-source-tools-reclaim-digital-privacy/</guid><description>&lt;img src="https://wjhnow.com/img/open-source-tools-digital-privacy.jpeg" alt="Featured image of post Internet Users Are Shifting Towards Open-Source Tools. Does That Really Reclaim Their Digital Privacy? " /&gt;&lt;p&gt;People are actually moving. Not just talking about it. And Vitalik Buterin said the same thing publicly, that he ditched Gmail for Proton and Google Maps for OpenStreetMap through Organic Maps. You don&amp;rsquo;t switch your entire email and your maps setup just for fun. That&amp;rsquo;s annoying to do. You do it because something is pushing you. I think people are just tired of being told &amp;ldquo;trust us&amp;rdquo; by apps that never really explain what they do.&lt;/p&gt;&#10;&lt;h2 id="thats-why-open-source-feels-like-the-answer"&gt;That&amp;rsquo;s why open source feels like the answer&#10;&lt;/h2&gt;&lt;p&gt;Code is public. Anyone can look. Signal&amp;rsquo;s protocol is open and it&amp;rsquo;s been picked apart for years by actual cryptographers, not just random GitHub comments. Closed app says trust us. Open app says check it yourself. It flips the whole power thing. It&amp;rsquo;s a good idea. Honestly it&amp;rsquo;s the right idea.&lt;/p&gt;&#10;&lt;p&gt;Except there is a big difference between can and do. That&amp;rsquo;s the whole problem hidden inside that sentence.&lt;/p&gt;&#10;&lt;h2 id="everyone-has-the-tools-now"&gt;Everyone has the tools now&#10;&lt;/h2&gt;&lt;p&gt;Like literally, open source models, scrapers, fact-checker widgets, browser extensions that claim to strip trackers — all free on GitHub. People are using them way more than before. Users are more aware than even two years ago. They know what to ask an AI, what prompt to use.&lt;/p&gt;&#10;&lt;p&gt;The problem is they won&amp;rsquo;t sit and verify the answer. And who can blame them?&lt;/p&gt;&#10;&lt;p&gt;A ten-second answer from AI Mode pops up, sounds confident, has a citation link that looks legit, you just go with it. I&amp;rsquo;ve seen it sometimes call a facts blog a &amp;ldquo;breaking news tracker&amp;rdquo; and people would still believe it because the tone was so sure. That&amp;rsquo;s the new thing — we got better at asking, but worse at double checking, because the answers feel too good to question. Tools are everywhere, patience isn&amp;rsquo;t. That&amp;rsquo;s the bottleneck now, not access.&lt;/p&gt;&#10;&lt;p&gt;And privacy is worse than fact-checking. Fact-checking a headline takes like 3 minutes of Googling. Checking what an app actually does with your data? You have to read code. Or at least understand what you&amp;rsquo;re reading. Most people don&amp;rsquo;t even finish the privacy policy of the apps they already use — they scroll and hit accept. So expecting them to open a repo and audit it is kind of fantasy. So &amp;ldquo;open source&amp;rdquo; just becomes another word we use to feel safe. Like &amp;ldquo;secure&amp;rdquo; used to be. Or &amp;ldquo;encrypted&amp;rdquo; a few years ago. A label that makes us feel better without us actually confirming anything.&lt;/p&gt;&#10;&lt;p&gt;Trust doesn&amp;rsquo;t disappear with open source. It just moves. From a company in a building somewhere to some crowd on the internet you hope looked at the code.&lt;/p&gt;&#10;&lt;h2 id="sometimes-that-crowd-wasnt-really-there"&gt;Sometimes that crowd wasn&amp;rsquo;t really there&#10;&lt;/h2&gt;&lt;p&gt;Or it was super thin.&lt;/p&gt;&#10;&lt;p&gt;OpenSSL is the classic one. In April 2014 Netcraft estimated that more than 66% of internet servers used some version of it &lt;a class="link" href="https://scrippsnews.com/science-and-tech/open-source-software-funding-to-stop-bugs-like-heartbleed" target="_blank" rel="noopener"&#10; &gt;https://scrippsnews.com/science-and-tech/open-source-software-funding-to-stop-bugs-like-heartbleed&lt;/a&gt;. Then Heartbleed blew up — attackers could read chunks of memory from vulnerable servers. And before that, the whole project that the entire internet depended on was &lt;a class="link" href="https://en.wikipedia.org/wiki/Core_Infrastructure_Initiative" target="_blank" rel="noopener"&#10; &gt;getting like $2,000 a year in donations&lt;/a&gt;. Two thousand. The code was open to the whole world. Almost no funded review in any serious way. Everyone assumed someone else was looking.&lt;/p&gt;&#10;&lt;p&gt;Then xz. That one is weirder and kind of scarier because someone was there — inside. Someone with maintainer-level access appears to have slowly planted a backdoor over several years into xz Utils, a tool that&amp;rsquo;s in basically every Linux distro &lt;a class="link" href="https://www.darkreading.com/cyber-risk/xz-utils-backdoor-implanted-in-intricate-multi-year-supply-chain-attack" target="_blank" rel="noopener"&#10; &gt;https://www.darkreading.com/cyber-risk/xz-utils-backdoor-implanted-in-intricate-multi-year-supply-chain-attack&lt;/a&gt;. The backdoored versions (5.6.0 and 5.6.1) were only in unstable and beta releases of distros like Fedora, Debian and Arch. It got caught not because of regular audits but because a Microsoft dev, Andres Freund, noticed a response-time slowdown in SSH logins. If he hadn&amp;rsquo;t noticed that, it could have reached stable releases everywhere. They fixed it in days, yeah, open source is fast when it works. Community jumped on it. But if safety depends on one person noticing lag by accident, what does that mean for a normal user who will never open the source code in their life?&lt;/p&gt;&#10;&lt;h2 id="also-you-only-ever-see-half"&gt;Also you only ever see half&#10;&lt;/h2&gt;&lt;p&gt;That&amp;rsquo;s the part people don&amp;rsquo;t say out loud.&lt;/p&gt;&#10;&lt;p&gt;Proton Meet is a good example for that. The client you install — yeah, open source, you can verify it. The server part that actually routes your calls? Closed. So you&amp;rsquo;re still trusting the company on the other half &lt;a class="link" href="https://www.kunalganglani.com/blog/proton-meet-privacy-review.md" target="_blank" rel="noopener"&#10; &gt;https://www.kunalganglani.com/blog/proton-meet-privacy-review.md&lt;/a&gt;. That&amp;rsquo;s not a scandal. It just means &amp;ldquo;open source&amp;rdquo; can describe one half of a product, and the other half still counts a lot.&lt;/p&gt;&#10;&lt;p&gt;And there&amp;rsquo;s another quiet problem. Even if both client and server are open on GitHub, unless you host it yourself you don&amp;rsquo;t actually know if the code on GitHub is what&amp;rsquo;s running live on their production servers. You have to trust their build process. Plus encryption only hides what you said, not who you talked to. Matrix protocol for example — messages can be encrypted, but it doesn&amp;rsquo;t protect metadata, so a homeserver admin can still see who you talk to and how often &lt;a class="link" href="https://git.hackliberty.org/Git-Mirrors/privsec.dev/commit/e20f1f303685d8a78c8f6814044eb87f2a4cbafe" target="_blank" rel="noopener"&#10; &gt;https://git.hackliberty.org/Git-Mirrors/privsec.dev/commit/e20f1f303685d8a78c8f6814044eb87f2a4cbafe&lt;/a&gt;. So a fully open, fully encrypted app can still leak a lot about your life without leaking a single word of content.&lt;/p&gt;&#10;&lt;h2 id="so-what-do-you-actually-do-if-youre-not-a-coder"&gt;So what do you actually do if you&amp;rsquo;re not a coder?&#10;&lt;/h2&gt;&lt;p&gt;You don&amp;rsquo;t need to become a researcher. Honestly don&amp;rsquo;t. That advice is useless after what we just said about patience.&lt;/p&gt;&#10;&lt;p&gt;Instead, maybe smaller things that actually stick.&lt;/p&gt;&#10;&lt;p&gt;Look for an independent audit, not just a public repo. That means someone qualified already did the boring checking for you. Check who maintains it and how they get paid — is it one tired volunteer or a funded team? Is it just the app that&amp;rsquo;s open or the server too? And ask what they can still see even after encryption. That last one tells you more than &amp;ldquo;we use end-to-end encryption&amp;rdquo; ever will.&lt;/p&gt;&#10;&lt;p&gt;And maybe just use fewer apps. I know that sounds counter-intuitive in a privacy article. But every new privacy app is another thing you&amp;rsquo;re trusting. A short list you actually understand and keep updated is way better than a long privacy-stack of 15 tools you installed and forgot.&lt;/p&gt;&#10;&lt;h2 id="so-does-open-source-bring-privacy-back"&gt;So does open source bring privacy back?&#10;&lt;/h2&gt;&lt;p&gt;On its own, no. Not really. It gives you the right to check. That&amp;rsquo;s important. But that right only becomes real protection if somebody actually uses it. Or if there&amp;rsquo;s a system that makes sure somebody does.&lt;/p&gt;&#10;&lt;p&gt;We have the tools now, we have more knowledge than before, forums, explainers, everything free. What we don&amp;rsquo;t have is time. And until we fix that boring part — time to check, or an easy way to know who already checked for us — picking an open source app is a good decision, but part of it is still just trust. Different trust, maybe better trust, but still trust.&lt;/p&gt;&#10;</description></item></channel></rss>