this post was submitted on 28 Feb 2025
28 points (93.8% liked)

Privacy

34388 readers
685 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

So, I have always just used one browser, Firefox, with javascript and cookies turned off and whitelisted sites that I needed to use that required javascript or cookies or both to actually work.

My threat model isn't the tightest and could best be described as "I don't see why they should have my data if I am blocking the ads they use it to try to deliver to me". This browser setup coupled with tracking blocking at the DNS level has made me feel comfortable that while some of my data is being collected I am stopping most of the collection.

With the advance of fingerprinting and the recent change of a certain browser's terms of use it is probably time to review this setup.

I believe that it is usually advisable to use two different browsers. One where you are identifying yourself by logging in and one where you are just browsing. As logging into sites usually involves javascript and cookies I was going to use Librewolf with javascript and cookies turned off for general browsing and Mullvad browser as it comes for sites that require javascript and cookies.

I feel as though I have read a thousand discussions on this subject over the years so I apologise. Does anyone have any suggestions for a more private setup browser-wise? Tracking blocking at DNS level will continue and I'm on debian-based linux.

Thanks for any help in advance.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 day ago

You got most things right about UDP and TCP. They both work in the transport layer of the OSI model. They are also completely different protocols, related yes but independent.

UDP is "simpler" as it basically throws data packages in to the network and hope they reach their destination. TCP on the other hand has checks in place that verifies that a data package has actually reached its destination.