Vitor PamplonaandClaude Opus 5 3f4723437e refactor(commons): move the top-nav per-relay filter values out of the app ...

The topNavFeeds package holds two layers. The value layer — the per-relay
filter sets, plain `Map<relay, filter>` of authors, hashtags, geohashes —
is pure data. The resolution layer around it (TopNavFilter, FeedFlow, the
loaders and decryption caches) evaluates feeds against the live event
graph and needs LocalCache, NoteState and the outbox loaders, so it is
app-coupled by nature and stays put.

Moving the 25 value types lets commons describe a feed selection without
depending on the app, which is what an ExplainedFilter needs if it is to
carry the top-nav scope instead of a flattened List<HexKey>. Desktop gets
them too.

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

2026-07-30 22:14:15 -04:00

..

plans

docs(plan): record note-ui-commons extraction progress + findings

2026-07-17 22:50:09 +00:00

src

refactor(commons): move the top-nav per-relay filter values out of the app

2026-07-30 22:14:15 -04:00

.gitignore

Starting a new module for app benchmarks

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

ARCHITECTURE.md

Removes Threading checks on Commons since Main Threads don't exist over there.

2026-06-15 10:41:40 -04:00

build.gradle.kts

chore(deps): update dependencies across all modules

2026-07-19 14:06:37 +00:00

consumer-rules.pro

Starting a new module for app benchmarks

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

proguard-rules.pro

build: remove unused :ammolite module

2026-05-16 14:40:03 +00:00