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.
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.
Re:Hashify: what becomes possible when one is able to store ...
by friggeri on Friday December 30, 2011 @06:26AM
(#3407305)
The real trouble is that when you link to a hashified URL, you are actually embedding in your web page (an encoding of) the content of the page you are linking to. Think matryoshka.
Re:Hashify: what becomes possible when one is able to store ...
by austintaylor on Saturday December 31, 2011 @01:32AM
(#3410348)
Right. Even without link cycles, any link would have to contain (nearly) the whole internet.
Re:Hashify: what becomes possible when one is able to store ...
by LeafStorm on Friday December 30, 2011 @10:58AM
(#3407999)
Not to mention that makes link cycles impossible.
Re:Hashify: what becomes possible when one is able to store ...
by aurelianito on Friday December 30, 2011 @11:35AM
(#3408124)
Nah! I am pretty sure that a quine can be made using this! http://en.wikipedia.org/wiki/Quine_(computing)
Re:Hashify: what becomes possible when one is able to store ...
by seanp2k2 on Friday December 30, 2011 @10:22PM
(#3410019)
in essence, this would be moving away from a model of "large networks of connected pages/sites" to "a large amount of single documents with no meaningful mechanism of inter-connectedness".
Think about this like a PDF where stuff is embedded instead of in separate files.
Trouble is, there might be a DNS-like system needed to match hashify URLs to more human-readable strings (or a way for existing DNS to resolve to hashify style URLs).
Neat idea.