Re:Hashify.me - store entire website content in the URL
by jurjenh on Tuesday April 19, 2011 @07:08PM
(#2464598)
I tried to make a self-referencing page, but you need to be able to generate the hash of the page url that includes its own hash...
Not having the time to do so, I leave the challenge here: http://bit.ly/ialoWI
Re:Hashify.me - store entire website content in the URL
by th on Tuesday April 19, 2011 @10:25PM
(#2465024)
That's not possible because the base 64 encoding is longer than the plaintext. There are 4 characters of text in the URL for every 3 characters of text entered.
Re:Hashify.me - store entire website content in the URL
by sesqu on Wednesday April 20, 2011 @10:36AM
(#2466753)
If you're willing to jump through hoops and js-compress your content, you can deal with this issue, unless your compressor uses something like crc. That way, you can grow the plaintext faster than the b64 - though you'd still need to do clever things with the url.
Re:Hashify.me - store entire website content in the URL
by jarin on Tuesday April 19, 2011 @07:59PM
(#2464725)
That's essentially what you're doing when you are trying to mine Bitcoin :)
Re:Hashify.me - store entire website content in the URL
by jantangring on Thursday April 21, 2011 @12:08PM
(#2471153)
Re:Hashify.me - store entire website content in the URL
by messel on Tuesday April 19, 2011 @07:13PM
(#2464615)
until you jumped the api limit :D
why not hot swap any shortner?
Re:Hashify.me - store entire website content in the URL
by hashify on Tuesday April 19, 2011 @10:28PM
(#2465030)
bit.ly is the only URL shortening service to support cross-origin resource sharing, as far as I'm aware.
The _right_ thing to do would be to build a shortening service designed to handle URLs of arbitrary length. I'm not sure that I'm willing to take on that responsibility, though.
Not so. hashify.me has no server-side component (beyond nginx serving three static files). _bit.ly_ kindly provides the hash table. ;)