[deleted]
Hashify: what becomes possible when one is able to store documents in URLs?
11–20 of 84 posts
Re: Hashify: what becomes possible when one is able to store documents in URLs?
#12Earlier quoted context omitted.
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.
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
Wouldn't the document also be stored in your URL browsing history?
Re: Hashify: what becomes possible when one is able to store documents in URLs?
#13The first use case that comes to mind is anonimity.
Re: Hashify: what becomes possible when one is able to store documents in URLs?
#14Boiling it down, it's a new file format with a built in viewer. You need to find a way to store the data. Interesting, but I can't think of any practical application, apart from the service provider not having to worry about storage (maybe that's key ... more thinking needed).
It would be except it's not new, it's a dupe of post from not too long ago that had a large amount of points: http://news.ycombinator.com/item?id=2464213
Re: Hashify: what becomes possible when one is able to store documents in URLs?
#15The first use case that comes to mind is anonimity.
Solutions like pastebin.com provide the same, with a small url.
Re: Hashify: what becomes possible when one is able to store documents in URLs?
#16"Internet Explorer cannot display the webpage" is what happens here (IE 8).
Re: Hashify: what becomes possible when one is able to store documents in URLs?
#17"Internet Explorer cannot display the webpage" is what happens here (IE 8).
[deleted]
Re: Hashify: what becomes possible when one is able to store documents in URLs?
#18What becomes possible? The entire internet could effectively get rid of hosting account providers, with each page in every site being contained in a hashify URL, and with each page linking to other pages using other hashify URLs. 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.
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 documents in URLs?
#19The original version of Mr Doob's GLSL Sandbox at http://mrdoob.com/projects/glsl_sandbox/ used the same approach, but increased the maximum possible size of the document by doing LZMA compression before base64.
The project later moved to http://glsl.heroku.com/ with an app-driven gallery, and that particular feature went away. I think that is a pretty natural evolution of any such idea, so I'm not convinced of hashify's logevity, but hey, simple sometimes is really enough.
Re: Hashify: what becomes possible when one is able to store documents in URLs?
#20I took a similar approach to this with http://cueyoutube.com and recently found snapbird which gives extended twitter search capabilities. So the URL contains the playlist and twitter becomes the data base, so I just tweet my playlists and they're "saved". You can see all the lists I've created by searching the account iaindooley and search term cueyoutube in snapbird.