Be careful logging into new clients like current. It looks like contact list handling is a bit buggy and may nuke your follows and relay list. Always use a test account on new nostr clients.

#[0]

Reply to this note

Please Login to reply.

Discussion

I will stick with #[3]​ thanks #[2]

Relay value outdoing the best meat birds nest?

Are those relay arrangements all set in stone?

Well, Test Account wouldn’t show you this behavior unfortunately

Good advice Willard

don’t we have a cached copy on Damus?

Only during the session. We should save it.

Not only that, we should save the last N versions of the contact list, and have the ability to roll back to any previous state.

So you think you can handle the temporal impact of going full scale running off beat?

do we have use case that we need to roll back in time?

Same thing with Iris, when you save your relays publicly. Your following list is gone after that !

これは気をつけなきゃ❗️

My follows got nuked a few times, it's a right of passage

This shows how important it is that we need delegation keys that don’t give the full access like nsec does.

This is happening a lot. I get so many DMs from users facing the same issue.

#[3]

I was working on a profile manager micro app that allows users to backup and restore previous versions of there follow list. Sort if lost momentum before a production release. https://github.com/DanConwayDev/nostr-profile-manager

I was just about to suggest something like this. You should keep at it. I'm sure you could get funding too.

Good Advice - I will start doing that!

Thanks for the feedback! Kind 3 events are definitely challenging. I looked into this and it seems like Damus is using Kind 3 events to store relay lists in their content field, right?