#nostrdesign I need some help again. I'm trying to overhaul the whole relay system in noStrudel to add better support for inbox / outbox relays and relay sets.

I'm running into a few UX issues that I don't know how to fix and I need some ideas.

My goal is to make the users inbox / outbox relays completely separate from the apps relays and call them "Mailboxes"

So going forward the app will store its current relays in local storage instead of nip-65. this will allow the user to change relays on the fly while keeping the inbox / outbox relays the same.

The part I'm stuck on is I cant figure out what the UX should be around managing the users "mailboxes"

I want to separate the concept of setting up your "mailboxes" from configuring the app relays so they have to be on a different view then the apps relay config.

A few ideas I'm looking for:

- Whats the best way to visually distinguish a users Inbox relay from a users Outbox relay beside using an icon?

- What (if any) relay recommendations should I show on the "mailboxes" view when the user is setting or changing their mailboxes

- How should it show a warning if one of the users current inbox or outbox relays is offline / rejecting events?

nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac and anyone else who has ideas

Reply to this note

Please Login to reply.

Discussion

I'm curious why they'd be separate? Also, are these separate relays for DMs? you say Inbox / Outbox so sounds like DMs unless I'm not understanding correctly.

I'm calling all the Inbox and Outbox relays under a users NIP-65 relay list "Mailboxes". I think this would help communicate to users exactly what these relays are supposed to be used for.

also NIP-65 "mailboxes" are useful for a bunch of other stuff besides DMs. (relay hints, gossip model, notifying users when tagging "p")

My goal is to have the user setup 4-5 "mailboxes" when they first setup the app, then ideally never change them.

Then the app can use a completely different list of relays, so the user could either use the gossip model or change relay sets on the fly

Mailboxes is confusing to me. It sounds like it’s for messages - dms to be precise.

What if you just call them relay sets?

What is the use of Mailboxes?

Btw, I would think well before ,,introducing a new concept; maybe adding an attribute to "relays" is enough, and it keeps back compatibility too.

"mailboxes" are just the users Inbox and Outbox relays in nip-65

Their primary use is for other users to send "notification" events to the user. and for the user to publish their content to so others can find it.

What relays the app is currently reading from can differ from a users "mailboxes". the best example of this would be the gossip model where a client is dynamically picking relays to pull the follow feed from

Maybe you can find useful how I organized the relay view in Gossip:

You actually find the "Inbox" and "Outbox" terms here.

The interface mix them with the "Read" / "Write" flag, that have a wider application. You can then filter the relays list by kind.

Btw I'm not 100% sold on this, the inbox/outbox labeling is not so obvious.

oh cool, I like how this is organized. What dose the Discover switch do?

I don't know how much the Inbox / Outbox or "Mailboxes" labels will help but I'd like to give it a shot and at any rate noStrudel needs to stop storing the clients "read" relays in the nip-65 event

Discover: where you discover other people's relays lists

PS: Currently there is a tooltip for every toggle, I think we will transform them in a more visible contextual help; some concept can be abstracted a little but at the end, being really new and innovative, they need to be explained with some details.

Cool! I see where you're going with this πŸ‘ Love that you're separating those sets.

I also need to see solve this for some other apps where you want to be able to go check out niche relays without messing with your main relay set up. Have some fun ideas for visualizing this. Hope to find time for this by the end if the week

Lists, toggles and fancy names will not clear up that much confusion I'm sfraid. Even for us lol πŸ˜‚

Hello... My nostrudel had been unable to load any nostr conetents for 3 days. I'm using brave , chrome and opera browsers with getalby extension.

While other clients like primal , snort , wherost are working well.

Mobile app amethyst also doing well

I tried uninstall getalby extension and starts fresh .. still the same.. anyone has this issue?