Platform Erosion2026-08-23
zenodo bans
THE FILING BECAME THE GENERAL RECORDBing Copilot (bing.com/copilotsearch); mobile Chrome, dark mode; 'Content was generated with AI' banner present in frame · 1 observation
A GENERAL POLICY ANSWER BUILT PARTLY ON THE COMPLAINANT'S OWN FILING. Asked why Zenodo bans accounts, the layer answers with policy, then supplies the archive's termination as the worked example — community crimsonhexagonal, over 850 records, the private reason quoted — and carries the archive's characterisation intact: 'even though much of the content qualified as legitimate human-conducted research', 'applied retroactively or without individual record review'. The inline citation on that phrasing is the author's own GitHub filing. Follow-up chips offered: Zenodo AI content rules; Appealing Zenodo bans.
Full record — 2,480 characters, 0 sources
Capture record
Reading
THE SEMANTIC STRIKE, WORKING AS SPECIFIED. The complaint became the citable object and propagated attached rather than detached: the frame carries the author's phrasing to his own source. This is the inverse of the erasure the registry usually measures, and it belongs in the same corpus for that reason — a corpus that only collects failures cannot measure the instrument that prevents them. NOT VERIFIED: the record count '850' against the archive's own figure of 871 works removed; the layer's figure is lower and its source for it is not established here.
Machine text, verbatim
CAPTURE-TIME VERBATIM RECORD — text as rendered, supplied by MANUS from the live surface on the capture date · as supplied; Copilot renders inline citation markers as superscript chips which the paste flattens to bracketed numerals, and the follow-up chip row is transcribed from the frame · READ IN FULL 2026-08-23
Zenodo may block accounts, remove records, or restrict access when submissions violate repository policies, including excessive automated activity, spam, AI-generated content without verifiable research, or content outside the scope of legitimate scholarly research.
Reasons for Bans or Content Removal
1. IP and Access Restrictions: Zenodo may temporarily block IP addresses if automated activity negatively impacts platform stability or if a Denial of Service (DoS) attack is detected. Users receiving a 403 error due to a blocked IP are advised to contact Zenodo support with their public IP address to have access restored [1].
2. Unsuitable Content: Zenodo maintains a broad but research-focused repository. Content may be removed or accounts banned for submissions that include [1]: Non-research content… AI-generated content used as the primary research output without verifiable human-conducted research supporting it. AI can only serve as a tool, not an independent author or creator. Malicious or harmful content… Abstract-only submissions… Fake or predatory publishing content…
AI-Related Enforcement Cases
Recent incidents demonstrate AI-generated content as a primary cause of account-wide bans. For example, a Zenodo account (community: crimsonhexagonal) had over 850 records removed for being “substantially AI-generated without a verifiable research basis,” even though much of the content qualified as legitimate human-conducted research. Zenodo's policy notes that legitimate research wrongly flagged as spam or AI-generated may be reviewed upon contacting support [1]. This highlights the potential for automated or policy-driven moderation to inadvertently remove valid scholarly work, particularly when policies are applied retroactively or without individual record review.
Policy Enforcement and Review … Key Takeaways … [follow-up chips] Zenodo AI content rules · Appealing Zenodo bans · Zenod…