Hm..

Well one extreme option is just to get rid of them. When a user navigates to this page, check for changes and merge in any remote changes. When a user makes new changes to the local settings (new sets, updating existing ones, etc) just push those changes out on completion. And you could include a "force refresh" button with a tooltip that explains (something like, "will check your read/write relays [link to these settings] for relay sets you've previously used").

I'm not sure if that would make things _more_ confusing though. And then you'd have to do some local caching stuff for that if you aren't already.

It really comes down to whether you want to jumble's relay set interface to be one-to-one with a user's remote relay sets, or if you want them to be able to have local-to-this-device sets that they don't publish.

Either way, it should be noted somewhere how that works, maybe before signup, especially if you go with "any changes you make here are automatically persisted out to your relays" as someone could end up overwriting remote data without realizing it