What’s this? News about robot dogs comes out, and there’s no video of the bots busting a move on the dance floor? Nope — it looks like quadruped robots are finally going to work for real as “ground drones” are being deployed to patrol Cape Canaveral. Rather than the familiar and friendly Boston Dynamics “Big Dog” robot, the US Space Force went with Ghost Robotics Vision 60 Q-UGVs, or “quadruped unmanned ground vehicles.” The bots share the same basic layout as Big Dog but have a decidedly more robust appearance, and are somehow more sinister. The dogs are IP67-rated for all-weather use, and will be deployed for “damage assessments and patrols,” whatever that means. Although since this is the same dog that has had a gun mounted to it, we’d be careful not to stray too far from the tours at Kennedy Space Center.
In honor of our recently announced 2022 Cyberdeck Contest, we decided to do things a little differently for this week’s Hack Chat. Rather than pick just one host, we looked back through the archive and selected some of the most impressive builds we’ve seen and asked their creators if they’d like to take part in a freewheeling discussion about their creations and the nascent community surrounding these bespoke computing devices.
Despite conflicting time zones and at least one international vacation, we were able to put together an impressive panel to helm this special Cyberdeck Brainstorming Hack Chat:
So what did this accomplished group of cyberdeck builders have to talk about? Well, quite a bit. During a lively conversation, these creators not only swapped stories and details about their own builds, but answered questions from those looking for inspiration and guidance.
bootdsc’s radio-packed VirtuScope
The discussion immediately kicked off with what’s perhaps the most obvious question: why build a cyberdeck if we already have laptops and smartphones — mobile computing form factors which [Io Tenino] admits are likely as close to perfect as we can get with current technology. Most of the builders agreed that a big part of the appeal is artistic, as the design and construction of their personal deck allowed them to show off their creativity.
But what of productivity? Can these custom machines do more than look good on a shelf? There seemed to be consensus that it was difficult to compete with a standard laptop in terms of general purpose computing, but that a cyberdeck tailored to a specific use case could be a powerful tool.
For example, [bootdsc] built a high-power WiFi adapter as well as an RTL-SDR receiver and up-converter into the VirtuScope, while [Io Tenino] says the Joopyter’s integrated printer is occasionally used to run off a grocery list. [H3lix] also mentioned that the trend towards ever-thinner laptops has meant removing ports and expansion options which used to be taken for granted, a potentially frustrating situation for hardware hackers that a cyberdeck can alleviate.
Naturally, the Chat also covered more technical aspects of cyberdeck design. There was quite a bit of discussion about powering these custom machines, and whether or not internal batteries were even a necessary design consideration. In keeping with the survivalist theme, [cyzoonic] included 18650 cells and an integrated charger, while [Io Tenino] is content to use a standard USB battery bank. Ultimately, like most aspects of an individual’s cyberdeck, the answer largely depended on what the user personally wished to accomplish.
[Io Tenino]’s Joopyter comes from a decade that never existed.As you might expect with [Back7] in attendance, there were also several questions about the logistics of using a Pelican case as the enclosure for your build. Different techniques were discussed for mounting hardware within the case without compromising its integrity, such as gluing your fasteners to the inside of the case, or 3D printing an internal framework.
Others wondered if the protection provided by these cases was really necessary given the relatively easy life most of these machines will lead, especially given their considerable cost. Although to that end, we also saw some suggestions for alternative cases which provide a similar look and feel at a more hacker-friendly price point.
Though they are certainly popular, Pelican cases are just one option when planning your own build. Many chose to 3D print their own enclosures, and there’s even the argument to be made that the rise of desktop 3D printing has helped make cyberdeck construction more practical than it has been in the past. Others prefer to use the chassis of an old computer or other piece of consumer electronics as a backbone for their deck, which fits well with the cyberpunk piecemeal aesthetic. That said, the Chat seemed in agreement that care needed to be taken so as not to destroy a rare or valuable piece of vintage hardware in the process.
This Hack Chat was a great chance to get some behind the scenes info about these fantastic builds, but even if you didn’t have a specific question, it was an inspiring discussion to say the least. We’re willing to bet that the design for some of the cyberdecks that get entered into the contest will have been shaped, at least in part, due to this unique exchange of niche ideas and information. Special thanks to [bootdsc], [Back7], [H3lix], [a8ksh4], [Io Tenino], and [cyzoonic] for taking the time to share this glimpse into their fascinating community with us.
The Hack Chat is a weekly online chat session hosted by leading experts from all corners of the hardware hacking universe. It’s a great way for hackers connect in a fun and informal way, but if you can’t make it live, these overview posts as well as the transcripts posted to Hackaday.io make sure you don’t miss out.
This week, Editor-in-Chief Elliot Williams and Assignments Editor Kristina Panos convened in a secret location to say what we will about the choicest hacks of the past week. We kick things off by discussing the brand new Cyberdeck contest, which is the first of it’s type, but certainly won’t be the last. In other contest news, we recently announced the winners of the Hack it Back Challenge of the Hackaday Prize, which ran the gamut from bodysnatching builds to rad resto-mods and resto-recreations.
IBM’s Linkway, French edition. Très tubulaire, non?
Taking top honors in wow factor this week is [Stuff Made Here]’s jigsaw puzzle-solving robot. This monster can currently tackle small laser-cut puzzles, but is destined to solve an all-white 5000-piece nightmare once all the engineering pieces have come together.
Then we took a field trip to Zip Tie City, where the plastic’s green ♻ and the wiring’s pretty, admired volcano nuts from afar, and briefly considered the idea of a 3D printer with a heating zone of programmable length.
Finally, we take a look at a creatively destructive robot that’s akin to a useless machine, bloviate about books you should read, and dance around the topic of learning by playing.
So you may have gotten a Slack password reset prompt. Something like half a percent of Slack’s userbase had their password hash potentially exposed due to an odd bug. When sending shared invitation links, the password hash was sent to other members of the workspace. It’s a bit hard to work out how this exact problem happened, as password hashes shouldn’t ever be sent to users like this. My guess is that other users got a state update packet when the link was created, and a logic error in the code resulted in too much state information being sent.
The evidence suggests that the first person to catch the bug was a researcher who disclosed the problem mid-July. Slack seems to use a sane password policy, only storing hashed, salted passwords. That may sound like a breakfast recipe, but just means that when you type your password in to log in to slack, the password goes through a one-way cryptographic hash, and the results of the hash are stored. Salting is the addition of extra data, to make a precomputation attack impractical. Slack stated that even if this bug was used to capture these hashes, they cannot be used to directly authenticate as an affected user. The normal advice about turning on 2-factor authentication still applies, as an extra guard against misuse of leaked information. Continue reading “This Week In Security: Breaches, ÆPIC, SQUIP, And Symbols”→
Testing any kind of project in the real world is expensive. You have to haul people and equipment around, which costs money, and if you break anything, you have to pay for that too! Simulation tends to come first. Making mistakes in a simulation is much cheaper, and the lessons learned can later be verified in the real world. If you want to learn to fly a quadcopter, the best thing to do is get some time behind the sticks of a simulator before you even purchase anything with physical whirly blades.
Oddly enough, the same goes for AI. Microsoft built a simulation product to aid the development of artificial intelligence systems for drones by the name of Project AirSim. It aims to provide a comprehensive environment for the testing of drone AI systems, making development faster, cheaper, and more practical.
Long-time readers of Hackaday will know that we attend quite a few events, including summer hacker camps. Here in Europe this year there are two large events, the British Electromagnetic Field, and the Dutch MCH, or May Contain Hackers. These events are put together by volunteers from within the community, and as part of the MCH setup I noticed they needed drivers for their off-site logistics. I have a licence to drive medium-sized trucks in Europe so it seemed like a perfect fit. I traveled early on the first set-up day to the Dutch city of Utrecht, and found myself behind the wheel of a large Volkswagen box van. My brief career as a trucker had begun!
An Empty Field Of Dreams
The tents stand in isolation at the end of day one.
The Netherlands is a relatively small country and the MCH site at Zeewolde is roughly in its centre, so while the traffic could be heavy the distances weren’t large by American or even British standards. There were however a wide variety of loads waiting for me and my fellow driver, and a few obstacles such as the hottest days of the year and angry Dutch farmers blockading the roads. If you’re interested in the logistics behind a large hacker camp then our journeys provided an insight that maybe wandering around the field doesn’t quite deliver.
Arriving on site on the first day gives a perspective on how much of the infrastructure comes from specialist contractors and thus isn’t delivered by the hackers. Articulated trucks from the marquee company were disgorging the main tents, with their crews expertly assembling them in record time. The toilets and showers were arriving as self-contained hook lift container units, and yet more contractors were delivering fencing or tables and chairs. I can add the power infrastructure to this list, but due I’m told to delays at another event this wasn’t on site on the first day. Continue reading “What Goes Into A Hacker Camp”→
You’ve probably heard about Google Chromebooks. Like Android, Chrome OS is based on some variant of Linux, but it is targeted at the “cloud first” strategy so Chromebooks typically don’t have a huge amount of storage or compute power. If you have a real Chromebook, you can also use it to run certain other kinds of programs via virtualization. However, Google has recently pushed out Chrome OS Flex which is meant to install on a spare laptop you might happen to have hanging around. Seems attractive to take that only Windows 7 laptop and repurpose it to run Chrome OS, especially if you can run Linux apps on it. Unfortunately, Chrome OS Flex has a very different use case and I would only recommend installing it if you meet the exact use case it addresses.
The other option, of course, is to just install Linux on that old hardware. There are several distributions that are made for that purpose and, honestly, even most of the major distributions will work fine on older hardware with a little tweaking to turn off some of the more resource-costly features. That assumes you know how to install, tweak, and maintain Linux.
