Contact
Role addresses only. Mail sent to an individual is usually slower to reach the right person.
| Purpose | Address | Typical response |
|---|---|---|
| Operations, sync problems, mirror requests | ops@20140714.xyz | 2 working days |
| Abuse, excessive load, scraping | abuse@20140714.xyz | 1 working day |
| Security disclosure | security@20140714.xyz | 48 hours |
Before you write
Most messages we receive are answered by the FAQ. In particular:
slow downloads are usually the concurrency limit, and 404 responses inside a
distribution tree are almost always an upstream packaging issue rather than a sync failure.
When reporting a sync problem, include the tree name, the exact URL, the timestamp in UTC and
the output of curl -sI against that URL. Without these we cannot tell a mirror
fault from a client misconfiguration.
Security disclosure
Please do not open a public issue for security problems. Mail
security@20140714.xyz, preferably encrypted with the key below. We will
acknowledge within 48 hours and aim to publish a short advisory once a fix is deployed.
The machine-readable version of this policy is published at /.well-known/security.txt, as described in RFC 9116.
Operational GPG key
Used for signing status advisories and for receiving encrypted reports.
- Key ID
- 77BE 2226 F867 5DCC
- Fingerprint
- F000 B7B7 92A8 00AD 837A A8A0 77BE 2226 F867 5DCC
- Algorithm
- Ed25519 (sign) + cv25519 (encrypt), created 2026-10-31, expires 2028-10-30
- Download
- /.well-known/openpgp-key.asc