Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refine publish notifications #95

Open
GBKS opened this issue Oct 7, 2024 · 0 comments
Open

Refine publish notifications #95

GBKS opened this issue Oct 7, 2024 · 0 comments
Labels

Comments

@GBKS
Copy link
Owner

GBKS commented Oct 7, 2024

When a note is published to a relay, a notification shows up for that process. It updates as the state changes (publishing -> done/error). It is certainly nice to know what is happening. But when you publish to 5 relays, you get 5 notifications. And the ones that don't work out stick around until you click them off.

It would be a lighter experience if there's a summary notification that shows a dot per relay and it turns blue/green/red based on the status.

From my experience, you're never perfectly connected to all your relays. And maybe it's OK if publishing to 4 of 5 relays is successful, and one fails. For errors, the notification should also be clickable so you get an explanation.

For most clients, it's probs not a big deal if a like reaction to a post does not get published everywhere. But your profile, follow and relay lists are special. You really want them correctly updated everywhere. Getting this right will probably be a continuous effort.

Nosta could even automatically, in the background, update outdated profiles when you visit the site. It's just reposting an existing event. Risks are that the user actually come to restore an older version. Just going to have to weigh these things off and figure out what works best IRL.

@GBKS GBKS added the design label Oct 7, 2024
@GBKS GBKS pinned this issue Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant