Vitor PamplonaandClaude Opus 5.5 cd5c92bd1b fix(concord): put a new membership in any held List fragment it fits ...

With part of a fragmented Community List missing, a new membership always went
to the lowest held fragment, so once fragment 0 filled every join was refused
even with room in another fragment the device held. Take the lowest held
fragment it still fits in; refuse only when none does, since opening a new
fragment is a repack that needs the complete List (CORD-02 §8).

Adds an end-to-end test of the List past one fragment through
ConcordChannelListState: 250 heavy memberships split into fragments that each
fit the 64 KiB event ceiling (measured on the signed JSON), another device reads
every membership and secret back from the published fragments, cross-device
leave and join converge, and a partial device neither overflows nor erases the
fragments it never held.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-29 15:18:34 -04:00

..

plans

refactor(screens): step 6 wave 2, an AppPlatform slot and 37 more screens in commonsUI

2026-09-28 21:20:53 +00:00

src

fix(concord): put a new membership in any held List fragment it fits

2026-09-29 15:18:34 -04:00

.gitignore

Starting a new module for app benchmarks

2024-02-05 18:18:33 -05:00

ARCHITECTURE.md

docs: one UI for Android and Desktop, and the measured Wave 4 plan

2026-09-27 23:00:45 +00:00

build.gradle.kts

refactor: drop androidx.security from commons' key storage

2026-09-23 20:14:04 +00:00

consumer-rules.pro

Starting a new module for app benchmarks

2024-02-05 18:18:33 -05:00