mleku on Nostr: man, that took me ages but finally built and tested a shiny new key codec for the ...
man, that took me ages but finally built and tested a shiny new key codec for the rewrite of realy
mostly because it was very repetitive stuff, just a bunch of key field codecs and a neat mechanism to string them together so it's easy to avoid mistakes because everything is neatly labeled with the type, you generate your field values with one function, you create an encoder from these variables with another, and a decoder with another, and then one method strings them all together and zips and unzips them.
now what was next... i have pretty much totally just ripped off the go-nostr event and filter code, so i know that all of it will work, i guess i can start working on the ... idk... i have to write the database engine now, probably that's going to come first because i already have a reasonable set of test events to throw at it, may just build a new set, much bigger, from the many collections of events i have from exporting the old realy deployment, which i know will be a big enough set to test everything. just to keep that trove inside the test packages tho, no sense in them getting inside the binary.
Published at
2025-06-05 21:42:07Event JSON
{
"id": "c7d023e32736099f75343c60180d726ad322198f1ef9fbf1c35c760a3b5108bd",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1749159727,
"kind": 1,
"tags": [],
"content": "man, that took me ages but finally built and tested a shiny new key codec for the rewrite of realy\n\nmostly because it was very repetitive stuff, just a bunch of key field codecs and a neat mechanism to string them together so it's easy to avoid mistakes because everything is neatly labeled with the type, you generate your field values with one function, you create an encoder from these variables with another, and a decoder with another, and then one method strings them all together and zips and unzips them.\n\nnow what was next... i have pretty much totally just ripped off the go-nostr event and filter code, so i know that all of it will work, i guess i can start working on the ... idk... i have to write the database engine now, probably that's going to come first because i already have a reasonable set of test events to throw at it, may just build a new set, much bigger, from the many collections of events i have from exporting the old realy deployment, which i know will be a big enough set to test everything. just to keep that trove inside the test packages tho, no sense in them getting inside the binary.",
"sig": "f739590847de3bfe6cb5a013cdedcbc711d7dbafd3bce2a95f3178c6bb62714adb2e4539bcff626d3e5ec9731ee71568b56be494ed3a58a4c91382cbe40d253e"
}