this post was submitted on 16 Sep 2025
33 points (90.2% liked)

3DPrinting

19719 readers
125 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: or !functionalprint@fedia.io

There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml

Rules

If you need an easy way to host pictures, https://catbox.moe/ may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] zipsglacier@lemmy.world 14 points 12 hours ago (3 children)

Here's the paper where they explain it. Basically, they make subtle fluctuations in layer height, adding or subtracting small amounts that are not visible to the naked eye, to encode 0s and 1s. So, maybe in principle this could run at the firmware level on your printer. Then, someone can use a microscope to read off the code from pieces of the printed part.

I would have some doubts about how reliable this is, given the relatively large tolerances in fdm printing, but they have a section about that in the paper, so I guess they at least have thought about it.

[–] B0rax@feddit.org 8 points 4 hours ago

Fluctuations in layer height that are not visible? Dude, most printers are not even able to achieve a layer height consistency that would be invisible to the naked eye if they wanted to.

[–] mctoasterson@reddthat.com 8 points 5 hours ago (1 children)

This has to be borderline useless as a positive identification tool, given that people can...

  1. Make their own models
  2. Run open source slicing software
  3. Inspect their own gcode
  4. Print from flashcard on a 100% offline printer with known clean firmware, such as the most common Ender 3.

How about they just focus on other methods of apprehending violent criminals and leave hobbyists alone.

[–] zipsglacier@lemmy.world 3 points 4 hours ago

This is right, for as long as the fdm printer hobbyists can avoid the lockdown and enshittification that some printer brands are definitely pushing. The value of this paper, for it's authors, seems more like a proof of concept: fingerprinting is possible. And I think that's actually it's same value for hobbyists: the problems with a closed system and proprietary printer firmware are not hypothetical.

[–] ThePantser@sh.itjust.works 13 points 11 hours ago* (last edited 11 hours ago) (1 children)

So when I turn on variable layer height this whole thing goes out the window. Or if I post process and sand the parts. Oh I know what if I use a slicer and firmware like klipper to bypass everything. No 3d printer that isn't locked down already by closed ecosystem will never have this "code" in the parts.

[–] Decq@lemmy.world 9 points 10 hours ago (1 children)

Sand paper wouldn't really help. They could just cut a part in half. But yeah no way in hell this will ever end up in any of the open source printer firmwares. So it's a moot point.

[–] zipsglacier@lemmy.world 4 points 10 hours ago (1 children)

The fact that this could only work in 100% locked down ecosystems was my thought too. About cutting the part up, that seems to be what this particular paper is most proud of: they did a bunch of math to make some codes that they could still figure out even when they were cut into pieces and mixed up---like if a person broke their printed part after using it. Sort of like error-correcting codes I guess, but able to be reassembled from fragments.

[–] golgorath@lemmy.world 1 points 8 hours ago

Why would you cut it into pieces. Just burn it i'd say...