220 karma · joined May 8, 2010
henrian.com · io@henrian.com
[ my public key: https://keybase.io/chbrown; my proof: https://keybase.io/chbrown/sigs/kf-oAAgnHRc59Gxg8w4qJdjXYZrGgvorVKCQPkZt2QM ]
5. The copyright holder reserves the right to revoke this license on anyone who uses this copyrighted work at any time for any reason.
And his explanation from the README:
Lamson is licensed under the license in the https://github.com/zedshaw/lamson/blob/master/LICENSE file. It's a variant of the BSD license that is revokeable and makes contributor's rights clear up front.
It's a phenomenal idea. I'm gonna start buying stuff in revokeable cash.
Did anyone actually try any of these? None of them work.(Correct me if I'm wrong -- I didn't try them _all_)
https://github.com/gaubert/gmvault/issues/4
(Issue number 4 on the github project.)
I added my output to the issue.
I'm on Gmvault v1.0-beta from pypi. It doesn't recognize the --restart option. "gmvault: error: unrecognized arguments: --restart"
It already timed-out once (no discernable reason), and after restarting, went right to email number 1 (forgetting about the 1800 emails it had already gotten through).
Great A&B testing, guys.
I think the source of confusion is that he calls his project "Knyle Style Sheets," whereas a more accurate name would be "Knyle markup for Preprocessed Style Sheets" (or Kml*SS).
Keep up the great work, btw! I'm pretty excited to move up to Node 0.6 (probably-statistically-insignificant regression on IO-write regardless)!
AWS doesn't provide a way to serve from S3 without the help of a CNAME redirect, which means that you're out of luck if you want to use the Jekyll+S3 setup with a naked domain name (naked, as in no "www" or "blog" subdomain). And it also means that you're going to have to get some other server (Google Apps can do it), to redirect your *.domain.com queries to www.domain.com. And then your users' DNS is running all over the place, incurring, in my opinion, unneeded delay.
What I took issue with was that you are internally inconsistent, yet claim to be "honest." Ha! Whatever it was that made you once say you WILL NEVER attempt to solicit business on Hacker News---well, obviously, you don't believe in that anymore.
1. Put your camera on continuous shoot. My Canon 20D could do 3 frames/second. My 7D can do 7 frames/second.
2. Make sure your shutter speed maxes out at 1/10th of a second or so. Blurry pics are totally fine. Try to keep it landscape, though. Fixing the portrait shots is a pain.
3. Hold down your shutter button a lot. Turn on AF and give your camera to other people and tell them to do the same.
4. Download your 5000+ pictures to your computer later.
5. Open up VirtualDub, and load in all the JPEGs, tell it to resize to 1/4, and set the framerate to 10 frames/second or so.
6. Layer over with some music. I recommend sorting by duration in iTunes to find something that is as long as your video.
a) I had to send if off to the refurb. center after about two months of use (and pay my own shipping).
b) I haven't seen much progress in the app except stability increases. With all that raw data, I can imagine tons of fun features, particularly social applications.
c) Their website's claim, "You pick the factors and Wakelytics shows how they affect your sleep," translates to "You tag your nights and we let you sort by those tags." This is typical of the lackluster analysis-web app that your sleep data gets uploaded to.
d) The app self-admittedly cannot analyze sleep periods of less than 3-4 hours, and in reality considers anything less than 5-6 hours too short to recognize or record. (There is no mention of this shortcoming/limitation anywhere on their website.) This makes it pretty much useless for polyphasic sleep. Or naps of any kind.
No big deal, though. $60 is not that much money. It's a nice effort, and a good idea, but just not a very satisfying execution.
That's a big "if." Big enough to lose interest.