Keep a published card's representative across restarts

The account that provides a published card stays its representative
ahead of server-fetched metadata, and after a restart it is recognized
by the text of the active card. Server-fetched metadata only counts as
trusted when the catalog URL is the podcast's origin, since an account
can point its synced catalog URL anywhere.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
sanapachandClaude Opus 5.5 committed 2026-11-20 15:12:52 +02:00
1 parent 767134d1dd
commit bbdac75967
3 files changed
+140 -26

No files matched your search

+8 -4
View File
@@ -144,10 +144,14 @@ your progress, history, listening counts, device names or your account.
node key that publishes its music library), not with an identity of your
account. When several accounts of this server share the same podcast,
the server publishes one card for it, built from one of these accounts'
copies of the feed (preferably one the server downloaded itself, and the
same account as long as it keeps sharing, so another account sharing the
podcast later does not replace the card's text), and keeps it while any
of them still shares it. Other members see that this server shares the
copies of the feed, and keeps it while any of them still shares it. The
account whose copy the published card shows keeps providing it while it
shares (also after a server restart, recognised by the card's text), so
another account sharing the podcast later does not replace the card's
text; a new card preferably uses a copy the server downloaded itself
from the podcast's original address. If that account's copy changes
while the server restarts, the card may be rebuilt from another sharing
account's copy. Other members see that this server shares the
podcast, not who. Podcasts shared by a deactivated account are no longer
published (within five minutes).
- The podcast page says what this server does with the card: published,
+7 -3
View File
@@ -240,9 +240,13 @@ only while the overlay runs.
- `aggregate_share_states` keeps the accounts for which `effective_share`
holds and whose card has no privacy warnings or a matching confirmation,
and builds one `PodcastShareState` per podcast with
`privacy_confirmed = true`. Representative: no warnings, then a catalog
from the server's own fetch (`meta_from_feed`), then the previous
round's representative (kept in memory), then the smallest account id.
`privacy_confirmed = true`. Representative: no warnings, then the
incumbent (the previous round's representative, kept in memory, or after
a restart an account whose card text equals the active card's text from
`PodcastDht::published`), then `AccountShare::trusted_meta`
(`meta_from_feed` and the catalog URL is the origin; an account can point
its synced catalog URL anywhere before the server fetches it), then the
smallest account id.
- At most 192 podcasts (replicas keep 256 records per publisher, tombstones
included), allocated round-robin over the sharing accounts (`allocate`):
each account's queue holds its podcasts the node already publishes