How Facebook Responded to Tunisian Hacks
January 25, 2011
Share this post
2 Comments

Law Bytes
Episode 275: David Loukidelis on Why Stripping Privacy Enforcement from Canada’s Privacy Commissioner in Bill C-36 is Unnecessarily Risky Policy
byMichael Geist

June 22, 2026
Michael Geist
Search Results placeholder
Michael Geist on Substack
Recent Posts
Why Being Locked Out of Frontier AI is The Sovereignty Threat Canada Missed
Blocked Twice: How Bill C-34’s Kids’ Social Media Ban Would Compound the Online News Act’s Harm to Young Canadians’ News Access
The Law Bytes Podcast, Episode 275: David Loukidelis on Why Stripping Privacy Enforcement from Canada’s Privacy Commissioner in Bill C-36 is Unnecessarily Risky Policy
The Data on Australia’s Social Media Ban: The Better the Privacy Protection, The Less Effective the Ban
Shaky Ground Gets Shakier: What the U.S. Supreme Court’s Location Data Decision Means for Bill C-22

uhm, and what about the rest of us?
Hopefully I don’t get slapped down for lifting this one sentence from the article (fair dealing right? does that still exist?)
> First, all Tunisian requests for Facebook were routed to
> an https server.
Good for Tunisians. What about the rest of the world that is susceptible to Facebook’s apparent lack of care for the security and privacy of it’s users?
Sure, anyone can *optionally* choose to use the secure https service, but really? Everyone has to know that? Does my mom? I doubt it. Does your mom?
Why is Faceboot so careless with everyone’s privacy?
Oh Ms. Stoddart? Where are you?
Maybe she has already come down on FB for this lack of mandatory security of one’s privacy. TBH, I wouldn’t go near FB with a 100′ pole so I have not really read her criticisms of FB’s privacy (doesn’t affect me), but I sure hope this lack of mandatory encrypted connections is one of her requirements.
…
The real problem was that the Tunisians were getting the Facebook data for free. Everyone else is paying for it.