It's really a debate about orthodoxy: should everyone be forced to conform to our definition of the word "hacker"? or should we learn tolerance of the fact that most people use the word differently than we do?
I cannot think of anything least hackerish than demanding that everyone use the word "hacker" the same way I do.
Words do mean things. For example, I have a constant battle with lawyers who think "open source" means "Gnu" and therefore it all has a copyleft, and I have to explain the subtle differences.
On the other hand, a lot of things are meaningless, like whether GNU is capitalized, how you pronounce Linux, or whether you should name it giving credit to contributors (i.e. actually it's GNU/RedHat/IBM/Microsoft/Intel/Google/..../Linux).
We rightly should push back again misuse of words in some cases. If ardent supporters of "autonomous vehicles" started calling them "autos", we should rightly point out that this is stupidly confusing. It's where we are with "crypto" right now.
But "hacker" meaning "cybercriminal" isn't some new confusing use of the term, but an alternate definition that goes back to the very beginning.
One of my frustrations with the "hacker" community is that there are a lot of orthodoxy. There's people trying to be different -- then there's people trying to force you to be their kind of different.
This one time I was invited to a meeting with stuffy government types. We were told to write our names and affiliation on a folded piece of paper to put on the table in front of us. I wrote "Rob Graham -- HACKER" -- knowing full well this would be confusing for them.
The reason is because they aren't necessarily distinct. If you write a script to scrape a website by incrementing a number, then whether you've committed a crime is an arbitrary decision by prosecutors.
Which was the point I eventually got around to discussing -- not that "hacker" and "cybercriminal" were distinct, but that they overlap -- that what we think of as unorthodox use of technology they might think of as crime, like scraping a website.
Describe yourself as "hacker", knowing this causes confusion among journalists and government types. This is great, confusing them is fun.
But don't police how they use the word "hacker". That's just imposing your orthodox views on them. It means you aren't one.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The solutions to your problems may involved "cloud" thingies, incidentally, but a cloud thingy is not the solution to your problems. Those pushing "cloud" thingies as the forefront of their solution to your problems, e.g. Brad Smith, are pushing, well, snake oil.
It's like that recent municipal water "hack". Nobody knows what happened, or even if it was a "hack". Yet everyone is promoting their solutions to the problem.
If you are promoting a solution and can't tell me how the hack happened, then your solution to the "hack" is snake oil.
I need to dribble out JSON output a few times second, each looking like {stuff}. How should I do it:
[
{stuff},
{stuff},
...
]
or:
{stuff}
{stuff}
{stuff}
...
In other words, a single item that if redirected to a file, would parse as JSON, even though it's meant to be read live. Or as a series of independent JSON objects?
Thanks the twitters! My answer is #2. I changed the option in the code to say "--ndjson-status" to communicate what's going on. Here are the two references people pointed me to: jsonlines.org ndjson.org
It's always "them" who don't understand, not "us". "We" have the clue, "they" don't.
In fact, it's this person who doesn't understand climate change. That's why deniers exist -- while climate change is real and important, those on the other side still misrepresent it.
It's like being correct that God exists -- and then claiming thus anybody who disputes "indulgences" is a heretic and must be excommunicated as a denier. No, Martin Luther believed in God, he just didn't believe in the excesses of the church.
No, climate change doesn't make everything worse. On average, 50% of changes are for the better, 50% are for the worse. The idea that climate change can only make things worse is so statistically improbable as to automatically be rejected by serious people
One of the things I hate about open-source is the paranoia that this "pull request" containing a useful update to my code is actually a trojan vuln/backdoor. github.com/robertdavidgra…
This sounds like a really useful feature, but at the same time, is enough code I can't simply press the "accept" button to accept the changes.
I'm tweeting about this because there are legal concerns. Whenever I talk to law enforcement, they demand it's my responsibility to verify that contributors aren't just adding code to help illegal activities.
If this sounds like a wackjob conspiracy theory, it's because this is a wackjob conspiracy theory. Signal's source code and algorithms are open. Just because some government departs have given it funding doesn't mean it's a secret plot by the CIA.
Signal uses well-known crypto algorithms. If they are insecure, well, then all cryptography is insecure and it doesn't matter which encrypted messaging app you use.
If there's a backdoor in the code, well, the code is open source and people would be able to find it.
Here's is the "censorship episode" of the show "WKRP in Cincinnati", where you see Andy (radio station program director) argue "free enterprise" against preacher "Dr. Bob Hallier" who is using boycotts to get them to remove music from the radio: