So here is the solution for writing apps "on Nostr": https://github.com/nostr-protocol/nips/blob/master/78.md

Reply to this note

Please Login to reply.

Discussion

And also if you see yourself wanting to save preferecens, settings, anything that you know other apps won't care about. That's probably the way to go. The NIP can still be improved.

Cloud database in Nostr? 😅

I'd love to run sqlite3 on relays

now u can

Only if this NIP gets included?

#[2] This message has a link but it not linked in the Amethyst v0.23.1. I think it's bug, right?

I think so. Previous versions also had that bug.

lol

i would propose that all apps be written with nip78 first, then, once they desire interoperability, a standard can be proposed

this is the best way to produce standards in the long run

1. observe usage

2. produce a standard that mirrors existing usage

design by committee will turn into bikeshedding and weird stuff that nobody uses or cares about

At first I thought this was quite comical, as relays send notes from one user to another and (remote) storage is a different market, with 1000s of petabytes

But if used carefully it could work very well. Small configs, or even better, just a bit of references that link to the world of persistent storage and data

Will people use it that way? Possibly not. But that it can be done could be very useful.

#[2]​ i think this is what you wanted!

Apps can still be interoperable, if they just use the same tags, such as settings/colorScheme.

Would be cool to also have listing for all your settings with wildcard filter "settings/*". That would make it a bit like a filesystem.

Because people were already doing it anyway?