fucking idiot
🔔 This profile hasn't been claimed yet. If this is your Nostr profile, you can claim it.
Edit
fucking idiot
Does anyone know someone at tryspeed.com?
Thanks for sharing man, it looks great and quite affordable 🙏
Thanks!
blades for normal rasors are stupidly expensive. Do you know/use any razor brands that make things that are higher quality without stupid prices? #asknostr
Enigmatico, intrigante
weird. They could render kind 1111 just as kind 1
You raise some good points. I would say in general the tradeoff is simplicity vs flexibility. WS allow to make many small requests, where HTTP does it with batching. WS pays a bigger cost at the beginning, which may get compensated, depending on the usage. WS are more complex to deal with, almost all client devs I met complained about WS being unreliable, having issues with reconnection etc. Maybe poor libraries? idk I don't get the point about getting rid of IPs, DNS etc. Relays are HTTP servers that hijack the connection to upgrade to WS, so they have to comply with all that. If you are hinting about the fact that a CVM provider could use someone else's relay to serve its customers, I would agree only partially. The latency alone would likely render this business not very efficient at serving its customers. It's a nice to have but I don't think it will be relevant in practice IMO. > I wish it could be transport agnostic so I can implement it in Relatr. Let's talk about it mate. We may design something even better!
curious to learn more about yours 😉 But the relay when receives any kind of REQ it will index the subscription, which is not super cheap. Nostr should have separated the request response command from the subscribe command IMO. In that way it can be efficient.
DVMs were a tragedy. It never made sense to build a request/response pattern on top of a pub/sub pattern (relays). Plain HTTP still undefeated
simplifying the social graph so you can focus on building great experiences