Currently designing a better relay management UX, and its a nightmare, send help!
Login to reply
Replies (5)
UX people, assemble!
View quoted note →
why is it a nightmare? does it use normal relay lists or a new kind? what does it need to use a relay is it similar to nip17? would it help if relay operators publish a nip66 with a whitenoise tag to indicate suitable for use with whitenoise?
Yeah, it's not easy. Here's a mockup I created (via a broken mkstack implementation 😂):
One difficult decision is whether to group selections by relay with the ability to change their function (like coracle does), or to group by category with the ability to add/remove relays (like flotilla does). The many different categories of relay make it difficult for users to comprehend, which probably requires clients to help out.
All that to say, I don't really know how to solve it.
One difficult decision is whether to group selections by relay with the ability to change their function (like coracle does), or to group by category with the ability to add/remove relays (like flotilla does). The many different categories of relay make it difficult for users to comprehend, which probably requires clients to help out.
All that to say, I don't really know how to solve it.why not just use outbox relays for that?
View quoted note →
It's a mess because now there are four different relay lists, and that's difficult to design.
We have something pretty coming in the next release tho!