/users/:id returns 404 on users with no mutual guilds about discord-api-docs

[yonilerner]

The change is being reverted

[Vendicated]

Considering that this worked fine before today and you can still fetch bots fine, just not users, it seems like this change might have been intentional. Maybe to improve security / prevent user scraping?

If yes, I ask you to please reconsider. There are many good use cases for a bot needing to fetch arbitrary users and this breaks a ton of apps that do so.

And this achieves really little for actually improving privacy. Nor does it do much to prevent scraping because you still need the full user id to even use this endpoint. Noone uses this endpoint for scraping, much more effective is to just join massive servers

If anything, this change encourages bots to mass save data about users and thus worsens privacy. Let's say I have a moderation bot and want to have a command to query old cases. I now need to store the user data in my database because I can no longer rely on being able to fetch their username and such on demand

[KrashV]

This is a very sudden and unwelcomed change. We store Discord IDs of the users we banned from our guild, and for readability and enforcing we used this call.
I really hope this is something they published by mistake and will revoke soon.

[CrystiqDev]

This is a very bad change. I have a discord bot that has to check rather or not a user is still using the bot so it can comply with data removal times (it checks if the user is still in a server with the bot). But due to the new change it can't check that and it breaks my whole code.

[SinisterRectus]

Now, if you get a 404, you know they are not in a mutual guild! 🤣

[SemiMute]

Please revert this very irrational change. This does nothing but hurt bots as a whole.

[CrystiqDev]

Now, if you get a 404, you know they are not in a mutual guild! 🤣

It doesn't get past that line of code tho, it just breaks. therefore i cannot "delete" their data

[ypisetsky]

Revert should be out now.