A few years ago, [Mike] heard about orthotic devices for people in wheelchairs that make it easier to them to move their arms. His daughter had the opportunity to demo one of these devices, and the results with the device were good. The fights with the insurance company were not so good, but this really was a device that could be made on a 3D printer with a few rubber bands, after all. Thus, [Mike] invented 3D printed antigravity arm floaties.
The name basically tells the story — these antigravity arm floaties work well to counter the pull of gravity for individuals with low muscle tone. [Mike]’s daughter found the professional, official, not-covered-by-insurance version useful, so [Mike] decided to build his own. There’s really not much to it – it’s just a few 3D printed parts attached to a wheelchair with a few rubber bands giving the mechanical linkages some resistance.
In the true hacker spirit, [Mike] took the basic idea of these spring-loaded arm floaties and put a new twist on it. He’s using a chain as the mechanism that allows freedom of movement in the XY plane. This makes the device slightly better, and is by every account an improvement on the commercial version. That’s what you get when you can iterate quickly with a 3D printer, making this project an excellent example of what we’re looking for in the Assistive Technology portion of the Hackaday Prize.
The de facto standard for Raspberry Pi operating systems is Raspbian–a Debian based distribution specifically for the diminutive computer. Of course, you have multiple choices and there might not be one best choice for every situation. It did catch our eye, however, that the RaspEX project released a workable Ubunutu 16.10 release for the Raspberry Pi 2 and 3.
RaspEX is a full Linux Desktop system with LXDE (a lightweight desktop environment) and many other useful programs. Firefox, Samba, and VNC4Server are present. You can use the Ubuntu repositories to install anything else you want. The system uses kernel 4.4.21. You can see a review of a much older version of RaspEX in the video below.
Around the beginning of October, news of an IoT botnet came forward, turning IP webcams around the world into a DDoS machine. Rapidity Networks took an interest in this worm, and set out a few honeypots in the hopes of discovering what makes it tick.
Looking closely at the data, there was evidence of a second botnet that was significantly more sophisticated. Right now, they’re calling this worm Hajime.
In what might be one of the coolest applications of laser cutting, joinery, puzzles, writing, and bookbinding, [Brady Whitney] has created the Codex Silenda — a literal puzzle book of magnificent proportions.
[Whitney] had originally conceived the idea of the Codex for his senior thesis research project at Iowa State University, and the result is something for almost everyone. On each of the Codex’s five pages lies a mechanical puzzle that must be solved to progress to the next, while an accompanying text weaves a story as you do so. These intricate pages were designed in SolidWorks and painstakingly assembled from laser cut wood. Breaking the fourth wall of storytelling by engaging the reader directly in uncovering the book’s mysteries is a unique feat, and it looks gorgeous to boot.
Every time we hear about one walled-garden protocol not speaking to another, and the resulting configuration mayhem that ensues, we can’t help think that [Mike] was right: home automation has a software problem. But that’s putting the blame on the technology. (We’re sure that [Mark] could have made the kettle work if he’d just applied a little Wireshark.)
There’s another mismatch here — one of expectations about the users. A water kettle is an object that should be usable by grandmothers, and a complex networked device is clearly aimed at techies and early adopters. Combining the two is asking for trouble. Non-functioning IoT devices are the blinking 12:00 of our generation.
What do you think? Where’s the blame here? Poor design, bad software stack, stupid users, or failure of mega-corps to integrate their systems together? More importantly, how could we make it better?
Looking at the ingredient list of some popular processed foods will produce a puzzled look on the typical hacker’s face. Tricalcium phosphate, thiamine mononitrate, zinc proteinate, pyridoxine hydrocloride… just who the hell comes up with these names anyway? It turns out that there is a method to the madness of chemical name structures. Some of them are well known, such as sodium chloride (NaCl) and hydrogen peroxide (H2O2). Others… not so much. In the early years of chemistry, chemical substances were named after their appearance, affects and uses. Baking soda, laughing gas and formic acid (formic is Latin for ant, and responsible for the sting in an ant bite) to name a few. As more and more chemical substances were discovered over time, a more structured naming convention was needed. Today, the above are known as sodium bicarbonate (NaHCO3), nitrous oxide (N2O) and a type of carboxylic acid (R – COOH, think of the “R” as a variable) respectively.
In today’s article, we’re going to talk about this naming structure, so that next time you admire the back of soup can, you won’t look so puzzled. We’ll also cover several common definitions that every novice biohacker should be familiar with as well.
Like all our meetups, we’ve gathered some of the neatest technologists to spill the beans on what they’re doing and how they’re doing it. Madison Maxey, founder of Loomia and designer of soft, blinky circuits will be there. Dr. Ellen Jorgensen, co-founder and executive director of Genspace, the citizen science biotech ‘hackerspace’ in the heart of New York will be there too. Kari Love & Matthew Borgatti of Super-Releaser, most famous for their super cute pneumatic soft robots will also be there. It’s still up in the air if we’ll be racing these robots. Of course there will also be opportunities for you to present a lightning talk at the meetup.