3 ms·
> The endpoint matches phone numbers to Twitter accounts for those people who have enabled the “Let people who have your phone number find you on Twitter” opti
by jrochkind1 7y ago
> The endpoint matches phone numbers to Twitter accounts for those people who have enabled the “Let people who have your phone number find you on Twitter” option and who have a phone number associated with their Twitter account.
I don't recall hearing about this option. I followed the link they helpfully included[1] to see if I had it set.
I found that I DID have "Let people who have your phone number find you on Twitter" checked. But did NOT have "Let people who have your email address find you on Twitter" checked.
It's possible I actually chose that at some point, for some reason decided I was okay with "by phone number", but not "by email". But that doesn't sound like me, I'm wondering if I unchecked the "email address" one at some point when the "phone number" one didn't exist; then they later added the "phone number" one defaulted to on?
I am guessing they intend to default all of these to on (opt-out rather than opt-in), cause few people would take the trouble to go and opt-in even if they didn't mind or would like it.
But... you know. Anyway, I've unchecked both of them now.
I don't entirely understand the vulnerability, it sounds like it was "letting people who have your phone number find you on Twitter" just as advertised. "we immediately made a number of changes to this endpoint so that it could no longer return specific account names in response to queries." OK, so... you can't use the API to do that anymore, but can still use the twitter web app directly? I mean, it says right there you are letting people who know your phone number find you on twitter, which I would assume means find your account name.
It kind of sounds like they realized this whole feature was privacy-violating, or would be perceived as such, but they haven't gotten rid of the feature... I'm confused what they considered the vulnerability and what they changed or didn't, and to what extent usernames and phone numbers can still be matched by a third party on twitter.
[1]: https://twitter.com/settings/contacts https://twitter.com/settings/contacts
- arkadiyt 7y agoYou can also delete your phone number completely - there's no real reason for Twitter to have it, especially now that it's not required for 2fa.
- larrik 7y agoDidn't you use to tweet via SMS? I assume that's still an option? Seems like a valid reason for them to have it.
- tedunangst 7y agoThey turned it off after somebody simjacked jack.
- dylz 7y agoYou will receive account suspensions shortly after / days after removing it, at least in my experience.
- dandellion 7y agoThat happened to me, although I contacted support and they restored it the following day, no questions asked.
- EGreg 7y agoHonestly, there is a world of difference between having an API to do things in bulk and only allowing rate-limited clients to do something. Both require authentication (although new court rulings may technically be outlawing all charging and quotas for APIs!) But the API has far more permissive bulk actions. Of course, with a botnet and enough time and effort one could execute a sybil attack to circumvent any per-account quotas, and use per-resource quotas to launch a DDOS attack on some resource to any non-authenticated parties. I wish there was - service to prevent sybil attacks somehow. Just make it exponentially more expensive to create multiple identities / accounts on networks. Has anyone got links to papers or projects or anything in that direction? It would be hugely valuable. PS: Twitter and other startups don’t particularly care about sybil attacks and fake users when they are growing, it helps them “innocently” report great user numbers to VCs. So they don’t spend much effort preventing sleeper bots from joining in the network’s growth phase.
- jrochkind1 7y ago> a world of difference between having an API to do things in bulk and only allowing rate-limited clients to do something. Sure, the difference you speak of is only and exactly if the rate-limiting on your API is different than on the other rate-limited (web?) clients, right? It doesn't have to be, but it often is, for various reasons intentional or accidental. Making the rate limiting the same might be another way to fix the "vulnerability" then? It depends on what they consider the vulnerability exactly; if you don't know what it is you consider the problem, it's hard to fix it, or for you or anyone else to judge if you've fixed it! I find their statement to be vague on what the problem was exactly, as above.
- jsnell 7y ago> (although new court rulings may technically be outlawing all charging and quotas for APIs!) That seems quite hard to believe. Do you have a link?
- EGreg 7y agohttps://news.ycombinator.com/item?id=22180559 https://news.ycombinator.com/item?id=22180559
- tzs 7y ago> It's possible I actually chose that at some point, for some reason decided I was okay with "by phone number", but not "by email". But that doesn't sound like me, I'm wondering if I unchecked the "email address" one at some point when the "phone number" one didn't exist; then they later added the "phone number" one defaulted to on? I looked at mine, which I'm sure I've never touched before because I never cared about Twitter settings. As with my Facebook account, my Twitter account was mostly just created to get an acceptable name in case someday I actually wanted a serious social media presence. Both are unchecked. The account was created in early 2008.
- fernandotakai 7y agoyeah, same. account created in oct 2007, never checked and i have everything turned off.
- disiplus 7y agoalso unchecked,and i have my phone number there.
- nyuszika7h 7y agoIf you’re in the EU they were likely disabled in 2018 as part of the GDPR prompt.
- segmondy 7y agoI have the inverse, I never did check it myself. That I can assure you of. I don't care for anyone finding me on social media.
- rcthompson 7y agoBased on the "large network of fake accounts", I'm guessing the attackers were doing something to effectively query every possible phone number and associate an account to each one.
- ramses0 7y ago@fake_twitter_account_212_111_xxxx w/ a phonebook contact list of "212-111-0000" => "212-111-9999". Lather, rinse, repeat. You'd need ~10M accounts w/ ~1000 phone numbers in each, and that can be reduced by some percentage if you know how U.S. phone numbers are assigned (ie: don't check for xxx_555_xxxx numbers, prefer highly populated prefixes, etc.) Good thing they SUSPENDED those accounts! /s
- rcthompson 7y agoYou can probably narrow down the list to just existing mobile numbers by sending a text message to each one, and then just do this for ones where the text message actually goes through.
- codedokode 7y agoMaybe you can upload lists several times from same account? Then you don't need 10M accounts.
- deleted 7y ago[deleted]