this post was submitted on 26 May 2024
8 points (83.3% liked)
Lemmy.world Support
3228 readers
60 users here now
Lemmy.world Support
Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.
This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.
This community is subject to the rules defined here for lemmy.world.
You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world/
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is one of those things that sounds really easy but would just be a ton of work, and Lemmy is just 2 devs afaik. How do you know this query parameter is a tracker vs something required for the page? There's no way to know programmatically, so they'd need to maintain a list of known bad parameters - and even then those are probably site specific. What if one site uses the query parameter as tracking and another uses the same name coincidentally and it's a part of filtering or sorting?
This sounds like a better task for a browser extension or an npm package they could consume instead, rather than it being a part of Lemmy itself.
I maintain a list and it's not that big a deal. It doesn't try to be leakproof. It has maybe a dozen actions (code fragments) a table of site names mapping names to actions.
Then I'd say that'd be a great 3rd party plugin for Lemmy (which they just enabled support for btw). I don't think that should be a core lemmy feature, to be dependent on a list of query parameters that need to be kept up to date, but it would be a perfect use case for a plugin, which could call out to a database/script/file of known trackers and their domains, and throw up a warning like you're saying.
Not trying to demoralize you, actually the exact opposite, this would be a great project for you if you already have a list! If you built a plugin that could do that for Lemmy I would be one of the first instances to install it!
Tbh 5 or so parameters take care of 80% of cases. I'm not conversant enough with lemmy implementation to know the difference between core and non core features but it has to be on the server side because there are too many clients.
plugins are server side
I mean the lists for this already exist because there are firefox plugins that do this and often these kinds are open source. This could surely be a case for crowdsourced / collaborative data.