Re:DEF CON's response to the badge controversy
by tptacek on Saturday August 10, 2024 @06:36PM
(#41212734)
It sounds to me like they were mad at Dmitry for including an "easter egg" in their badge firmware that solicited donations to a Bitcoin address.
[ Parent
| on HN ]
Re:DEF CON's response to the badge controversy
by Dylan16807 on Saturday August 10, 2024 @07:34PM
(#41212994)
It was definitely an easter egg. A secret screen that gives credit to someone that worked on a thing and otherwise wouldn't get credit is the textbook example of an easter egg.
It probably shouldn't have had the Bitcoin address, but it doesn't sound like that would have been treated much differently.
Re:DEF CON's response to the badge controversy
by tptacek on Saturday August 10, 2024 @07:39PM
(#41213010)
I think you're going to find that firms who contract embedded designs have viewpoints about "easter eggs" that would be surprising, even off-putting, to message board communities that savor them like single malts. Generally, when firms arrange to deliver hardware/software to their own customers sourced from vendors, they want a clear understanding of what the software actually does.
Re:DEF CON's response to the badge controversy
by Dylan16807 on Saturday August 10, 2024 @07:42PM
(#41213018)
I know some companies dislike easter eggs a lot, and some of their reasons are valid.
But it's objectively an easter egg. Why the scare quotes?
Re:DEF CON's response to the badge controversy
by tptacek on Saturday August 10, 2024 @07:44PM
(#41213029)
Because it solicited money.
Re:DEF CON's response to the badge controversy
by Dylan16807 on Saturday August 10, 2024 @07:50PM
(#41213049)
I will note that it's not soliciting money for the person that put it there. So I don't think that's even close to disqualifying it.
Re:DEF CON's response to the badge controversy
by tptacek on Saturday August 10, 2024 @08:05PM
(#41213094)
You do you!
Re:DEF CON's response to the badge controversy
by jsjohnst on Saturday August 10, 2024 @11:36PM
(#41213827)
I mean, you are you, but maybe take a breath and stop picking fights?
Re:DEF CON's response to the badge controversy
by josephg on Saturday August 10, 2024 @08:33PM
(#41213200)
Yep. But again, it’s really not clear in this case if DEFCON was paying their vendor (EE) for software at all. I can see how it was ambiguous from their side given Dimitri was friends with the hardware design company. But from the POV of Dimitri and EE, DEFCON was paying for hardware and a separate 3rd party (Dimitri) volunteered to write the software. It’s very spicy to attack people in your community who volunteer their time.
And unpaid programmers doing cheeky things with code because they want to is the heart of DEFCON.
I can see where DEFCON is coming from with the calls they made here. But it’s a mistake to treat Dimitri as if he were a vendor. He's not.
Re:DEF CON's response to the badge controversy
by kalleboo on Saturday August 10, 2024 @10:17PM
(#41213576)
This is a hacker con, not an enterprise engineering con, Easter eggs have always been a part of hacker culture.
Re:DEF CON's response to the badge controversy
by tptacek on Saturday August 10, 2024 @10:21PM
(#41213594)
Tell me more about DEF CON.
Re:DEF CON's response to the badge controversy
by rrix2 on Saturday August 10, 2024 @11:14PM
(#41213768)
I heard they got canceled this year