There are broadcast buttons.

Reply to this note

Please Login to reply.

Discussion

If your event makes it to one of the medium or large-sized relays, it gets pulled by aggregators and quickly shows up all over. Then you get around rate limits.

The problems arise for people only using the very biggest relays and/or with no outbox model.

This last note was on at least 98 relays within 15 seconds, according to https://nadar.tigerville.no/

Damus broadcasts automatically with geometric backoff if it fails to write to the relay, you don’t need to do it manually. If clients don’t do this then notes are easily lost during connection issues

Yes, I have that problem on Freerse.

I think Nostrudel retries. Never seem to lose anything, there. Same with Coracle.

yeah nostrudel and coracle have both had this since i first used the beginning of this year... the client should keep a queue and a checklist of which relays it has got to and some sort of scheme for backing off

one of the differences with web clients though is that queue is nixed when you refresh the page, and sometimes the page scripts are broken and make this refresh happen on clicks unintentionally

Unthrottling the Damus relay would be a nice premium feature. That's one of the best relays.

Good idea

Unthrottle + long term backup by mirroring to a purple relay for members 🤔

i already subscribe to wine and land i'd be up for damus as well

Same.

Probably would go for Damus Premium for the GitCitadel npub, to maximize reach.

Would also be good if the Premium offered a good spam filter or some advanced search, or something.

On the relay, I mean.

Some of us are relay customers, more than client customers. We're sort of client nomads, but we use the same relays everywhere.

And we'd be more-inclined to use a client, if it offered us controls for a relay, like relay.tools does.

hitchhiker?

this is what all proper network clients do... you can see examples of it in the bitcoin core and btcd p2p code as well

front end devs are not often so well versed in the problems of socket networking, being used to HTTP APIs... websocket libraries don't give you any tools for this either