31–40 of 75 posts
similar 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
> 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?
Now for online, the data is in the URL already, publicly available (unless shared privately), and the "loader" is still served from the server, so you have to trust the server not to exfiltrate the data.
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…
What's the point? You still have to share the link somewhere, why not just share a block of text (invitation, campaign, whatever) directly instead?
I think its just for fun :)
Like this: https://nowhr.xyz/s#yzXyzs8PcDbxyQ_0KbYMzzRNytKNyE0JDM0x8zT2...
> 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??
I am using similar method to share Markdown files as one big URL like this: https://mdview.io/#mdv=N4IgbiBcCMA0IBMCGAXJUTADrhzWOAtgnjgMQ...
Earlier quoted context omitted.
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?
Sure, but what's the point then? Seems like .html with extra steps, not to mention that the URL itself won't work. Now for online, the data is in the URL already, publicly available (unless shared privately), and the "loader" is still served from the server, so you have to trust the server not to exfiltrate the data.
Literally says in the submission title and the website itself: An entire website encoded in a URL.
And yes, the domain part of the URL might not work, but whatever URL you use locally would work just as well if you switch the domain, unless I'm missing something.
> Now for online, the data is in the URL already, publicly available (unless shared privately), and the "loader" is still served from the server, so you have to trust the server not to exfiltrate the data.
Yes, the data is in the URL, seems to be the single point of this entire project. I don't seem to find any "server" doing anything of worth here, all the meat really sits in the client-side code, which you can serve however you like, might even work through file://, haven't tried it myself.
Earlier quoted context omitted.
Sure, but what's the point then? Seems like .html with extra steps, not to mention that the URL itself won't work. Now for online, the data is in the URL already, publicly available (unless shared privately), and the "loader" is still served from the server, so you have to trust the server not to exfiltrate the data.
> Sure, but what's the point then? Seems like .html with extra steps, not to mention that the URL itself won't work. Literally says in the submission title and the website itself: An entire website encoded in a URL. And yes, the domain part of the URL might not work, but whatever URL you use locally would work just as well if you switch the domain, unless I'm missing something. > Now for online, the data is in the UR…
It is very much not, open the network tab on any of the examples, behold.