coracle/flotilla
1
6
Fork 23
Code Issues 42 Pull Requests 2 Actions Packages Projects 5 Releases Wiki Activity

Improve Relay Selection #21

New Issue
Closed
opened 2026-02-17 18:05:27 +00:00 by hodlbod · 3 comments
hodlbod commented 2026-02-17 18:05:27 +00:00
Owner
Copy Link
Copy Source

Imported from https://github.com/andotherstuff/universes/issues/21 by @staab on 2025-11-14T18:26:02Z

Relays are inscrutable to new users, so custom selections should be considered an advanced feature. This means that we'll want to provide reasonable defaults, and if the user hasn't set their relays, prompt them to publish them the first time they're needed. Use the defaults, but allow them to set custom selections if desired.

  • When a user attempts to publish a public post, prompt them to create inbox/outbox relays
  • When a user attempts to send a DM (or interacts with chat at all), prompt them to create dm relays
  • Re-work the relay settings page to be a dashboard type thing rather than mere settings. Look at relayman for inspiration.
_Imported from https://github.com/andotherstuff/universes/issues/21 by @staab on 2025-11-14T18:26:02Z_ --- Relays are inscrutable to new users, so custom selections should be considered an advanced feature. This means that we'll want to provide reasonable defaults, and if the user hasn't set their relays, prompt them to publish them the first time they're needed. Use the defaults, but allow them to set custom selections if desired. - When a user attempts to publish a public post, prompt them to create inbox/outbox relays - When a user attempts to send a DM (or interacts with chat at all), prompt them to create dm relays - Re-work the relay settings page to be a dashboard type thing rather than mere settings. Look at relayman for inspiration.
hodlbod added this to the Current milestone 2026-02-17 18:05:27 +00:00
hodlbod self-assigned this 2026-02-17 21:26:04 +00:00
hodlbod commented 2026-03-11 22:59:08 +00:00
Author
Owner
Copy Link
Copy Source

Attached is the mockup our designer came up with. Suggested relays is kind of pointless, and relay policies are better under privacy settings so I didn't include those. Our settings pages aren't currently full-width either, so side-by-side cards doesn't really fit (although we should add a full-width layout for mega-wide screens eventually). So what I did was put the action items in a button at the top of the relay list. This can be fleshed out for sure, currently we don't really check relay connection or anything. The rest should probably wait on #22

Attached is the mockup our designer came up with. Suggested relays is kind of pointless, and relay policies are better under privacy settings so I didn't include those. Our settings pages aren't currently full-width either, so side-by-side cards doesn't really fit (although we should add a full-width layout for mega-wide screens eventually). So what I did was put the action items in a button at the top of the relay list. This can be fleshed out for sure, currently we don't really check relay connection or anything. The rest should probably wait on #22
Screenshot 2026-03-11 at 3.49.48 PM.png
233 KiB
Screenshot 2026-03-11 at 3.49.48 PM.png
hodlbod modified the milestone from Current to Future 2026-03-11 22:59:21 +00:00
hodlbod commented 2026-03-19 17:55:59 +00:00
Author
Owner
Copy Link
Copy Source
  • If the user has no DM relay selections, or health check fails, open a dialog which offers to fix automatically or "fix it myself"
  • Add action items above relay settings
- [x] If the user has no DM relay selections, or health check fails, open a dialog which offers to fix automatically or "fix it myself" - [x] Add action items above relay settings
hodlbod commented 2026-03-23 21:37:15 +00:00
Author
Owner
Copy Link
Copy Source

Closed with 1de6d7a874 b716f3f792 75053bbbb1 f9c7ed4936

Closed with 1de6d7a87453b9f482a570bf8fa6b7982e1a85d3 b716f3f792a1bbdb1f65922e7d1320f6eceff1ca 75053bbbb1f4ec917739c44cbc45fa1c17fd3dd5 f9c7ed49362c6388e086a8e0991b055547f02f42
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design
For issues related to design work. Development should be done in another issue and refer back to this one.
 dev
Issues related to development work
 easy
Issues that can be executed on by new contributors
 idea
For issues that aren't yet actionable
 priority
For issues related to high priority features and bugs
 usability
Issues that have to be validated with real live human beings.
No Label
Milestone
No items
No Milestone Future
Projects
Clear projects
No project
Assignees
Clear assignees
hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees hodlbod
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#21
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?