3 Commits

Include renames

Author	SHA1	Message	Date
thepraandClaude Opus 5.5	bb9bd71391	P5, first batch: summaries stop hiding articles, personas get reachable names, blocks federate ... - A remote `summary` is a content warning only on a Note or Question, or when `sensitive` is set. On Articles, Events, Videos, Pages and Audio it is an excerpt (WordPress teasers, Mobilizon dates and places, Mbin titles) and is now kept as `Post.Excerpt` instead of hiding the post. `Post.ObjectType` records the remote type, and the Mastodon API shows a remote non-Note object's title above its body again. - Persona usernames must match `^[a-z0-9_]+$`, as groups already did; a name outside it was unreachable from Mastodon and Misskey. - `postingRestrictedToMods` is defined in our JSON-LD context (Iceshrimp.NET drops undefined terms). - `Vary: Accept` on actor and object URLs. - Owner decision: blocks federate. A block sends `Block`, an unblock `Undo{Block}`; checked live against GoToSocial. - Owner decision: a persona's and a group's `published`, and the day in new ids, is a random day up to two weeks before creation, so personas made the same day no longer share a date. Migration _007 gives existing ones theirs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-01 17:39:58 +02:00
thepraandClaude Opus 5.5	31542a181e	Remote posts take their timeline place on arrival, and an unedited one has no edit date ... Found by the first live run against GoToSocial: - A remote post's id came from its published second plus random bytes, so a reply arriving in the same second as the post it answers could sort under it, and a late arrival landed behind a client's since_id. A post published within the last hour now gets an id for its arrival; backfill keeps its published time. - NoteParser.Time returned default(DateTime) for a missing "updated", so every remote post was stored as edited in year one. Migration _006 clears the stored ones. - published now carries milliseconds, so peers that derive ids from it (GoToSocial, Mastodon) keep our posts in order within a second. 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
thepraandClaude Opus 5.5	e99b76dbd7	Home timelines, mention notifications, and threads that fetch their parents ... Fanout writes a TimelineEntry for every persona a post should reach: the author, local followers of a local author, local followers of a remote one, the members of a direct conversation or a circle. Mastodon's home rules apply when it is written: a reply shows only to followers of both sides (or to the one replied to), a reblog only where reblogs are wanted. A mention of a local persona becomes a Mention notification. Inbound posts are now also kept when a persona follows their author. RemotePosts holds what CreateHandler and backfill share: building a Post from a note, and fetching a public parent the first time a reply to it arrives, so its author is known (a reply to an unknown or non-public parent stays out of home timelines). Each fetched ancestor queues a FetchAncestors job for the next one, up to ten deep. /clientapi/timeline/home and /clientapi/notifications (with /notifications/read) page by max_id for the persona's own root only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-01 11:37:41 +02:00