Closed nakoyasha closed 5 months ago
What features rely on it being there?
Anyway, I've made the change in a PR: #25. What do you think? I'm just hoping it doesn't have the opposite effect of triggering antispam because we're trying to imitate a web client.
What features rely on it being there?
Okay, I shouldn't have mentioned it since it's mostly just experimental features that rely on it (e.g, some experiments (aka, discord's implementation of a/b testing) will only be sent to the client if it's build_number
is higher/is 269579)
I'm just hoping it doesn't have the opposite effect of triggering antispam because we're trying to imitate a web client.
It shouldn't! although it might be a good idea to update it every so often - Discord might find it suspicious that there's a big number of users with a really old build_number
for example - but I don't think there's been any documented cases of that happening yet
Anyway, I've made the change in a PR: https://github.com/DiscordMessenger/dm/pull/25. What do you think?
For now, I think it's good! The only issue I have is the one I've mentioned above (client config with an outdated build_number
), although I think it would be pretty hard to automate, so it's out of scope for the PR imo
X-Super-Properties
is a base64-encoded JSON header that identifies the client by letting the server know it's build number, release channel, etc It might be a good idea to support it as Discord might otherwise flag accounts for sending user-api requests without it (as some features rely on it being there) Example:More info about the header is documented here!