The Facts on News Reports About Facebook Data
21–30 of 60 posts
Re: The Facts on News Reports About Facebook Data
#22Facebook is using doublespeak here. > It is important to understand that malicious actors obtained this data not through hacking our systems but by scraping it from our platform prior to September 2019. .. a couple paragraphs later :: > We believe the data in question was scraped from people’s Facebook profiles by malicious actors using our contact importer prior to September 2019. Gee, that sounds a lot like someone…
Re: The Facts on News Reports About Facebook Data
#23My phone number was removed and my account deleted when they say this hack happened. My phone number is in the leak. Doesn that mean that my phone number was in it because other people's contacts were imported, or because they didn't actually delete my info?
If you are an EU resident, this can be a GDPR violation so you should follow up.
Re: The Facts on News Reports About Facebook Data
#24I thought US Court of Appeals established that web scraping is legal?
Re: The Facts on News Reports About Facebook Data
#25As someone who has an account (begrudgingly for Messenger since you can't solely use a phone number anymore) but doesn't use it, can I just say:
Wait, what?! Since when does Facebook have health information!
I don't know conceptually what portion of Facebook they're referring to but that's news to me.
Re: The Facts on News Reports About Facebook Data
#26Facebook is using doublespeak here. > It is important to understand that malicious actors obtained this data not through hacking our systems but by scraping it from our platform prior to September 2019. .. a couple paragraphs later :: > We believe the data in question was scraped from people’s Facebook profiles by malicious actors using our contact importer prior to September 2019. Gee, that sounds a lot like someone…
From the article it appears that the contact importer is an API endpoint which returns a set of Facebook profiles given a set of phone numbers. In that sense, it did exactly what the developer intended.
If I write a script to query google.com and get a response back you could say I'm not using google search as intended, but most software engineers would laugh at me if I claimed to have "hacked" Google in this way.
Re: The Facts on News Reports About Facebook Data
#27Re: The Facts on News Reports About Facebook Data
#28> The information did not include financial information, health information or passwords. As someone who has an account (begrudgingly for Messenger since you can't solely use a phone number anymore) but doesn't use it, can I just say: Wait, what?! Since when does Facebook have health information! I don't know conceptually what portion of Facebook they're referring to but that's news to me.
Re: The Facts on News Reports About Facebook Data
#29Facebook is using doublespeak here. > It is important to understand that malicious actors obtained this data not through hacking our systems but by scraping it from our platform prior to September 2019. .. a couple paragraphs later :: > We believe the data in question was scraped from people’s Facebook profiles by malicious actors using our contact importer prior to September 2019. Gee, that sounds a lot like someone…
> Gee, that sounds a lot like someone abused your contact importer tool to do something you didn't intend for it to do. From the article it appears that the contact importer is an API endpoint which returns a set of Facebook profiles given a set of phone numbers. In that sense, it did exactly what the developer intended. If I write a script to query google.com and get a response back you could say I'm not using googl…
"Facebook confirmed to me that the vulnerability was genuine, that the exploit would enable a “bad actor” to connect phone numbers and user details, and that it has prompted changes to be made. They pointed out to me that the exploit process is “complex,” but nonetheless did leave the platform open to abuse and put users at risk."
Re: The Facts on News Reports About Facebook Data
#30Facebook is using doublespeak here. > It is important to understand that malicious actors obtained this data not through hacking our systems but by scraping it from our platform prior to September 2019. .. a couple paragraphs later :: > We believe the data in question was scraped from people’s Facebook profiles by malicious actors using our contact importer prior to September 2019. Gee, that sounds a lot like someone…
> Gee, that sounds a lot like someone abused your contact importer tool to do something you didn't intend for it to do. From the article it appears that the contact importer is an API endpoint which returns a set of Facebook profiles given a set of phone numbers. In that sense, it did exactly what the developer intended. If I write a script to query google.com and get a response back you could say I'm not using googl…
Not sure they envisioned someone enumerating phone numbers and pulling all data. But that would be hilarious if they claim that's what they intended and that was a feature.