I think you misunderstood. The 1963 term is "hacker", and its 1963 meaning is "computer intruder". I.e. the journalists are using the earlier definition and the definition referred to by "Hacker News" came later.
Ah, I see now that journos were referring to the older definition of hacker. I suppose newer interpretations have a ways to go in gaining acceptance, though I am not sure why the phrase hacker/cracker is even used, when other words could be used too, like tamperer (for intrusion) and tinkerer (for non-builder/non-intruder (i.e. on their own equipment, or a lab's equipment, and learner). Kind of like the phrase "me and the gang," although that word might never gain a total conversion, nor should.
Yes, a failure of both the journalist and the editor.
Sadly, this kind of failure is all too common. I encounter articles that often omit a photo of the "thing" the article is describing. This (no photo) might have made some sense fifty years ago in the heyday of paper print where including a photo was much more work. But today, for HTML publishing, it is just an indication of failure on the part of the publisher.
50 years ago was 1976. Pretty sure there was no particular problem incuding photos or illustrations in paper journalism at that time. Maybe for very low-budget newsletters it would have been.
That depends. For the most modern presses (1970s modern) it was no problem but many small newspapers still used the linotype and a press that couldn't handle pictures without much effort.
I think USA Today (1980) was considered repulsive not just because it was colorized and a newspaper but simply because it put more space/resources into illustrations than was considered tasteful. A typical paper would reserve photographers and illustrators for front page and significant stories.
i see the opposite a lot, too, though: articles that don't need a picture but have some marginally-related stock photo tacked on just so there's a picture.
The map is wrong - but the article is right - it mentions that the longer route higher up on the peninsula from Skabo to Flode has been chosen but most internet maps show the shortest route from Eide (which has not been chosen). There is only one map I found showing the correct slighly longer route at https://www.tu.no/artikler/kjemper-fortsatt-for-ny-trase-for...
100×10^12 km is about 10.6 light years. There are about 16 other stars closer to the sun than that. It's a bit like a human body containing blood vessels with total length greater than twice the Earth's circumference.
I wonder if these measurements were done in similar fashion to how they measured kudzu coverage in the US. For the longest time it was assumed that one of the initial projections was correct; however, under closer examination that estimate was off by a factor of 30. Kudzu wasn’t enveloping the South. It did like the byways though.
Imagine if a 3year old has only one single blood vessel:
The single blood vessel grows by approximately 88 kilometers per day since conception.
Here is the quick calculation using that timeline:
•Total Days: ~1,365 days (270 days in the womb + 1,095 days of life up to age 3).
•Total Length: ~120,000 kilometers.
That breaks down to an astonishing 3.7 kilometers of growth every single hour.
Typical adult walking speed: ~5 km/h . Next time you are walking then imagine the tiny thin blood vessel growing behind you almost at the same speed you are walking. If you slow down and stop it will catch up to you.
Please consider putting the first paragraph of [1], "iroh is a modular networking stack written in Rust. It provides the building blocks to create applications that can communicate using fast, cheap, and reliable connections.", at the top of the blog post and the main website. The middle two lines of [2] are good as a follow-up.
The current stuff about dialling is pretty incomprehensible, as shown by the many confused comments here. No one "dials" IP addresses (or keys), and no one wants to, so the word "dial" shouldn't be part of the title or description. The word "key" would be better not mentioned until you start talking about implementation, and the brief high level "what it is" and "what it is for" stuff should come before implementation.
Iroh seems quite relevant to some projects of mine, but after reading the blog post and the main page, I still had no idea of that relevance until I had read over a hundred comments here (many of them confused about what Iroh was).
It's not for street cred, it's what makes it usable everywhere: Rust, JavaScript (server or browser), Python, Kotlin, Swift, C. Written in JavaScript or Python means limited use, Kotlin or Swift means it could be tricky outside their main platforms, C means worrying about potential vulnerabilities and core dumps. I.e. "written in Rust" is definitely relevant here.
How will that help your computer behind your NAT communicate with my computer behind my NAT? (I think you're still stuck on the blog post's very confusing opening, which does indeed make it sound like a terrible alternative to DNS, but it's actually something entirely different, for a very different purpose.)
reply