Vitor PamplonaandClaude Opus 5.5 07c1a7489e fix(concord): only create a community once a relay holds its genesis ...

The genesis (metadata + #general) was published fire-and-forget and the
community saved to the List regardless. If no relay stored it, because the relay
refused it or the app was killed mid-send (routine on low-memory tablets), the
community sat in the List forever with nothing anyone could fold, including
us after a restart. Reproduced on the SM-T220: the genesis of a community
force-stopped right after creation never reached relay.us.whitenoise.chat.

Creation now confirms every genesis wrap with at least one relay before saving,
and the create screen says so when none accepts it.

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

2026-09-29 14:59:05 -04:00

..

src

fix(concord): only create a community once a relay holds its genesis

2026-09-29 14:59:05 -04:00

.gitignore

refactor: split Compose UI out of commons into a new commonsUI module

2026-09-12 16:26:59 +00:00

ARCHITECTURE.md

refactor(note): move the NoteCompose group to commonsUI

2026-09-28 20:03:58 +00:00

build.gradle.kts

refactor(ui): user avatar, name, loaders and user observers move to commonsUI

2026-09-28 16:51:05 +00:00

consumer-rules.pro

refactor: split Compose UI out of commons into a new commonsUI module

2026-09-12 16:26:59 +00:00