I've found a note from beginning of 2024 in which I was trying to come up with ideas for Nostr mini apps that would be written in WASM and shared as events. The idea at the time was to have something that fetched events and rendered tables with clickable buttons.
These were the examples I listed at the time:
- recover old contacts deleted by mistake
- cleanup inactive follows
- suggested people (based on lists of people you follow)
- event deleter
Turns out that, thinking about it now, the single "display()" function is pretty reasonable. All these functionalities can be done by just fetching the correct events (kind:0s for displaying profiles, I guess), then expecting the client to have its own delete button, follow button, unfollow button, that's it.
Login to reply
Replies (1)
Yeah, because the client controls the context in which the scroll is invoked, the display function can be infinitely overloaded and presented as buttons, notes, grids, whatever.
The use case I want to solve is custom tabs in Flotilla. Basically, the relay would publish one or more self-signed scrolls with a name (or a list of scrolls), and those would show up as tabs in the navigation. Click on the tab, and you get a page based on some presentation template suggested by the list/scroll. The thing that's missing is interactivity I suppose. It would be nice for the mini app to be able to define clickable buttons, inputs, etc.