New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove tracking elements from URLs #545
Comments
@Swrup Thank you for suggestion. For AndStatus this could be a global option that changes clickable URLs on the fly, so a User could try different options or even turn the feature on/off without losing original content. The questions are: Q2. What are that configuration parameters, |
Hello, The most simple UI will be a "URL Tracking Protection On/Off" button in the settings with an additional text explaining what it does. For removing trackers a file containing all the regex rules to apply is needed: It is not a fast moving target, so it is fine to include it in the app. Here is a well documented python example on how to use the rule file to clean urls: This should be applied to every post before they are shown to the user. I hope this is helpful. |
OK, so no configuration except for turning it on/off for the start... |
@yvolk What about calling an external URL cleaner app via API? |
We could use that. The main problem is to find such a service that is free for use and reasonably sustainable. What would be a way to earn money for that service in order to at least pay for its hosting and support? |
@yvolk Thank you. Léon is an excellent and maintained URL cleaner app, also available in F-droid. I opened a feature request so that
|
Many websites use tracking elements in the URL (UTM parameters).
They are not necessary for a website to be displayed or work correctly and can therefore be removed.
To protect users privacy, I propose to clean URLs from posts.
This can be easily implemented.
The firefox add-on ClearURLs already does that and keep a list of UTM parameters to remove :
https://gitlab.com/KevinRoebert/ClearUrls
See related issue for doing it on mastodon server: mastodon/mastodon#16008
The text was updated successfully, but these errors were encountered: