utm_* parameters are not stripped - making extension useless in some cases

[scraunt]

Tracking Token Stripper 2.10 / Firefox 130.0 / Windows 10

When navigating to https://www.plex.tv/blog/plex-pro-week-24-does-your-server-suck-energy/?utm_internal=pro_week_tim_blog_24 the UTM parameter is not stripped.

From having a quick glance it looks to be the same issue as in #62 & #64

Those issues were just closed (would be helpful to have included the reason) - are there any plans to fix / investigate this?

I think on balance it is fair game to strip anything with ?utm_*=. I see the #63 Custom parameters issue exists, this would solve this problem. Are there any plans to implement this feature? What would be the limitation on this feature being added?

If the feature is not / cannot be implemented then there should be some sort of note to alert users to the fact that this extension does not block all kinds of UTM parameters - whether this is a technical limitation or not.

Finally, thank you for creating this extension in the first place.