Shared publicly  - 
Just getting this on record before the 1.0 release, I'll reveal it later.
Ivan Miljenovic's profile photoSimon Meier's profile photoFelipe Lessa (meteficha)'s profile photoMichael Snoyman's profile photo
One of the instances of "private page" in steps 4 or 6 should probably be "public page". (I'd infer from the FAQ that step 4 would be first sending a link to the public page).

Pretty cool idea for a site btw, and I don't think it's overkill :)
Cool idea! :) And as Conrad said, the "private" should be "public" in FAQ 4.
Thanks for the feedback guys, I've updated the site. This was one of those "wouldn't it be cool if..." moments that only took a few minutes to implement.
The last FAQ answer should be more than just "Yes". I would suggest "Yes, but this is a cool hack".
MD5? Wouldn't surprise me if you have like 5 predictions ready to match that hash. :)
So yesod- is out; what was the prediction?
Here was my prediction:

Turns out I was dead wrong, there were instead an inordinate number of comments comparing to Snap. As a community, I think we need to coordinate a bit more on this stuff, but I'll leave that as a discussion for later.

And you guys think I should switch to SHA-512? Thanks to +Vincent Hanquez's cryptohash, it's just a matter of changing imports.
+Jason Dagit Yeah, just share the private URL. I was considering making this more sophisticated where you have an account and a dashboard with all of your predictions, and you can reveal them whenever you want, but there was a slightly higher barrier to entry with that: it meant I needed to spend more time coding, and users would need to create an account.
+Michael Snoyman Could you, for convenience and compatibility with the sha512sum command line program, please also provide a hexadecimal representation of the SHA512?
+Michael Snoyman the new bytestring builder provides the function you are looking for. I'll compare it on your benchmark right now.
That's very exciting. Personally, I'm eagerly awaiting the release of the new bytestring library, even if it means I'm going to spend 5 hours updating cabal files...
+Michael Snoyman agreed, having "native" builder support would be nice (especially since blaze-builder depends upon text, which in my use-case I don't need).
Hmm, yes. However, Duncan mentioned that it will not be before the next GHC release. So you'll have to eagerly wait some more time... ;-)
Yes, text providing native builder support would/will also be nice.
Yes, it does have a builder. What is missing are functions like 'encodeUtf8Builder :: Text -> Builder' which can be used to assemble output from smallish Text values in a zero-copy fashion with a guarantee on a large average chunk size (required for few system calls).

Moreover, the new builder infrastructure also provides support for implementing fast custom encodings (mostly used for escaping + UTF-8 and the like). See this thread for some benchmarks:

In the future, I imagine that functions creating sequences of bytes always result in builders instead of bytestrings, as this gives good compositionality + good performance. For this to happen, builders must be provided together with the bytestring library.
+Michael Snoyman, it seems that the site is not working anymore.  I've just remembered about this post and I'm not able to see what your prediction was =(...
Turns out I was totally wrong: . I expected a lot of dynamic typing fans to pop in, I don't really remember seeing any. I based this prediction on the fact that I hear that claim made so often before I start demoing Yesod (once I give concrete examples, it's hard to argue against them).

The site's still working, but the domain name without the leading www is pointing at the wrong IP address. I'll get that fixed.
Add a comment...