Unfollow Everything
Unfollow Everything was a browser-extension product for giving users control over Facebook feeds. Public evidence shows enforcement pressure from a large platform even though the tool modified workflows on behalf of users.
View original storyProduct snapshot
What it was
Unfollow Everything was a browser extension that let Facebook users mass-unfollow friends, groups, and pages to empty their News Feed while keeping the rest of Facebook usable.
Who it was for
Problem / value
It gave users a fast way to reduce algorithmic feed exposure and make Facebook less habit-forming without deleting their account.
Core workflow
Users mass-unfollowed Facebook friends, groups, and pages to empty the News Feed while keeping direct Facebook access.
Core dependency
Public sources report that the solo developer behind Unfollow Everything took the extension down after Facebook/Meta enforcement pressure, including a cease-and-desist letter and account bans.
Product form
Pricing model
No public pricing data found; public reports frame it as a user-control tool rather than a commercial SaaS.
Competitors or alternatives
What happened
Summary
Unfollow Everything was a browser extension that automatically unfollowed friends, groups, and pages on Facebook to empty the News Feed.
Outcome
The 2024 complaint says Meta's letter demanded Barclay shut down the tool, delete associated Facebook data, and promise not to create another tool interacting with Facebook or Instagram.
Core risk
Platform Dependency And Terms Enforcement
Timeline
- The extension was released by UK developer Louis Barclay before being taken down in 2021.
- Public reports say Facebook sent a cease-and-desist letter and permanently disabled the creator's Facebook and Instagram accounts.
- A 2024 AP report and federal complaint describe Unfollow Everything 2.0 as a later legal/research follow-on.
Before you build
Why it matters
Solo extension builders often depend on large platforms' interfaces and terms. This case shows how distribution and product existence can be constrained by platform enforcement, not only by user demand.
Primary check
Map platform enforcement risk and build a backup path before shipping a tool that changes how a major social platform works.
Checklist
- Can you name the first buyer segment and the repeated job they need solved?
- Can you reach that segment without relying on one fragile channel?
- What happens if the platform, API, or data source changes terms or blocks access?
- What evidence would disprove the platform dependency and terms enforcement risk?
- Before building on a platform, map the exact terms, automation limits, and enforcement history.
- A tool can create user value while still being unacceptable to the platform it depends on.
- For risky extensions, legal exposure and account dependency should be evaluated before public launch or research partnerships.
Relevant if
- You are building a similar chrome extension with public-source distribution risk.
- Your product depends on another platform, search channel, API, or third-party data source.
- You need to validate who will repeatedly pay before investing in product polish.
Less relevant if
- You already control a reliable acquisition channel for the exact buyer segment.
- The product is an internal tool with no need for public distribution.
Pre-build tests
- Run a landing-page or concierge test with the narrowest buyer segment before building the full workflow.
- Ask users to commit to a paid pilot, not only to join a free waitlist.
- Prototype the highest-risk platform or data dependency first and document backup options.
Transferable lessons
- Before building on a platform, map the exact terms, automation limits, and enforcement history.
- A tool can create user value while still being unacceptable to the platform it depends on.
- For risky extensions, legal exposure and account dependency should be evaluated before public launch or research partnerships.