Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache user data locally and allow posting to relay(s) of choice #65

Open
kirillkovalenko opened this issue Feb 2, 2023 · 2 comments
Open

Comments

@kirillkovalenko
Copy link

I have an account with my information (avatar, about, nip-5, etc.) filled-in, but I have no idea or control from which relay it has been fetched.

Now that damus has been released and we have influx new users many relays have died, I removed many default Amethyst relays and added some new ones.

My profile info is now empty.

Suggested behavior: Last seen profile info is cached locally (ideally all my notes all too!) and I have an ability to selectively this infoset to relay(s) of my choice.

Makes sense?

@greenart7c3
Copy link
Contributor

Maybe use the gossip model too.

https://github.com/mikedilger/gossip

Gossip follows people wherever they post, dynamically detects where events might be, and dynamically connects, subscribes, and disconnects to various relays as needed to get those events.

@kirillkovalenko
Copy link
Author

kirillkovalenko commented Feb 2, 2023

@greenart7c3 while I have absolutely nothing against gossip or any other similar technology my thought was around

a) being sovereign with our own data just how we already are with our private keys
b) ability to move the notes across relays
c) better UI/UX is case of network disruption events

using command line tools it's already pretty easy to backup / move notes. it would be nice if UI clients allow it too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants