Waters v. Meta Platforms: what the pleadings presented—and what the court actually addressed
This page performs a claim-by-claim audit of a pre-service, sua sponte dismissal with prejudice. It separates verified allegations, the plaintiff’s legal arguments, the district court’s stated reasons, matters the court did not separately address, and the later appellate disposition.
The narrow question is not whether every allegation was ultimately true. It is whether five claims and an emergency request for protection were accurately characterized and resolved through reasons that a party, reviewing court, legislator, or member of the public can test against the record.
The problem is visible without mastering the whole case.
Five documentary comparisons explain why this record deserves legislative and professional scrutiny.
The complaint expressly tied both § 1985(2) counts to identified federal proceedings. The dismissal nevertheless required protected-class animus while quoting authority that assigned that requirement to a different clause.
Reconsideration acknowledged that class-based animus was not required for conduct tied to prior federal actions, but then called that federal connection unclear—even though both the complaint and the dismissal order had identified it.
The dismissal said Meta’s alleged knowledge was merely general. Paragraph 21 alleged a direct email to Meta’s appellate lawyers containing screenshots, identifying the disputed threats, and requesting an investigation.
Counts I and II, Meta’s alleged role, damages, state-action theories, the underlying constitutional deprivation, and federal action did not receive separate element-by-element treatment.
The TRO was denied solely because the court found no likelihood of success. The order made no findings on alleged irreparable harm, the balance of equities, or the public interest.
An unpublished May 2, 2024 memorandum found insufficient conspiracy and state-action allegations. That outcome is disclosed here; its reasoning is linked below and reserved for a separate appellate audit.
The federal connection was explicit before the court called it unclear.
These four steps can be verified directly from the complaint and the court’s two orders.
The complaint identified federal proceedings.
Count I identified First Circuit No. 21-1582. Count II identified Supreme Court No. 22-5133. Both claim headings said “Federal proceeding.”
The dismissal itself described that connection.
Its background quoted paragraph 132 and said the alleged conduct occurred while the case was pending in the First Circuit.
The dismissal applied the other clause’s requirement.
It required class-based animus while quoting Bretz language expressly referring to the “second clause” of § 1985(2).
Reconsideration conceded the standard, then changed the premise.
The court acknowledged that animus was unnecessary for prior federal actions but described the federal connection as unclear and gave no replacement element analysis.
What happened, in order
Issue map
The labels describe the treatment visible in the written record. “Not separately analyzed” does not by itself prove that a claim was legally sufficient; it means the order did not explain the issue on its own terms.
| Issue | Record footprint | District-court treatment | Audit classification |
|---|---|---|---|
| Pre-service screening posture | IFP application; injunction and summons requests | No defendant merits briefing; court screened and dismissed with prejudice | Process context |
| Federal nexus and class animus | FAC ¶¶ 1, 132, 154; claim headings | Federal nexus described, wrong-clause animus rule applied, then nexus called unclear | Record conflict |
| Count I: Kearney/WDM conspiracy | 21 substantive claim paragraphs, plus incorporated facts | All elements declared deficient; no Kearney/WDM element analysis | Reasoning gap |
| Meta’s specific notice | FAC ¶¶ 16–34; especially ¶ 21 | Characterized as general awareness; direct notice allegation not discussed | Record conflict |
| Meta agreement or participation | FAC ¶¶ 146–150; TRO motion pp. 8–10 | No conspiracy facts found; circumstantial sequence not analyzed | Reasoning gap |
| Count II: June 2022 incident | 7 substantive claim paragraphs | Grouped with Count I; no separate element analysis | Grouped ruling |
| Injury and damages | FAC ¶¶ 145, 151–152, 158–160 | All elements declared deficient; injury allegations not analyzed | Reasoning gap |
| Count III: § 1986 | 6 substantive claim paragraphs | Dismissed only as derivative of § 1985 | Derivative ruling |
| Count IV: deprivation and state action | At least 48 paragraphs in dedicated sections | Only FAC ¶¶ 69–78 expressly cited; underlying deprivation not reached | Partial treatment |
| Count V: Bivens/federal action | FAC ¶¶ 102–111, 184–190 | Dismissed under a state-actor rationale | Category error |
| Emergency relief | 10 listed questions; four injunction factors briefed | Denied on likelihood of success alone | Other factors unreached |
| Leave to amend and reconsideration | With-prejudice judgment; Rule 59(e) request | Futility tied to animus; animus premise later withdrawn | Rationale displaced |
| Appellate disposition | Three-page memorandum | Affirmed on conspiracy/state-action insufficiency | Outcome disclosed |
They count numbered paragraphs devoted to an issue, not “proven facts.” Incorporation by reference and overlap are identified rather than inflated.
A verified complaint is evidence of what was presented under oath; verification does not itself establish that every allegation is true.
The page says “not separately analyzed” or “not reached.” It does not treat every omitted argument as automatically meritorious.
Every material issue in the supplied district-court record
Open only the issues you want to inspect. Each section identifies the question, the plaintiff’s position, the court’s stated basis, the objective audit result, and pinpoint source links.
Issue 0 · Procedural posture The case was screened and terminated before summons or defense merits briefing The court was authorized to screen the IFP complaint; the consequence was that its own grounds were never tested before becoming a with-prejudice judgment.
Plaintiff’s procedural position
The plaintiff filed an IFP application, an amended verified complaint, emergency-relief papers, and requests for summons. The injunction filing states that Kearney had been notified but had not been served by the Marshal. The plaintiff sought prompt service and merits proceedings.
Court’s action
Acting as duty judge, the court screened the complaint under § 1915(e)(2)(B), denied emergency relief, dismissed every count with prejudice, denied IFP status as moot, denied other pending motions as moot, and entered judgment.
The Ninth Circuit later said the motions to issue summons were properly denied as moot because the action had already been dismissed.
Audit result · Authorized screening, no adversarial correction
Pre-service screening is authorized; absence of a defendant response is not itself proof that dismissal was improper. It is crucial context, however: every dismissal ground came from the court, no defendant had defended it, and the plaintiff received no pre-judgment opportunity to address those grounds before the judgment became final and with prejudice.
Issue 1 · Counts I–III Federal proceedings and the class-based-animus requirement The controlling dismissal premise was conceded on reconsideration, then replaced with a record-inconsistent characterization.
Plaintiff’s record and argument
The complaint’s introduction alleged interference with First Circuit No. 21-1582. Count I repeated that docket number; Count II identified Supreme Court No. 22-5133. Both headings expressly described a conspiracy to deter a party or witness in a “Federal proceeding.”
The injunction motion and appellate brief argued that Kush, Bretz, and Ninth Circuit authority distinguish the federal-court clause from the state-court/equal-protection clause.
Court’s stated basis
The dismissal’s own background described the First Circuit proceeding and quoted paragraph 132. Its legal analysis nevertheless required class-based animus and quoted Bretz language expressly concerning the “second clause.”
Reconsideration then said that if the challenge concerned prior federal actions, animus was unnecessary—but called that connection unclear and still found no claim without naming the missing element.
Audit result · Legal standard corrected; replacement premise contradicted
The federal nexus was not implicit or buried. It appeared in the introduction, both claim headings, two numbered claim paragraphs, and the dismissal’s own background. After withdrawing the animus requirement, the reconsideration order supplied no element-specific alternative basis.
Issue 2 · Count I The alleged November 2021 conspiracy by Kearney, WDM, and named participants A Meta-specific example did not explain why the allegations against the other defendants failed every statutory element.
Plaintiff’s record and argument
Count I alleged a coordinated effort to create and use fabricated online threats to deter free participation in First Circuit litigation. It identified alleged participants, the #BlogDat group, WDM-controlled assets, timing, statements said to show coordination, later use of the material in court, and claimed resulting impairment.
The appellate brief organized those allegations around conspiracy, acts in furtherance, the federal proceeding, and injury. Those are the appellant’s allegations and inferences—not findings of fact.
Court’s stated basis
The order stated that the plaintiff had “failed adequately to aver any element” of both § 1985(2) claims. Its only factual example concerned whether Meta knew of or joined the alleged conspiracy; its other stated defect was class-based animus. The element formulation it recited addressed injury because of prior federal-court participation, while the complaint also invoked the statute’s distinct deterrence-by-intimidation branch.
The order did not identify why the separately pleaded allegations against Kearney or WDM failed conspiracy, deterrence, federal nexus, an act in furtherance, or injury.
Audit result · Conclusory treatment
The court could have found the allegations implausible or legally insufficient. It did not explain that conclusion defendant-by-defendant or element-by-element, and it did not say how its retaliatory-injury formulation disposed of the separately pleaded deterrence theory. A Meta-specific deficiency cannot, without additional reasoning, explain why Count I failed against Kearney and WDM.
Issue 3 · Meta knowledge Specific notice was characterized as general awareness Paragraph 21 alleged that screenshots and an investigation request went directly to Meta’s lawyers in the allegedly obstructed appeal.
Plaintiff’s record and argument
Paragraph 21 alleged that on November 19, 2021, the plaintiff emailed Meta’s lawyers in First Circuit No. 21-1582, included screenshots of the disputed profile and threats, asked who created them, requested an investigation, and said he would contact federal marshals.
Other paragraphs alleged that Meta was a codefendant in the federal litigation, knew of asserted platform dependence and safety violations, opposed an investigation, deleted the plaintiff’s account shortly afterward, and knew of prior litigation-related threats.
Court’s stated basis
The background said Meta was alleged to know about Kearney’s Facebook activity “generally,” community-standard violations, and a claimed 2018 employee conversation. The analysis then said the complaint failed to allege that Meta knew of an intent to intimidate or interfere with the litigation.
The order did not mention paragraph 21’s alleged email to Meta’s counsel or distinguish notice of the disputed incident from notice of a conspiratorial purpose.
Audit result · Material allegation omitted from the characterization
Paragraph 21 does not by itself prove that Meta shared an unlawful objective. It does directly contradict the broad proposition that the complaint alleged only general awareness or no notice tied to the federal litigation. The legally distinct questions—notice, knowledge of purpose, and agreement—should not have been collapsed.
Issue 4 · Meta participation The alleged circumstantial sequence was rejected without being analyzed Notice is not agreement; the unanswered question is why the pleaded sequence could not support a plausible inference at the pleading stage.
Plaintiff’s record and argument
The pleaded inference relied on a claimed employee discussion about payment for account protection, continued posting privileges after suspension, direct notice to litigation counsel, deletion of the plaintiff’s account after the disputed incident, opposition to an investigation, and the platform’s alleged importance to Kearney’s operation.
The motion argued that agreement and participation may be inferred from circumstantial conduct and timing when the sequence is assessed as a whole.
Court’s stated basis
The order said there were no facts showing a conspiracy and summarized only three categories: general activity, rule violations, and the 2018 employee discussion.
It did not address the alleged direct notice, account deletion, opposition to investigation, timing, or the difference between alleged knowledge and alleged agreement.
Audit result · Explanation missing, not proof established
The pleaded sequence may ultimately be too speculative to establish an agreement. But “no facts” is not an accurate description of a complaint that pleaded several circumstantial facts and expressly stated the inference drawn from them. A reviewable decision would identify why that inference was implausible.
Issue 5 · Count II The June 2022 witness-deterrence claim received no separate analysis A distinct event, federal proceeding, alleged mechanism, and injury were grouped into the Count I ruling.
Plaintiff’s record and argument
Count II alleged that June 18, 2022 threats were intended to deter a witness and impair presentation of a petition in Supreme Court No. 22-5133. It alleged that WDM’s social-media assets were deliberately structured to mobilize followers and make accountability harder, and that the conduct deterred testimony and impaired the plaintiff’s work on the petition.
Court’s stated basis
The background described the June incident and said the plaintiff did not identify threats targeted at himself. The legal analysis then resolved both § 1985 counts together through the Meta-awareness example and class-based-animus requirement.
The order did not say whether a threat to an identified witness could injure a party’s ability to present a federal case, or which Count II element remained absent.
Audit result · Distinct claim grouped without claim-specific reasons
Whether Count II stated a viable claim is a legal question. The written order did not answer it separately. Its observation that no threat targeted the plaintiff did not address the pleaded theory that intimidation of a witness impaired the plaintiff’s federal proceeding.
Issue 6 · Counts I–III Injury and damages were pleaded but not analyzed The order said every element failed without explaining why the alleged impairment and personal injury were legally insufficient.
Plaintiff’s record and argument
The complaint alleged that the two incidents impaired concentration, sleep, work, witness participation, and effective presentation in the identified federal proceedings. It also alleged mental anguish and aggravation of a diagnosed adjustment disorder.
The motion and appellate brief cited Head v. Wilkie and argued that traditional tort injury and witness-intimidation injury were cognizable under § 1985(2), not limited to lost property or economic loss.
Court’s stated basis
The court recited an injury-or-damages element, then said every element was inadequately pleaded. It provided no injury-specific discussion and did not cite or distinguish the pleaded damages paragraphs.
Audit result · Element named, application omitted
The order identified the element but did not apply it to the alleged injuries. A minimal finding could have stated whether the problem was causation, legal cognizability, factual plausibility, or some other defect.
Issue 7 · Count III The § 1986 neglect-to-prevent claim was dismissed only as derivative Its knowledge, power, diligence, prevention, and causation allegations were never independently reached.
Plaintiff’s record and argument
Count III alleged that Meta obtained knowledge through its attorneys and role in the prior litigation, could have investigated the disputed account and screenshots, could have stopped alleged special posting privileges, and could have confirmed evidence said to undercut later retaliation.
The motion distinguished this claimed duty from publisher liability and framed it as a § 1986 duty based on knowledge and power to prevent a § 1985 wrong.
Court’s stated basis
The order correctly treated § 1986 as dependent on a viable § 1985 claim and dismissed Count III on that basis. It did not reach the separate § 1986 elements.
Audit result · Derivative dismissal
This was not an independent merits ruling on § 1986. Because the § 1985 dismissal relied in material part on a class-animus rule later withdrawn, the court should have stated whether Count III still failed and on what element.
Issue 8 · Count IV The alleged constitutional deprivation was not reached after state action was rejected The complaint asserted due process, class-of-one equal protection, fabricated-evidence, and punishment-like public-shaming theories.
Plaintiff’s record and argument
Count IV alleged punishment-like public shaming without adjudication, use of fabricated material, arbitrary differential treatment as a “class of one,” state-enabled access to information and databases, alleged judicial and police assistance or nonprotection, witness deterrence, and resulting liberty, reputational, and emotional harm.
The motion cited due-process, fabricated-evidence, equal-protection, and public-shaming authorities and argued that the state-action facts had to be considered in combination.
Court’s stated basis
The order rejected the state-action gateway and therefore did not analyze whether the alleged conduct deprived the plaintiff of a protected right, whether “stigma plus” or another doctrinal limit applied, or whether the class-of-one allegations were sufficient.
Audit result · Underlying constitutional theories not reached
A dispositive state-action ruling can make further analysis unnecessary. The page therefore does not call this omission an independent legal error. It does show that the dismissal was not a merits rejection of every constitutional theory asserted in Count IV.
Issue 9 · Count IV At least 48 dedicated state-action paragraphs were reduced to one subset The court expressly cited FAC ¶¶ 69–78 but did not address the alleged judicial-conspiracy facts in ¶¶ 79–101 or Count IV’s later theories.
Plaintiff’s record and argument
The complaint and motion presented several routes to state action:
- access to state databases or state-issued credentials;
- joint action and alleged transfer of nonpublic information;
- significant encouragement and alleged mutually beneficial relationships;
- alleged conspiracies with judicial actors and failure of independent judgment;
- allegedly discriminatory nonprotection and a class-of-one theory; and
- an aggregate, fact-bound assessment rather than one isolated fact.
Court’s stated basis
The order called defendants private and found no plausible state action. It expressly discussed only an attorney login used to search court information and claimed police/government connections, citing FAC ¶¶ 69–78.
It did not mention FAC ¶¶ 79–101, the alleged judicial-conspiracy and failed-independent-judgment theories, the later Count IV paragraphs, or the motion’s aggregate-analysis argument.
Audit result · Partial treatment of a fact-bound gateway
Paragraph volume does not equal legal sufficiency, and several theories face substantial doctrinal hurdles. But the order treated one subset as if it represented the entire state-action presentation. A reviewable ruling should identify which theories were considered and why the pleaded aggregate remained insufficient.
Issue 10 · Count V The Bivens claim was dismissed under a state-actor rule The district order merged § 1983 and Bivens even though one concerns state action and the other federal action.
Plaintiff’s record and argument
Count V alleged federal action through a claimed conspiracy involving a federal judge, prior sua sponte procedure, alleged factual and legal mischaracterizations, denial of post-judgment response, and the asserted role of federal law. The motion argued that federal-action analysis parallels state-action analysis.
Court’s stated basis
The district order said that “Claims 4 and 5 for violation of § 1983 and Bivens” could be brought only against state actors, then conducted only a state-action analysis.
The Ninth Circuit later stated the basic distinction: Bivens replaces the state actor required by § 1983 with a federal actor. The appellate panel nevertheless affirmed because it found the allegations insufficient.
Audit result · The stated category was wrong
The district court did not analyze the claim under its asserted federal-action theory. This does not establish that Count V was viable; Bivens remedies are narrowly limited and the pleaded theory faced serious obstacles. It does establish that “defendants are not state actors” was not a reasoned analysis of the federal-action claim actually pleaded.
Issue 11 · Emergency relief The TRO was denied on likelihood of success without findings on the remaining factors The motion separately briefed irreparable harm, equities, public interest, and requested consolidation.
Plaintiff’s record and argument
The motion requested temporary and preliminary restraints related to alleged harassment of parties, witnesses, lawyers, and court officials. It separately argued likelihood of success, continuing and irreparable harm, equities, public interest, and consolidation or advancement of merits proceedings.
The asserted harm included witness deterrence, litigation impairment, health effects, and a claimed continuing risk while the action was pending.
Court’s stated basis
The order recited that likelihood of success was a threshold showing. It denied the TRO because the complaint failed to state a claim and therefore did not analyze the other factors.
All other pending motions were denied as moot when the action was closed.
Audit result · Safety allegations left without findings
A court may treat failure on likelihood of success as dispositive. The objective gap is that serious safety and witness allegations received no findings at all, while the merits premise included the errors and compressed reasoning documented above. That combination made the emergency issues difficult to review while relief could still matter.
Issue 12 · Finality and correction The stated reason for denying leave to amend was displaced on reconsideration The with-prejudice ruling relied on inability to plead class animus; reconsideration acknowledged that animus was unnecessary for federal-action conduct.
Plaintiff’s record and argument
The appellant’s procedural history says the Rule 59(e) filing promptly identified that the order had applied the second clause’s animus rule to first-clause federal-proceeding claims. The appellate brief also argued that a pro se civil-rights complaint should not have been terminated with prejudice without an opportunity to cure.
Court’s stated basis
The dismissal found amendment futile principally because the plaintiff could not allege class-based animus and expressly maintained that it was unnecessary. For Counts IV and V, the order said leave was unwarranted “for the reasons listed above” without identifying an incurable defect.
Reconsideration accepted the possibility that animus was unnecessary, then stated only that the complaint still failed and that the remaining arguments were unpersuasive.
Audit result · Finality remained after its clearest rationale fell away
The reconsideration order did not explain why any remaining defect was incurable, which element could not be amended, or why the explicit federal docket references were unclear. The case remained closed with prejudice even though the original futility analysis for Counts I–III rested on a requirement the court no longer defended.
Issue 13 · Arguments not adjudicated Section 230, issue preclusion, early merits procedure, and several remedial questions were not reached These should not be described as issues the district court decided.
Plaintiff’s record and argument
- Section 230 allegedly did not bar duties based on conduct, advance knowledge, or § 1986 rather than publisher status.
- Prior litigation allegedly did not preclude claims based on later conduct and issues not actually litigated.
- Rule 65(a)(2) consolidation and early partial merits treatment were requested.
- Nominal, compensatory, and punitive remedies were pleaded.
Court’s stated basis
The district court did not rely on Section 230 or issue preclusion, did not adjudicate summary judgment, and did not reach damages after finding no viable claim. Related pending motions were denied as moot.
Audit result · Preserve the boundary
These are part of the plaintiff’s litigation position, not holdings of the district court. Listing them prevents later readers from mistaking judicial silence for a merits rejection—or mistaking an untested argument for an established rule.
Issue 14 · Appellate status The Ninth Circuit affirmed; that disposition must be read with the district record The outcome is disclosed prominently rather than hidden in an archive.
Appellant’s position
The opening brief challenged the clause error, factual characterizations, conspiracy analysis, state-action treatment, injunction denial, and lack of findings. It asked for reversal and prompt relief.
Ninth Circuit disposition
On May 2, 2024, a three-judge panel affirmed in an unpublished memorandum. It found insufficient facts to show a conspiracy to deter federal-court participation or action under color of state law; treated the injunction challenge as moot; upheld reconsideration; and held the summons and deposition motions moot after dismissal.
The panel also correctly described Bivens as substituting a federal actor for § 1983’s state actor.
Audit result · Final outcome disclosed, reasoning reserved
The affirmance is part of the record and should appear on every public version of this page. It does not erase the documented district-court errors; it means that any claim that those errors required reversal must also confront the appellate panel’s alternative insufficiency holding. A separate page can audit that holding with the same claim-by-claim method.
A direct conclusion without overclaiming
The documents establish
- the complaint expressly identified two federal proceedings;
- the dismissal applied a class-animus rule tied by its own cited language to a different clause;
- reconsideration acknowledged animus was unnecessary for the federal clause but called the explicit nexus unclear;
- a specific alleged notice to Meta’s counsel was omitted from the court’s “general awareness” characterization;
- the Bivens count was analyzed under a state-actor rule;
- multiple claims and theories received grouped or conclusory treatment; and
- no defendant had filed a merits response before the court supplied and accepted the dismissal grounds.
The documents do not by themselves establish
- that every allegation in the verified complaint was true;
- that every legal theory was viable;
- that Meta or any other defendant joined a conspiracy;
- that any judge acted with a particular subjective motive; or
- that the district-court errors necessarily required reversal after the Ninth Circuit’s alternative holdings.
The case illustrates three correctable system failures.
Minimal findings
Require the controlling standard, material facts, and principal reason for rejecting each high-impact claim or motion. “Every element fails” would not substitute for application.
Review the minimal-findings proposalExpedited plain-error review
Permit narrow early review when a written ruling applies an objectively inapplicable standard or relies on a factual premise contradicted by the filed record.
Review the expedited-review proposalNotice before consequential sua sponte action
When feasible, identify dispositive grounds before a with-prejudice ruling so a party can answer them while correction remains practical.
Review the sua sponte failure modeDocuments used for this audit
Readers can audit the page from the original filings and orders. The appellate memorandum is linked from the Ninth Circuit’s official site.
- First Amended Verified Complaint — Dkt. 17, filed March 24, 2023.
- TRO / preliminary-injunction / consolidation filing — supporting filing dated March 27, 2023.
- Order denying TRO, dismissing complaint, and entering judgment — April 5, 2023.
- Order denying reconsideration — May 17, 2023.
- Appellant’s opening brief — Ninth Circuit No. 23-15547.
- Ninth Circuit memorandum — filed May 2, 2024.
Use the record to evaluate the safeguards.
This case is not offered as a demand that legislators decide civil liability. It is a test of whether consequential judicial errors are made visible, explained, and correctable while correction still matters.