2024-03-20T09:09:11Z https://njump.me cane https://njump.me/npub1ru4vtz2nvae48ht7ww64u24pjej4nrt7d2rxzaqkx6jnh58kfgfqfx6gxv https://i.ibb.co/vqGR0h2/b0291163-06eb-4a92-9bd7-25b489cffd14-small.png https://i.ibb.co/vqGR0h2/b0291163-06eb-4a92-9bd7-25b489cffd14-small.png https://njump.me/nevent1qqs9l7g7h7usa9v3yuyva4h5q6y7ldtkj8dq90hlydpsgt0lfzww3hszyq0j43vf2dnhx57a0eem2h325xtx2kvd0e4gvct5zcm22w7s7e9pyp84fkw In reply to <a href='/nevent1qqsgtyp2mehrzarp3rdnnygf7z3pey7atpmam3rjgjkqsw9cj2enkxshh2tpf'>nevent1q…2tpf</a><br/>_________________________<br/><br/>It sounds like the base abstraction here is &#34;tagging.&#34;<br/><br/>At the protocol level, would it make sense to focus on a generic tagging system that could describe any kind of event? <br/><br/>It seems like that would be broadly useful while still allowing clients to decide at the application level if they want to, say, use tags to describe a person&#39;s relationships. 2023-09-05T09:09:00Z