The last one likely matters the most, at least in my case. Ambitious ideas take more time than just product development/implementation. Marketing and business development run on much lengthier schedules. At half a year in on savings, I'm being pulled away from full-time on my startup back into contract work, where I'm constantly encouraged to just go full-time instead with these companies (mostly founding-stage startups with funding). Meanwhile, my entrepreneur friends who come from exceptionally wealthy backgrounds have no such constraints or risk of going homeless if their startup doesn't get funding or start making revenue. I'm not sure if I'll be able to make rent next month, short of a loan, unless I get a contract invoice paid in full within two weeks. I'll be just fine, but that fear of not making it on the basics is not weightless. I suspect I'll be looked at differently when it shows that it took me N months to get to X revenue, instead of 0.25N, as a result of just needing to survive.
As someone who tried to run such a service years ago, I mostly agree. Even the very best stories written through this method were troublingly self-inconsistent. On the other hand, they were often hilarious a well. We published a few anthologies of short stories written with this method here: http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Dap...
The experience for writers was surprisingly rewarding, but the end result was not for mass consumption. Still, as a writing tool, it showed great value.
Think I just found a way using canvas with a semi transparent element inside of it, then overlaying that on each square, grabbing the computed/resulting color of the canvas to decipher which block is what. S O O N
I spent an unfortunate chunk of time trying to auto-click all the red square via jquery in chrome console. After a lot of reading and experimenting, I can verify that the exploit is thoroughly addressed (so far), and I cannot achieve my goal because of it :(.
The most promising workaround would be to find a JS screenshot tool that doesn't rely on the DOM, and then run some client-side image analysis to get the index values of the red squares, and then go from there to click the things. Well played, exploit fixers, well played.
If someone built one of these mobile webapp frameworks using famo.us, but exposed it to the developer as something much less alien vs actual famo.us... I would be so happy.
I winced, because it seemed like the kind of pep-talk speech you might have to hear over and over again when you get called into a very high-level meeting without any discussion about execution, in the middle of a workday where you have code to build and ship instead. There's little here that appeals to my actual intelligence or abilities that screams "challenge". We can say we're in it for the social impact and "meaning", but if there's no succinctly-stated technical challenge to face and succeed over, there's no food on that fishing hook.
Glad to see this out. I've been waiting on famo.us to become available for quite a while now. Exciting stuff.
Now, where is the documentation? The readme from the repo points to a docs folder that does not exist, and links to the online versions of documentation lead me to login-only pages... registering only puts me in line for access.
Have you read the issue? The problem is that the current way things are done requires manual merge requests because of merge conflicts resulting from the updated userlist array. The github api method is 1:1 with the requirements of joining the community and leaves no room for human error (unless the person in charge of pull requests does not standardize their own process for automatic merges).
> Really? Yeah, I get that it not being a microtransaction-pile-of-garbage probably helped, but did you play it? Seriously, nobody at the beginning could have thought it was good. After the buzz, quality isn't relevant.
I learned about it through a girl I'm currently seeing. She is very far removed from the whole tech scene. Her cousin told her to try it, and then she told me to try it and impress her by getting a high score. So I tried it, enjoyed it (masochism involved here), and the very next day my roommate asked me if I knew of the game. We've been competing with each other for high scores ever since.
But never implemented / merged. Surprised the powers-that-be are resisting the most elegant solution. Then again, I came up with it, so I remain bitter and biased :)
The step of just adding yourself to the userlist seems ill-conceived. Automatic merges are just going to overwrite the last person added unless manually merged. Can I propose this just use github for authentication, and only allow those on the contributors list (http://developer.github.com/v3/repos/#list-contributors) to successfully log in?
Agreed. Also, this looks way more like a case where the author mis-structured his data for his intended use case, and is blaming the tool instead of the skill level used to implement it. Nesting deeper than one level in a document is rarely going to result in sufficient query capability with respect to the nested items. Even MySQL can't nest rows inside other rows, which is what he seems to have wanted. Maybe he chose MongoDB because he wasn't ready to think around the architecting issues that an SQL-based database would require, which happen to be, although not immediately obvious, similar to those in Mongo.