privacy-budget VS community-edition

You can't block fingerprinting completely without breaking a ton of useful features. But the sandbox has a concept called the privacy budget which tries to determine if a site is collecting too much information. It should allow sites that actually use some of these features to continue to work.

The idea is that if sites that query fonts, engage canvas, read the user agent information, etc, they are likely trying to build a fingerprint, so the browser will start to return generic data.

Presumably - hopefully - it would allow users to set their own privacy budgets. Even better if it supports granular per-site control, which may be needed to certain specialized websites.

https://github.com/mikewest/privacy-budget

I don't think there are any plans to make this a pop-up. But it's still useful to move this entropy to be something that has to be actively collected: people can see which sites are collecting what information, and eventually browsers can start enforcing something like privacy budgets (https://github.com/mikewest/privacy-budget). You can't do these with something always sent automatically.

Someone from Chrome has proposed something similar in the form of a "privacy budget". Each fingerprintable surface gets a score and each origin has a budget. Once you go over, something(?) happens.

https://github.com/bslassey/privacy-budget

https://github.com/bslassey/privacy-budget

With our data safely stored on our local machine, it was time to spin up a new instance of Plausible. For this, I recommend the official Community Edition Guide from GitHub.

Plausible seems like a fine choice for simple cases.

It is still oriented at websites, but you can send events directly to the API: https://plausible.io/docs/events-api

It is self-hostable, too. https://github.com/plausible/hosting

I'm working on creating an EC2 instance that will use Docker Compose to run the open-source Plausible service. It contains a web app, a smtp server, and a few DBs. The data on the DBs are going to be stored on Docker volumes.

sudo apt update -y curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg echo "deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu focal stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update sudo apt-get install docker-ce docker-ce-cli docker-compose containerd.io -y sudo mkdir /var/www cd /var/www sudo git clone https://github.com/plausible/hosting cd hosting sudo git clone https://github.com/TheBrianGraf/AmazonLightsail/ sudo chmod +x ./AmazonLightsail/Plausible-conf-setup.sh

We'll use the Plausible nginx example as a template:

cd /home/cleavr mkdir plausible cd plausible git clone https://github.com/plausible/hosting cd hosting key="$(openssl rand -base64 64 | tr -d '\n' ; echo)" echo " ADMIN_USER_EMAIL={{ADMIN_USER_EMAIL}} ADMIN_USER_NAME={{ADMIN_USER_NAME}} ADMIN_USER_PWD={{ADMIN_USER_PWD}} BASE_URL={{BASE_URL}} SECRET_KEY_BASE=$key " > plausible-conf.env docker-compose up -d

$ curl -L https://github.com/plausible/hosting/archive/master.tar.gz | tar xz $ cd hosting-master

For this little project, we will use their up and running template that has everything we need to boot up our Plausible server.

git clone https://github.com/plausible/hosting cd hosting

How did you try to get it running? They have a docker-compose setup[1] that was super easy to use. It looks to be 5 months old so if you tried before then, good news, it's easy now!

[1] https://github.com/plausible/hosting