Facebook's Privacy Settings Present Intrinsic Limitations To The Platform
I've written countless times about Facebook's “privacy facade” and how it could develop potential problems in their global expansion. Today, some developers and bloggers were disappointed that Facebook did not open …
Context & Ripple Effects
In April 2009 Facebook cracked its door open: it began letting third-party developers build applications around status updates, photo sharing, and link sharing — its answer to Twitter's real-time stream. The pickup was broad for a platform story, with the L.A. Times Tech Blog and ReadWriteWeb both covering it within days, and ReadWriteWeb's verdict was blunt: despite the new openness, Facebook remains fundamentally closed.
AllFacebook has been arguing for months that this is a 'privacy facade' — settings that look granular but structurally cap what outsiders can do — and this week developers and bloggers confirmed the disappointment directly when the opened stream turned out not to grant the access they expected. The tension sits against a busy month at Facebook: an open user vote on governing documents ran through mid-April, and just before this story the company polled some users on paying for vanity URLs as it hunts for revenue.
First-order effects
- Developers who built applications on the newly shared status, photo, and link feeds hit the privacy wall immediately: content can be surfaced inside Facebook apps but cannot be exported or reused freely outside the platform's own permission boundaries.
- Bloggers and analysts covering the launch now have concrete evidence for the 'intrinsic limitation' thesis — Facebook controls openness at the data layer, not the feature layer, so no amount of new API surface changes what third parties can actually hold.
Second-order effects
- With Facebook's stream gated by its privacy architecture, Twitter's comparatively open approach becomes the default home for real-time developers — the L.A. Times explicitly framed the two as different models, turning developer disappointment into competitive advantage for the rival.
- An underground market for Facebook public profiles, circulating as industry buzz though unconfirmed, points to where pressure lands next: whatever data does become externally visible tends to get monetized by third parties regardless of what Facebook intended, raising the stakes on every permission decision.
Third-order effects
- If the pattern holds through Facebook's global expansion, the gap between perceived user control and actual data exposure becomes the platform's central structural risk — the kind of mismatch that historically draws regulator attention to default settings rather than features.
- Platform strategy splits into two durable camps — walled-garden openness versus portable-data openness — forcing every social network to choose which side of the permission boundary its developer ecosystem lives on.
The trend: Social platforms are learning that selective openness layered over a private data core caps third-party ecosystems more than any single API decision, making the permission boundary itself the strategic battleground.