-
Notifications
You must be signed in to change notification settings - Fork 291
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
Too Many Relays Warning #544
Comments
Ah so having less than 15 relays is recommended - good to know. I've been running 18 for the past week and experiencing a range of issues |
Yes. Take a look at nostr.watch, to check how relays perform for you. |
related to the relay suggestions work |
Seems to still affect some users. Warning of too many relays would be a helpful guardrail to help prevent a negative user experience for some users. |
Thanks @ser-sleepy There is a trade-off in onboarding: just hit "start" and post a note as quickly as possible vs doing a nostr relay tutorial, and other nostr/LN tutorials. Maybe we could use Tipkit #1255 to prompt education in app, post onboarding, in addition to adding the too many relays warning. |
One thing that might be really useful is for damus to track relay stats.
It can measure the latency of pings and requests, and then automatically
disable certain relays if they are dead, slow, or unresponsive. Damus
could automatically pick the top performing relays, instead of blindly
blasting to all of them.
|
@dskvr does nostr watch API exist and allow for this? |
On Mon, Dec 04, 2023 at 10:09:55AM -0800, alltheseas wrote:
> One thing that might be really useful is for damus to track relay stats.
> It can measure the latency of pings and requests, and then automatically
> disable certain relays if they are dead, slow, or unresponsive. Damus
> could automatically pick the top performing relays, instead of blindly
> blasting to all of them.
>
>
@dskvr does nostr watch API exist and allow for this?
we don't need an api, we can do this inside damus in realtime.
|
No problem! Im thinking of a possible solution being a "tutorials" section on the menu below "merch" n above "settings" which can be "skipped" during the onboarding process if you just want to jump straight into posting and go back to it at a later time.. just an idea |
This is @robagreda territory - my gut feel is that any tutorial functionality should happen as the Damus user is opening a new |
18 relays user reporting warm phone: npub18dlusgmprudw46nracaldxe9hz4pdmrws8g6lsusy6qglcv5x48s0lh8x3 |
User Story
As Damus engineer who wants to ensure Damus newbies avoid relay onboarding pitfalls, I want to warn Damus users if they are adding too many relays, so that they do not run into bandwidth, and/or machine performance issues.
Acceptance Criteria
"
You might also want to warn them that this app requires large quantity of data transactions when using mobile-data network…
"-Pomcan npub15threpkztu32y0st67u27xrrr2v5hrt848a60djh48dkx4sv33rssf7rxu
https://damus.io/note149d3x2jwm6epwgwfd7spj9aswggumjsw9255sur86zkn5etlfm0sfe6znr
"
Definitely need warnings when users add too many relays
"-@jb55
https://damus.io/note1vvlmvtcsjf5djmx22dr76rvl50gqud9t2tfajxv04tpnl844fmaqvxjzpm
The text was updated successfully, but these errors were encountered: