4 ms·
It also assumes that there's no limit on URL space that bit.ly provide. Tomorrow they could just max out the "long_url" field or whatever they call it to just a
by djhworld 15y ago
It also assumes that there's no limit on URL space that bit.ly provide. Tomorrow they could just max out the "long_url" field or whatever they call it to just accept 1500 chars or something
- mattvot 15y agoThere is: "Storing a document in a URL is nifty, but not terribly practical. Hashify uses the [bit.ly API][4] to shorten URLs from as many as 30,000 characters to just 20 or so. In essence, bit.ly acts as a document store!" http://tinyurl.com/3n6h8px http://tinyurl.com/3n6h8px
- zalew 15y agohence the "bit.ly – "rate limit exceeded" :\" message on top... maybe switch to goo.gl?
- djhworld 15y agoThis was my point, they're passing their 30,000 char URL to bit.ly to return a short URL (20 chars) But what happens if bit.ly just say "Sorry incoming URLS (long urls) can only be a maximum of 1500 chars"?
- andypants 15y agoAnd then the next paragraph: While the HTTP specification does not define an upper limit on the length of a URL that a user agent should accept, bit.ly imposes a 2048-character limit.
- brador 15y agoWouldn't the document also be stored in your URL browsing history?