twitter tracking parameter not removed about rules

[rrerrptile]

Okay I just learned this was actually fixed a little bit ago and reverted since it was causing issues. In the meanwhile, is there any way for me to use my own custom rules that dont require me to host the rules file online?

[KevinRoebert]

Can you export your ClearURLs settings and attach them to the issue or email me to support (at) clearurls.xyz

[iam-py-test]

Not sure if this is a prefect solution, but you could host a local server on your device (i.e. with sudo python3 -m http.server) and then subscribe to the rules from http://localhost:8000/rules.txt

[rrerrptile]

no dice. I can access the file in the browser when I host it like that, but the addon seems to ignore my custom ruleset

[KevinRoebert]

You must also provide a valid SHA256 hash of the rules file. See https://docs.clearurls.xyz/1.22.0/specs/rules/ for more information.

[rrerrptile]

Still no dice. I even made the hash file the same way as the gitlab generates it: sha256sum data.minify.json | awk '{print $1}' > rules.minify.hash I've verified it even outputs the same hash on an existing rules file as the gitlab artifacts.

[rrerrptile]

CUserver.zip

[amalic]

@KevinRoebert I've created a pull request. I didn't test it because it's quite annoying that it requires a sha256 hash file to work which seemed to be too much work for such a small change.

[KevinRoebert]

@amalic The rule for the t parameter was intentionally removed. This field is also used for URLs in emails sent by Twitter – e.g. to reset the password.

See also https://docs.clearurls.xyz/1.22.0/further_readings/excluded_fields/ and https://gitlab.com/ClearURLs/rules/-/merge_requests/21 for more information.

[KevinRoebert]

CUserver.zip

@rrerrptile
I've found the error. Your data.minify.json has a new-line at the end of the file. Thus, the SHA256 hash does not match. If you remove the new-line at the end of the file, everything will work.