Live data from Hacker News

Show HN: Minimalist editor that lives in browser, stores everything in the URL

github.com

21–30 of 172 posts

Re: Show HN: Minimalist editor that lives in browser, stores everything in the URL

#23
post #15
post #12

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...

LOL Tapping the address bar crashed my Chrome on mobile.

Re: Show HN: Minimalist editor that lives in browser, stores everything in the URL

#26
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.

Re: Show HN: Minimalist editor that lives in browser, stores everything in the URL

#29
post #12

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.

Post reply on HN