Vitor PamplonaandClaude Opus 5 ecb9bd557c fix: ask the relays a geocache names for its found logs ...

NIP-CC lets a listing declare, in its `r` tags, the relays its finds should
be logged to, and Amethyst honours that when publishing one -- but the
engagement watcher only ever asked the cache owner's inbox relays and
whatever relay the listing happened to arrive on. A cache whose log relays
are neither of those had its write and its read land on disjoint relay
sets: the logs sat exactly where the listing said to look, and the cache
screen reported "No one has logged this cache yet".

Adds the declared relays to relayUrlsForReactions() rather than swapping
them in, so the existing sources still apply. Two tests cover it; both fail
without the change.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-21 16:09:22 -04:00

..

plans

fix: audit of commons and commonsUI — 34 verified bug and performance fixes

2026-09-12 22:03:11 +00:00

src

fix: ask the relays a geocache names for its found logs

2026-09-21 16:09:22 -04:00

.gitignore

Starting a new module for app benchmarks

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

ARCHITECTURE.md

refactor: move reply-context logic to commons.model; keep the Compose compiler in commons by measurement

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

build.gradle.kts

fix(commons): declare okio so the Apple targets compile after the Compose split

2026-09-13 00:36:31 +00:00

consumer-rules.pro

Starting a new module for app benchmarks

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