pull down to refresh

what nostr has to do with it exactly? Let's say I am a liquidity provider, how and where do I touch nostr while making a swap as a maker?

nostr is only the transport / communication layer.
This is where many people are confused and consider nostr a new stupid social media crap. Nostr is a protocol not a platform!

reply

hmmm, I remember someone saying that nostr will likely even solve the DNS mess. It makes sense now, thanks.

reply
0 sats \ 26 replies \ @ek 27 Mar
nostr will likely even solve the DNS mess

lol

@remindme in 1 year so I can laugh again

reply

why?what do I get wrong? Feel free to school me

reply

you are confusing http with dns. Are not the same thing.
Nostr still depend on DNS but not http.
nostr relays are using wss (websocket) and is different than http

https://www.geeksforgeeks.org/what-is-web-socket-and-how-it-is-different-from-the-http/

reply

so the nostr network can't be used to bind domains to IPs in a decentralized way?

reply

what is s DNS in fact? just an IP.
You can use wss://84.26.71.58 for example, without a domain name.
btw... there no "decentralized internet" you still depend on your ISP to assign you a public IP... and one day you will be forced to give away liberties and rights in order to have an IP.

All this with "decentralized social media" and crap like that is a myth as long we do not have a real decentralized way top manage IPs.
You can have all the freedom you like on nostr, but one day your lovely gov will decide to cut your internet for what you said on nostr. And you can do nothing about that.

reply

Yes, but my question is instead of using a centralized server that says a certain domain is binded to a certain IP, could it be done using nostr relays to "gossip" the domain resolution instead of centralized servers?

0 sats \ 4 replies \ @ek 27 Mar

Websockets are based on HTTP. To open a websocket you send a special HTTP request.

reply
WebSocket is distinct from HTTP used to serve most webpages. Although they are different, RFC 6455 states that WebSocket "is designed to work over HTTP ports 443 and 80 as well as to support HTTP proxies and intermediaries", thus making it compatible with HTTP. To achieve compatibility, the WebSocket handshake uses the HTTP Upgrade header[3] to change from the HTTP protocol to the WebSocket protocol.

https://en.wikipedia.org/wiki/WebSocket

reply
0 sats \ 2 replies \ @ek 27 Mar

The last sentence in your quote confirms what I said

Swapserver announce themselves every 10 minutes or when liquidity changes with a replaceable nostr event, clients query them and can select one. When doing a swap the client and server communicate over encrypted nostr events too.

reply