Almost none of Matters' governance tools was designed from scratch. Most were forced into being, one step at a time, by real events: a flood of porn ads gave rise to account deletion; deletion proved too heavy a penalty, so it gave rise to the quiet room; and because spam floods could never be fully held back by hand, the model was finally pushed to the front line to stand guard. On the timeline below, the red dots are governance events and the blue dots are service upgrades — a line that finally converges on the Lunar New Year of 2025 and a mistaken block that rewrote a domain query (DNS-RPZ).
- 2018.10Service Upgrade
All articles uploaded to distributed storage (IPFS)
Decentralized storage goes live, laying the groundwork for future censorship resistance: content is backed up to a distributed network, so even if the domain is blocked, it can still be read via its content fingerprint.
- 2018.12Governance Event
First concept for the admin backend
Operations colleagues joined the discussion; at first only three features were imagined: hiding inappropriate articles, muting accounts, and freezing accounts.
- 2019.06Governance Event
Hong Kong anti-extradition movement: surge of impersonation accounts
Fake accounts impersonating Jiang Zemin and Wu Den-yih appeared, and Wu Den-yih's office actually wrote in asking us to deal with it; the platform built its first community governance framework.
- 2019.08Governance Event
Community litigation system goes live
An early attempt to devolve governance to the community: filing a complaint plus tips from 20 people would trigger a vote. It later gave rise to problems such as bloc voting and sock-puppet vote-rallying.
- 2019.12Governance Event
Account deletion feature goes live
Prompted by a winter flood of pornographic ads (escort spam); deletion is irreversible and was initially used only against pornographic ads.
- 2020.04Service Upgrade
Fingerprint blocking and human verification (reCAPTCHA)
Facing coordinated like-farming and bot registrations, this cut down invalid activity at the behavioral layer.
- 2020.12Governance Event
The era of political flooding begins
Guo Wengui arrived, and Matters began to be furiously flooded with political posts; operations spent a long stretch manually taking down individual articles.
- 2021.03Service Upgrade
Circle launches; architect jury
An architect jury replaced universal voting, responding to the bloc-voting problem of community litigation.
- 2022.06Governance Event
Secondary-scam posts appear en masse
The fuse for the later 2025 Lunar New Year DNS-RPZ blocking incident—this kind of content tripped the Taiwanese government's anti-fraud scanning.
- 2022.07Background
Largest denial-of-service attack (DDoS) ever
To fend off the attack, Cloudflare protection was enabled.
- 2022.09Service Upgrade
IPNS decentralized personal pages enabled
Using a fixed address to point to an updating content fingerprint, making decentralized content easier to organize and to subscribe to.
- 2022.12Service Upgrade
ENS integrated with IPNS
Using memorable .eth names to point to a user's IPNS, for example vitalik.eth.
- 2023.04Service Upgrade
Blackhouse feature (backend version) goes live
It kicks an entire account off the article list. Once the blackhouse existed, flooding could mostly just be tossed in there, and deletion was rarely used anymore.
- 2024.08Service Upgrade
First spam-detection model goes live
Moving from keyword filtering to a model that “understands meaning”: built on a BERT architecture, using the IBM Granite embedding model with LoRA fine-tuning, starting with roughly 40,000 positive and negative samples.
- 2024.11Legal Event
iWIN reports pornographic content
iWIN, an internet content safety body established by the private sector under a Taiwanese government commission, reported inappropriate content on the site.
- 2025.01Governance Event
TWNIC “DNS query rewriting (DNS-RPZ)” wrongful-blocking incident
During the Lunar New Year holiday some Taiwanese users could not reach matters.town; the assessment was that TWNIC had blocked it by rewriting domain queries. Over the holiday, procedural remedies could not be initiated in time.
- 2025.02Service Upgrade
IPFS migrated to Storcha & Pinata
Moving from self-managed nodes to storage service providers; the IPNS service was discontinued.
- 2025.03Service Upgrade
Human verification (reCAPTCHA) and email allowlist retired
Because the spam-detection model was already effective enough, some of the old behavioral-layer restrictions were removed.
- 2025.07Service Upgrade
New homepage goes live
The homepage ranking logic was updated—what everyone calls “the algorithm.”
- 2025.08Service Upgrade
Updated spam-detection model goes live
Adding a comment model, ring detection, and a “when in doubt, don't judge” decision mechanism, pushing the false-positive rate even lower.
Lunar New Year 2025: when the platform first became the governed
During the Lunar New Year holiday, some users in Taiwan suddenly could not reach matters.town; a black warning screen popped up reading “this is a counterfeit site / counterfeit address.” The team's assessment: after receiving a report, the Taiwan Network Information Center (TWNIC) blocked Taiwanese users from connecting by DNS-RPZ Tampering at the level of the internet's “phone book”: the lookup result for a given address is altered or blocked, so users can no longer reach the original site. . A platform that normally blocks others got, for the first time, a taste of being blocked itself — with nowhere to turn for help.
Should a single content violation really get the entire site blocked at the infrastructure layer? This is the first question the incident left behind — the “principle of proportionality.”
“Matters was always the one blocking others… all we ever thought about was how to judge which accounts were problematic… so is there a corresponding remedy mechanism? This was a very good moment of reflection for us.”
Ironically, the calls to the remedy hotline “came to nothing.” In the end it took a project lead who had once served at the Ministry of Digital Affairs, reaching the TWNIC director-general directly, to get access restored within hours. The article itself in fact still existed on distributed storage (IPFS) and had never been destroyed, yet most users simply “couldn't see it,” because what had actually been cut off was the everyday entrance (the domain). “Delete the domain, the content fingerprint remains” turned from a technical claim into a real-life escape — while also exposing its cruel limits.