mirror of https://github.com/vitorpamplona/amethyst.git synced 2026-10-05 11:18:24 +00:00

Files

T

Claude f72388a559 refactor: rename packages, helpers and app code after the NIP event renames

Follow-up to the event class renames: the names around those classes now
match too.

Quartz (published API, every old name kept as a @Deprecated alias/forwarder):
- nip51Lists packages moved: followList -> starterPack, hashtagList -> interestList,
  peopleList -> followSet, labeledBookmarkList -> bookmarkSet. The old packages
  keep a Deprecated.kt with typealiases and forwarding extension functions
  (ReplaceWith points at the new package).
- LnZapPrivateEvent -> PrivateZapEvent, LnZapReceiptValidator -> ZapReceiptValidator,
  ChannelListDiff -> PublicChatListDiff, HashtagListDiff -> InterestListDiff.
- Kind 30063 now indexes NIP-82 release notes for search (never NIP-51 content,
  which can hold encrypted private items). searchable-events docs updated.

App code (amethyst, commons, desktopApp, cli; no aliases needed):
- model packages nip51Lists.{hashtagLists,peopleList,labeledBookmarkLists,relayFeeds}
  -> {interestLists,followSets,bookmarkSets,favoriteRelays}.
- State/cache/UI names derived from the old event names: HashtagListState ->
  InterestListState, PeopleListsState -> FollowSetsState, FollowListsState ->
  StarterPacksState, LabeledBookmarkList -> BookmarkSet, RelayFeedListState ->
  FavoriteRelayListState, ContactCardsState -> UserAssertionsState, NIP90* view
  models/renderers -> Dvm*, LnZap* handlers -> Zap*, SealedRumor* -> Seal*, and
  Account.peopleLists/followLists/hashtagList -> followSets/starterPacks/interestList.
- String literals were left untouched, so preference keys and @SerialName values
  stored on disk are unchanged.
- The generic PeopleList UI model (shared by follow sets and starter packs) and the
  EmojiPackSelection route (which shows a kind 30030 pack) keep their names.

Docs: plans, brainstorms, changelogs, skills and READMEs use the new names.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015VvJ8XpeYqBe8bYT3bJ7UD

2026-09-26 20:56:07 +00:00

960 B

Raw Blame History

TODO

DM: Mixed NIP-04 + NIP-17 conversations

Question: What happens when a conversation with an npub has both NIP-04 (kind 4) and NIP-17 (kind 14/15 in GiftWrap) messages?

Current behavior to investigate:

NIP-04 messages use EncryptedDmEvent.chatroomKey(pubKey) → creates a ChatroomKey based on recipient
NIP-17 messages use ChatMessageEvent.chatroomKey(pubKey) → also creates a ChatroomKey based on group members
Do these produce the same ChatroomKey for 1-on-1 chats? If yes, both message types merge into one conversation. If no, they appear as separate conversations.
Android Amethyst handles this — check how Account.kt merges them
Edge cases: timeline ordering, decryption display, NIP-04 messages showing as "legacy" vs NIP-17

Action: Test with a real conversation that has both types. If they split into two rooms, we need to merge them in ChatroomListState or unify the ChatroomKey derivation.

960 B Raw Blame History

TODO

DM: Mixed NIP-04 + NIP-17 conversations

960 B

Raw Blame History