We know this update is coming later than we said it would, and we appreciate your patience as we work through this.
Here’s where things stand: we’ve done additional outreach to some creators and will continue through September. We’ll share full details on the updated solution and timeline in October.
Since we shared our initial plans for Scoped IDs, we’ve heard clearly from many of you about concerns with the implementation and its impact on moderation. We’re taking the additional time to address those concerns properly, and we’re continuing to pressure-test our approach against moderation workflows.
Thank you and let us know if you have any questions.
Roblox has proved time and time again how terrible their moderation is, so people in the community have created resources to do moderation themselves. These third party tools make Roblox safer when Roblox themselves fail to do so.
I feel like Scoped User IDs are being implemented in bad faith toward these tools, as they make them completely ineffective. So why go through with this?
You can say that developers aren’t allowed to save user data in external databases, I totally agree with that, but we need a better cross moderation tool first.
It’d be really helpful to provide a complete list of APIs and return types that will not be affected by this change, if any. Additionally, documentation should be updated for those APIs to clarify that they will take/return a global user ID instead of a scoped one.
Good on you for realizing the moderation issues this can cause. Now we’ll have to see if you guys actually do the work required to reduce these possible issues to zero.
Sounds like y’all are cancelling it (watched greenlegocat’s video). Regardless of whether you decide to do that or not, putting the prviacy update on hold is a great decision. Respect to y’all, you have been cooking this month honestly!
Please reconsider or hold off on publishing this update.
A user should remain identifiable with a consistent ID across experiences. We don’t have access to sensitive personal data like IP addresses anyway. What kind of “privacy” is this supposed to protect? Hiding how many coins or pets a player owns?
Instead of solving real privacy issues, this change just creates friction and confusion for developers who have relied on the standard Player.UserId method for years.
