31–40 of 172 posts
I like these kinds of projects, but adding a file export/import is inevitable. It's less about the limits of a URL and more about practicality. I also have no way to confirm that URLs aren't logged server side, so I'd never trust the claim about "no tracking". That's why these projects also end up self-hosted.
Half a megabyte for a URL. That certainly is a thing.
Now if you bootstrap the app code into the url too then you can have a minimal kernel to run any machine in url.
Then you can also make a Quine somehow.
I like these kinds of projects, but adding a file export/import is inevitable. It's less about the limits of a URL and more about practicality. I also have no way to confirm that URLs aren't logged server side, so I'd never trust the claim about "no tracking". That's why these projects also end up self-hosted.
hash part of url only available in the browser, as far as I know, server doesn’t have access to # value
The Crime and Punishment one consistently crashes Brave mobile for me. I assume it's the length of the URL - and seen another commentator say the same for chrome mobile (sure they both use the same codebase so likely an upstream issue).
Per the spec [0], a URL can hold at least 8,000 characters. > It is RECOMMENDED that all senders and recipients support, at a minimum, URIs with lengths of 8000 octets in protocol elements. Note that this implies some structures and on-wire representations (for example, the request line in HTTP/1.1) will necessarily be larger in some cases. Mainstream browsers support at least 64,000 characters [1], and Chrome suppor…
> Per the spec [0], a URL can hold at least 8,000 characters. > It is RECOMMENDED that all senders and recipients support, at a minimum, URIs with lengths of 8000 octets in protocol elements. It is always worth remembering that, unless you have already ensured that the content has been rendered into a URI-safe subset of ASCII, a character and an octet are not the same thing.
Per the spec [0], a URL can hold at least 8,000 characters. > It is RECOMMENDED that all senders and recipients support, at a minimum, URIs with lengths of 8000 octets in protocol elements. Note that this implies some structures and on-wire representations (for example, the request line in HTTP/1.1) will necessarily be larger in some cases. Mainstream browsers support at least 64,000 characters [1], and Chrome suppor…
Chrome limit is 2MB, Firefox is 1MB, WebKit is no limit. Here is the Crime and Punishment by Fyodor Dostoevsky: - https://medv.io/goto/crime-and-punishment-by-fyodor-dostoevs...
https://github.com/swiftlang/swift-corelibs-foundation/blob/...
I built Ponder in the same vein. It, however, has 10 files. I did not use the URL, did not have double the fun, and now I’m sad.