Sorry but I dont understand now whats the final problem. If you update your relays in amethyst it will be later pulled in plebstr same what happened now, where you updated in plebstr and it got updated in amethyst.

Can I ask for more info, whats needed to be fixed in plebstr? 😊

Reply to this note

Please Login to reply.

Discussion

It published automatically.

In Amethyst or Nostros there's an extra step.

I probably spent too much time on those so my thinking was used to that.

An extra step would be nice.

That would fix it and make it more safe to edit the relays list without worries....

yes- spend time learn more -

BACKUP GOOD profile.json always any issues that PUSH that from any compatible client

Oh ok now I understand. We will be redesigning a bit those parts of plebstr, where that β€œextra step” will be. Sorry for the bad experience that happened to you now. Hopefully it will change soon πŸ€™πŸ«‚

Not bad, i have the list backed up :).

But the extra step would be awesome for user experience.

I like the Nostros way: has both push/publish and refresh. So any mistakes user makes in other clients are easily fixable.

Amethyst only has push which is also ok.

Thank you! πŸ™

Thank your for the feedback too πŸ€™

πŸ«‚πŸ’œ

Thank you Plebstr for being open to this.

Not doing it automatically and requiring an extra step before publishing the relays list is the way to go for a nicer user experience in all clients.

Would fix a lot of relays discussions...

#[2]