Nostr Web Client

Sure, but the question was if we can add more pre-processed attributes (key-value pairs) to the Event objects so that when it loads from the disk it's not just a raw event. Most of the processing Amethyst does is in the "getting an event ready for the UI" phase, like zap amount sums, reply counts filtered by the user's hidden words list, creating blurhash bitmaps, tables for zap comments per note etc. That's were 95% of the app's CPU usage goes.

jb55 1y ago

Ah yeah that’s the same with damus, which is why I’m trying to put most of that upfront work into nostrdb. i feel a bit uncomfortable putting too much business logic into it, but the multithreaded ingester at least does content parsing, fulltext indexing, stat counting (zap amounts soon, likes, etc). Once it’s all ready the subscription is then updated for the UI.

Content is parsed into “blocks” which is also queryable and available for all notes. This was the slowest code for damus.

I want to put in all the complicated stuff that would be common in all the clients I build.

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 1y ago

I wouldn't hardcode any specific business logic. I would just have a map in each event so that the dev can add/remove whatever they want to store together with the event. The db just stores this map in the same way it stores the event fields.

jb55 1mo ago

our metadata table achieves this now! you can add metadata of any type to nostrdb that is tied to a note id. currently powers our like/quote/reply counts