damn, this nip doesn't use a single letter tag
i have to make a new thing for the ... where... hmmmmmmm
easy enough to do this with the local database event store but when there is layer 2s hmmm
i think, firstly, the events with these tags will now have to have this added to the index, with a new prefix for expirations, and then the expiry timestamp, and then the index serial
secondly, probably going to need some kind of further API method to actually implement this, simple enough for now, this is essential feature IMO so i'll do it, sorry to break yer store.I implementations if any y'all made one, probably not, because it's still pretty new so i get a bit of latitude to mess with things like adding an interface method for this case
the existing and only layer 2 event store i have written i'm right in the process of integrating to work with the new realy codebase (was from old replicatr) so it's actually the perfect time to add this capability
how to implement tho... it could be a filter extension, but that seems like big, and it breaks the filter spec somehow
need to think about this, it's an internal thing, really, just that because of the composition of event stores possible with the layer2 event store it needs to be visible from the interface
gonna ponder upon this while i go for a walk
nostr:nevent1qvzqqqqqqypzqnyqqft6tz9g9pyaqjvp0s4a4tvcfvj6gkke7mddvmj86w68uwe0qyghwumn8ghj7mn0wd68ytnvv9hxgtcpzamhxue69uhk6mr9dd6jumn0wd68yvfwvdhk6tcpzemhxue69uhk6mr9dd6juun9v9k8jtnvdakz7qg4waehxw309a6x2um59eex2ctv0yhxcmmv9uq3samnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5hszythwden5te0dehhxarj9emkjmn99uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsqgzgqnx8lgduwumu9c9s6us0hdsf28yys58v2782fnpflhfxz5m8ps2fhsxt
Showing page 1 of
1 pages
