fix: stricter url matching

[SethFalco]

In user-scripts, you can use the match directive multiple times.
So we match /channels/* since that's what we need for the web app anyway.
We also match /app and /login for when a user is being redirected to the web app from them, totherwise the user script won't be initialized.

This prevents issues like the following on other parts of the website:

/robots.txt

The box appearing at the bottom is because of this user-script.

Main Site (i.e. /company)

The extra whitespace appearing at the bottom is because of this user-script.

I believe the only pages we'd want the button to appear on would be under /channels anyway, for example:

• Home: https://discord.com/channels/@me
• DM: https://discord.com/channels/@me/{ID}
• DM Message Link: https://discord.com/channels/@me/{ID}/{ID}
• Guild Channel: https://discord.com/channels/{ID}/{ID}
• Guild Channel Message Link: https://discord.com/channels/{ID}/{ID}/{ID}

We then need to cover these because of web app navigation:

• https://discord.com/app
• https://discord.com/login

I tested the password reset flow (https://discord.com/reset) and can confirm there's no need to match this. It redirects to /app which is already covered.
There's no need to cover /channels itself because that's a 404.

[SethFalco]

@abbydiode This might be a good one for you as well?

[victornpb]

@SethFalco thank you for the detailed description

[victornpb]

following the same logic I added ptb and canary urls, someone requested it in another issue

// @match         https://discord.com/app
// @match         https://discord.com/channels/*
// @match         https://discord.com/login
// @match         https://ptb.discord.com/app
// @match         https://ptb.discord.com/channels/*
// @match         https://ptb.discord.com/login
// @match         https://canary.discord.com/app
// @match         https://canary.discord.com/channels/*
// @match         https://canary.discord.com/login

[SethFalco]

Suggested change

	// @match https://ptb.discord.com/app
	// @match https://*.discord.com/app

Maybe better to cover ptb and canary together like this?
Not sure if that would include no subdomain as well.

[SethFalco]

Matches any URL that uses the https scheme, is on a google.com host (such as www.google.com, docs.google.com, or google.com), as long as the path starts with /foo and ends with bar

— https://developer.chrome.com/docs/extensions/mv3/match_patterns/

Looks like *.discord.com would actually match all 3, the base domain, and both subdomains.

Might be worth replacing the 9 entries with just 3 using *.discord.com. (Haven't tested it manually.)