/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Meta says it has fired “roughly 20” employees who leaked “confidential information outside the company” and expects “there will be more”

here's why Bluesky: Jeff Horwitz / @jeffhorwitz : Risks rise with datapoints.  If you share one document that's accessed by ten people, you're probably fine.  If you share 20 docs accessed by 10 people that may be trouble.  Sometimes its better to share docs with the proviso that they remain unused until you've left the company. Jeff Horwitz / @jeffhorwitz : With Meta out there banging on the “snitches get stitches” drum, seemed like a good time to lay out my best guidance for tech industry employees who feel a need to speak up.  Below are a few notes:  —  www.theverge.com/labor/621059... Jeff Horwitz / @jeffhorwitz : Know that documents become less traceable over time.  If you've accessed something sensitive, giving it a few weeks/months to cool off before sharing it (or at least before a reporter contacts the company about it) makes the log history a lot harder to track. Threads: Brian Penny / @thebrianpenny : Can't help but appreciate that the bulk of this article is from leaked internal communications. Alex Cranz / @alexhcranz : leaks are always a major sign of a morale problem.  if you have bad leaks it's because you have bad morale.  you should fix that rather than loudly threatening employees.  that will only make morale (and leaks) worse.  -signed someone who worked at GO during the collapse of Deadspin X: Rat King / @mikeisaac : leaks drive execs their crazy but as they likely know by now that's the game. does always remind me of mark's 2010 email to staff after a particularly irksome leak [image] Jason Kint / @jason_kint : If I read this correctly, some of these employees were fired for leaking about leaking. And it's filed by someone who senior execs leak to last I checked. All so performative but maybe it will chill more leaks ahead of every consequential April trials in DC and Delaware. [image] Rat King / @mikeisaac : this is meta going scare tactics mode they send these sorts of emails every so often, but this is more explicit b/c they want it up on techmeme and for people to pass it around internally folks who are smart about it (no work devices etc) are fine [image] Alex Heath / @alexeheath : News: Meta tells me it has fired “roughly 20” employees for leaking and plans to fire more https://www.theverge.com/... Forums: r/technology : Meta fires 20 employees for leaking Chobeat To / Beehaw : Meta fires 20 employees for leaking

The Verge Alex Heath

Context & Ripple Effects

Meta’s action arrives after a period of internal-policy upheaval: reports described employee anger over changes to Meta’s moderation rules, followed by the company’s termination of major DEI programs. The firings make control of internal information a more explicit management priority amid that tension.

This is not Meta’s first use of employee discipline over alleged misconduct; it previously disciplined employees and contractors over user-account takeovers. Here, however, the stated issue is disclosure outside the company, bringing internal communications and press engagement into focus.

First-order effects

  • Roughly 20 Meta employees have lost their jobs over alleged external disclosure of confidential information, and the company signals that its investigation and enforcement will continue.
  • Remaining employees face a clearer deterrent around sharing internal material externally, while Meta gains a more direct mechanism to limit dissemination of unreleased decisions and debates.

Second-order effects

  • The firings can deepen caution inside teams already affected by contentious policy changes, potentially reducing internal circulation of sensitive material as well as external leaks.
  • Other large technology employers confronting labor or policy disputes may point to similar enforcement; Google previously fired and suspended staff over internal-information sharing amid labor tensions.

Third-order effects

  • If enforcement becomes a recurring response to leaks, employee-information disputes may increasingly be treated as confidentiality and trade-secret matters rather than solely as workplace-relations conflicts.
  • The enduring tension is between companies’ need to protect confidential operations and workers’ ability to raise concerns; the eventual boundary will depend on the facts of individual disclosures and applicable protections.

The trend: Big Tech is tightening control over internal information as workforce disputes and consequential policy changes make employee disclosures more consequential.

Discussion

  • @jeffhorwitz Jeff Horwitz on bluesky
    Risks rise with datapoints.  If you share one document that's accessed by ten people, you're probably fine.  If you share 20 docs accessed by 10 people that may be trouble.  Sometimes its better to share docs with the proviso that they remain unused until you've left the company.
  • @jeffhorwitz Jeff Horwitz on bluesky
    With Meta out there banging on the “snitches get stitches” drum, seemed like a good time to lay out my best guidance for tech industry employees who feel a need to speak up.  Below are a few notes:  —  www.theverge.com/labor/621059...
  • @jeffhorwitz Jeff Horwitz on bluesky
    Know that documents become less traceable over time.  If you've accessed something sensitive, giving it a few weeks/months to cool off before sharing it (or at least before a reporter contacts the company about it) makes the log history a lot harder to track.
  • @thebrianpenny Brian Penny on threads
    Can't help but appreciate that the bulk of this article is from leaked internal communications.
  • @alexhcranz Alex Cranz on threads
    leaks are always a major sign of a morale problem.  if you have bad leaks it's because you have bad morale.  you should fix that rather than loudly threatening employees.  that will only make morale (and leaks) worse.  -signed someone who worked at GO during the collapse of Deads…
  • @mikeisaac Rat King on x
    leaks drive execs their crazy but as they likely know by now that's the game. does always remind me of mark's 2010 email to staff after a particularly irksome leak [image]
  • @jason_kint Jason Kint on x
    If I read this correctly, some of these employees were fired for leaking about leaking. And it's filed by someone who senior execs leak to last I checked. All so performative but maybe it will chill more leaks ahead of every consequential April trials in DC and Delaware. [image]
  • @mikeisaac Rat King on x
    this is meta going scare tactics mode they send these sorts of emails every so often, but this is more explicit b/c they want it up on techmeme and for people to pass it around internally folks who are smart about it (no work devices etc) are fine [image]
  • @alexeheath Alex Heath on x
    News: Meta tells me it has fired “roughly 20” employees for leaking and plans to fire more https://www.theverge.com/...
  • r/technology r on reddit
    Meta fires 20 employees for leaking