zlacker

>>ptorro+(OP)
This will cause 3D printer usability to go down massively. A bit like the multicolored tracking dots - https://en.wikipedia.org/wiki/Printer_tracking_dots that causes the driver to tell you "you can't print black and white as you're out of yellow".

>>Anothe+4a
As far as I know, the tracking dots aren't even a legal requirement. Nothing stops you from making a printer without it, unlike is the case here.

>>digiow+9S1
When the FBI comes to you, an executive at a printer manufacturer, and says “implement tracking dots or we will discover criminal images on your son’s laptop” or some similar situation the existence or lack thereof of any legal requirement is irrelevant.

>>ls612+fv2
Blackmail an Executive? That's a complete overkill.

It's so much easier just to "recruit" the direct manager of the firmware engineering team. Convince them it's their patriotic duty to add "tracking dots" to the design requirements without drawing attention to where the requirement came from.

The engineers implementing it will assume the requirement came from somewhere above, or another engineering team. And if the executives ever notice, they will assume it came from somewhere below. Both will probably assume the legal department was responsible, and that there is some kind of law somewhere requiring them to implement that functionality.

>>phire+rA2
The most unrealistic part here is that you're assuming they can even find their desired firmware manager on the org chart.

Moreover, most executives don't require blackmail; they tend to go along to get along.