Live data from Hacker News

nowhere: an entire website encoded in a URL

hostednowhere.com

11–20 of 75 posts

Re: nowhere: an entire website encoded in a URL

#13

> hosted nowhere > present everywhere > Still here when the internet isn't I'm afraid the OP may not have full understanding of how internet works. This is either some kind of a post irony, or some vibe code fever dream. Either way, I'm deeply confused.

I guess in theory if this is packaged as a PWA (or the old-school way, a single .html with everything needed inside of it) you could actually run this anywhere and without internet access easily.

Besides loading the frontend resources, is there anything else that wouldn't work? Seems like a simple idea, so as long as the assets could be loaded, you'd be able to "load" the "apps", wouldn't you?

Re: nowhere: an entire website encoded in a URL

#14

> hosted nowhere > present everywhere > Still here when the internet isn't I'm afraid the OP may not have full understanding of how internet works. This is either some kind of a post irony, or some vibe code fever dream. Either way, I'm deeply confused.

The technology is interesting and has some merit, but the way it's communicated is clearly style (and grand, vague claims) over substance.

Re: nowhere: an entire website encoded in a URL

#15
post #7
post #4

If 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

> Very cool concept, just read about fragments on the MDN docs a couple month ago

Crazy to hear someone reading about something today, that been around since the 90s and probably is one of the first parts you touch when doing web development, but I guess you're just another one of the 10K lucky ones :) (https://xkcd.com/1053/)

Re: nowhere: an entire website encoded in a URL

#17
post #2

How 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 platform that can decide your content should not exist.

Except for https://nowhr.xyz, which becomes a single point of failure for all of these sites...

Re: nowhere: an entire website encoded in a URL

#20
> The internet promised freedom. Platforms delivered permission.

> Private through physics. Not through policy.

Goodness, LLM really convinced itself this was groundbreaking.

You could describe a .html file sitting on your computer with all of the same marketing bluster.

Someone has to send it to you all the same, and you might as well not rely on some random internet service to render it??

Post reply on HN