4 ms·
There is a size limit though that quickly gets exhausted if you are storing text (2000 chars)
by tlarkworthy 4y ago
There is a size limit though that quickly gets exhausted if you are storing text (2000 chars)
- rmetzler 4y agoThis is the right answer here. The solution works until it doesn’t. Browser URLs are limited in real life. So when the state grows it will break sooner or later. Of course it depends on the usecase.
- tonerow 4y ago(maker of flowchart.fun here) This is technically true but it's a little more nuanced. The 2048 character limit comes from Internet Explorer. There's a great answer on SO https://stackoverflow.com/a/417184/903980 https://stackoverflow.com/a/417184/903980 Still on FF I opted to use LZ Compression (pretty sure many other sites do this as well) to get the number of characters down
- tlarkworthy 4y agoI have done this myself and various tools e.g. slack, Twitter will truncate long urls. Eventually it will break somewhere, not just in the browser. If your tool has a hard limit on information content it's ok, but that does not seem to be the case here.
- escot 4y agoYou're right, its a limitation. Knotend also supports upload/download of a .knotend file to get around this.
- __MatrixMan__ 4y agoStore the content in ipfs and just put the hash in the URL? I haven't used https://github.com/ipfs/js-ipfs https://github.com/ipfs/js-ipfs in this capacity but I'm under the impression that that's moving bits around like that is more or less its purpose. Although I suppose this puts a burden on the URL-creator to pin the content until the URL-clicker doesn't need it anymore, which is not how URLs are supposed to work.