I don’t want to verify ID for privacy reasons. And for the phone number I don’t have that because you can reset password with it which opens up a security hole…
Maybe add using devex as a way to be verified too.
I don’t want to verify ID for privacy reasons. And for the phone number I don’t have that because you can reset password with it which opens up a security hole…
Maybe add using devex as a way to be verified too.
I like this change, however:
What will stop users from using a fake/temporarily phone number from a website to verify them self?
You can read verrifs privacy policy, they delete the image right after you verify. And it takes 1 minute it All done by a robot.
You still can if you open inspect and copy the link to the verification in the network tab.
Nothing… however random dudes uploading a couple models with a virus in them isn’t a big deal, that’s not what causes problems for the marketplace (they’ll eventually get banned).
What causes problems for the marketplace is dedicated attackers creating thousands of different accounts to spam the marketplace with bad models, and procuring thousands of fake/temporary phone numbers is significantly harder.
Good intentions, not so well executed.
As multiple people here said, having a verified phone number and/or email does not prove a person is trustworthy. I think it would be much better if there was a way that a model would be checked for malicious scripts prior to uploading it to the marketplace.
And regarding the verified check mark, I think it should be earned rather than obtained through verification. Similarly, how you earn trust on devforum, you should be able to get trust on the marketplace for posting amazing, original creations without any viruses in them, and those who do indeed upload creations with malicious scripts should be restricted or completely banned from the marketplace.
I honestly can say this was a good update. I am happy to see security updates being developed but not forcing those who cannot or don’t want to ID verify have an option to still use the platform on the same level as those who do. I know people are going to hate on this, but in my opinion, what’s wrong with having a filter on those who choose not to verity at all. I’d be unhappy if this was only for ID verified, but most people have phones these days so it gives everybody an option to be seen. It isn’t perfect, but it is a step in the right direction in my opinion.
Good change.
This update is quite good with the voice chat side, as Roblox wants a piece of that Metaverse pie, and expanding Voice Chat to as many as possible is important on getting that piece, but for the Marketplace, that’s kind of lowering safety. Phone verification is easier than ID Verification, due to phone generators, but we should be able to define between phone-verified developers and ID-Verified developers.
Either way, my summary is;
Voice-chat is now Metaverse-goodish.
Marketplace Safety is a bit worse.
Anyways, thanks for listening to my TED Talk.
This update definitely has some good intentions behind, but I am still surprised why stuff like IDs and phone numbers are used to verify trustworthiness.
I, and many developers would love roblox to start using a combination of things to verify whether the user is trustworthy or not. Devexing is a good metric to ensure that the developer is at least more trustworthy than the average developer. Also, you can determine whether the user is trustworthy or not by seeing if he purchased anything from roblox, as you wouldn’t normally purchase some robux and then violate some rules and risk account termination unless, you want to waste some money.
There are many things to determine trustworthiness of a user, but IDs and phone numbers aren’t one of those
It doesn’t, just like ID verification doesn’t.
The point here is making it harder for people to make multiple accounts for malicious intents.
OK, but I don’t have a phone number either, so this is useless to me.
Let me verify myself by the quality of my work, not by linking my Roblox account to a real life identity.
Thank you all for the great feedback! We’d like to make 2 key clarifications to address some concerns:
Please let us know if you have any further questions.
Thank you!
This is a great change, I can now upload enough audio for my experience whenever it’s being updated & I can now use voice chat in my experiences.
I love this change, it makes things a lot better for everyone.
While phone number generators work on other sites, Roblox is requiring users to verify they have access to the phone numbers. This means very few of these sites will actually work.
An example of where users could get phone numbers is something like Google Voice. The only thing is that real phone numbers aren’t actually that easy to come by, so many of these sites have security around giving free phone numbers (captchas or other requirements involving captchas).
This will not help with safety at all. A
while true do
local teleportservice = game:GetService("TeleportService")
--Teleport code here
end
will be prohibited from roblox, but come on, it’s now difficult to do this and i wanna opt-out of this. Horrible change.
This impacted my workflow. I was recently browsing plugins from the creator marketplace via create.roblox.com/marketplace and searched for keywords. The search results were very few, all you get is one page worth of creations, here is what I mean:
This takes up more time because you have to go to the filter and click toggle “Include unverified creators”, and the page refreshes too.
Immediately after toggling the unverified creators filter, I received at least seven pages worth of results compared to the unverified filter toggled off. This makes it difficult for a majority of developers who want to quickly install a plugin or take a model from the creator marketplace website.
A filter is supposed to block everything except for a chosen few, not the other way around.
I think this topic might be of great interest to you, given that it has lots to do with Marketplace Safety:
wowowowow roblox your phone verify thingy is soooo epic
Thank you for this. I am genuinely very happy for everything you guys have done to keep Roblox a safer place. By doing this, we can ensure that we don’t get involved with a lot of bad stuff. But will this also help with the problem regarding the inappropriate models being uploaded, or that already was uploaded?
I mean let’s just put it this way - someone having a phone number doesn’t necessarily mean they are trustworthy or even above thirteen years old for that matter. In fact, sometimes I wonder if thirteen-year-olds are even mature enough to be using spatial voice and other features on the platform that require identity verification. I’ve personally never used voice chat even thought I’m fifteen - I just don’t have a driver’s license or ID, nor do I feel particularly comfortable with giving that sensitive information to Roblox and I’m sure other people would feel the same way.
Anyway, getting back to my argument earlier about some thirteen years old not being mature enough to use voice chat. Just because some people that “meet the age requirement” for voice chat aren’t mature enough to use it doesn’t mean that everyone should be denied access to the feature. But if someone on the platform does want to use voice chat, they need to verify their age - with a phone number, or ID card. The phone number in my opinion is about ten times less secure than the ID verification mainly that isn’t gonna stop people visiting those websites where you can generate phone numbers for one-time use. Let’s not forget that most people wanting to use voice chat are generally quite young and most likely don’t have a phone or can’t afford to purchase a phone.
One last thing - the developer identity verification seems like a great idea and will make developers seem more reputable and so younger creators can see which developers make the safest models for them to use for free from the toolbox.
So, I understand what you are trying to do here Roblox, but there is still some questions that people like me, and others in this thread still want some answers to. I look forward to hearing any updates from Roblox or other developers in this thread.