Event JSON
{
"id": "04757962e450dd3c62965ca22c6671aa4a2c09ea75aaefbc7e244bab6ff6261a",
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"created_at": 1746465600,
"kind": 1,
"tags": [
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"wss://nostr.land/",
"jb55"
],
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24",
"wss://nostr.wine/",
"Derek Ross"
],
[
"p",
"a23185a552ba605d7cb7b42ab75a3ee1bca64fa769a5c8e4aef0b54c9525bd5b",
"wss://nostr.bitcoiner.social/",
"daomah"
],
[
"e",
"bf3a12309bd982bdd615a8f11790e91bb61f0880b0d254eff475552e5e75643a",
"wss://hbr.coracle.social/inbox",
"root"
],
[
"e",
"eced02419175d21b1929f0231ee3194715674235e4de78d152a57d9896c5c052",
"",
"mention"
],
[
"e",
"57992a501dc5c3991678c3901bfcce564cb63bf9aef43bd5577427aa8edcced5",
"wss://relay.damus.io/",
"reply",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"client",
"Coracle",
"31990:97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322:1685968093690"
]
],
"content": "That's the kind of arbitrary limitation I'm talking about. Why not include nip 50 search in feeds? What about feeds powered by third party services that index the whole network for content outside your wot? I don't see why that stuff should a priori be excluded from feeds. It's fine to implement fast local feeds, but it should be an implementation detail behind a more generic interface, not the interface itself.",
"sig": "848e79d51733bc352261c267bd6098cb268aa924f6715d494b7e68f2dca799e944ce0df11797d26c17a96b29954e1a71083bb34069d6084887936f8bc83e5cca"
}