Standard way of syncing nostr clients' settings #932
Replies: 5 comments
-
This would be great. Right now coracle does an encrypted json blob of channelId/timestamp for keeping track of last seen, but it gets out of sync frequently which is the same problem in general with lists. I'd like to see more granular events for these, maybe where |
Beta Was this translation helpful? Give feedback.
-
I can use if somebody goes to the trouble of defining a spec for this :) |
Beta Was this translation helpful? Give feedback.
-
Is this really a problem for normal users or is it just a problem for hardcore users like us who test a million different clients? I'd say it would be nice to have but probably not worth the trouble. |
Beta Was this translation helpful? Give feedback.
-
It reduces the friction involved in switching clients, so I definitely think it's a good thing. |
Beta Was this translation helpful? Give feedback.
-
We now have a very simple draft PR for a NIP to keep track of seen events by @staab. Closing the discussion here, any further comments can be made in the PR. |
Beta Was this translation helpful? Give feedback.
-
Currently I have seen primal.net make use of NIP-78: Application-specific data to keep track of opened DMs, seen notifications etc. It's probably not worth it, should we consider standardizing some of these settings, so that they can be used across most other apps?
Here are some things that we can standardize:
etc
Beta Was this translation helpful? Give feedback.
All reactions