Here you go. I need to do more work on it, but this should be a good first start.
Discussion
Oh! Wooow! Will give it a whirl as soon as I can after all the xmas stress dies down! Merry Christmas!
I gave it a whirl, and it definitely shows promise, but I actually failed to get it to work, I think :-)
I removed a couple of relays and added two new ones. So that I had 4 inbox and 2 outbox relays. Then I pressed publish, and got to sign a few events through my alby-hub extension. But then I got the following error:
One thing I think needs clarification is what is supposed to happen after that publish succeeds. Does that update my relay settings in Primal and Amethyst, or am I expected to do more there?
And an idea for a first step before getting to update the settings would be a basic "score" on my settings. Like "These settings look okay" or "You will have trouble reaching your followers" or "You will experience slow search" etc. If this worked well I could check this website every few months and check if my settings make sense still. I think that is a reasonable use case for a site like this, to be able to periodically check my settings.
this updates all of your applications that use your nostr profile's nip-65 relay settings, so yes, Amethyst and Primal would see updates.
as for that error, im wondering if it's because you added zero write relays and you were not able to write any changes do the read-only relays in your list.
let me fix this so people must have at least one write and one read relay for people that don't understand what they're doing here. thank you!
fixed! 
Nope, I still get the same error. What I did was remove the two slowest of my four relays in the first screen, so that I only had two "read"-relays. Then I added two new relays as both read and write. And pressed publish. Same error message as before.
im wondering if you're still using the old version of the application? can you please do a hard refresh? depending on what device yoiu're using, you'd need to delete cache or shift f5 or control r.
or i guess it's possible you're only adding relays that you don't have permission to write to? i don't believe im checking for that issue, but i think it's as cache issue.
I did a ctrl-f5, and when I tried without any write relays (just to test your new feature) I got the error that I would not be able to publish.
I am adding damus.io and primal.net strfry instance. Any specific ones that I should try instead, to check?
awesome! thank you for doing that and checking my sanity :)
those relays are fine. though you can pick smaller relays here and be just as successful since the inbox and outbox model allows users to choose any size and popularity of relay and still be able to communite with everyone. it helps with decentralization.
public relays are good for inbox, so everyone can comment, unless you want to limit who can comment. smaller relays are good for note storage, to help with decentralization so we don't all crowd around the top relays.
pick what you want and if it doesn't seem like a good choice, you can always choose another relay.
Hmm, I got it to work now. Don't know if you made any changes, or if it was something I did.
What I did was actually go into amethyst and change my one outbox relay from one that I was getting error messages from to nos.lol. I did that last night. And this morning when I tried relayopti it worked.
So maybe relayopti is trying to publish my changes through the broken relay that I already had?
I don't quite understand how I could be posting anything at all when my outbox was broken?
I am pretty sure I had two writes and four reads at least one of the times that I got that error. I tried three times.
I am going to try to stay clueless in my usage attempts, that is the target audience, right? 😃