Dr. Hax on Nostr: Why haven't I seen any relay implementations that leech off corporate services? Let ...
Why haven't I seen any relay implementations that leech off corporate services? Let them unknowingly pay the cost of operating a relay.
Post your note to X, LinkedIn, Reddit, and GDocs. Fetch from the same.
Sure some will get squashed, but #nostr is designed to handle that.
I'm guessing there's some technical reason for this not existing, like nostr clients expect a certain API. And if that's the case, it'd be great to see a client with a built in proxy or scraper or something to bridge between the API the nostr client expects and the API for each of these corpo services. #cypherpunk
Published at
2024-08-27 07:09:53Event JSON
{
"id": "0143982ce3a054849a93091a43810f0e189f8bda82557a7017a04200e848129a",
"pubkey": "d30ea98ea65e953f91ab93f6b30ea51eb33c506f87d49f600a139aef00aa9511",
"created_at": 1724735393,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"cypherpunk"
]
],
"content": "Why haven't I seen any relay implementations that leech off corporate services? Let them unknowingly pay the cost of operating a relay.\n\nPost your note to X, LinkedIn, Reddit, and GDocs. Fetch from the same.\n\nSure some will get squashed, but #nostr is designed to handle that.\n\nI'm guessing there's some technical reason for this not existing, like nostr clients expect a certain API. And if that's the case, it'd be great to see a client with a built in proxy or scraper or something to bridge between the API the nostr client expects and the API for each of these corpo services. #cypherpunk",
"sig": "bd79270252d59b9f310152cee8428bf2eee01821366736337e1b9127c72f9618c75176bb53af83e05197820ba4bb4e3d4fbb4fe90f9e9002039d450defa648d9"
}