Skip to content

Add Threads entry and "xmt" rule#179

Open
rileychh wants to merge 1 commit intoClearURLs:masterfrom
rileychh:threads-xmt
Open

Add Threads entry and "xmt" rule#179
rileychh wants to merge 1 commit intoClearURLs:masterfrom
rileychh:threads-xmt

Conversation

@rileychh
Copy link
Copy Markdown

@rileychh rileychh commented Sep 12, 2025

Removes the xmt tracking parameter from Threads share links.

Example

Before:
https://www.threads.com/@ntut.uk/post/DWMXR8hkvbI?xmt=AQF0X5xurim8xkCkUa9dIycDta4luuIZx-jFf80eaQqd0Q

After:
https://www.threads.com/@ntut.uk/post/DWMXR8hkvbI

Copy link
Copy Markdown

@AkitsukiNagi AkitsukiNagi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed your PR and found a structural issue in the JSON file:

The provider "threads" should be a key within "providers". However, it is sibling to it currently.

Current:

{
    "providers": {
        ...( the others)
        "viglink.com": {
            ...(VigLink rules)
        }
    },
    "threads": {
        ... (Threads rules)
    }
}

Corrected:

{
    "providers": {
        ...(the others)
        "viglink.com": {
            ...(VigLink rules)
        },
        "threads": {
            ...(Threads rules)
        }
    }
}

Tip

You may change the provider name to "threads.net" as most providers are named so.

@rileychh
Copy link
Copy Markdown
Author

rileychh commented May 4, 2026

Thanks @AkitsukiNagi, fixed and force-pushed. Also rebased onto latest master and added an example URL to the PR body.

Kept the key as "threads" since bare-name keys are common in the file. Can rename to "threads.com" if you prefer (the pattern matches .com, not .net).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants