Read the article please - quote:
“Facebook asked me to pass this on to you. They require it of all visitors to their facilities. It only applies to things that you might accidentally stumble upon while you are there and covers nothing discussed during our news conference. Please either bring a signed copy or be ready to sign upon arrival.”
Which makes sense, imo, given the open work environment at Facebook.
regexp != regular expression like xyzzyz said. This script uses backreferences which give regex's more "computing power" than regular expressions actually have, but remove the guaranteed runtime of an O(n) regular expression.
Quote:
One common regular expression extension that does provide additional power is called backreferences. A backreference like \1 or \2 matches the string matched by a previous parenthesized expression, and only that string: (cat|dog)\1 matches catcat and dogdog but not catdog nor dogcat. As far as the theoretical term is concerned, regular expressions with backreferences are not regular expressions. The power that backreferences add comes at great cost: in the worst case, the best known implementations require exponential search algorithms, like the one Perl uses. Perl (and the other languages) could not now remove backreference support, of course, but they could employ much faster algorithms when presented with regular expressions that don't have backreferences, like the ones considered above.
Random thought: If the bitcoin currency fails, would people turn their bitcoin mining rigs into hash cracking rigs? I wonder if it's more economical to be mining bitcoin or to crack hashes.
Try the demo ui at:
http://fromjeffrey.com/pc/
and see if it works better for you - supports live preview, move, rotate, and scale.
Originally we were planning Facebook integration so that we'd have one click image uploads and tagging to Facebook, but the FB API has been in flux lately so it's taken longer than expected. We're pretty happy with what we have over two nights of hacking. =]
This is 110% an alpha build and the UI def. has to be more intuitive (like rotate is based on mouse drag in X-axis, but how does the user know that??)
Uses processingjs to do the heavy lifting with PHP backend - still getting out of memory errors with large pictures, so try to start with something reasonable (IE: not 5 megapixels dimensions 2000px and smaller recommended)
The problem is probably that in the url:
src="../photos%2FProfile%20Pictures%2F432293561980.jpg"
some browsers will convert %2F to "/", whereas others don't
Going back to the barcoding of trees, how would you do it? I assume you'd use some sort of SNP identification or specific DNA primers, but then you've just got a bunch of DNA in a tube.
The typical way of visualizing DNA is using an electrophoresis gel - most of the components are cheap/easy to obtain (agarose, electrodes, power supply, buffer), but how would you visualize your gel? Typical ethidium bromide stains are probably out of the question, given that ethidium bromide is so carcinogenic - most people probably don't have access to ethidium bromide. Maybe use a safer stain? (googling seems to point to invitrogen's SYBR Safe DNA stain as a possibility).
Then again, you could just use a UV spec to measure concentration, but how many people have a UV spec?
Looking forward to your results! In the future I think it would be nice to have open source enzyme starters (kind of like brewers/bakers yeast starter kits?) so that people could just grow+purify their own enzymes. (after the open source centrifuge that is =P )