Hackaday Columns

4773 Articles

This excellent content from the Hackaday writing crew highlights recurring topics and popular series like Linux-Fu, 3D-Printering, Hackaday Links, This Week in Security, Inputs of Interest, Profiles in Science, Retrotechtacular, Ask Hackaday, Teardowns, Reviews, and many more.

If You Can’t Say Anything Nice

October 12, 2024 by 398 Comments

[Editor’s Note: After we posted this, we got hit by a comment-report attack, and about 1,000 (!) comments across the whole site got sent back into the moderation queue on Saturday. We’ve since re-instated them all, but that took a lot of work.

About halfway down the comments in this article, the majority of comments are “hey, why did you delete this?”  We didn’t, and they should be all good now. We debated removing the “try deleting this!” comments, but since we didn’t delete them in the first place, we thought we should just leave them. It makes a royal mess of any discussion, and created a lot more heat than light, which is unfortunate.]

You know what your mom would say, right? This week, we got an above average number of useless negative comments. A project was described as looking like a “turd” – for the record I love the hacker’s angular and futuristic designs, but it doesn’t have to be to your taste. Then someone else is like “you don’t even need a computer case.” Another commenter informed us that he doesn’t like to watch videos for the thirtieth time. (Yawn!)

What all of these comments have in common is that they’re negative, low value, non-constructive, and frankly have no place on Hackaday. The vast majority are just kind of Eeyorey complaining about how someone else is enjoying a chocolate ice cream, and the commenter prefers strawberry. But then some of them turn nasty. Why? If someone makes a project that you don’t like, they didn’t do it to offend you. Just move on quietly to one you do like. We publish a hack every three hours like a rubidium clockwork, with a couple of original content pieces scattered in-between on weekdays.

And don’t get us wrong: we love comments that help improve a project. There’s a not-so-fine line between “why didn’t you design it with trusses to better hold the load?” and “why did you paint it black, because blue is the superior color”. You know what we mean. Constructive criticism, good. Pointless criticism, bad.

It was to the point that we were discussing just shutting down the comments entirely. But then we got gems! [Maya Posch]’s fantastic explainer about the Lagrange points had an error: one of the satellites that Wikipedia said was at an earth-moon Lagrange point is actually in normal orbit around the moon. It only used the Lagrange point as a temporary transit orbit. Says who? One of the science instrument leads on the space vehicle in question. Now that is a high-value comment, both because it corrects a mistake and enlightens us all, but also because it shows who is reading Hackaday!

Or take [Al Williams]’s article on mold-making a cement “paper” airplane. It was a cool technique, but the commenters latched onto his assertion that you couldn’t fly a cement plane, and the discussions that ensued are awesome. Part of me wanted to remind folks about the nice mold-making technique on display, but it was such a joy to go down that odd rabbit hole, I forgive you all!

We have an official “be nice” policy about the comments, and that extends fairly broadly. We really don’t want to hear what you don’t like about someone’s project or the way they presented it, because it brings down the people out there who are doing the hard work of posting their hacks. And hackers have the highest priority on Hackaday.

This article is part of the Hackaday.com newsletter, delivered every seven days for each of the last 200+ weeks. It also includes our favorite articles from the last seven days that you can see on the web version of the newsletter. Want this type of article to hit your inbox every Friday morning? You should sign up!

Hackaday Podcast Episode 292: Stainless Steel Benchies, Lego Turing Machines, And A Digital Camera Made Of Pure DIY

October 11, 2024 by No comments

Here we are in October, improbably enough, and while the leaves start to fall as the goblins begin to gather, Elliot and Dan took a break from the madness to talk about all the wonderful hacks that graced our pages this week. If there was a theme this week, it was long-term projects, like the multiple years one hacker spent going down dead ends in the quest for DIY metal 3D printing. Not to be outdone, another hacker spent seven years building a mirrorless digital camera that looks like a commercial product. And getting a solderless PCB to do the blinkenlight thing took a long time too.

Looking to eliminate stringing in your 3D prints? Then you’ll want to avoid the “pause and attach” approach, which intentionally creates strings in your prints. Wondering if you can 3D print bearings? You can, but you probably shouldn’t unless you have a particular use in mind. And what happens when you have an infinitely large supply of Lego? Why, you build a Turing machine on steroids, of course.

Finally, we take a look at this week’s “Can’t-Miss” articles with a look into plastic recycling and why we can’t have nice things yet, and we take a trip out into orbit and examine the ins and outs of Lagrange points.

And a little mea culpa from the editing desk: Sorry the podcast is coming out late this week. Audacity ate my files. If you’re ever in a similar circumstance, you can probably halfway save your bacon with audacity-project-tools. Ask me how I know.

 

Where to Follow Hackaday Podcast

Places to follow Hackaday podcasts:

Download the zero-calorie MP3.

Continue reading “Hackaday Podcast Episode 292: Stainless Steel Benchies, Lego Turing Machines, And A Digital Camera Made Of Pure DIY” →

This Week In Security: The Internet Archive, Glitching With A Lighter, And Firefox In-the-wild

October 11, 2024 by 7 Comments

The Internet Archive has been hacked. This is an ongoing story, but it looks like this started at least as early as September 28, while the site itself was showing a creative message on October 9th, telling visitors they should be watching for their email addresses to show up on Have I Been Pwnd.

There are questions still. The site defacement seems to have included either a subdomain takeover, or a long tail attack resulting from the polyfill takeover. So far my money is on something else as the initial vector, and the polyfill subdomain as essentially a red herring.

Troy Hunt has confirmed that he received 31 million records, loaded them into the HIBP database, and sent out notices to subscribers. The Internet Archive had email addresses, usernames, and bcrypt hashed passwords.

In addition, the Archive has been facing Distributed Denial of Service (DDoS) attacks off and on this week. It’s open question whether the same people are behind the breach, the message, and the DDoS. So far it looks like one group or individual is behind both the breach and vandalism, and another group, SN_BLACKMETA, is behind the DDoS.

Continue reading “This Week In Security: The Internet Archive, Glitching With A Lighter, And Firefox In-the-wild” →

Supercon 2023: Receiving Microwave Signals From Deep-Space Probes

October 10, 2024 by 5 Comments

Here’s the thing about radio signals. There is wild and interesting stuff just getting beamed around all over the place. Phrased another way, there are beautiful signals everywhere for those with ears to listen. We go about our lives oblivious to most of them, but some dedicate their time to teasing out and capturing these transmissions.

David Prutchi is one such person. He’s a ham radio enthusiast that dabbles in receiving microwave signals sent from probes in deep space. What’s even better is that he came down to Supercon 2023 to tell us all about how it’s done!

Continue reading “Supercon 2023: Receiving Microwave Signals From Deep-Space Probes” →

Fail Of The Week: The Case Of The Curiously Colored Streetlights

October 9, 2024 by 119 Comments

What color are the street lights in your town? While an unfortunate few still suffer under one of the awful colors offered by vapor discharge lamps, like the pink or orange of sodium or the greenish-white of mercury, most municipalities have moved to energy-saving LED streetlights, with a bright white light that’s generally superior in every way. Unless, of course, things go wrong and the lights start to mysteriously change colors.

If you’ve noticed this trend in your area, relax; [NanoPalomaki] has an in-depth and surprisingly interesting analysis of why LED streetlights are changing colors. After examining a few streetlights removed from service thanks to changing from white to purple, he discovered a simple explanation. White LEDs aren’t emitting white light directly; rather, the white light comes from phosphors coating the underlying LED, which emits a deep blue light. The defunct units all showed signs of phosphor degradation. In some cases, the phosphors seemed discolored, as if they experienced overheating or chemical changes. In other LEDs the phosphor layer was physically separated from the backing, exposing the underlying LEDs completely. The color of these damaged modules was significantly shifted toward the blue end of the spectrum, which was obviously why they were removed from service.

Now, a discolored LED here and there does not exactly constitute a streetlight emergency, but it’s happening to enough cities that people are starting to take notice. The obvious solution would be for municipalities to replace the dodgy units Even in the unlikely event that a city would get some compensation from the manufacturer, this seems like an expensive proposition. Luckily, [NanoPalomaki] tested a solution: he mixed a wideband phosphor into a UV-curable resin and painted it onto the lens of each defective LED in the fixture. Two coats seemed to do the trick.

We have to admit that we have a hard time visualizing a city employee painstakingly painting LEDs when swapping out a fixture would take an electrician a few minutes, but at least it’s an option. And, it’s something for hobbyists and homeowners faced with the problem of wonky white LEDs to keep in mind too.

Continue reading “Fail Of The Week: The Case Of The Curiously Colored Streetlights” →

FLOSS Weekly Episode 804: The AI Alliance — Asimov Was Right

October 9, 2024 by 1 Comment

This week Jonathan Bennett and and Dan Lynch chat with Anthony Annunziata about Open Source AI and the AI Alliance. We get answers to our burning AI questions, and talk about the difficulty of defining what Open Source means for these large models.

Continue reading “FLOSS Weekly Episode 804: The AI Alliance — Asimov Was Right” →

Art of 3D printer in the middle of printing a Hackaday Jolly Wrencher logo

3D Printering: Listen To Klipper

October 8, 2024 by 10 Comments

I recently wrote about using Klipper to drive my 3D printers, and one natural question is: Why use Klipper instead of Marlin? To some degree that’s like asking why write in one programming language instead of another. However, Klipper does offer some opportunities to extend the environment more easily. Klipper runs on a Linux host, so you can do all of the normal Linux things.

What if you wanted to create a custom G-code that would play a wave file on a speaker? That would let you have custom sounds for starting a print, aborting a print, or even finishing a print.

If you recall, I mentioned that the Klipper system is really two parts. Well, actually more than two parts, but two important parts at the core. Klipper is, technically, just the small software stub that runs on your 3D printer. It does almost nothing. The real work is in Klippy, which is mostly Python software that runs on a host computer like a Raspberry Pi or, in my case, an old laptop.

Because it is Python and quite modular, it is very simple to write your own extensions without having to major surgery or even fork Klipper. At least in theory. Most of the time, you wind up just writing G-code macros. That’s fine, but there are some limitations. This time, I’m going to show you how easy it can be using the sound player as an example.

Macros All the Way Down

Normally, you think of gcode as something like: G1 X50 Y50. Some of the newer codes don’t start with G, but they look similar. But with Klipper, G1, M205, and MeltdownExtruder are all legitimate tokens that could be “G-code.”

For example, suppose you wanted to implement a new command called G_PURGE to create a purge line (case doesn’t matter, by the way). That’s easy. You just need to put in your configuration file:

[gcode_macro g_purge]
gcode:
# do your purge code here

The only restriction is that numbers have to occur at the end of the name, if at all. You can create a macro called “Hackaday2024,” but you can’t create one called “Hackaday2024_Test.” At least, the documentation says so. We haven’t tried it.

There’s more to macros. You can add descriptions, for example. You can also override an existing macro and even call it from within your new macro. Suppose you want to do something special before and after a G28 homing command:

[gcode_macro g28]
description: Macro to do homing (no arguments)
rename_existing: g28_original
gcode:
M117 Homing...
g28_original
M117 Home done....

Continue reading “3D Printering: Listen To Klipper” →