it's just a http accessible event database with filters + extra + fulltext search capability
the extra is it lets you query by instance-internal references to events (database serial keys), it lets you just get event IDs also, instead of the whole event, and it will have a full text search that lets you get the event IDs as results
all of this is core database functionality, and something i've learned from my work at the fiat mine is that very often internal things are useful. and that cat, the snipey, whiny one who has an ok business serving nostr clients, apparently, gave me the idea of opening up the internal references as it is a far simpler sync mechanism than retardonegentropy, because actually, nodes are subjective, and their internal references make a lot more sense as a way to request data.
doesn't mean they'll give it tho, some data is private so there would be gaps but that's literally internal, and private, it's just there because it is the simplest way to enable another party to sync data. this is my zero, ok, here it is. etc. the database search can also find these by all the possible other ways but it's a one-stop to just ask it for "the event you call 203"
mleku
npub1fj…mleku
2025-06-12 15:43:00
in reply to nevent1q…mrc3
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2025-06-12 15:43:00Event JSON
{
"id": "10fd28f6f7b9429a87e7de847c639496aef7d149eef8d85ec2ba971af5b30814",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1749742980,
"kind": 1,
"tags": [
[
"e",
"00d8b745e61777b30a030ba9ec63eade52ac2d1a809b92b6fec5ca3883dda1d0",
"",
"root",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"e",
"16cb8eae568ee02f6d459149cee919ac6c739d1f4a73b270617293dd4f4b54a9",
"wss://relay.damus.io/",
"reply",
"75d12141a391994c4062501f155c2e34e41a8c3cf9bef9e4d7d298253458d1e2"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"b90c3cb71d66343e01104d5c9adf7db05d36653b17601ff9b2eebaa81be67823"
],
[
"p",
"637a2f1da5d2fc1976c14ec00f8eae4015afe99bb2554f1d537d0086a169dd8f"
],
[
"p",
"75d12141a391994c4062501f155c2e34e41a8c3cf9bef9e4d7d298253458d1e2"
]
],
"content": "it's just a http accessible event database with filters + extra + fulltext search capability\n\nthe extra is it lets you query by instance-internal references to events (database serial keys), it lets you just get event IDs also, instead of the whole event, and it will have a full text search that lets you get the event IDs as results\n\nall of this is core database functionality, and something i've learned from my work at the fiat mine is that very often internal things are useful. and that cat, the snipey, whiny one who has an ok business serving nostr clients, apparently, gave me the idea of opening up the internal references as it is a far simpler sync mechanism than retardonegentropy, because actually, nodes are subjective, and their internal references make a lot more sense as a way to request data. \n\ndoesn't mean they'll give it tho, some data is private so there would be gaps but that's literally internal, and private, it's just there because it is the simplest way to enable another party to sync data. this is my zero, ok, here it is. etc. the database search can also find these by all the possible other ways but it's a one-stop to just ask it for \"the event you call 203\"",
"sig": "27a98cb93b580a44df93c4c88d6e302136354b084b1196ef92f71a134de55df4d8b5662615031d3961480faa7425087890e051d5e2d03328e24a7b3f94f9860e"
}