First podcast of the new year! Editors Elliot Williams and Mike Szczys look back on the most interesting hacks and can’t-miss articles from the past week (or so). Highlights include abusing IPv6 addresses, underclocking WiFi, taking Wii out of the livingroom, scratch built microphones, computer prophecy coming true, and the end of an automotive era. Full show notes below.
This week, Hackaday Contributor Bob Baddeley came on the show to discuss developments in facial recognition technology and its use in the wild.
Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!
Direct download (60 MB or so.)
Episode 1 Show Notes:
We’re calling this Episode 1 because we zero-index… the 2018 Year-in-Review Podcast is episode 0
New This Week:
- Elliot is back from 35c3 where he hosted the Hackaday Assembly and had way too much fun.
- Talk on Bluetooth bug seeking software
- Talk on DOS viruses and pranks
- Talk on Drivers written in high-level languages
- Circuit Sculpture Contest finished strong. Take a look at all the entries
- Random example: 555 Spider
- Random example: Freeform Peacock
Interesting Hacks of the Week:
- DIY Ribbon Element Upgrades A Studio Microphone
- Underclocking the ESP8266 Leads To WiFi Weirdness
- IPv6 Christmas Display Uses 75 Internets Worth Of Addresses
- Pokemon Cries and How They Work
- A Practical Portable Wii Emerges From the Memes
- Preserving Floppy Disks Via Logic Analyser
- Portable Pi Teensy Thumboard
- Making An Ultrasonic Cutter For Post Processing Tiny 3D Prints
- An Electronic Love Letter to the Wind
- The Very Slow Movie Player Does It With E Ink
Can’t-Miss Articles:
- Retrotechtacular: The Mother Of All Demos, 50 Years On
- Goodbye Chevy Volt The Perfect Car For A Future That Never Was
- Irene Joliot Curie And Artificial Radioactivity
- Your Face Is Going Places You May Not Like
Errata
- 15:00 — Mike says there is enough IPv6 address space for 2128 of these displays. That number is actually just the size of the address space. There’s enough room in IPv6 to have 1027 of these displays. Regarding the actual size of the display: “the total number of IPv6 addresses used is 160x120x224, which is 75 times larger than all possible IPv4 addresses! “
- 24:30 — It’s a “This old Tony” video (not “My old Tony”)
- 43:50 — Mike misspoke when referencing number of passengers through Shanghai airport, saying seventy-thousand instead of seventy-million. The actual example is as follows: “70,000,000 people flow through Shanghai’s airport per year. 99.5% accuracy means nearly 1,000 false identifications per day.”
Awesome!!! Congrats on the first episode in a zero indexed array of episodes!
Thanks! If anyone has constructive feedback, lay it on us. As you can tell form the title, we’re figuring this all out as we go, but having a ton of fun doing so!
+1 for Mike showing up at 36c3 :)
Great podcast, looking forward to this series!
I suggest doing a video version, if appropriate. Nothing fancy. Just two guys at a bench works. Reactions and incessant hand-waving sometimes actually add to the entertainment value. :)
I think that would be mostly 2 web cam video feeds as they live on different continents, not sure how much that would add :)
I personally enjoy podcasts over videos for this kind of content, nothing I can potentially miss by not watching the video and only listening.
I think if we did that we’d need to splice in images of the stuff we’re talking about and then you descend into editing madness ;-)
What we should do is video episodes when Elliot and I are actually in the same place for the podcast. Supercon for sure… maybe if I can figure out how to get to CCCamp this August.
If there’s nothing visual for us to demo, it’s really just watching Mike and I videoconference. How much fun is that? Or rather, how much _additional_ fun?
Because we have been talking about doing a weekly video series for ages, and never doing it. The work involved in doing sound _and_ visuals is somehow much more than 2X the hassle of just doing sound, so the visuals have to be worth it. If we’re not walking you through hacks on our desk, there’s just not that much to gain.
The advantage of a podcast is that you can listen virtually anywhere, without having to look at a screen. If you’re looking at a screen, you should probably be reading Hackaday anyway. :) (What, work?!?)
Anyway, that’s our logic. We’re really stoked to be able to highlight some of our favorite posts/articles on Hackaday, because it _is_ hard to keep up with everything these days and we don’t want you to miss anything important. We hope that adding an extra medium help you find the good stuff.
There’s plenty of series on YouTube that are just the audio of the podcast playing with some random visualizations and such in the video. It’s not really meant to be watched exactly, it’s basically just using YouTube as an additional platform to get the podcast out there. If you’re already checking YouTube daily and have subscriptions there, it’s nice to just listen to the podcast through that than requiring a separate app.
Pictures that go along with the hack being talked about would be ideal, but definitely not required. Most people will probably just have it running in a different tab while they do something else.
I’m already RSS’ed to the HaD feed. Should I add the podcast’s RSS, or will podcasts continue to get posted on the regular feed? Thanks!
Just attempted to migrate to dual stack (IPV4/IPV6). IPV6 is hugely more complex. The autoconfig part makes life interesting (my router announces a subnet of the address space to my nets, which I want a dhcpv6 service handles address delegation and Dynamic DNS). Unfortunately I ran into a router bug that hosed several of my Linux boxes. Not sure of my route forward.
On the ‘read the magnetic flux’, there are several kits that allow us to read the magnetic flux, interpret, and store the disks image. We need it to save vintage floppy disks along with our vintage computers. It will even read (and write – I think) Apple II disks.
Audiophile note: I just streamed the podcast, and noticed that the stream has significantly more compression artifacts than the downloadable MP3. If the hissing hurts your golden ears (it does mine, frankly) then go with the direct download. It’s only 45 megs…
I checked the downloaded version, and it matches the file I uploaded bit-for-bit, but whatever they’re streaming is significantly lower quality. Soundcloud suggests uploading a lossless file, which we’ll do next time, but I’m not convinced that will solve the problem.
If anyone knows a workaround, we’d be glad to hear it!
(Oh yeah — and I panned Mike and me a bit hard this time. I’ll dial that back next time. Apologies to the monaural out there.)