Conversation

Notices

1. Embed this notice
   jb55 (32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245@mostr.pub)'s status on Thursday, 04-May-2023 23:49:54 JST jb55

   • fiatjaf
   How is this not a valid response. The web can’t make dns requests. This was @3bf0c63f ‘s original concern as well if I remember correctly. Generally I try to not add features that web clients can’t take advantage of to not further fracture nostr.
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Thursday, 04-May-2023 23:49:54 JST feld

     in reply to

     • fiatjaf
     > The web can’t make dns requests.
     
     Why can't javascript make a DNS over HTTP request?
   • Embed this notice
     fiatjaf (3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d@mostr.pub)'s status on Thursday, 04-May-2023 23:57:48 JST fiatjaf

     in reply to
     My concern was that there were two ways of doing the same thing and supporting both would just double the work for everybody, so we had to pick one.
     
     The /.well-known/nostr.json HTTP request is better because
     
     1. a single provider can host infinite names
     2. it's still simple and free to host a static site once you have your own domain
     3. it could be expanded with more metadata if necessary
     
     Web support was a thing but I've implemented it with DoH which was good enough before deciding to switch to the HTTP.
     Alex Gleason likes this.