Even with the new element reload feature in Plume I'm noticing, even with no active websocket connections clogging up the pipes, that it often takes two or three attempts to pull a profile or quoted note. Not every time, but frequently. So it's not getting lost in the noise of open websocket connections and loading/sorting process, it's simply not getting responses from relays reliably. On perfectly fine equipment with perfectly find Internet. So it's the relays. I keep coming back to it.
So my next question; is it the relay software, or the hardware? Are we simply not using powerful enough servers, or is nostr's basic building block, the relay, missing something that'll change the whole nostr experience?
#asknostr
Matt
npub1cl…a3zny
2026-10-04 07:09:42 UTC
Author Public Key
npub1cllf97qv29kqc493t6xj26kqw2qsxmvnf6sl7w0mpnv2plt8wumqta3znyPublished at
2026-10-04 07:09:42 UTCEvent JSON
{
"id": "06f6bbd211d69d13c5c31114b9d120c980c5ea59c0d649a542c00c3b716e0963",
"pubkey": "c7fe92f80c516c0c54b15e8d256ac07281036d934ea1ff39fb0cd8a0fd677736",
"created_at": 1791097782,
"kind": 1,
"tags": [
[
"client",
"Plume"
]
],
"content": "Even with the new element reload feature in Plume I'm noticing, even with no active websocket connections clogging up the pipes, that it often takes two or three attempts to pull a profile or quoted note. Not every time, but frequently. So it's not getting lost in the noise of open websocket connections and loading/sorting process, it's simply not getting responses from relays reliably. On perfectly fine equipment with perfectly find Internet. So it's the relays. I keep coming back to it. \n\nSo my next question; is it the relay software, or the hardware? Are we simply not using powerful enough servers, or is nostr's basic building block, the relay, missing something that'll change the whole nostr experience? \n\n#asknostr",
"sig": "6a8ee096d530107e38081e8ae5c7239bb2bbb3984ad2e8a200bd3dd1e4bbbc0455e3f893390f25e975b5bf3e88ab931e56fd7fc10284b8db333d9863c6084d29"
}