hodlbod on Nostr: Yeah, because the client controls the context in which the scroll is invoked, the ...

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.