yeah, I like this approach. It's what I'm following already, but not at the same level of categorization
- library for data structures (now go-nostr, but not for long)
- relay framework = rely (was, messages, relay logic)
- database (nostr-sqlite)
I'm trying to take a different path with my Nostr library stack. So far I've done the consensus layer for the Nostr protocol (roots) and the websocket message schema (roots-ws) in both go and typescript. And I'm working on the basic messaging library (honeybee). And as you need advanced features, the goal is to place them in separate libraries. And then you compose the parts you need into an app.
Discussion
Yeah, mine has a similar goal of splitting functionality up across repositories, but done up differently. I don't know how it'll all shake out yet.