Android.

Edited my relays list in Plebstr to only 6.

That fucked up my relays list in Amethyst which now from 22 has only the 6 relays i've set up in Plebstr.

Thankfully i can post this from Nostros which is always reliable and never screws up anything lol.

Reply to this note

Please Login to reply.

Discussion

relays r always attached to npub profile gets pushed all clients u use. LoL u did it urself ! hahaha

someone posted Lion pic before !

always use dummy npub when testing new client - not ur main - plus some apk clients allowed profile relays vs their picked ones only

Yeah, tweaking relays in one client makes trouble in another. Not quite sure but are relays managed at npub layer or client layer. seems to be like the first one!

Not really a big problem, i'll populate again in Amethyst.

I use all of the clients at once :)) so i'm careful to always have relays noted and Nostros is always reliable, so i have them here.

Unfortunately if i hit push relays in Nostros that doesn't populate Amethyst so i have to do it by hand...

Today i learned: don't edit down relays list in Plebstr :)).

yup it is by design - play n learn - do what is suitable - takes time understand - relay management always ongoing process

backup when u correct profile info - or metadata messup can happen

Clients will publish a note containing your relay list, so that it is consistent on other clients.

Would be nice if they asked before pushing.

Like Amethyst or Nostros.

Plebstr just does it automatically.

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? 😊

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]

That’s how nostr is designed to work, updating your relay list in one client will then send an updated list of your relays to the relays you’re connected to.

Yep, i know. The unexpected part was that Plebstr does it automatically unlike Amethyst and Nostros which both ask before publishing.

An extra step is needed and it seems they listened and they'll get it πŸ’œ.

Ah makes sense, sweet!