Instead of using a database I'm storing events in a file. Memory mapping lets you access a file as if it was entirely in memory, and the OS pages it in and out for you automatically doing the reads and writes and stuff.

Each event just gets appended, which requires a write lock (one writer at a time) but readers can keep reading while writes are happening so it is less contentious than a traditional RWLock which blocks readers while writes happen.

The indexes are functionally similar to key-value btrees which map certain query tuples like (pubkeyhex, createdat, idhex) to an offset into the event file (the length of the event is encoded in the serialization so we just need the offset). The serialization is very minimal, just enough to have a length and to be linear. Each key in each index must be unique (or else we would lose events) which is why they end in the "idhex". We can scan a time slice (before/since) as they are grouped together on the btree, so I can iterate from (pubkey, before) to (pubkey, since+1) to get all that person's events within that time range. I'm intersecting multiple index results by hashing results and checking that map each time I run through the next index, discarding matches that come up missing (from the previous index). That should cover all possible queries, not in an ideal way, but in a simple and relatively fast way. strfry has more indices (all the common ones) and falls back to scanning a flatbuffer event sequence for matches. It also uses LMDB for the events rather than trying to memory map directly. I'm using sled for the indexing. I don't know if my indexing merging scheme is going to be faster or not. Probably slower in most cases, but faster then when strfry doesn't have a suitable index. That's my guess anyhow. My code is at least easy to reason about. I came up with mine before talking to Doug.

There is a little bit of BlueSky chat amongst people I know. Not much interest, but some inkling of something happening. Nostr is completely off the radar. If I said 'nostr' out loud people would just think I was choking on something.

"have to"

I'm not basing this on stats or logic. Just a gut feeling and BlueSky capturing all the attention which was dispersed around other twitter alternatives. Although some people have pointed to stats on nostr band. I haven't looked closely enough. I also think it will be revived after abandonment tho. Also based on nothing lol. I'll try to stick around for all of it lolol. I saw it in a dream.

Yeah I know. I use amethyst cos it works best. P shit really. But I'm sort of the opinion that nostr will be abandoned anyway so part of me is a bit fuck it, about it. I will happily jump ship when something works as well as amethyst. Plebstr doesn't even let you upload photos (does it?? Maybe I eed to update or stop being so thicc 💅)

When did bitcoin culture™ become this lame influencer aesthetic that resembles something like those awful 'vanlife' YouTube videos vibe? Yuck.

You have the Bert and Ernie vibe going

Yeah, so there's this

It’s greatest asset. Thank you to #[2]​ for setting this in motion.

Again assuming the thoughts of every single market actor. Maybe some people like collecting beenie babies. They're stupid for thinking they might be worth more in the future but that doesn't mean they are all scammers. Is TY toys a scam? Or are they just a free market actor?

Tell that to the government when they'll join the call 🤣

I'd just like to interject for a moment. What you're refering to as Nostr, is in fact, NIPs/Nostr, or as I've recently taken to calling it, NIPs plus Nostr. Nostr is not a social media unto itself, but rather another free component of a fully functioning communication system made useful by the NIP event kinds, clients and the vital relay system comprising tamperproof events via schnorr signatures

Many users run a modified version of the NIP system every day, without realizing it. Through a peculiar turn of events, the version of NIPs which is widely used today is often called Nostr, and many of its users are not aware that it is basically the NIP system, developed by fiatjaf.

There really is a Nostr, and these people are using it, but it is just a part of the system they use. Nostr is the framework: the system that ensures events are usable and interoperable between clients/relays. Nostr is an essential part of decentralised social media, but useless by itself; it can only function in the context of a complete client-relay system. Nostr is normally used in combination with the NIP guidelines: the whole system is basically Nostr with NIPs added, or NIPs/Nostr. All the so-called Nostr distributions are really distributions of NIPs/Nostr!