Looks like people are already doing this with emojito by nostr:nprofile1qythwumn8ghj7enfd36x2u3wdehhxarj9emkjmn9qyt8wumn8ghj7enjv4h8xtnwdaehgu339e3k7mgpp4mhxue69uhkummn9ekx7mqqypl62m6ad932k83u6sjwwkxrqq4cve0hkrvdem5la83g34m4rtqege7llfh and it's just being published under kind 30030
Do we even need a new kind? 🤷♂️
Seems like nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcpz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309amxjar0wghxummnw3erztnrdakj7qpqgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqyw43nv is just working around it client-side
nostr:nprofile1qyv8wue69uhk6mmwv9jzu6nzx56jucm0d5arsvpcxqq3wamnwvaz7tm9vdkxjurnv5h8qatz9aex2mrp0yqs6amnwvaz7tmwdaejumr0dsq3qamnwvaz7tmwdaehgu3wwa5kuegpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq32amnwvaz7tmjv4kxz7fwd4hhxarj9ec82cspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqpqxtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzs6dze5x , this seems to be a pretty good idea; I think it's still best paired with a global search library so you aren't bound by the collection you have, but it's nostr native and api-limit free
Example event:
{
"created_at": 1717552866,
"content": "",
"tags": [
[
"d",
"Reacts"
],
[
"title",
"Reacts"
],
[
"emoji",
"puppyeyes",
"
"
],
...
,
[
"emoji",
"whatthefuck",
"
"
]
],
"kind": 30030,
"pubkey": "d7607464225c8ab610da99495bc70c8a3a45a03f8a22a95f06fcb5bc421e573a",
"id": "518b723ae57751bfadd37a6744159f41fda5d95638b89a3e9e728762e9531188",
"sig": "791db349d5fc87b4a9daef13c9181783b0c5e5f735ce446386d6e7e573000817a0d031e70edd2238b2da0b302ed622149ca533d04f3c4aaaa0390817b4909733"
}
Reference library:
