Keep replica room for the cards a rebalance publishes
Replicas count unexpired tombstones toward the 256 records per publisher and refuse new keys beyond it. A round now admits at most as many podcasts that need a new key as that room allows, so a fair-share rebalance never displaces cards for newcomers the replicas would refuse. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
4b45aa5805
commit
767134d1dd
3 files changed
+213
-27
No files matched your search
@@ -168,7 +168,10 @@ your progress, history, listening counts, device names or your account.
|
||||
because other accounts share many podcasts. When the limit is reached,
|
||||
only podcasts of accounts beyond their part wait (newest shares first;
|
||||
cards already published are kept before new ones), and the podcast page
|
||||
says that the card is held back.
|
||||
says that the card is held back. Members' caches keep at most 256
|
||||
records per server, including revocations of the last 24 hours, so a
|
||||
new card also waits while recent revocations fill that room, and no
|
||||
published card is given up for a card the federation would not store.
|
||||
- A podcast whose stored data cannot be read (for example after a damaged
|
||||
import) is treated as not shared, and its card is revoked; the other
|
||||
podcasts are still published and revoked as usual.
|
||||
|
||||
Reference in new issue
Block a user