Facebook Lied : A Facebook Feature Which Kills Another Feature

I wouldn't say Facebook is "fooling" you per se. I think it's just a matter of perspective: the user and the developer.

I feel like the "Profile Picture Guard" is really only there to "guard" against the not-so-tech-savvy people. I mean I could easily open up the DevTools to pull in the link for somebody's Facebook (or any other social media) profile picture. For the common user, they wouldn't even know that the DevTools existed. Since most of the world are not as familiar of web technologies as we—the developers—are, then yes, you could say that Facebook is fooling the developers. Otherwise, for the normal user, they are not exactly being "fooled" because most of the world is not even aware of the fact that you can pull in profile pictures yourself. The "Profile Picture Guard" acts as a pseudo-guard against the normal users.

In conclusion, the "Profile Picture Guard" is indeed protecting you from the normal users, which constitute most of the world. With that said, Facebook is not exactly fooling anyone but the developers.

Yes, one can argue that the users are also being fooled by extension if the developers are also fooled. On that note, then sure, Facebook is in fact fooling everyone with the feature. However, I wouldn't see it as a big deal. The user did upload their picture to the Web. It has to be expected that anything that comes into the Web can never be taken back. There is no magic undo button. It just comes with the fact that the user "agreed" to the Terms and Conditions and the Privacy Policy of Facebook upon the creation of their account. At that moment, the user surrendered their rights to have a say on what can be done with their profile pictures.

This comes on the same day it's revealed that Facebook sold Netflix and Spotify info about private DM conversations.

Very hard to give them the benefit of doubt on any of this.

If you care that much about privacy why are you using FB in the first place? They are not really known for being user privacy oriented corp... If someone cares that much about their pics being used in a malicious way, they wouldn't share them publicly, right? I'm not that familiar why is this specific to India but once you put something on the internet there is not much you can do about it, and skillful (or enough motivated) people will always find a way to get this kind of data that is at the end publicly available on the client side of the application.

Reminds me of an article about Quora and their attitude towards The Internet Archive. quora.com/robots.txt

# People share a lot of sensitive material on Quora - controversial political
# views, workplace gossip and compensation, and negative opinions held of
# companies. Over many years, as they change jobs or change their views, it is
# important that they can delete or anonymize their previously-written answers.
# 
# We opt out of the wayback machine because inclusion would allow people to
# discover the identity of authors who had written sensitive answers publicly and
# later had made them anonymous, and because it would prevent authors from being
# able to remove their content from the internet if they change their mind about
# publishing it. As far as we can tell, there is no way for sites to selectively
# programmatically remove content from the archive and so this is the only way
# for us to protect writers. If they open up an API where we can remove content
# from the archive when authors remove it from Quora, but leave the rest of the
# content archived, we would be happy to opt back in. See the page here:
# 
# https://archive.org/about/exclude.php
# 
# Meanwhile, if you are looking for an older version of any content on Quora, we
# have full edit history tracked and accessible in product (with the exception of
# content that has been removed by the author). You can generally access this by
# clicking on timestamps, or by appending "/log" to the URL of any content page.
# 
# For any questions or feedback about this please email robotstxt@quora.com.

Because adding a line to your robots.txt is totally going to make mirroring the site impossible.

As Some Dood said, there are a bunch of ways of getting around this, from pulling the image off the webpage source to screen capture to photographing your monitor. One wonders why they even tried.

On the other hand, I’m shocked to learn Facebook lied! No, wait, the other thing.

I wouldn’t be surprised if they’re just playing stupid to avoid paying a bounty.

Solid and beautiful article, I was translating DDHH report on Basecamp's outage for a friend and I remember her surprise on the fact that a CEO was "taking the fall" for the whole company. We need more of that, and we need it now!