Hackaday Berlin: Final Schedule, Last Call For Tickets, And More

Hackaday Berlin is just about a week away, and we’ve just put the finishing touches on our preparations. And that includes a snazzy landing page, the full schedule, details on the Friday night meetup, and more.

We’ll be meeting up Friday the 24th at 19:00 at DogTap / Brew Dog, Im Marienpark 23 for an ice breaker. This is a great time to unwind from your travels, catch up with old friends, and start getting into gear for the days ahead.

Saturday the 25th starts off at 9:30, you’ll get your badge and schwag bag, and have some breakfast. Then it’s talks, workshops, lightning talks, badge hacking, food and music until the wee hours.

Sunday morning starts up again at 11:00, but it’ll feel like 10:00 due to Daylight Savings time. We’ll have brunch, show off whatever cool hacks you’ve brought along, and just generally chill out into the afternoon. Some people are planning to go sightseeing around Berlin afterwards, so if that’s your thing, you’re in good company.

For any chat related to Hackaday Berlin, we have a not-so-cryptically named #Berlin channel over on the Hackaday Discord server.

There are still a few tickets left, so you procrastinators, now’s your time to snap them up. All the rest of you, put those finishing touches on whatever you’re bringing with you, and we’ll see you next week!

(Oh, and press the play button on the landing page.)

Hackaday Berlin: The Badge, Workshops, And Lightning Talks

Hackaday Berlin is just under two weeks away, and we’ve got news times three! If you don’t already have tickets, there are still a few left, so grab them while they’re hot. We’ll be rolling out the final full schedule soon, but definitely plan on attending a pre-party Friday night the 24th, followed by a solid 14-hour day of hacking, talks, and music on Saturday the 25th, and then a mellow Bring-a-Hack brunch with impromptu demos, workshops, and whatever else on Sunday from 10:30 until 14:00.

The Badge Round Two

Many Europeans weren’t able to make the flight to Supercon, so here’s your chance to get hands on Voja Antonic’s superb down-to-the-metal computer trainer-slash-retrocomputer on this side of the Atlantic. It’s been re-skinned for Berlin, with a couple hardware tweaks because nobody can leave a board revision alone, but it’s 100% compatible with the badge that took Supercon 2022 by storm.

If you want to read more about it, you should. We loved it, and so did the crowd. One of the coolest badge hardware hacks was a “punchcard” reader, but there was also a lot of work on the software side as well, and we got pull requests for most of the cool demos. If you’re coming, and if you’d like to start your badge hacking a bit early, you could start your research now.

We’ll have a Badge Hacking Ceremony Saturday night, so you can show off whatever you made. It’s lots of fun. Continue reading “Hackaday Berlin: The Badge, Workshops, And Lightning Talks”

Computers For Fun

The last couple years have seen an incredible flourishing of the cyberdeck scene, and probably for about as many reasons as there are individual ’deck designs. Some people get really into the prop-making, some into scrapping old tech or reusing a particularly appealing case, and others simply into the customization possibilities. That’s awesome, and they’re all different motivations for making a computer that’s truly your own.

But I really like the motivation and sentiment behind [Andreas Eriksen]’s PotatoP. (Assuming that his real motivation isn’t all the bad potato puns.) This is a small microcomputer that’s built on a commonly available microcontroller, so it’s not a particularly powerful beast – hence the “potato”. But what makes up for that in my mind is that it’s running a rudimentary bare-metal OS of his own writing. It’s like he’s taken the cyberdeck’s DIY aesthetic into the software as well.

What I like most about the spirit of the project is the idea of a long-term project that’s also a constant companion. Once you get past a terminal and an interpreter – [Andreas] is using LISP for both – everything else consists of small projects that you can check off one by one, that maybe don’t take forever, and that are limited in complexity by the hardware you’re working on. A simple text editor, some graphics primitives, maybe a sound subsystem. A way to read and write files in flash. I don’t love LISP personally, but I love that it brings interactivity and independence from an external compiler, making the it possible to develop the system on the system, pulling itself up by its own bootstraps.

Pretty soon, you could have something capable, and completely DIY. But it doesn’t need to be done all at once either. With a light enough computer, and a good basic foundation, you could keep it in your backpack and play “OS development” whenever you’ve got the free time. A DIY play OS for a sandbox computing platform: what more could a nerd want?

New Raspberry Pi Camera With Global Shutter

Raspberry Pi has just introduced a new camera module in the high-quality camera format. For the same $50 price you would shell out for the HQ camera, you get roughly eight times fewer pixels. But this is a global shutter camera, and if you need a global shutter, there’s just no substitute. That’s a big deal for the Raspberry Pi ecosystem.

Global vs Rolling

Most cameras out there today use CMOS sensors in rolling shutter mode. That means that the sensor starts in the upper left corner and rasters along, reading out exposure values from each row before moving down to the next row, and then starting up at the top again. The benefit is simpler CMOS design, but the downside is that none of the pixels are exposed or read at the same instant.

Continue reading “New Raspberry Pi Camera With Global Shutter”

Hackaday Berlin: First Round Of Talks

We’re super excited to announce the first round of speakers for Hackaday Berlin!  We’re set to convene on Friday night, March 24th for an evening warm up before the main show on Saturday, March 25. Featuring the triumphant return of Voja’s 4-bit badge, a crew of awesome speakers, lightning talks, workshops, music, food, badge hacking, and all the best of the Hackaday community, this will be a day to remember. And then we’ll chill out Sunday morning with a Bring-a-Hack brunch.

So without further ado: the first round of speakers!

Jiska Classen
Hacking Closed-Source: Reverse Engineering Real-World Products

Closed-source software is prevalent in our everyday lives, limiting our ability to understand how it works, which privacy implication it poses to the processed data, and addressing potential issues in time. Despite the growth of open-source movements, users often have no choice but to rely on closed-source solutions, e.g., for medical devices and IoT products. We’ll discuss key techniques to help you get started with reverse engineering. Hacking your own devices can be challenging, bricking a device is not uncommon, but so is celebrating the moments of a revived and modified device.

James Bruton
Being a Full-Time YouTuber

 

YouTube is my full-time job and has been for four years. I create STEM education content using everything from 3D printing, CNC, Welding, to Microcontrollers and Coding. Find out how I got started, how I make money, what goes on in the background, and what my future plans are. I’ll tell you how you can do it too!

Trammell Hudson
Hacking your dishwasher for cloudless appliances

Why does your dishwasher, laundry or coffee-pot need to talk to the cloud? In this presentation, Trammell Hudson shows how he reverse engineered the encrypted connections between Home Connect appliances and the Bosch-Siemens Cloud servers, and how you can control your own appliances with your self-hosted MQTT home automation system by extracting the devices’ authentication keys and connecting to their local websocket ports. No cloud required!

Bleeptrack
Oops, my project ended up in a museum

Parameterized design allows for the adaption of projects to different needs but can also change the aesthetic to a persons liking. Bleeptrack will walk you through the creation process and tools of her generative projects, talk about her experience manufacturing unique pieces and explains how to cope when your freshly finished project gets locked up in an art exhibition for a few months.

Ali Shtarbanov
Creating Hardware Development Platforms for Real-World Impact: FlowIO Platform

What does it really take do create and deploy a development platform for real-world impact? Why do we need development platforms and how can they democratize emerging fields and accelerate innovation? Why do most platform attempts fail and only very few succeed in terms of impact? I will discuss the key characteristics that any platform technology must have in order for it to be able to useful for diverse users. FlowIO was the winner of the 2021 Hackaday Grand Prize as well as over a dozen other engineering, research, and design awards.

Come join us!

You!

Whatever you’re up to.

We want you to bring your current project, world-changing ideas, or simply fun hacks for a 7-minute lightning talk!

 

ChatGPT, Bing, And The Upcoming Security Apocalypse

Most security professionals will tell you that it’s a lot easier to attack code systems than it is to defend them, and that this is especially true for large systems. The white hat’s job is to secure each and every point of contact, while the black hat’s goal is to find just one that’s insecure.

Whether black hat or white hat, it also helps a lot to know how the system works and exactly what it’s doing. When you’ve got the source code, either because it’s open-source, or because you’re working inside the company that makes the software, you’ve got a huge advantage both in finding bugs and in fixing them. In the case of closed-source software, the white hats arguably have the offsetting advantage that they at least can see the source code, and peek inside the black box, while the attackers cannot.

Still, if you look at the number of security issues raised weekly, it’s clear that even in the case of closed-source software, where the defenders should have the largest advantage, that offense is a lot easier than defense.

So now put yourself in the shoes of the poor folks who are going to try to secure large language models like ChatGPT, the new Bing, or Google’s soon-to-be-released Bard. They don’t understand their machines. Of course they know how the work inside, in the sense of cross multiplying tensors and updating weights based on training sets and so on. But because the billions of internal parameters interact in incomprehensible ways, almost all researchers refer to large language models’ inner workings as a black box.

And they haven’t even begun to consider security yet. They’re still worried about how to construct obscure background prompts that prevent their machines from spewing hate speech or pornographic novels. But as soon as the machines start doing something more interesting than just providing you plain text, the black hats will take notice, and someone will have to figure out defense.

Indeed, this week, we saw the first real shot across the bow: a hack to make Bing direct users to arbitrary (bad) webpages. The Bing hack requires the user to already be on a compromised website, so it’s maybe not very threatening, but it points out a possible real security difference between Bing and ChatGPT: Bing gives you links to follow, and that makes it a juicy target.

We’re right on the edge of a new security landscape, because even the white hats are facing a black box in the AI. So far, what ChatGPT and Codex and other large language models are doing is trivially secure – putting out plain text – but Bing is taking the first dangerous steps into doing something more useful, both for users and black hats. Given the ease with which people have undone OpenAI’s attempts to keep ChatGPT in its comfort zone, my guess is that the white hats will have their hands full, and the black-box nature of the model deprives them of their best hope. Buckle your seatbelts.

Simultaneous Invention, All The Time?

As Tom quipped on the podcast this week, if you have an idea for a program you’d like to write, all you have to do is look around on GitHub and you’ll find it already coded up for you. (Or StackOverflow, or…) And that’s probably pretty close to true, at least for really trivial bits of code. But it hasn’t always been thus.

I was in college in the mid 90s, and we had a lab of networked workstations that the physics majors could use. That’s where I learned Unix, and where I had the idea for the simplest program ever. It took the background screen color, in the days before wallpapers, and slowly random-walked it around in RGB space. This was set to be slow enough that anyone watching it intently wouldn’t notice, but fast enough that others occasionally walking by my terminal would see a different color every time. I assure you, dear reader, this was the very height of wit at the time.

With the late 90s came the World Wide Web and the search engine, and the world got a lot smaller. For some reason, I was looking for how to set the X terminal background color again, this time searching the Internet instead of reading up in a reference book, and I stumbled on someone who wrote nearly exactly the same random-walk background color changer. My jaw dropped! I had found my long-lost identical twin brother! Of course, I e-mailed him to let him know. He was stoked, and we shot a couple funny e-mails back and forth riffing on the bizarre coincidence, and that was that.

Can you imagine this taking place today? It’s almost boringly obvious that if you search hard enough you’ll find another monkey on another typewriter writing exactly the same sentence as you. It doesn’t even bear mentioning. Heck, that’s the fundamental principle behind Codex / CoPilot – the code that you want to write has been already written so many times that it will emerge as the most statistically likely response from a giant pattern-matching, word-word completion neural net model.

Indeed, stop me if you’ve read this before.