My idea is that it could be built on top if the relay communication is flexible enough. most nostr libraries build the auth, limitations, and connection policies at the "new WebSocket()" level, but that makes it difficult to add additional types of behavior that a different client might want later
For example you could implement a relay blacklist at the websocket level so that it would throw an error (or make it look offline) if the client connected to a blacklisted relay. or you could extend that relay pool class to ensure it never even tries to connect to blacklisted relays. all of this is just a theory though, I still have to put it into practice to see if it works
hzrd149
npub1ye…pknpr
2025-04-01 17:10:33
in reply to nevent1q…wjq2
Author Public Key
npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknprPublished at
2025-04-01 17:10:33Event JSON
{
"id": "a9cd8cdaa75955fa16a6b4a776013fc181e10cc8820a7698af10c93ef86583c3",
"pubkey": "266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5",
"created_at": 1743527433,
"kind": 1,
"tags": [
[
"e",
"7232af889e79b07bc8dab1307acc24766bd869f9a9be3ff86f8239be532ef2f9",
"wss://hbr.coracle.social/inbox",
"root"
],
[
"e",
"06f52ac9a686f723f7a5b91df210ccf78892a4fe396da8986922da78243201c3",
"wss://nos.lol",
"reply",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5",
"wss://nostr.wine/",
"hzrd149"
],
[
"p",
"c6603b0f1ccfec625d9c08b753e4f774eaf7d1cf2769223125b5fd4da728019e",
"wss://nostrelites.org/",
"Cesar Dias"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "My idea is that it could be built on top if the relay communication is flexible enough. most nostr libraries build the auth, limitations, and connection policies at the \"new WebSocket()\" level, but that makes it difficult to add additional types of behavior that a different client might want later\n\nFor example you could implement a relay blacklist at the websocket level so that it would throw an error (or make it look offline) if the client connected to a blacklisted relay. or you could extend that relay pool class to ensure it never even tries to connect to blacklisted relays. all of this is just a theory though, I still have to put it into practice to see if it works",
"sig": "456144210a65d8b04e69f26a421f88184b0806f21f5fd13e92c5a38c9de99dd2bc320c4a8aac2278c8fd4d82b646692f80c7a31cab04c6cf98d99dc77b40d110"
}