I'd suspect this is more about combating abuse (both spam and "interpersonal abuse") than it is about preventing duplicates – by comparison to Twitter, Facebook has done well out of using mobile numbers as a unique identifier (compared with email, which is easy to sign up for another Gmail account or even use a +extension on an existing one) to combat abuse.
Most virtual SMS services won't receive SMSes from shortcodes (e.g. Twilio won't – their docs are quite explicit: https://www.twilio.com/help/faq/sms/can-i-send-messages-from-facebook-and-other-services-to-twilio), which is done because they're listed with the mobile operator as virtual numbers rather than actual mobiles. Probably a workaround around somewhere, but if you look at the articles about some of the Facebook spam farms (this one is particularly good as a long curious read: https://theweek.com/articles/560046/inside-counterfeit-facebook-farm) you'll find that they have to swap SIMs continually, which would suggest to me there isn't an easy online service for it. The bigger challenge to me as someone who used to consult to enterprise on social platforms is what mobile number you associate with your 'big brand' account (e.g. @nike) – do you buy a "work phone" that will exist just to get 2FA codes and be the backup number, or do you use your social media manager/coordinator/whatever's (personal or work) phone, knowing that they may leave? There are some interesting outcomes that can occur as a result of the inevitable sharing that needs to happen. Facebook "solved" a lot of that by creating their work logins (different to FB @ Work) and telling everyone to stop using shared-login 'grey' accounts and instead to use personal accounts to connect to company Pages, but that's obviously a bit more tricky on Twitter – they've tried to do a bit of that with TweetDeck Teams though, but it's very light by comparison. Hugh On Monday, 8 February 2016 13:13:27 UTC+11, Dean Collins wrote: > > Was setting up a new twitter account this morning for a new project and > noticed that the boom has fallen and Twitter now demanding a mobile number > to send a sms verification before enabling an account. > > > > So far none of my accounts have a phone number associated......but now > there doesn’t seem a way around it, not sure if they are preventing > duplicates etc yet. > > > > Still easy enough to setup a temp number to receive a sms using something > like this - > https://www.raymond.cc/blog/top-10-sites-receive-sms-online-without-phone > but wonder when they are going to start being problematic around this. > > > > > > > > Regards, > > > > Dean Collins > Cognation Inc > de...@cognation.net > <javascript:>+1-212-203-4357 New York > +61-2-9016-5642 (Sydney in-dial). > +44-20-3129-6001 (London in-dial). > > > -- -- You received this message because you are subscribed to the Silicon Beach Australia mailing list. Vist http://siliconbeachaustralia.org for more Forum rules 1) No lurkers! It is expected that you introduce yourself. 2) No jobs postings. You can use http://siliconbeachaustralia.org/jobs To post to this group, send email to silicon-beach-australia@googlegroups.com To unsubscribe from this group, send email to silicon-beach-australia+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/silicon-beach-australia?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "Silicon Beach Australia" group. To unsubscribe from this group and stop receiving emails from it, send an email to silicon-beach-australia+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
