Oh I was wrong, after further reading this looks to be a lot better than what I was thinking.

I must have been thinking about another methodology of attempted privacy over a dataset.

Before I start reading, if this has anything to do with differential privacy, I’m going to be disappointed.

Edit:

Differential Privacy Algorithms

I should have known. Look, in practice it’s plausible enough… and if they truly have secure enclaves where they pull in all of the audience data and it only exists in there at that one or two seconds it takes to perform bidding/matching then yeah, I could see it work. But across a big enough dataset which advertisers already have, (if I am to believe what I’ve already read on the subject which could have been wrong) differential privacy isn’t real privacy.

But hey, they are in mozilla now, and mozilla does have an acceptable track record on it so hopefully it’s for the better.

https://reddthat.com/signup

2nd best reporting in.

A faster db. Just the regular performance benefits, https://www.postgresql.org/about/news/postgresql-16-released-2715/

Also, Lemmy is built against v16 (now) so at some point it will eventually no longer JustWork

The script will be useless to you, besides for referencing what to do.

Export, remove pg15, install pg16, import. I think you can streamline with both installed at once as they correctly version. You could also use the in place upgrade. Aptly named: pg_upgradeclusters

But updating to 0.19.4, you do not need to go to pg16… but… you should, because of the benefits!