Summary by TwinMind · 28m 8s

Summary by TwinMind · 28m 8s

How I (Almost) Got Sued By Big Tech

How I (Almost) Got Sued By Big Tech

Theo - t3․gg

Theo - t3․gg

Introduction and Personal Context

  • Content creator discusses article about handling cease and desist letters from Big Tech
  • Author has personal experience battling Big Tech in similar situations
  • Disclaimer: Neither creator nor article author are lawyers - seek legal counsel
  • Creator's background: Published Chrome extensions targeting Facebook/Microsoft

Facebook Cease and Desist Case Study (July 2021)

  • Facebook sent cease and desist to developer of "Unfollow Everything" Chrome extension
  • Extension helped people use Facebook less by automating unfollowing
  • Letter from Facebook Inc. (Menlo Park) and Facebook Ireland Ltd (Dublin)
  • Violations cited:
    • Unauthorized functionality on Facebook
    • Mass following/unfollowing automation
    • Impermissible use of Facebook trademarks
  • Developer's account banned 5 hours before receiving letter at midnight Thursday
  • 48-hour response deadline demanded

Creator's Similar Experiences

  • "Buzz Off" extension: Hid BuzzFeed posts from Facebook feeds
    • Too small to attract Facebook attention
  • "Chrometana" extension: Redirected Bing searches from Cortana
    • Microsoft interviewed creator about why extension was made
    • Microsoft went to Google to remove extension over trademark issues
    • Trademark dispute over Cortana blue colors in Chrome-style logo
    • Microsoft bot automatically invited top Chrome extension developers to Edge store
    • Creator submitted Chrometana, went through 3 review phases before rejection
    • Microsoft created new terms specifically to block the extension

Preparation Strategies (Before Receiving Letter)

  • Anticipate Risk: Any software interacting with Big Tech platforms risks cease and desist
    • Even non-adversarial interactions can trigger letters
    • Lifetime bans are real possibility
  • Risk Reduction Methods:
    • Work with large organization having legal team
    • Focus on clearly public interest projects
    • Note: NYU researchers still received cease and desist in 2021
  • Preparatory Steps:
    • Download all data from services you rely on regularly
    • Ensure nothing critical depends on the platform
    • Read platform terms of service thoroughly
    • Consult lawyer in your jurisdiction about terms vs IP law

Jurisdictional Differences

  • US vs Other Countries:
    • US: Defendant pays own legal costs even if they win
    • Other countries: Losing party pays winner's legal costs
  • Non-compete Examples:
    • California: Non-compete clauses basically unenforceable
    • Other states: Non-competes can be legally enforced
  • Data Rights:
    • UK/EU: Legally entitled to data even after being banned
    • US: No such protection

Initial Response Strategy

  • Immediate Actions:
    • Know you'll probably be okay - letters designed to scare
    • Cease and desist ≠ formal legal action started
    • Companies can make outrageous/unenforceable claims
    • Many terms of service contain illegal provisions
  • First Steps:
    • Pause software/service if relatively costless
    • Don't rush to respond to aggressive deadlines (48 hours unreasonable)
    • Ignore laundry list of demands initially
    • Find lawyer before responding
    • Download remaining data if not yet banned

Response Options Analysis

  • Three Options: Ignore, Comply, Defend
  • Ignoring: Extremely risky, likely leads to court
  • Complying: Best way to make issue disappear
    • Can comply selectively (stop service, ignore other demands)
    • Exception: If accounts critical to livelihood, comply fully
    • Still no guarantee of account restoration
  • Defending: Requires significant time, money, willpower
    • Even if legally right, process is painful and expensive

Public Opinion Strategy

  • Court of Public Opinion: Most viable fighting option
  • Tactics:
    • Post cease and desist letter everywhere
    • Maintain consistent drumbeat of posts
    • Cold outreach to sympathetic journalists via social media
    • Reach out to app users and sympathizers for viral sharing
    • Contact local politicians (Senator, Representative, MP)
  • Media Preparation:
    • Consider online media training before interviews
    • Be prepared for overwhelming response from journalists/supporters
    • Strategy works best if software/research serves public interest

Follow-up Communications

  • Facebook Example: Followed up for entire year (July 2021 - June 2022)
  • Proposed Agreement Document (7 months later):
    • $30,000 automatic penalty for any breach
    • Meta entitled to recover attorney fees
    • Dangled possibility of account restoration with no guarantee
    • Meta reserves right to terminate license anytime at sole discretion
  • Key Points:
    • Expect follow-ups for extended period
    • Account restoration promises often meaningless
    • Don't sign agreements with automatic financial penalties

Long-term Strategy and Acceptance

  • Reality Check: Most cases result in:
    • No account restoration
    • Cannot continue targeted software/research
    • No resources for court battle
  • Regulatory Impact: Public stories contribute to legislative pressure
    • Politicians use Big Tech horror stories for regulation arguments
    • Companies fear regulatory backlash more than individual disputes
    • EU regulations often result from accumulated complaints
  • Continued Advocacy:
    • Keep writing about experience
    • Regular updates to politicians
    • Build bridges with tech advocacy organizations (First Amendment Institute)
    • Band together with other targeted developers
    • Collective advocacy for systemic change

Creator's Additional Insights

  • Twitch Example: Senator's uninformed questions to Bezos about content theft
    • Bezos had to respond publicly about platform he didn't understand
    • Negative political attention drives internal company decisions
  • Strategic Leverage: If your story risks becoming political ammunition:
    • Companies will often back down to avoid regulatory attention
    • Potential legislative damage > cease and desist enforcement costs
    • Present escalation risk to get internal company attention