3 ms·

There is a limit to url length

bko 6y ago
Correct, safely you can make the url 2,000 chars [0]. The base will be 29 chars (https://ballertodo.com?n=u=i= https://ballertodo.com?n=u=i=) Then each additional todo would be 6 chars (impact and urgency score to 2 decimal places e.g. .65, 1., .7) + the length of the name So assuming the average to-do name is 14 chars, you can safely fit 98 to-dos in the url ((2000 - 30) / (14 + 6)) If the name is 40 chars, you can fit ~41 I think that will fit 90+% of use cases. [0] https://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers https://stackoverflow.com/questions/417142/what-is-the-maxim...
- educated_idiot 6y ago
  Eventually, depending on how it goes, the URL will contain a key to some DB entry, so multi-device persistence can work. Adding all this to the URL is doable too, I might just start with that, thanks for the idea ;)
  - bko 6y ago
    If at all you could make it stateless, you should. For one, you don't need a db. Also, there were some people in the thread that liked the local storage feature. Finally, as a user, I can feel safe using your service because I know at any time, if you site disappears, I have the url and I can trivially parse the url into json and do whatever I want with it. You could even build the parser or have an export to json button. If you want to add more stuff like images, longer descriptions, some links, etc, then yeah you'll likely need a backend
    - educated_idiot 6y ago
      Yeah, I haven't given it that much thought. It only started as a weekend project. I would like to keep it as local as I can. Possibly, there will be 2 uses: a non-db, non-url, local version AND an account based thing.
- catchmeifyoucan 6y ago
  I’ve done this for a website, but when you’re pasting a really long link and texting to a friend, it can get a little frustrating, since it eats the entire chat window.
  - bko 6y ago
    Good point, maybe leverage a link shortener built into the app?
    - catchmeifyoucan 6y ago
      Yup, but you’d still need a database since you need to store that lookup somewhere from long URL to short url.
      - robotwizard 6y ago
        What about using an IPFS key and using js-ipfs to look it up?
        catchmeifyoucan 6y ago
        If I'm not mistaken. I think IPFS keys might also be too long. Since a shortcode is only 6 chars long. Here's the website[1] I built with base64 encoding to share weblinks. I've been trying to think of a non-db approach, but haven't found one yet for link shortening. [1] http://share.getamna.com http://share.getamna.com

bko 6y ago

Correct, safely you can make the url 2,000 chars [0]. The base will be 29 chars (https://ballertodo.com?n=u=i= https://ballertodo.com?n=u=i=) Then each additional todo would be 6 chars (impact and urgency score to 2 decimal places e.g. .65, 1., .7) + the length of the name So assuming the average to-do name is 14 chars, you can safely fit 98 to-dos in the url ((2000 - 30) / (14 + 6)) If the name is 40 chars, you can fit ~41 I think that will fit 90+% of use cases. [0] https://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers https://stackoverflow.com/questions/417142/what-is-the-maxim...

educated_idiot 6y ago
Eventually, depending on how it goes, the URL will contain a key to some DB entry, so multi-device persistence can work. Adding all this to the URL is doable too, I might just start with that, thanks for the idea ;)
- bko 6y ago
  If at all you could make it stateless, you should. For one, you don't need a db. Also, there were some people in the thread that liked the local storage feature. Finally, as a user, I can feel safe using your service because I know at any time, if you site disappears, I have the url and I can trivially parse the url into json and do whatever I want with it. You could even build the parser or have an export to json button. If you want to add more stuff like images, longer descriptions, some links, etc, then yeah you'll likely need a backend
  - educated_idiot 6y ago
    Yeah, I haven't given it that much thought. It only started as a weekend project. I would like to keep it as local as I can. Possibly, there will be 2 uses: a non-db, non-url, local version AND an account based thing.
catchmeifyoucan 6y ago
I’ve done this for a website, but when you’re pasting a really long link and texting to a friend, it can get a little frustrating, since it eats the entire chat window.
- bko 6y ago
  Good point, maybe leverage a link shortener built into the app?
  - catchmeifyoucan 6y ago
    Yup, but you’d still need a database since you need to store that lookup somewhere from long URL to short url.
    - robotwizard 6y ago
      What about using an IPFS key and using js-ipfs to look it up?
      - catchmeifyoucan 6y ago
        If I'm not mistaken. I think IPFS keys might also be too long. Since a shortcode is only 6 chars long. Here's the website[1] I built with base64 encoding to share weblinks. I've been trying to think of a non-db approach, but haven't found one yet for link shortening. [1] http://share.getamna.com http://share.getamna.com