nowhere: an entire website encoded in a URL

Post by 5t34k » Sat, Apr 25, 2026, 1:20 AM UTC

embedding-shape wrote: post #28

Markoff wrote: 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…

> A site that was never put on a server can never be taken off one. There is no account to suspend, no host to pressure, no platform that can decide your content should not exist. Each copy of the link is a complete copy of the site data. 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 ju…

Post by culi » Sat, Apr 25, 2026, 6:28 AM UTC

huflungdung wrote: post #37

foltik wrote: post #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??

You’re absolutely right. This changes everything. The html file is the smoking gun. Let me delve into this to give the user a clearer picture.

Post by cidra » Tue, May 05, 2026, 6:41 PM UTC

varun_ch wrote: post #66

cidra wrote: post #58

Earlier quoted context omitted.

Digital restaurant menus!

so they’d need to change their QR codes every time the menu changes?