skysight-inc/HackerNews huggingface dataset:
> Everything does not have to be looked at via the lens of societal privilege.

I don't mind looking at nearly everything through that lens, even if not exclusively. We probably should think, in general, about differential healthcare outcomes even, and especially, now, for example. What I object to in this case is the smear tactic. "It's just crazy rich white people who are afraid to die." As you say, it's shaming. And, it leads to that other assumption, that this will always only be for rich people. I'm no fan of abject capitalism, but there are rich people who make things cheaper for everybody. Ford didn't own the only automobile, nor Boeing the only airplane. They, and other manufacturers, are interested in bringing costs down in order to get more buyers.
Try pressing space (or page down on keyboards with pg down).
I didn't know you could defenestrate abstract things. I thought it was just for people.
w3m had its fair share of vulnerabilities :)

It's parsing untrusted data using C. It's not secure because it renders to a terminal!
I suppose the question would be whether the chip could be as fast at a similar price and also not suffer from the vulnerability...
They certainly do.

Not being able to burn a mix-CD for friends is something that bothers almost anyone.
Contralto?
Not quite what you're asking, but if you just want to get a shell on the machine, IRIX often had a bunch of accounts with no password. Try lp, demo, games, and guest.
What complexity is added by keeping data in the tree? If we are talking about GB+ datasets, then yes that shouldn't be stored in the tree. But a small list of products that needs to be manually updated regardless of where it is stored? That is perfectly fine to store in the tree and I think the author was talking about that sort of data.

As always, it depends on the data. Sometimes git is fine. Sometimes you need S3. Sometimes Postgres. There is no one size fits all solution.
Small note here: I was told the above reads like sarcasm, and i'd like to state that the lines above the edit are 100% not sarcastic and meant exactly as stated.
Because that comment was incredibly wrong - look at the front page and see what's plastered all over it: Spectre and Meltdown. HN definitely "cares"
My parents bought a Packard Bell PC as the first family computer, back in 1999 or so, that had a Cyrix, 333mhz from what I recall.
From the article:

> This attack is called XeroDay
Not sure why my comment was down-voted so viciously, was it that stupid? I think there may be a mod bot that automatically bestows -2 points to any comment mentioning Trump, we'll soon find out :)
Looks like 1.3B in public hands may be a bit of a low estimate. From this article seems like the founders have ~20-40% of circulating XRP.

https://www.forbes.com/sites/workday/2017/11/22/formula-1-le...
Static linking too. Most of us rely on library code maintained by others we trust. Reads from registers that should be empty isn't flagged by most code auditing software.
This is true, but like other extinction level events it might actually open up the space for some new ideas.

Someone on my twitter put it this way: microkernels could see a resurgence if the cost of a context switch into kernel is just as high as the cost of context switching between 2 processes.
Yes of course, it depends on your workflow.

I switch between apps and I often keep windows almost maximized.

I also only do web work, so I look at webpages all day.
There's some potentially interesting data here but I found it disappointing that this article was mainly showing averages. I'd love to learn what distinguishes the most productive folks from the average. Are they more consistent? Do they check email a lot less? Do they tend to work more in the morning?
The people that were aware were probably extracting value out of the fact that not everyone knew.

Could be not worth making a public stink, could be weaponizing the exploit, could be coordinated disclosure.
> I think part of it is that you're conflating writing music with sound design.

That's a distinction I've totally missed until now, as you pointed out, I've mostly thought about synths like they are traditional music instruments, which ain't really the case and as such added a lot to my confusion about "How to make something other than noise with this?".

Thank you for, yet another, very helpful comment!
I'm literally blown away by the sheer number, and quality, of useful resources and information being shared here. Kudos to the HN community!
In my mind Rust macros are easily the least appreciated feature of the language. Nearly every non-trivial library I've had any contact with use macros in some manner to enhance their API and usually the result is very good. For me one of the most compelling things about Rust when I first learned of the language was print!() and how it comprehensively solves the type-safe string interpolation problem better than anything that has ever been provided in C and C++.
I like RescueTime, although I think it’s good to use for a few months, get a baseline, and then move on.

More to the point, and taking out my axe to grind, all of this focus on productivity and being a “success!” is helpful, but also amusing and adisheartening. Please stick with me here, but if you look into sociology written over the last 20 years, it’s tragic (but also inspiring) how Americans tried and tried to work harder, even though the cost of everything went up 3x and the amount of work needed to attain that same stuff also went up 3x, thus meaning everything required 9x more effort.

I love people working hard, but it’s shocking when you learn that adjusted to BOTH population growth and inflation, an apartment in New York City should rent for about $900 today.

If linear trends continue (they won’t fortunately, some kind of large crisis will reset them) we’ll be talking about preparing kids to be a “CEO!” at 14 or earlier, maybe even there will be “CEO Camps”. What a delight...
If you're running SQL in a VM ... I'm pretty sure I know how to improve your performance by 30%.
Since I can think I've always loved the idea of changing the source code of life, I also never understood why we don't regrow body parts once we have lost them.

From a nature standpoint of view, nature does not care about the single individual as long as the species survives.
I don't like that behaviour.

Imagine a caveman who lost his arm in a fight with some animal.
It just takes more energy to regrow parts and the caveman would be vulnerable all the time so nature decided to take that awesome feature away.

What nature does not realise is, that we now have the time to regrow body parts, there is no danger anymore, somebody who lost a leg can recover in a hospital.

And I'm 99% certain that we will regrow body parts in the next 15-20 years and I'd love to be a part of that revolution.

CRISP is another big thing that has the potential to cure diseases, those we call incurable.

All those facts and the possibilities of extending the human race makes me very excited.

So my niche would be Biochemistry, I choose that field because I think Biochemistry is the C and Assembly language of the human body.
ContrAlto won't work, since it's the name of the Alto simulator written by the Living Computers Museum. (It's a very good simulator, letting you see what happens right down to the microcode.) I'm going to use XeroDay for the attack name.

https://github.com/livingcomputermuseum/ContrAlto
> Manila (most dense city)

This comment doesn't take away from your point - but isn't densest either Dhaka or Mumbai?
Passwords like "HGFIHD" and "AAJMAKAY" look like initialisms. It might be fun to try to decode them. (xxxAKAY on a Xerox PARC disk from the 70s/80s... could it be?)
Show HN: Hourly updated list of subdomains from CT logs
Processes can run a long time and pass data around. This isn’t realistic.
The sensations you call your body change over time, until there's nothing but fatigue and pain left. If someone offered to let you resume consciousness on artificial hardware after your body had ceased to function, you might take them up on it.

In fact, some of my eldest relatives are in high spirits but also looking forward to death, because they have religious convictions about a wonderful, energetic, pain-free afterlife.
I find moving authority from the cities to the state more acceptable in this case because it merely mandates allowing economic activity to occur. None of these policies prevent citizens from voting with their wallets, developers will still only build things they can make a profit on.
Wow, I've had a completely different experience to others.

I think the trackpad is great, comparable to my Air 13 although slightly wanting in tap to click. No palm detection issues. I guess you just need to give it a try yourself.
The 360-Degree Selfie|Breakthrough Technologies
Yes, I updated the article based on the discussion here. But I still need a logo :-)
I really, really wish they would have bought Waze. It was a big coup for Google to buy them up. Had Apple bought Waze, Apple maps would be much better today.
Yes, this would have a bonus effect of actually gaining IPC in multi process loads.
If I make a perfectly identical clone of you, and then shoot you dead, will you resume your consciousness in that clone?

Why?

Alternatively, if I shoot the clone, will the clone resume its consciousness in you? By what process?
Those GPUs needs to be located somewhere (in a housing), with power, and won't include any of Google's nice software stack to use the.
My understanding:

Because it may not be known whether or not the read will have ended up being prohibited at the time it's speculatively executed. Think of a simple for loop over the contents of an array: usually at the end of each loop iteration you jump back to the beginning of the loop, until the last time you don't, when i > array.length or whatever. The branch predictor will likely predict that the last time you'll jump back again (you always have before, and it doesn't know the actual value of array.length yet since that takes hundreds of cycles to come back from memory) and try to speculatively execute the contents of the loop body on what turns out to be out-of-bounds data. That's not typically malicious; it's at the end of pretty much every iteration over an array ever.

So then, if we can reliably get our loop to operate on a bit of data that might turn out to be out of bounds, the trick is then to have a loop body like this:

if (potentially_illegal_bit == 1) {
load_legal_location_1()
} else {
load_legal_location_2()
}

After the branch misprediction occurs, the state of the program gets rolled back so we don't know what potentially_illegal_bit itself was anymore, but we don't have to, we can surmise it from the cache contents. The program isn't going to do an illegal read, it's going to do a legal one, to either legal location 1 or legal location 2, and see which is faster (as only one of them should be cached). Both reads are legal and will succeed, so the only difference is the speed. We've now exfiltrated one bit of data from outside of your array bounds, but the only actually illegal read was speculative, which, as far as the CPU is concerned, is par for the course (predictions are wrong all the time), so no harm, no foul.
Ack. Error in the second step of the divide-by-19 example -- hat tip to Josh Jordan on Twitter -- and it's now too late to edit.
Zuck's text is marketing, not an actual goal.
Looking at the plots, it seems obvious that it is useless to work on Mondays and Fridays. I cannot agree more.
Here's the 1997 Intel optimization manual: https://www.ece.cmu.edu/~ece548/localcpy/24281603.pdf

In 2.1.3, that pertains to the original Pentium processor, it describes how the predicted branch target instruction is fetched.

This is not commonly considered speculative execution in computer architecture terminology.

In 3.2.1 it describes how on later OoO processors the fetched instructions are speculatively executed.

Here in the description of the 21064, another in-order processor, the pipeline is described (under "Conditional-Branch Pipeline Flow") as potentially taking zero cycles for correctly prediced branches, meaning that the instruction decode is also pipelined: http://collaboration.cmc.ec.gc.ca/science/rpn/biblio/ddj/Web...
According to this, people are mostly pretending to work hard.
About your 3rd point, recent results (clonal haematopoeisis, single cell genomics) do in fact suggest that life extension interventions will be highly technical, ongoing and very expensive.
We don't know when it was discovered first though. We only know that it's been disclosed now.
If AMD spotted the issue and avoided it deliberately all those years ago, why didn't they tell anyone?
To this point, I'd like to know what distinguishes the least productive from the average. Or more plainly stated: what are the traps everyone should avoid to maintain reasonable levels of productivity.
Mixed debugging in AS has never worked for me, I'd call it about the same if you've done NDK work before.
Doesn’t Spectre just require speculative fetching? In which case in order is not sufficient as to guarantee immunity.

It’s Meltdown that relies on out of order execution.

https://meltdownattack.com/meltdown.pdf

https://spectreattack.com/spectre.pdf
Aren't screen sizes typically based on that diagonal size (i.e. a 15" screen is a diagonal 15")? If so, doesn't that make parent's link more accurate?
Might you be referencing the sigils (@ and ~), because thry've been gone for a few years now.

The syntax is light and clean, eschewing redundencies like parens around if conditions.

More lifetime inference and non-lexical lifetimes help to clean it up even more.
That you would analogize congress doing something productive to moving a star illustrates my point that our status quo has failed.

That you'd rather argue about the degree of failure that's acceptable contributes towards the perpetual failure.
Right, so the mismatch here is whether or not the CPU is being pitched as wholly secure. If it is "mostly secure with insecure performance enhancements" or really "mostly secure with performance enhancements that have an unspecified level of security", then... It's "not a bug".

It's a huge lapse in customer trust, for sure. But if you're just going to play that semantics game...

I think the good point here is whether or not Intel engineers knew of patterns like this (they should have) and is it negligent or unethical to release products that have these vulnerabilities built in. Insecure (or "undefined") by intention or by coercion.
Sparta (Oracle) | FULL-TIME, ONSITE | Seattle, WA or SFBay or Boston

Sparta aka Oracle Cloud Infrastructure (OCI) is Oracle's bare metal cloud; most of us are in
Seattle and there are branch offices in the SF bay area and Boston area. We’re looking for
senior developers to help build services and tools for OCI's Operations group. This is a new
team in a relatively new org, so it's a good chance to make an impact and the vast majority
of the work will be greenfield.

Minimum Qualifications:

- BS CS or related technical field, or equivalent practical experience
- Five years of software development experience
- Strong knowledge of CS fundamentals
- Mastery of one or more of: Java/C*/Python or similar
- Proficiency working in a Linux environment

Preferred Qualifications:

- Graduate work in CS, especially in the fields of Systems or Machine Learning
- Prior experience architecting and operating large scale systems/services
- Some familiarity with systems administration or DevOps/SRE experience
- 10+ years of software development experience

Resumes / questions to: mike.o.jackson@oracle.com
Automation–The Good, the Bad, and the Ugly
What would be the sales pitch within the NSA to create tooling to allow this sort of stuff to be exploited for useful intelligence purposes? What would the tooling look like, how would it be used, etc?
I think light scattering is an atmospheric phenomenon.
When I said we, I meant it. Even I find myself excited about the new Dell Laptop even though I know it has defective hardware in it, straight out of the box.

NPR did run a meditation story this morning too,

https://www.npr.org/sections/health-shots/2018/01/04/5751679...

So I'm failing to see how it's wrong. Are you going to put off a purchase because of Meltdown? Are you going to do anything beyond complain for a few threads on HN, apply kenrel patches, and go back to business as usual? Are any of your actions going to cost Intel in any significant way?

I did at least disable javascript in my browser. That's probably more than what most have done so far.
I'm confused, it sounds like you want a European keyboard layout, and the European configurations go up to 16GB with a normal display:

> i7 | 16GB | 512GB | FHD non-touch (1920 x 1080)
What if the court is in the same pocket as Intel?
A python file with a list in it, is significantly simpler than a remotely stored data file, which brings with it parsing, error handling, issues developing offline, and still requires AWS permission understanding and some S3 teaching.

Git, and GitHub, at the level we teach them, are not very complex.
I addressed this elsewhere (https://news.ycombinator.com/item?id=16072690) but to quickly recap: that's not the hard problem, and hardened SAML IdPs that have the option of exploiting this turn out to have per-tenant keys anyway so that they can get cryptographic binding instead of counting on audience restrictions being checked.

Additionally, your TLS terminating stack is much better hardened than median in-app crypto code.
Did you even read my comment? They're not perfect, but you were expecting them to be fake. Someone not told there would be computer generated images would be considerably easier to fool.

Also, probably the bigger risk is not that you'll be shown an entirely fabricated image, but rather that someone could convincingly be inserted into an existing image.
Microkernels you say? Yay, more complexity!

In all seriousness, the Nintendo Switch users a microkernel and just got completely p3wned. It's extremely fanciful that we know how to build robust modular microkernels when we can't even get the simple stuff right.
I can understand the OP's thinking, although I have Lenovo's Yoga 2 Pro.

With my laptop in my lap, I typically have to be leaning back to comfortably use the keyboard. Sitting up or slightly leaning forward, it's more comfortable to grasp and scroll with the screen itself, maybe bent a little further back than typical usage. It's a more comfortable resting position.

Although sometimes I just flip my yoga into a tablet and that's just swell
Note: I was obviously being facetious, but It made me wonder how far back branch prediction goes not being a microarchitecture expert... Surprised to find even the old 68k utilises it! not that they necessarily suffer the same fate through the concept alone of course.
I remember seeing this suggestion earlier. If I'm not mistaken a commentor stated that a) this would come with a huge performance penalty b) there would be synchronization problems in multithreaded scenarios.

Don't take my word for it though, I might have understood it wrong. I imagine concurrent/parallel execution involving system calls could maybe suffer from synchronization issues if processes/threads run on different physical cores with separate caches?
Also udocker for similar reasons
A lot of what I fear about death isn't the end of my experiences but the fact that the things I was doing while alive will cease. I won't be able to earn a living to support my loved ones any more. I won't know if anyone will continue the lines of research that I consider interesting. I can't be sure that the investments I have will still be managed well.

A "backup" of myself that retained my memories and abilities would solve these problems and others even though it wouldn't solve my personal existential dread over cessation-of-experience. (Though if someone did develop gradual replacement mind uploading I'd get to maintain continuity of experience too.)
I'm not sure why I would actively seek it out - ignorance is bliss.
You can consider wheat. Originally the number of seeds produced by a wheat stalk was small. Which meant needing to sow a high proportion of your crop for next year. With domestication the yields slowly increased over several thousand years.
This will give you only memory addresses of the data in question, right?
To use a really stupid analogy, imagine a cook in an Mafia-involved restaurant, and you're a cop (you're the adversary). There's a whiteboard in the boss' office with a number you want to know.

So you come there every day and say, "Hey, if the lights at (some address) are on, I want a cheese pizza, otherwise I want pasta.". In the beginning he sends his boy to check the light at that address, and the boy takes 20 minutes to go and check, and all that time he has to wait before he can make you the pizza. After a while the boy always says "The lights are on", so after a while the cook would still send the boy, but he would anticipate the answer "the lights are on" and he would start a making pizza. Once in a while (maybe once every 6 months) the boy would return saying the lights are off, so after 20 minutes of making the pizza, he would throw away the pizza and make you pasta.

After doing this a lot, you say, "Hey, if the lights at (some address) are on, I want a pizza with the topping from the box numbered according to the number written on your boss' whiteboard. Otherwise, I want pasta.". You know the lights will be off, but he starts making pizza with some topping you can't tell, but you notice he got a box from the fridge to put it next to his pizza-making table. The boy returns, he throws away the pizza and makes you pasta. Then you ask him, "Hey, I have another order, can I get a pizza with a topping from box 1?". If he goes to the fridge to get that box, then you know the box he picked up earlier (while he was guessing that the boy would say the lights are on) was not box 1, so you ask for another pizza with topping from box 2, etc. But if he doesn't go the fridge, you know he picked up that box previously (because he predicted the boy will tell him the lights will be on), and that's how you figure out what number is written on the boss' whiteboard: when the cook doesn't go to the fridge, it's because the box with that number is already on his table.

The whiteboard is the secret memory area, taking the box from the fridge is reading from some RAM address to cache (if it's already in cache, no need to read from RAM), and I hope the speculative execution is clear.

This analogy describes (very roughly) one of the exploits in Spectre.
I really resonate with his story about asking Nana about her history. My grandparents died several years ago, and just a couple years back I started to actually care about my family history and wanting to know more. I asked my dad a bunch of questions, and I was quite disappointed at how many of his answers were variants of: "Your grandma would know this, but I'm not sure. I was too young #{['to care', 'to remember', 'to understand'].shuffle.first}"

If your grandparents are still alive, I completely second the author's advice to talk to them about the family history. I'm in the process of recording podcasts (for family use only, never to be released publicly) with my parents while they still have sharp-ish minds. Assuming the AI apocalypse doesn't wipe us out, I think my kids will really treasure this, and their kids maybe more so.
It’s not ok if a non engineer erroneously drops a tag making the HTML invalid though, so I’m not sure directory permissions would be enough.

We just solve this with code review.
That page talks about both Meltdown and Spectre, as far as I can tell. AMD is vulnerable to Spectre; everyone agrees on that. According to https://www.amd.com/en/corporate/speculative-execution AMD claims it's not vulnerable to Meltdown (aka "Variant Three").
all of my best ideas are always given half seriously, those are the ideas worth listening to.
Or, more pessimistically, they couldn't get Apple Maps, Safari, Siri working well with big data so they hobbled them and claimed it was for a secure experience.