Where is the URL???? any example/demo.
nowhere: an entire website encoded in a URL
21–30 of 75 posts
Re: nowhere: an entire website encoded in a URL
#22Re: nowhere: an entire website encoded in a URL
#23Re: nowhere: an entire website encoded in a URL
#24If I understand correctly, when a nowhere URL is pasted in a browser, what happens is: 1. the browser downloads generic JS libraries from the main site 2. these libraries then decode the fragment part, and transform it into the UI If that's correct, someone still has to host or otherwise distribute the libraries - hence why you need the app to use it while offline (it ships the libraries). This is not criticism, I'm…
I think it still fulfills the brief; the website you are accessing is still hosted "nowhere". Very cool concept, just read about fragments on the MDN docs a couple month ago
Re: nowhere: an entire website encoded in a URL
#25So, its just like sending your sites link through email/whatsapp or any other channel. I don't know what the real usecase for this idea could be!!!!
Re: nowhere: an entire website encoded in a URL
#26Earlier quoted context omitted.
I think it still fulfills the brief; the website you are accessing is still hosted "nowhere". Very cool concept, just read about fragments on the MDN docs a couple month ago
But dependencies are part of a website? It literally says "Still here when the internet isn't." - but I can't go on there without an internet connection?
Re: nowhere: an entire website encoded in a URL
#27How it works A URL fragment is the part after #. The HTTP specification prohibits browsers from sending fragments to servers. The server that delivers the page never receives the content, never knows which site you are viewing, and has no way to find out. No content is collected, stored, or logged. The privacy is structural. A site that was never put on a server can never be taken off one. There is no account to susp…
> The server that delivers the page never receives the content, never knows which site you are viewing, and has no way to find out. Technically true, practically a lie. Because that server delivers the Javascript which decodes and presents the content, and that Javascript absolutely has the ability to inspect, modify/censor, and leak the content (along with fingerprints of the browser). > no host to pressure, no plat…
Re: nowhere: an entire website encoded in a URL
#28How it works A URL fragment is the part after #. The HTTP specification prohibits browsers from sending fragments to servers. The server that delivers the page never receives the content, never knows which site you are viewing, and has no way to find out. No content is collected, stored, or logged. The privacy is structural. A site that was never put on a server can never be taken off one. There is no account to susp…
Unless that site A is encoded in a format that only one other site B on the internet can decode and "serve" (even if it's all client-side) so whoever wanted to block site A would just block site B as a whole.
Re: nowhere: an entire website encoded in a URL
#29Re: nowhere: an entire website encoded in a URL
#30similar enough that i'll share, I think i learned this from an HN comment, you can put the code for a page in the url (with obvious limits): this works as a "url" in both chrome and safari: data:text/html, notes
data:text/html,