Re:Hashify: what becomes possible when one is able to store ...
by vidarh on Friday December 30, 2011 @05:43AM
(#3407237)
The data needs to be stored somewhere. In their implementation they in effect use bit.ly as the hosting provider for the data by shortening the url's, so while it's a fun little experiment, it boils down to a content addressable system. We already have good examples of content addressable systems. Git for example is built on content addressable storage.
[ Parent
| on HN ]
Re:Hashify: what becomes possible when one is able to store ...
by djhworld on Friday December 30, 2011 @05:52AM
(#3407250)
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
Re:Hashify: what becomes possible when one is able to store ...
by brador on Friday December 30, 2011 @05:57AM
(#3407262)
Wouldn't the document also be stored in your URL browsing history?
Re:Hashify: what becomes possible when one is able to store ...
by mattvot on Friday December 30, 2011 @05:55AM
(#3407254)
There 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
Re:Hashify: what becomes possible when one is able to store ...
by zalew on Friday December 30, 2011 @05:57AM
(#3407258)
hence the "bit.ly – "rate limit exceeded" :\" message on top...
maybe switch to goo.gl?
Re:Hashify: what becomes possible when one is able to store ...
by djhworld on Friday December 30, 2011 @07:29AM
(#3407422)
This 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"?
Re:Hashify: what becomes possible when one is able to store ...
by andypants on Friday December 30, 2011 @08:27AM
(#3407508)
And 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.