The title gets whitelist censored.
[url]Groups - Roblox
Don’t you love roblox’s ceoncorshipping? Makes everything soooooooooooooooo much better…
Same with talking/PM, your message may say “Hey whats up dude wanna join my group” but turns it into" “Hey ##### ## #### wanna join ## #####”
The filtering should only be seen by the end user and not everybody. Unfortunately this is only the case when chatting in-game.
There’s a difference between the whitelist and the blacklist. If someone says a bad word, it shows up in their chat but it’s hashed out in everyone else’s chat. The blacklist is to prevent people from seeing profanity and whatnot. The whitelist is not for that – the whitelist is to prevent little kids from giving out their personal information in accordance with some law or whatever. It too is not hashed out on the sender’s chat, but not because the purpose is the same. Since it’s to prevent them from giving out their personal information, you have to filter it for everyone. It’s a little overkill on group names though (who’s going to use that to give out their personal information?), so I don’t think we need it there.
There’s a difference between the whitelist and the blacklist…[/quote]You definitely misunderstood what I was saying. I am saying that the Filtering should not be based on who originally typed the message, but instead who is seeing the message. For example if I call me group “Dragon Legion” and Legion is not in the whitelist then users under 13 would see “Dragon ######” and users over 13 would see “Dragon Legion”.
For the sake of compliance I do believe that we require some filter to be in place. The question is should we use the same filter on site as in-game?
[quote] [quote=Echo]Since it’s to prevent them from giving out their personal information, you have to filter it for everyone. [/quote][/quote]No ROBLOX user should be giving out personal information, so you’d hope this was handled by the blacklist across ROBLOX in its entirety. This is not really relevant to the point I am trying to make. The end user should see age-appropriate content.
Not all little kids understand what info they should or shouldn’t give out online.
Let’s say some kid tried to make a group called “People Who Live In [town name]”. That would need to be filtered for everyone to prevent the kid from giving out this personal information. The whitelist in this case would be pointless if other people could still see the censored words.
The user creating the group should just be able to see the finalized group name (after censoring) before making the purchase, if this is not already a thing. Then if the name does get censored, they can go back and revise it if they want.
Obviously the whitelist itself could use a lot of improvements and additions, but that’s a different topic.
Yes, this is relevant. You’re making a misguided suggestion because you don’t understand why the whitelist exists. The blacklist can’t handle personal information. You can’t predict every person’s street address, phone number, school, parents’ names, etc. The reason childrens’ information warrants special protection isn’t just because they’re potentially not old enough to know that they shouldn’t be giving that information out – it’s because of actual U.S. laws. COPPA prevents companies from collecting or disclosing personal information of children under 13 without direct consent from their parents. ROBLOX obviously doesn’t want to go through the trouble of gaining permission for every single thing a < 13 year old posts to their site, so they just whitelist what they say. Anything stored to ROBLOX’s servers (bios, wall posts, forum posts, comments, and even the chat logged by them whenever someone uses the chat report) is classified as collecting information, and allowing others to see it (showing other people their chat, forum posts, bios, etc) is disclosing that information. They are legally unable to use just a blacklist for < 13 users – they have to use a whitelist.
A blacklist won’t work and the whitelist isn’t going away any time soon. The whitelist prevents all users from seeing the filtered text for a reason.
Thank you for taking the time to read our message.
`We reviewed this bug and it no longer appears valid.
If the issue persists or if you obtain any new information that could he7lp us analyze it further, please open a new report including all relevant details and a clear description of the problem.
Thank you again for your cooperation!