If you have to ask that; you really must have been living under a rock for the past 3-5 years.

I personally use Firefox still; and keep a fresh copy in a (Pixel only feature) Private Space (Basically an implementation of Android alternate user profile) as well. It works and accepts any privacy addons I throw at it.

Currently using:

• uBlock Origin
• Chameleon
• Privacy Badger¹
• LocalCDN
• Decentraleyes¹
• CanvasBlocker¹

¹ - May duplicate functions of other plug-ins; but provide additional protection layers and cover for the limitations of other addon(s)…

Being worried about addons adding to your fingerprint is something that I quite honestly find is not a significant issue usually…unless you’re explicitly doing something truly spooky if found out…then you should use Tor Browser ONLY.

As someone who formerly modded on reddit for over a decade; I do know what trips the alerts typically. The steps I give are important to establish a fresh account with nothing an idle internet sleuth can link back to you; as well as preventing Mod(Bots) from detecting you. Reddit Automoderator has ‘Admin eyes’…even if it lacks the permissions to act like one. It can, and will use algorithms on those eyes to assess your ‘threat level’. Knowing the trajectory of reddit when I quit; it probably uses AI now. Before it was a dumb blackbox of algorithmic rules the Admins never really made fully clear about how it worked. This dumb blackbox made frequent mistakes.

I’d say you can try do it; but I caution you on doing so. It will be problematic

You cannot be completely undetected if using the reddit app. You must avoid using a mobile device; these are too easily trackable and the browsers on mobile devices lack sufficient privacy protections.

• First and foremost you’ll have to setup to access reddit from a completely unique device. I recommend a virtual machine on a computer using a privacy respecting browser like Librewolf.
• Secondly, you’ll need a good paid VPN…I recommend Mullvad. Do not create your account with this VPN! It will trip alarms.
• Third, you’ll need a laptop with a similar private browser. do not use your main Windows user account. Create a new local account. This is to enforce that you do not access reddit for account creation using a “known” browser fingerprint.
• Fourth, you will need to travel. It must be somewhere out of town; and you should be using a public wifi network when creating the reddit account. Be aware of the ISP coverage in your area and travel far enough that you do not use the same ISP as your own. If you don’t know their coverage area; look it up online. Travel to a place they don’t offer service.
• Fifth, Once you have traveled, use the clean windows account you created to create the new reddit account. Do not name your account similar to your banned account, or subscribe to any subreddits that are outside of /r/popular.
• Farm some karma. Ideally 1k is enough. 100 will do in a pinch but you’ll need to keep farming it; which is a dumb idea to do on a VPN.
• Verify a fresh email address. Use only tuta.com as your mail provider.
• Stay off the reddit account on your home PCs and network. Use reddit only in a public wifi setting on the laptop as described above. Do this for no less than 30 days while farming karma. No need to travel out of town; local public/private wifi will do. (Just not yours).
• Once the account has aged a month; you can log in with the VPN as mentioned above at home using the virtual machine at home. Continue using the VPN for the foreseeable future. Enjoy sticking it to Spez.

I would recommend resurrecting it.

Once you do so; Lock it down, make everything private that you can.

Secondly change all the privacy settings and opt out of any AI training.

Then slowly go back through your history and scrub out your posts; replacing them with gibberish and junk. Do not use AI text IMHO; use something like ‘lorem ipsum’ or some kind of ‘Markov chain babbler’.

I would just suggest scrubbing back through your history slowly once a day; editing a few posts here or there. Look into what exactly the rate-limits might be; so that you can avoid triggering whatever automated suspensions that exist and edit one or two posts less than that a day.

Avoid using automation, as this too can be detected possibly…but do remember you can use other tools that run on your PC only to help streamline your editing.

In general, it’s better if you can manually review and scrub over your old posts slowly. That way you can best decide how each posting and image will be scrambled. Maybe one post gets lorem ipsum in strategic places and the other gets 1000xTranslated into a barely plausible word salad.

Perhaps other times you feed the post into a markov babbler and let it babble on for a few minutes. Perhaps you leave a few otherwise innocuous posts alone so that the poison doesn’t look so suspicious while you sanitize anything that you might consider sensitive.

Once a few months have passed and you’ve deleted all the sensitive information from the account that you can possibly edit or change; then you can proceed to deleting the account and waiting out that process.

1. Get help. Your mental health and physical health must always come first.
2. Privacy is not an all or nothing thing. Your mental health and physical health must always come first.
3. Continue practicing good privacy habits at a rate, level and depth that fits your situation and needs. No need to constantly adhere to Snowden levels of privacy seeking and hiding under rocks. There never was a need for this unless you are in a situation like Snowden. Your mental health and physical health must always come first.
4. It’s totally fine to be as genuine or as pseudonymous as you feel as your needs and wants demand. However, Your mental and physical health must always come first.
5. Relax. Current events have a way of making you paranoid but there truly is not usually a state level actor hovering over you waiting for your tiniest of mistakes. If you usually obey the law and do no significant harm to others, I doubt you have any significant worries. Your mental health and physical health must always come first though. Don’t obsess over it if it makes you feel mentally unwell.

lol

There’s something you need to know about the “anti-features” flags on F-Droid.

They’re too “greedy” and widely defined. What you really need to do is examine the app and how the developer might use said “Anti-Feature”. Not all internet access and telemetry is an anti-feature, and neither is reliance on a “third party service” where you can simply configure your app to use your own self-hosted server instance.

An app having no “Anti-Features” flag on F-Droid is absolutely not an informative indicator that it respects your privacy. Merely, it indicates common privacy foot-guns may not be present.

Frequently F-Droid also is far too opinionated in it’s application of the anti-feature flags; giving developers no reason or chances to appeal or change the decisions. It does not matter if the anti-feature flag is mis-applied in any specific situation; nor does it matter if the developer shouldn’t be getting an anti-feature label because they have everything open sourced and it’s clear to see there is no anti-feature there.

False.

The ad attribution system was proposed but never implemented due to user outcry.

Some telemetry has been a part of Firefox for quite some time now; but it has always been privacy respecting and they self-host all of it. In general you can easily turn most, if not all of it off. The telemetry thing has been around since before they even started seriously fast-cadence releases. Some of my memories of this date back to the Firefox 34 days even. None of the telemetry collected is mandatory, and it can be shut off in preferences as well as through advanced config; which is what most forks do if they don’t specifically rip the code out. You should read their source code sometime; it’s quite interesting.

I will however agree that Brave is way more intrusive than any misstep made by Mozilla in developing Firefox.

No.

Brave is factually bad. It’s a failed attempt at monetization of users seeking some form of privacy in browsing. From the entire crypto integration with BAT tokens to the weird VPN stuff and more; it’s clear that the company who makes the browser is pivoting rapidly and iterating the software to make money from somewhere, somehow.

Brave does treat it’s users like a product, and the company has made privacy-impacting decisions. They are very clearly a for-profit company with a well known CEO who operates on a for-profit basis only and never on a non-profit basis. You cannot say that Brave is operated on a non-profit basis. The entire concept of the Brave browser itself is to enable monetization methods that users and privacy advocates clearly want to see depreciated.

Mozilla on the other hand; has only recently begun to take some weird steps. Given that their exclusive contract with Google is likely to be dissolved in courts; they are simply stuck in a financially challenging situation. At no point has Mozilla or Firefox actually done anything actively hostile to privacy or users. While Mozilla does make mistakes; nothing notably wrong that they’ve done has actively been anything but a simple mistake. They have not yet crossed the threshold into malicious profit motive as of yet. Although many privacy enthusiasts are watching Mozilla very closely for any sign of them crossing that line right now.

And this is why Fwyfwy refuse to move away from Windows 10. Fwy refuse to use any version of Windows that truly integrates their AI bullshit…and Fwy actively breaks and blocks installation of it too; during updates via NTFS security, policies and other tactics to otherwise deny or break their store app from installing anything automatically. If I need some shitty UWP packaged app; I will pull it down and manually install it myself using PowerShell kthx.

Fuck your AI shit Microsoft. If I want AI; I’ll choose the models and run it locally on my own hardware and train it to my needs. If I need a screenshot; I have several app options to do so on command with a single keypress. I don’t need my PC taking timelapse photos of what I’m doing.

I don’t personally cut my usage of YouTube content at all; I just simply use necessary tools to prevent the apps and services from over-sharing too much data at a network level. DNS and IP level filtering is done typically to prevent well-known domains and telemetry targets from being utilized and any account preferences are set to minimize consent given. NewPipe and FreeTube are used interchangeably with yp-dlp if needed. No account is necessary…my viewing patterns aren’t being recorded except in a generalized aggregate manner which enforces a reasonable amount of privacy.

I’m of the opinion that a completely de-googled device lacks critical features I use often; and restoring equal function is oftentimes made difficult. Unfortunately this also covers video content; there’s no real viable FLOSS alternative with enough content. The creators typically do not have a motivation to use PeerTube or other viable FLOSS software that does exist currently and do not publish videos there; which introduces a heavy timelag; even if the creator or even someone else IS willing to export the YT content out to PT.

Network is standard double NAT grade B. [ISP <-> Router <-> Firewall <-> Client] with all necessary port forwards in place (TCP/UDP 1025-65535 to Firewall). Firewall is standard pfSense CE; and will forward invisibly and does automatically perform necessary UPnP and port forwarding as detected. STUN may be necessary but does function and establish the route(s) and the ports your application selected would ordinarily be invisibly NAT’ed quickly by the firewall as long as the packets are solicited. ICE Candidates udp <Public IPv4>:65359 srflx udp <Public IPv6>:65363 srflx udp [<Public IPv6 /64 issued by ISP>]:54597 srflx udp [<Public IPv6 /64 issued by ISP>]:58798 srflx Error: No active TCP candidates were found

To my knowledge your application does not appear to opinion or declare if it uses STUN. (Perhaps it should, there are valid reasons to offer STUN or not offer STUN). The application provides no meaningful errors so I can’t tell what might need adjusted or allowed network-wise.

Obfuscated code is not “Source Available”. You will need to provide the code without obfuscation; though I don’t personally blame you if you’re choosy about what reasons you will release the source for.

I’m of the opinion that you should probably provide Source Code on a “Source Available” basis to people who ask and have a need to see it to audit or self-compile. The lack of “Open-ness” in your code is disturbing.

I won’t comment or judge on your decision to refuse to offer this software on a Libre basis. You absolutely have the right to monetize as necessary; especially if this code is speaking to a backend infrastructure that you maintain for it. Even if all you do is aim to break even and pay for those servers.

The experience is extremely unintuitive. I couldn’t get your app to work at all on my privacy enforcing browser within the confines of my privacy enforcing LAN. (Yes; I do/did enable WebRTC and the other required technologies, however they’re enabled in a privacy respecting manner.) Neither of my devices would show or remain connected once added. There were no popups or information given to me by the app to troubleshoot the issue; and I’m not going to crank open a Dev Console for something that I can’t contribute to anyways. If your software is going to remain closed in source; “It should just work™”.

S/MIME is insecure, outdated, depreciated, and should be discontinued; yet people don’t want to adapt or grow or change.

Because some organizations do use S/MIME; all email software is required to implement it, that is if they want to be adopted and used by said influential organizations.

OpenPGP and PGP in general is secure but suffers from usability issues and is often wrongly painted as user-unfriendly. (it’s really no worse than S/MIME, installing and managing keys is exactly the same hassle as it is with S/MIME.) The main issue is that some people are too lazy or resistant to change to adapt to it.

Lack of detailed audits…only in this case specifically…does not imply lack of security and/or privacy.

The protocol that Signal uses, which is in fact firmly audited with no major problematic findings, plus the fact the client is OSS is generally enough to lower any concerns.

The server side software in production for Signal.org is not OSS. It will not be. You are required to trust the server to use Signal; because the protocol and the client renders it factually impossible for the server to spy on your messages. The server cannot read messages; or even connect who is messaging who if the correct client settings are used. (Sealed Sender).

Non-OS stats software in general is not automatically lacking in privacy or security, particularly not in this case where the affected software does interact only with software that is verifiably open-source and trustworthy in general due to the protocols and how they are implemented correctly in a verifiable manner.

E2EE is, theoretically, secure. It certainly prevents a government from hoovering up your data when they casually cast too wide of a dragnet while “chasing a criminal”. …At least, when it is implemented honestly and correctly.

Now if governments wanted to properly backdoor some E2EE implementation; all they really need to do is compromise one end of the conversation. Of course, they want to be able to do it auto-magically; through delivering a court order to a single point; and not through busting down the door, or capturing the user of, one end or another of the conversation and compromising the device.

The question therein lies; do you as a person want the government to be forced to bust down a door? Some people think they should be forced to break doors and others do not feel that it is necessary. There are many diverse stances on this question; all with unique reasons.

It’s clear to me that E2EE works properly…the governments would not be trying to “end Encryption” if it did not work. Therefore it stands to reason that E2EE is not compromised, if a government is forced to pass a law in order to compromise the encryption or turn it off entirely. That proves it works.

I just logically proved Encryption works, without even taking a stance on the matter. For the record however; I do support Encryption. I think this law undermining it is a massive governmental overreach that will quickly lead to that same government finding out how critical Encryption actually is to their people. Just give it time.

This just means you wrap your signal links in a URL shortener.

A slight hassle; but all the more reason to hate the muskratt.

We should be quietly linking anyone with a need to send a signal link to a nice privacy respecting URL shortening instance somewhere that will basically delete the link in 3-7 days unless told otherwise to keep it around by the user at creation.

Heck; host your own URL shortener while you’re at it.

Vanilla Ice ICE baby…

I.C.E. is obviously overstepping their boundaries here and needs to be pared down.

Someone should get on publishing EFF’s surveillance avoidance tactics in all the languages…or at least teach the immigrants in their lives to make sure to use throw-away emails, prepaid sim cards and pseudo-identities to criticize government.

Genuinely it’s not hard to not provide real world information online; you just keep your identities separated by a few things first. VPNs and Tor help as well to prevent tapping into data.

Actually it’s not that hard and it’s even probably possible to even host SearXNG on the same hardware, or kind of hardware, that you’ve hosted your Pi-Hole or DNS server on.

I actually self-host my own SearXNG and Invidious instances and customize the settings on both, and it’s super useful. (Example: My SearXNG instance is aware of my Invidious instance on my network and will use it to load videos when Invidious is queried via the !iv bang. By doing this I’m not relying on public invidious instances so much; which oftentimes experience downtimes…because youtube hates those more, and frequently bans the public instances.)

This is all doable with a little bit of Docker or Podman action and a bit of editing the appropriate YAML files prior to composing the containers.

So you might be able to spin up a SearXNG instance locally on your network for her to use and configure it to use Google and any other search engines she might prefer. Then use something like LibRedirect (Firefox and Chrome plugin) to redirect her to the local SearXNG instance. (instead of using Google)

A video about setting up SearXNG: https://www.youtube.com/watch?v=UBLypfM9U-g

Ah; yeah. Mullvad Browser is what I mean clearly; as I mentioned it’s maintained by a company, which while they are currently trusted by most people; are always a few management changes away from becoming corrupt and abusing customer trust.

In general Fwy does not agree with the Privacy Guides assessment; and feels that the concerns about the project are simply not credible without stronger evidence of excessively slowed or missed updates.

Project devs do have lives and I’m not personally going to punish that; so long as the software remains reasonably maintained and free of bugs while still considering the project’s number of devs.

Is it better than Mullvad Browser? Probably not in the strictest sense; but I’m also not happy with “Mullvad Browser” either; as this browser makes more choices that breaks functionality than Librewolf does in the pursuit of privacy.

Additionally; I cannot trust that “Mullvad Browser” will not enshittify; it is maintained by a company who is REQUIRED to some extent to make profits. That breeds enshittification. Mullvad would be one bad CEO or core executive team shift away from potentially being targeted as a profit vehicle and it’s privacy benefits weakened or removed entirely so the company can make money.

In general I trust Librewolf on a pretty regular basis to protect my privacy when my Addon-driven version of manually hardened Firefox breaks up a websites functionality too badly. It provides essential privacy protections without breaking too many things and serves as a good baseline browser.

As a rule; I keep several different browsers installed to mitigate lack of website function and isolate away any websites that would be more invasive in what privacy protections must be disabled to use properly. “Setting-Hardened and Privacy-Addon-driven Firefox” is what I use day to day, but “a semi-Amnesic* Librewolf (Incognito windows if untrusted website)” is second and is used daily in trusted website scenarios or in case a website is breaking too badly from plugin interactions. Finally; a fairly vanilla and infrequently used copy of Ungoogled Chromium is kept on hand for situations where Chromium is just required; where I can spin up empty profiles easily for anything I don’t trust and configure it to just flush everything on exit.

FreeTube is a useful project as it allows you to “fallback” on a non-preferred frontend.

https://github.com/FreeTubeApp/FreeTube

This allows you to continue to use Youtube irregardless of which frontend is (potentially not) working.

In ‘Settings > General’ you’ll want to select “Invidious API” as your “Preferred API backend” and specify your favorite invidious instance in the “Current Invidious Instance” field and click “Set Current Instance as Default”. This locks FreeTube into the specified instance.

Then, when you notice that FreeTube is issuing notices to you about your favorite Invidious Instance being down, you can wander back to ‘Settings > General’; hit the “Clear Default Invidious Instance” Button and wait as FreeTube magically contacts the “https://api.invidious.io/” page for you and selects a new, and hopefully online and working Invidious instance. (You may have to hit this button several times to roll a working instance, Hit the button, check the subs page and see if everything loads, repeat if it falls back on the Local API.)

When you run into instances where you can’t roll up a good Invidious instance; the built in Local API is running a NewPipe Extractor like API directly from your FreeTube client. Not the best; but at least it keeps things working while you wait for the Invidious devs to fix things up; and it still reasonably preserves as much of your privacy as it can while doing this to the best effort it can.

…Sadly this doesn’t work when Google manages a double combo of breaking both Invidious and NewPipe; but I have found that this is less often the case and the devs of either project are usually fairly quick about getting fixes out. Bless their hard work with a donation sometime maybe, if you can.

That’s not third person; those are specific pronouns that Fwy uses personally.

13

Wireguard can be configured to proxy specifically only any requests across the DNS and Encrypted DNS ports and protocols. It is extremely capable of being lightweight and not carrying all your traffic.

Fwy would recommend it; if you feel you can afford what they charge for their paid usage plan(s).

Fwy has used it for our own house; and it serves as the main DNS resolver for our PFSense box running in forwarding mode. Fwy is however transitioning to PFBlockerNG; and it’s own ability to block things via DNS locally; but will still be using NextDNS and probably Adguard’s DNS servers as backup/bootstrap resolvers once the plan Fwy has paid for is expired…assuming our house does not vote to keep NextDNS.

Either way; it’s only like about $25 a year if I recall correctly. Fwy doesn’t hate using NextDNS and it is a very good resolver; with lots of useful controls and portability as well as offering proper encrypted DNS service; which is invaluable on weird networks you may encounter when using cellular service or on the go via WiFi.

Further tip; Simple Login offers premium domains that aren’t listed and therefore have less negative reputation; as well as offering “Subdomains”.

I urge anyone who feels they can afford to pay for what SimpleLogin can offer to do so for those features; they’ve given me a pretty flexible subdomain which I use frequently. Wildcards are another helpful feature; particularly for subdomains; which allows you to “make up email addresses” on the fly and have them routed appropriately depending on whatever keywords you include.

lol you are so wrong.

TL;DR: I think this video oversimplifies the analysis according to the cards and gives Graphene OS undue weight without going into sufficient detail as to why each scored under each category.

I actually don’t agree with this video; and firmly believe it is more than a little biased.

For example, the Pixel, AOSP and Android are given several undeserved points due to lack of proper information or understanding of how certain features work. I imagine this is the case too for the iPhone; if a bit less so.

The review apparently doesn’t deep dive into settings or attempt to maximize privacy by turning off unwanted ‘features’ when settings switches are available to the user; nor does it assume that you set up accounts in as private of a manner as reasonably possible or toggle off as many default-on consent switches as needed.

While I would support scoring and dinging each case or instance for “Privacy Settings that don’t actually work”…this video really doesn’t do a lot of legwork and leans on the anecdotal evidence of scary news stories too much.

Worse was the fact that the entire video felt like they were shilling for Graphene OS; which is known to have a slightly unfriendly maintainer and community surrounding him to say the least.

No mention of Lineage or other privacy oriented Android ROMs were analyzed. AOSP too, was unfairly lumped in and dinged for specific points of the Default Pixel configuration…and yes there are major differences between AOSP and Pixel Android; even though Google tries to be less in-your-face invasive than the other OEMs. Not enough credit is given for the “On-Device” smart features implemented properly on the Pixels.

Out of personal experience; I’d actually rate a proper Lineage OS install of 4 whole Android versions ago to be more private than stock. Not quite as private as Graphene; but not quite as invasive and much more enforcing of privacy. The debloating provided by a clean AOSP-like ROM, such as Lineage, as opposed to a “Stock Android” configuration from a major OEM is stark.

Most importantly I personally feel that the privacy model chosen for the video is far too thickly detailed for an average person. Most of the privacy concerns listed on each card contained concern points that might only tangentally apply or don’t apply at all to mobile phones. The way that each card was scored and applied felt low effort. None of the points on any of the card(s) were weighted with average users in mind.

I really hope someone goes into a much deeper dive; this video is basically clickbait that parrots the commonly parroted advice in the privacy community; which isn’t even good advice, it’s just ‘One-Size-Fits-All’ style advice which gives the user no room to make necessary ‘Privacy vs Convenience’ tradeoffs that they themselves could have made if they understood proper threat modelling.

Actually; (basically) SIP over (basically) IPSec sounds pretty correct. Wish the dense technical manuals I read had explained it that way; makes a lot more sense to me as a Net Admin type of IT person.

I do remember reading that the protocol was basically encapsulated. Dunno about any encryption; probably there’s not any at the IPSec level. I do know that the SIMs themselves probably contain certs that have some value; I just don’t know if they handle any encryption or if they’re just lightweight little numbers for authentication only.

If I’m understanding how 'WiFi Calling" works; it’s still “identifying you” to the cell provider the same way; via your SIM. The only difference is they don’t get an exact location because you’re not using any cell towers typically.

I do suspect SIMs and eSIMs are still doing all the heavy cryptographic signing done on a typical phone network though…they’re just not screaming your IMEI/IMSI all over open or even encrypted airwaves; nor is a WiFI signal triangulate-able typically due to it’s short range.

They certainly make it easier to do so; by making it a switch you can toggle; which allows you to generate an identity; or choose not to and roll with the identity they’ve already seen.

Agreed.

Without concepts of privacy; things will soon fall into fascism.

(People can’t DM you)

This is false. However, you must generate an “identifier / group / channel” for them and share that link out-of-band to them." Basically it means nobody can slide into your DMs unless you yourself consent to it and forge a connection with them to do so. It does offer a way to invite other users to chat; but the other user must consent as well…which makes it far safer usually.

Now we wait for someone to build an absolutely wonderful chat app on top of this wonderful bit of PoC code…

I genuinely hope someone does. Imagine what this could do if this was routed over Tor using Private Services.

Run this over that; and you’d have a bullet-proof text chat. Wrap a nice GUI client around all of that and you have a proper secure, anonymous messenger with no problems. With a little more build-out; you could even implement the Matrix protocol over this wire-line and basically have full inter-federation and moderation over a secure wire protocol; allowing for complete privacy and client integration.

TL;DR: Matrix over PQChat over Tor. Think about it. A Post-Quantum Dark-Matrix web.

Can it? Maybe. It’s not impossible; but it isn’t practical and most ISPs limit their shenanigans to grabbing your unencrypted DNS requests.

Will it? Probably no; aside from the previously mentioned DNS redirections; they’re not interested in most people’s packets, only in how many they deliver.

Should you care? I won’t tell you not to take precaution, but I do urge you to consider your threat model carefully and consider the tradeoffs. When Security & Privacy goes up, Convenience and Functionality WILL go down. Balance your needs. Don’t put yourself in a state of Privacy fatigue.

Are there easy fixes? Maybe. I think a VPN or using Tor would solve your concerns here anyways; it’s not required that your modem be running OSS that you can control. If you can achieve it; that’s still good for you; but it’s not something to be sweating if your modem isn’t capable and your invasive ISP is the only effective option.