I think I'm going to let myself get distracted and build a framework like this

The goal is to separate the data fetching layer ( relay subs / outbox model ) of nostr web clients with the UI layer. This might help with debugging and might make it a lot easier to build UIs since all events are stored in a single place

Currently in noStrudel the events are spread across multiple "timeline loaders" and "profile loaders". this sometime leads to the UI not being able to find an event that another part of the UI was showing ( i.e. thread unable to find events shown in timelines )

Reply to this note

Please Login to reply.

Discussion

You pretty much need to build a pure data layer that can be run from cli / integration tests and UI is just a function of it

It could be used that way, but I'm mostly thinking of making it easier for me to debug complex apps :)

Sometimes when I see a really beautiful flow chart it sounds like a symphony in my head

Since all events are stored on a single place... where is this place?

In memory. that way all the UI elements subscribe for events and the loaders can pipe events into the store

Can I ask what software was used to generate the process map?

Obsidian. it has a nice canvas feature which I use to map out ideas

wen canvas nip? 😹

https://obsidian.md/

Awesome! Thanks!

"Loaderse"

its frech... a silent "e"...

i believe in you !

and for bonus points you should think of how to compartmentalize NoStrudel so that other Devs can contribute more to certain blocks of it

in a perfect world i should be the product manager, you should be the chief technical officer and then there should also be an army of suckers coding all the details

on second thought i don't know enough about latest and future features of NOSTR ( NIPs and stuff ) to be product manager

i should be in charge of Interface, Style and Usability

sounds fancy !

This is partly the idea. I probably wont build a whole framework but it will at least make building the UI a little more approachable