3 Commits

Include renames

Author	SHA1	Message	Date
thepraandClaude Opus 5.5	aa7e43a61e	T14: Lemmy 1.0 in the pasture ... peers/lemmy.sh runs the Lemmy 1.0.0-beta.2 backend on the shared Postgres. It trusts Caddy's CA through SSL_CERT_FILE and reaches the pasture through DANGER_FEDERATION_ALLOW_LOCAL_IP. Lemmy 0.19 cannot join: its rustls trusts only its bundled roots. LEMMY_LOG sets RUST_LOG. scenarios/lemmy.sh drives Lemmy through its v4 API. 20 checks pass, three runs in a row: - communities both ways; - a titled thread each way, and alice's mention of a Lemmy community becoming a thread there; - the Lemmy community's announce reaching alice's home; - comments both ways and alice's like as an upvote; - private messages both ways; - statistics. Two expected failures: votes, which Lemmy sends only through the community as Announce{Like|Dislike}, and a moderator's removal. Both belong to P7. What it showed, in docs/INTEROP.md: - Lemmy 1.0 keeps its user's thread in a remote community pending until the community announces it back. It clears the flag before answering that echo 400 ("Object is not remote"). Leaving the author's server out of the Announce, as tried here, left every such thread pending, so GroupDistributor now says why the echo stays. - Every bare Announce{object} is answered 400, as Lemmy answers its own compatibility Announce(Page). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ELjqpznMFMNrJoJUj6K5p2	2026-10-03 14:24:15 +02:00
thepraandClaude Opus 5.5	c301f0c498	T9: the pasture as plugins ... tools/pasture/run.sh up [peer...] | down | logs | ps and interop.sh [peer...] are now built from parts: - lib/pasture.sh: network, Caddy with its CA in a volume and copied to .ca/root.crt, Mongo, PrivaPub; - peers/<name>.sh: each peer's <name>_up; - lib/interop.sh: ok, ko, and xf for checks expected to fail until a later phase; privapub_token <persona>, which gives each peer its own persona under one root; and stats_check; - scenarios/<name>.sh: each peer's checks. GoToSocial is pinned at 0.22.1, the version the 33 checks were proven on. Its scenario gains four statistics checks: - the admin statistics describe gts.test as gotosocial; - they count inbound and outbound traffic; - they name no account. 37/37 passed three runs in a row. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ELjqpznMFMNrJoJUj6K5p2	2026-10-03 11:42:03 +02:00
thepraandClaude Opus 5.5	8f4d6cbdf9	A private fediverse on the workstation: PrivaPub against a real GoToSocial ... tools/pasture/run.sh starts PrivaPub, GoToSocial and Mongo on one podman network behind Caddy's internal CA, and interop.sh drives both through their own client APIs: follows (one to a locked account), posts, CW, replies, likes, boosts, DMs, edits, deletes and unfollow. All 25 checks pass, three fresh runs in a row. - Federation:AcceptAnyCertificate joins the two test-network switches; startup refuses all three in Production. - WebFinger falls back to http only when AllowPlainHttp is on. - A bootstrap logger, so a failure before the host is built is no longer silent. - P4 is ticked in the roadmap, with what has not been run live (Lemmy, a Mastodon circle member). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-01 13:19:16 +02:00