That's pretty cool! I'll do some testing around your nostrdb fork. However, due to the requirements of the project, I'll continue with DuckDB as it has a good set of features to better handle resources in resource-constrained environments. It's also an OLAP DB, which makes sense for social graph operations, and to cross that with other data in the same db. I've also discovered the pgq extension of DuckDB, which is pretty interesting but is not yet supported in the current latest version. It could also help for this