I wish they said which region specifically requires this. I was really curious while reading the post, but I guess we can’t know.
As I mentioned, the most likely areas are UK and Middle East on this matter.
“You’re only giving us barely any time to try to figure out a way to do this. From a legal standpoint of view, I view that this change is mostly occurring due to European Union, UK, California, and Middle East regulations (Saudi Arabia and UAE)”
Used to defend these updates but now the platform is becoming a landfill
There’s reasons not to work with this platform’s OAuth or the current publishing rules. With a worse UX, random body part colors could still be used to verify someone.
I think this is a sensible change overall.
While I understand that a small number of experiences may need to update their integrations, protecting user privacy and supporting child safety should always take priority. User descriptions can contain personal information or other content that developers don’t necessarily need access to through a public API.
Restricting access to a user’s own authenticated description while preventing third-party retrieval strikes a reasonable balance between functionality and privacy. It also helps ensure Roblox continues to meet evolving regional requirements and strengthens user trust across the platform.
I also appreciate the transparency around the rollout timeline and the acknowledgement that the notice period is shorter than usual. Hopefully the affected experiences can make the necessary changes before the update is fully deployed.
Overall, I think this is another positive step towards improving privacy, child safety, and responsible data handling across the Roblox ecosystem.
shh dont leak the strat man the mods are gonna find out and like block it
Please explain what reasons could possibly prevent someone from using either method. The only scenarios I can picture here for why someone would insist on archaic methods that check against their profile is either because they are directing children off-platform or they are purely lazy and refuse to upgrade their implementation.
Publishing rules should be a non-issue since you don’t want children being allowed into any space that would usually be locked behind such verification.
How is forcing players to navigate to their profile and change their description or anything about their already set customizations a better choice than native one-click authentication?
Changing a bio is more familiar and it’s impossible to delegate permissions. I do think there should be granular privacy with them though.
@TheGrimDeathZombie If you only need to identify a user, OAuth is not worth the hassle. Identifying and remembering an account isn’t dangerous. The old implementation does move more friction onto the users which gives more time to reconsider if they’d want to link.
I’m not interested in restricting more features behind ID verification as if the rest of game publishing isn’t torturous.
reminder that this is roblox we’re talking about, they’ll follow and comply with itty bitty region requirements and completely ignore the big ones and the lawsuits
Well this seems Pretty Foolish, especially when Roblox is really easy to just scrape.
What are they removing? I didn’t read either
Bloxlink uses OAuth as well, they haven’t supported game nor description verification in a while either.
But regardless, an alternative if games/services needed the description could be to switch to the OAuth-based/OpenCloud endpoint with an API key rather than a Bearer token?
https://apis.roblox.com/cloud/v2/users/{user_id}
Unless they also change that one to match, the affected endpoint listed doesn’t use authentication though so I presume that’s why it’s changing meanwhile the OC one isn’t listed. Clarity could be nice in that regard though rather than assuming it also won’t be affected ![]()
Really odd that they wouldn’t update their landing page to reflect that and still have it mislead you to believe description & game are the only ways.
that also being player.User is bullshit
As someone said above, you are able to check the description meta if you wish to grab the users bio!
descriptions (abouts) are not being removed! (try reading the post)
the api to get them in games and other sites is just beign removed.
It’s not just in-game, either. It affects the Web API as well.
The idea is that they want to “protect” certain data from being accessed through API requests. But in reality, this change will just push developers toward scraping user profiles instead.
Ironically, Roblox has kind of shot itself in the foot with this change. Instead of people using legitimate API requests, they’ll end up with far more bots scraping profile pages, which is arguably a much bigger problem.
is that not what is said just rephrased into slightly more coherent speak
regardless, it still can break old sites and such that relied on this. (before actual auth)