Rizful.com on Nostr: So we have been in the trenches with this issue for a few months. We're currently ...
So we have been in the trenches with this issue for a few months. We're currently using #nostream -- note that you'll need to make a lot of changes to the configuration file to change various "rate limiting" limits -- it's quite tricky because you probably won't know that you've hit these limits until your users actually start using
NWC (npub19hg…yv9p) a lot! .... But that's not it -- the challenge actually that we have been having is KEEPING THE CONNECTION ALIVE between our server and our relay -- that's actually our development focus right now. It's tricky because these websocket connections don't last for ever. You really I think need to set up constant monitoring - we have quite complicated monitoring in place with a demo NWC user, who makes a 1 sat payment every few minutes, and then we get alarms if it fails..... I think there is generally a need for some BEST PRACTICES to be established with LONG LIVED connections to relays.
Oh, and yes, in your #nostream configuration file, you will want to disallow probably some KINDs, so your relay only deals with NWC stuff. But again, this is not straightforward, I think that some clients won't use your relay if you limit the kinds too much?
Published at
2025-02-28 14:10:03Event JSON
{
"id": "92a21cb78247531bf2b0f7dc559ec643c52fa631a99a9cdeb95558440e8d3cf1",
"pubkey": "97f848adcc4c6276685fe48426de5614887c8a51ada0468cec71fba938272911",
"created_at": 1740751803,
"kind": 1,
"tags": [
[
"e",
"256286c148d80c1549dbbca87ffcd1a0366b795975d8768fd9e0b763b5fc6916",
"",
"root"
],
[
"p",
"d6149823c90c4865e4bc434a4be1a1ee8f72aabd8328dd059ba4f11f7633b0b6"
],
[
"t",
"nostream"
],
[
"p",
"2dd140ca80db62bcf377d7dbe68d22a95baa41d19c5b4971a78204af7596051a",
"",
"mention"
]
],
"content": "So we have been in the trenches with this issue for a few months. We're currently using #nostream -- note that you'll need to make a lot of changes to the configuration file to change various \"rate limiting\" limits -- it's quite tricky because you probably won't know that you've hit these limits until your users actually start using nostr:npub19hg5pj5qmd3teumh6ld7drfz49d65sw3n3d5jud8sgz27avkq5dqm7yv9p a lot! .... But that's not it -- the challenge actually that we have been having is KEEPING THE CONNECTION ALIVE between our server and our relay -- that's actually our development focus right now. It's tricky because these websocket connections don't last for ever. You really I think need to set up constant monitoring - we have quite complicated monitoring in place with a demo NWC user, who makes a 1 sat payment every few minutes, and then we get alarms if it fails..... I think there is generally a need for some BEST PRACTICES to be established with LONG LIVED connections to relays. \n\nOh, and yes, in your #nostream configuration file, you will want to disallow probably some KINDs, so your relay only deals with NWC stuff. But again, this is not straightforward, I think that some clients won't use your relay if you limit the kinds too much?",
"sig": "e6748ff87a1a009186d1824984c2e3ba668e8ea2fe3c961535e24aefb6a76c695a0e1191959e332054b81f6ed7d9eaf045fe14c6b910d4372bacd88406dab1e8"
}
