Amethyst 1.15.2 loads nested NIP-22 comments earlier

A root is not the direct parent

NIP-22 defines comments as kind 1111 events. Uppercase tags identify the conversation's root. Lowercase tags identify the item being answered. For an event identified by its ID, those tags are E and e; for an addressable root, the corresponding root tag is A.

Consider a file event, a comment on that file, and a reply to the comment. The first comment points both its root and its parent at the file. The nested reply keeps the file ID in E, but its e points at the first comment. A query for #e equal to the file ID therefore finds the direct comment but does not find that nested reply through its parent reference.

The existing engagement queries used lowercase tags. The thread screen already had its own subscription for the uppercase root, explaining why opening a conversation could reveal replies that had not arrived through the earlier query. The release moves that discovery into the engagement filters too.

Separate filters preserve the intended query

The patch adds an E filter for event IDs and an A filter for addressable content. Each new root filter uses a limit of 1000 and carries the existing per-relay since value. The direct-reply filters remain.

Putting both tag conditions into one filter would not solve the problem. NIP-01 requires every condition within a filter to match. A filter asking for both #e and #E to contain the root ID would still exclude a nested comment whose direct parent is another comment. Separate filters allow the client to ask for the two relationships independently.

The limit is a query parameter, not a promise that every comment in every thread will load. Relay availability, the selected relays and the time bounds still determine which events the client receives. The correction concerns what the client asks those relays to return.

Pull request revisions had the same mismatch

The new root filter for event IDs also includes kind 1619, the NIP-34 pull request update event. The NIP-34 example identifies the revised pull request with an uppercase E tag.

Previously, Amethyst listed that kind in a filter using lowercase e. Listing the right kind under the wrong tag did not discover updates following that example. The patch moves kind 1619 into RootScopedRepliesKinds. Git replies and status events keep their existing lowercase filter.

The added tests check that root filters are generated for both event IDs and addresses, and that uppercase and lowercase conditions are not combined. Separate assertions keep kind 1619 in the uppercase list and out of the lowercase list.

This is a client query correction. It does not change the NIP-22 event format or require authors to republish comments. The verified distribution is the GitHub release; its downloadable builds establish availability there, without establishing the status of any app store rollout.