Alex Gleason
53b8c0854e
Previously, clicking Reply on non-kind-1 events (treasures, themes, vines, etc.) would create a kind 1 event with NIP-10 tags. NIP-22 specifies that comments on non-kind-1 events must use kind 1111 with proper uppercase (root) and lowercase (parent) tag structure. - Detect non-kind-1 reply targets and switch to kind 1111 - Build NIP-22 tags: A/E/I + K + P for root scope, a/e/i + k + p for parent - Handle addressable, replaceable, and regular event kinds - Copy uppercase root tags from kind 1111 targets when replying to comments - Invalidate comments cache instead of replies cache for NIP-22 events