3 Commits

Include renames

Author	SHA1	Message	Date
thepraandClaude Opus 5.5	6fccb6fe35	P7: downvotes go out, and feeds are read through the server's reader ... Votes out. A persona's downvote is a Dislike (POST /api/v1/statuses/:id/downvote and /undownvote, the viewer's own as privapub.votes.downvoted). One vote a post: a changed vote is sent as the new vote alone, as Lemmy sends one, since an Undo of the old one beside it could arrive after it and take the new one away; Undo goes only when a vote is taken back. A vote on a post in a remote community goes to the community, which counts it, and to the author only when on another server: one copy a server, since PieFed drops a second copy of an activity it has just seen. Mbin keeps a favourite apart from a vote, so there a favourite stays after a switch to a downvote. Feeds followed (owner decision 2026-10-07: through the server). Following a feed (Lemmy's multi-community, PieFed's feed) keeps a FeedSubscription for the persona and nothing else; the new Service privapub_feeds (LocalActorKind.Reader, reserved by migration _017) follows every community of the feeds read here, reconciled when a persona follows or leaves one, when a feed's list is read again (kept as it was when it cannot be read) and every six hours. Its Following rows carry FollowerKind, so nobody's home gets what it brings in and its unanswered follows are sent again as its own. The persona reads GET /api/v1/timelines/feed/:id (the feed's threads, ours included) and lists its feeds at GET /api/v1/feeds. Checked in the pasture, every scenario: 873 pass. The 14 failures are Hubzilla's (identical on the previous commit: Hubzilla no longer answers a follow in this pasture since its restore) and two activities Smithereen never sent; followsync passes once the pasture's restore is older than the 14-day pause. Live: alice's downvotes count as downvotes on Lemmy 1.0 and PieFed, replacing her upvote; Lemmy 1.0 and PieFed take privapub_feeds' follows and their threads reach the feed timelines. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-08 02:15:28 +02:00
thepraandClaude Opus 5.5	01808fa644	Follow requests nobody answers are sent again ... A Follow was resent only when the persona followed again. Lemmy 1.0 sends nothing it queued for a server before it started sending there, so the Accept of a community follow made on first contact was lost for good: the village's persona stayed "requested" a day while Lemmy listed her as a follower, and every post the community announced was refused as not followed. A request still unanswered is now sent again, the same activity, after 15 minutes, an hour, 6 hours, a day, two and four days (FollowResender, every 15 minutes); a server that holds the follow answers the copy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw	2026-10-05 07:33:59 +02:00
thepraandClaude Opus 5.5	61f6ca0676	Personas can follow: locally at once, remotely by Follow and Accept ... Following records what a local persona follows, local or remote, with its state and the Follow activity's id. FollowService (behind /clientapi/follow, /clientapi/unfollow and /clientapi/following): - resolves @user, user@host or an actor URI; - a local account is followed in-process: accepted unless it approves followers by hand, a Follower row on the other side, a community gains the persona as a member, and a Follow or FollowRequest notification; - a remote account gets a Follow signed by the persona, at /grunts/follow-{id}, and stays Requested until an Accept; - unfollowing deletes the rows, or sends Undo{Follow} to a remote account. Inbound Accept and Reject are matched to the Follow by its id (or, for an embedded Follow without one, by its actor), and only from the account that was followed. A remote Follow now notifies the persona too. Notification is the per-persona record P1.2 builds on, deduplicated by type, persona, sender and post. TimelineEntry and Favourite are created with their indexes for the next commits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-01 11:32:33 +02:00