25 karma · joined June 13, 2016
toaster.cc
[ my public key: https://keybase.io/angusp; my proof: https://keybase.io/angusp/sigs/Mc3XMM_lxpNHCsQ03WGbbLdW8jIpgSsjbOjm3yN7uuk ]
Pretty-much true, but I remember a funny story from Dropbox where their websocket service couldn't come back up after a crash because their normal users trying to re-open super long lived connections all at once was well-beyond the capacity of the system
Surely to be racist, some degree of malice or ignorance is required - face recognition from visible light flat imagery will always struggle with low-contrast images, which is sadly what you get from a poorly lit black person's face. It's neither intentionally racist nor inadvertantly - there is just not the same amount if information available
- /r/Libertarian
I am at least relieved that this doesn't appear to be an Idea police AI nor a particularly liberally biased classifier
How so? C is low level, so to be secure you must be fully aware of the behaviours and side effects of what you're doing. In another, perhaps higher level language, sure, there may be less of these gotchas but to be properly secure you need a similar amount of knowledge about background behaviour.
That being said, I'm happy the web isn't still just plaintext or minimally styleable
By side-side motion I'm guessing you mean a tipping force - and the the answer would be that he's pretty hard to shove over, at the limit of his lean he's stable, 10 degrees tilt and he'll fall. From fully upright, you need a bit more of a shove - having just pushed one over. Sandy says they can tip themselves if you wobble fast enough.
We're guessing you were thinking of something like this --> http://i.imgur.com/Cmmwu5A.jpg
Still very alpha, specs currently are STM32F446RE (ARM M4), ESP8266 (WiFi, for control from a computer, phone...) and an accelerometer on-board. 9 channel servo control with current sensing, JTAG/USB for programming, i2c and serial interface for talking to it from an arduino, raspberry pi or other microcontroller. We're not expecting to have much GPIO free, and as I said, the firmware it's running is kinda complex, so we're not expecting most people to change it.
We're planning (read: really want to but might not have time to do everything initially) to target a wide range of programming environments, with Scratch as a really basic level; This would make Marty a kinda smart toy, being able to do logo-like things but not much more. The more complex approaches will of course allow a lot more to be done with Marty.
The control board itself is going to have a fair amount of smarts, with an ARM cortex M4 - but that'll be running our firmware, so playing with that would require somewhat in-depth mbed experience. We'd expect most people to use the i2c or serial interface to hack with Marty, by writing their own code on a microcontroller, RasPi or BeagleBone, and packing that in with our board. As it's all open source, adding to the firmware will be possible, just not the most beginner friendly thing.
As for the WiFi functionality, we're looking at the ESP8266, (not final but unlikely to change) and building a C++, Python and ROS (http://ros.org, serious robotics stuff, very cool) set of APIs to use with Marty.
tl:dr; Two types of control, _standalone_ with an added raspi/arduino/other microcontroller, and _wifi-connected_ to a program running on a computer (scratch, python, C++...)