stats NIP idea:
there could also be a NIP that implements getting stats for a set of ids via REST:
`POST ids -> /stats`
```
[ {id: "abcd...", replies: 12, reactions: 100, reports: 100, quoted_boosts: 10},
...
]
```
this could be very efficient and could aggregate many relays, have caching, etc. not everything needs to be over websockets.
jb55 /
npub1xt…vkk5s
2023-01-08 14:51:05
Author Public Key
npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5sPublished at
2023-01-08 14:51:05Event JSON
{
"id": "b528173180792c87c0060369f878d505552c24dc189c8046a3cd8ff9aaddeca1",
"pubkey": "32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"created_at": 1673189465,
"kind": 1,
"tags": [],
"content": "stats NIP idea:\n\nthere could also be a NIP that implements getting stats for a set of ids via REST:\n\n`POST ids -\u003e /stats`\n\n```\n[ {id: \"abcd...\", replies: 12, reactions: 100, reports: 100, quoted_boosts: 10},\n ...\n]\n```\n\nthis could be very efficient and could aggregate many relays, have caching, etc. not everything needs to be over websockets.",
"sig": "51e1254c977059832505040fce30744fd90f6f6a468ba121f5f752ec4b8d03dd6fb8443cd4d2e0166b2c2e8f14a1940983987610f157488305b84ace9b39d402"
}