skysight-inc/HackerNews huggingface dataset:
That is different, such laws are unenforceable because they have been ruled to be so by a court. The problem is with laws that are unenforced, but are still enforcable. If the situation of having unenforced laws becomes normalized, then legislatures will indeed not "waste time" removing them, and such laws will be only unenforced until some official decides they don't like you.
Oh, ok. I was concurring with the comment that said "There are plenty of inventions yet to make" and not really voicing an opinion about their difficulty.

However, after rereading it, I disagree with the top comment that said that "Centuries ago, it was easier to think of things to invent".

It's never easy to think of something to invent. Finding the problem, even just thinking there might be a problem where noone sees any, is a big part of any invention.

Also, in the past, inventions required a much larger leap of thinking than today. When we speak today about growing wings on creatures born without it, we kind of accept the idea, because we know it's already possible to grow eyes on flies' legs for example.

But inventing the steam engine, or disproving "spontaneous generation" and inventing vaccines, sound to me much more impressive because those people went where no one had dared go before them.
No, that's not what I mean.
If the illuminated areas are a very small portion of the entire map, then the circle metaphor actually may be more appropriate. But I see your point.

Hmm... Perhaps better still would be an immense valley of very uneven steepness and roughness, that we are climbing out of.
These questions are only relevant if you're not controlling and trusting all the code you're running that system. For a consumer system this is true if (and basically only if) you're running a web browser on that system.

If you're confident in the software you're running on a non-shared hardware, both Meltdown and Spectre are non-issues requiring no mitigation. This is a narrow class of systems, but it exists.
iOS can't even get text selection for copy/paste to work right!

Reported this several times from multiple devices to Apple from normsl support up to Tim Cook.

Apple is synonymous with Bugs.
Even better: https://static01.nyt.com/newsgraphics/2017/12/26/ai-faces/8e...

That's one heck of a receding hairline, meaning receding out of the plane of existence.
I think we have a conflict of definition? I would call instruction fetch and decode behind an unresolved branch speculation. If you have a machine with a single execution stage which can't issue instructions in parallel with the branch then of course you can't have these speculated instructions execute because whether they are valid will always be resolved before they get to the execution or writeback stages. But the mechanics of putting instructions into the pipeline on the basis of speculation and quashing them if the branch resolves differently than predicted is the same and re-use the same hardware mechanisms that handle exceptions, making the speculative issuing of instructions a clear win from a design perspective. It's the details of the pipeline that determine whether it's possible to trigger the Spectre vulnerability before the branch resolves.

Register renaming isn't required for speculation and you can even design out of order micro architectures without it. On an in-order processor you just have to make sure that writeback occurs after the branch is resolved and just flush the pipeline above the branch if the branch resolves incorrectly. No need to mess about with checkpoints because the register state is always valid. Well, there are some considerations with store commands too if you're using superscalar execution but it's still pretty easy. But again, these are all mechanisms you need in any event because your processor has to deal with interrupts that might be thrown at any moment by external triggers or memory faults.

EDIT: I suppose it's possible in theory that you could look at an upcoming branch, predict how it will resolve, and then fetch the relevant instruction data into your instruction cache. But I'd tend to call that an instruction pre-fetcher by analogy to the data pre-fetcher eveyone uses rather than a branch predictor. And I'm not aware of anyone every having done that.
> There, we’ll be working on expanding GitHub’s security tooling, like their recently announced vulnerable dependency alerting.

You don't have to suspect, it's in the article :)
I'm always disappointed in these comparisons since they never look at AWS spot instances, which are the real competitors for hobbyists.
Wouldn't that be less? Apple gets the 30%, the devs get 70% so they'd have to sell less than $330 to break even.
Toyota’s new self-driving car can ‘see’ up to 200 meters in every direction
Yes, I was just criticizing the example chosen, not the explanation itself (and judging from the votes, I was unclear).
They had like 6 months or so... how is more time going to make things less painful?
I'm sure they'll be happy to produce 24/7 or raise some prices to take care of that.
Arsonists set fires. Vendors create vulnerabilities, not pentesters.
That may have been fine in 1970, when there was very little to inherit (no thread handles, no named pipes, no semaphores, IIRC) and security wasn’t a big concern.

Nowadays, I think ‘whitelisting’ what the new process can do is the choice to make, not forking and then (hopefully) ‘blacklisting’ what you don’t want (that’s especially important if you eventually will be running code you didn’t write or, maybe, don’t even have source for)

That also is easier to test for. If you forget to specify a capability before forking, the bugs you see will be better reproducible than when you forget a thing you don’t need.

I can’t find it now, but try googling an article on how to properly fork a process nowadays. It is insanely difficult to do right.
If you follow the donations in this sector its usually boring and more towards whomever is in power. I would concentrate more on police and sheriff PACs and those related to the prison systems; not private but public which are most covered by PACs

while I find some things to like about this Administration as a Libertarian it stops when confronted with Sessions.

then again all this opens the door to more opportunities to flip this to Congress and put pressure there. The previous Administration did not push this either, they did their typical chicken move of pretending it wasn't an issue. As in, if we don't enforce the law then that means we don't support it. Yet no effort to repeal
You're talking about the C library function clone(). The actual system call "clone" on Linux doesn't care about functions, or stack pointers, it just sets a flag like the system call fork did. Everything else is implemented in the library by checking the return code.

This is all fine, there are two scenarios, neither of which is the imagined "race" described above:

1. "Fork-and-exec" Our new execution context will actually run a different program. We immediately do so, the new program doesn't care about most of the state of the old program, it throws that state away, including locks that were held by the old program's allocator.

2. "New Thread" Our new context will share all the state, if another thread has a process-wide lock for some reason, it can and should apply to us too. If it took a thread-specific lock, we're not that thread, so we already don't care.
Not genetically in that spot but doing family stuff discovered that I'm on a very out there part of my family tree (male decendent wise) four generations of only one son :-). It reminds me that improbable isn't a good defense.
I thought all since 1995?
An Introduction to Security Advisories and Response for VMware VSphere
And it's a good thing they did that because a motivated black hat with the correct skill set most likely did, too. Not to mention nation state cyber ops.
As a side note, his new (first?) book is just out.
No, I to think he's saying that -0.01 applies to everyone. Each individual choice is actually causing a loss of 80 million in utility (vs a gain of 1), but that loss is mostly borne by other people, so they are individually better off making that choice.
Arstechnica says it could be any processor since 1995.

https://arstechnica.com/gadgets/2018/01/whats-behind-the-int...
I think what you are doing is normalizing the idea of muslim ban by using it when its not really true.

Once its normalized it won't be such a big deal when it really happens.
Linode: CPU Vulnerabilities, Meltdown and Spectre
> that will only tell developers "this is unsafe, keep using JWT instead".

That's a good point. Maybe a header in the readme/docs like "Stateless Sessions", followed by "Using PAST/JWT/etc. for stateless sessions is a terrible idea, because kittens will die needlessly and painfully [ obviously using an actual summary of why ]. Don't just take my word for it, here are some resources explaining further..."
Lots of simple cores would be inherently better.
Video demonstration of the Meltdown attack was just taken down: https://www.youtube.com/watch?v=RbHbFkh6eeE due to "violating YouTube's policy on spam, deceptive practices, and scams."
It's not that it makes the practice of breaking into computers that much more interesting so much as it makes the underlying field much more interesting to work in. The engineering problems just got a lot more complex. We're all taking an attack vector seriously --- microarchitectural side channels --- that we weren't taking as seriously before, except as an abstract threat to crypto and a way of defeating a mitigation --- KASLR --- that nobody believed in anyways.

What's glorious is that serious software security people now have to start being literate about what it means to reverse engineer and dump the branch history buffers on different CPUs. Getting dragged through this kind of minutiae is the reason I'm still in this field after 22 years.

And I'm just a bystander here. Imagine what it must have been like for Jann Horn over the last several months!

This subsection describes how we reverse-engineered the internals of the Haswell branch predictor. Some of this is written down from memory, since we didn't keep a detailed record of what we were doing.

... because shit was so crazy while they were working this out that they didn't have the cycles to write everything down!
> This has nothing to do with infinity. This is solely due to the definition of a universe.

> A finite universe doesn't import anything as well, and this is no contradiction whatsoever.

It's not far-fetched that a satirical sci-fi series could have multiple universes with travel between them.

The Hitchiker's Guide actually both does and doesn't if you look at the "Whole Sort of General Mish Mash" joke. Though the WSOGMM joke is pretty explicit that it's one infinite mish-mash with infinite perspectives and universes are just an illusion.

> Also, an inifinitely large "part" can still import and export, despite being infinite. For example, take an infinite universe and split it into two halfs. Those "parts" import and export, despite being infinite.

He actually covers this in the quote on WSOGMM.

> The reason they are not universes is that any given universe is not actually a thing as such, but is just a way of looking at what is generally known as the WSOGMM, or Whole Sort of General Mish Mash. The Whole Sort of General Mish Mash doesn't actually exist either, but it is just the sum total of all the different ways there would be of looking at it if it did.

> The reason they are not parallel is the same reason that the sea is not parallel. It doesn't mean anything. You can slice the Whole Sort of General Mish Mash any way you like and you will generally come up with something that someone will call home.
Please feel free to blither now.

You can split the universe anyway you like, it doesn't make 2 universes, just a divide in the universe. Your 2 divides are exporting/importing but the universe as a sum is not.

Of course, we're just arguing over a joke in a fictional universe now. But if you're going to do that you should get the fictional physics right :P
Only 20% of Americans polled are against abortion entirely, it's not the powerful topic it used to be. You're right that marijuana prohibition is not a strongly supported topic either, or at least one that is met with a growing indifference. Almost no one (outside of Sessions) seems to have held strong opinions on the matter.

But regardless I highly, highly doubt this one law being overturned could be equated to states having free reign to do whatever they like, regardless of federal law. There are tons of these individual issues that are finely regulated between state and federal power balances.

Not to mention the Supreme Court doesn't work like politics where you trade one issue for going easy on another.
That demo is Linux, not MacOS: "Full Ubuntu was running with Firefox in the background. [...] it is only a demo app (a simple GTK application on Linux)."
New lithium-rich battery could last much longer
On one hand, great news for Intel: everyone needs a new chip. On the other, terrible news for Intel: AMD's offerings are pretty competitive these days. It'll be interesting to see how this plays out.
"Kill JS on the web" is easy and only mildly inconvenient using NoScript, but that doesn't mean most laypeople are going to do it.

Chrome and FF need "execute JS" to be an explicit per-site permission, similar to the permissions model of native smartphone apps.

Google will never do this because they're an ad company and care more about targeting ads than protecting Chrome users.
iOS app development on Windows
You will still get something very different from HSA's understanding of heterogeneous design or secure enclave processors (although those ones come closer to the idea).

The thing that is approaching it the most is a smartcard CPU. Flat X-i-P rom, cacheless, embedded mram or fram, <100 instructions, full register state determinism.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/fo...
> FN has also been known to murder French politicians.

Do you have any sources on that? With all the things the media in France is saying about the FN, I don't think they would have missed something so important.
sessions isn’t talking about Med, he’s talking about Rec.

fuck him, anyway. i’m glad weed gets you feeling better. it was only ever made illegal because racism and the cotton lobby.

fuck this system. fuck these entrenched interests.

fuck you, dad! i’m smoking weed no matter what u say!
This is really racism too. Just milder then kkk.
Google Summer of Code: 2018 Applications Open
Congratulations on your weight maintenance...that is wonderful.

Regarding using a throwaway, I understand the impulse. It's sad that in 2018 we are judged by potential employers or peers for just saying that a plant should be legal.

Personally, I decided last year to no longer hide my feelings on the matter. I believe this fear of being judged leads many of us to do so, and sadly, it impedes progress. So, I've started telling people openly and honestly how I feel. I'm no longer afraid to say it should be legal, and I'm not afraid for my wife, my children, my family, or my peers to know.

I'm not a regular user, but I know many who are and lead happy, functional lives, including the person I mentioned in the original post.

It should be legal.
> Hiniger makes $1 million? The total cost of 8 or 12 government cops.

You claimed that profits, not revenues, constitute "the profit motive sum" for private prison operators. But if revenue is tied to executive compensation, that's clearly not true. I didn't offer the number as a comparative, but rather as a way of refuting your claim that total revenues don't contribute to profit motive.

Aside from this point, I don't really think Hiniger's salary is relevant to this conversation.

> Peak war on drugs existed during peak government prison complex. Nobody likes to talk about that.

So are you really claiming that private prisons caused prison populations to decline? If not, what point are you trying to make by mentioning this obviously-not-causative correlation?

> rather, it's to highlight that the public system is radically larger and just as financially motivated

You'll find just as much "hysteria-like concern" here on hn, and elsewhere, about profiteering in public prisons. And yes, that includes concern over lobbying by prison guard unions.

I agree with your general point that a wave of stupid in the 80s and 90s is more to blame for our current situation than profit motive. And to get back to the article, Sessions has always been in the eye of that hurricane of stupid.

But profiteering -- by unions, by private prison suppliers, by suppliers to public prisons -- certainly helps sustain the present situation. Different people choose different subsets of that Goliath. So what?

Like I said above, I really, really don't understand the battle lines you're trying to draw here. Surely, we can all agree that the solution is putting fewer people in jails, right?
It’s worth noting that while the government in Taiwan still officially claims all of China, the government is currently led by a president (Tsai Ing-wen) whose party does not whole-heartedly endorse that position.
> This version requires a network connection when you attempt to install any OS software updates, because it needs to verify with Apple that the updates are legitimate.

They can't just verify the signatures?
Can't it be fixed with a microcode update?
How to protect your PC from Meltdown using Powershell
> We don't all profit from it, it's a total distraction for most people.

Collectively we do, just like we do from mathematics or museums. Also, imagine what the FOSS ecosystem could be if the underlying technologies where funded by governments around the world.

> I can't believe the amount of time I've wasted on Linux just trying to get my sound card to work, or a printer.

First, if these issues exist, then that is one more reason to fund it. Second, when did you try a modern distribution the last time? It has been a long time since I had problems like that. Usually, when I buy hardware and it doesn't work with free driver I send it back because it's non-functional in my eyes. It's very rare that I need to do that.

> Also, I really wouldn't waste children's time on FOSS. "Here's how to spend a week on Stack Overflow fixing your printer" is not a core subject.

Cleary, the hypothetical printer issue is not what should be tought. Good upstream support is the manufacturer problem, and regulation for labels of driver support would help a lot.

What should be thought are not specific programs but programming and the value of FOSS. Maybe, a few selected and curated and sufficiently funded FOSS programs can be presented to show how common problems could be solved.
Then you would be able to downgrade your OS version, they don't want that.

Edit: Apparently not, you can turn it off so it doesn't require network. See the other comment.
But much harder to program and not effective for speeding up quite a lot of software.
Roe isn't based on the commerce clause, so overturning Raich's Commerce Clause application wouldn't be particularly relevant to it.

OTOH, dodging the Commerce Clause and adopting a broad 10th Amendment interpretation might affect Roe, but a 10th Amendment interpretation powerful enough to affect otherwise Constitutional federal legislation (which Roe is not) would have broad and severe effects on federal power generally, far beyond marijuana policy and Roe.
This is probably the only possible answer to fake news. With human censors one can always cry “bias!” but a publicly published open source AI would be irrefutable.
Guys, let me compliment you on some nice work here. Maybe there's still a little spit and polish needed, but the important point is it moves the ball forward.

Sometimes there's so much passion here around implementing cool new things that, while those things are important, it can make it easier to forget that simplicity, and better outcomes on average, are not in any way lesser technical advancements. Simplicity also requires good taste to boot imo.

On a side note from one of your posts, doesn't it make you chuckle a little to think "If you've already decided to implement Javascript Object Signing and Encryption (JOSE), whether you want JSON Web Tokens, JSON Web Encryption (JWE), or JSON Web Signatures (JWS), you should question this decision. You're probably making a mistake.", given the massive growth they've seen over 2-3 years in some very high profile cloud systems? But what to do...onward and upward then. :)

Finally I appreciate the dispassionate viewpoints, i.e. "I'm not attached to it in some way (I never am, to technical decisions)". Always to pleasure to work on hard problems and debate with folks who have adopted that perspective.

Anyway, well done.
That sounds like a number that would be fairly closely guarded by anyone who could answer you :/
Genetics has something to do with my interest in genealogy, but honestly the direct familial connection is what is so interesting to me. Sure, I never met my great-great-great grandfather, and his genes probably have a negligible effect on my life now, but it's fun to think about his connection to me: My dad was really close with his grandfather Henry, who died when my dad was 12. Henry, in turn, had been very close with HIS grandfather, John, who died when Henry was 12. John fought in the Confederate Army for four years, got shot twice and stabbed once, including at Gettysburg.

My thoughts and beliefs have been greatly shaped by my dad, and I'm positive my dad is who is is at least partially because of his relationship with his grandfather. Carry that backward, and I'm only three degrees removed from a soldier in the Civil War -- it's not impossible to think, completely independent of genetic inheritance, that some of my personality quirks or principles worked their way straight to me from someone who was born in the 1840s.
Same -- still using it. Definitely recommend.
> "I'd prefer it to be builtin too"

Same, I can see all sorts of nefarious uses for this service (not necessarily by the guy who built it, more so by trolls who can use it to target HN users). If I really need something like this, I'm competent enough to build and host it privately for my own use. Given I'm not even a programmer by trade, I'm sure that last statement is even more true for the majority of users here.
This is a very good idea, I'll work on that thanks!
> For a consumer system this is true if (and basically only if) you're running a web browser on that system.

… which is pretty close to universally true, especially when you consider how many people use apps which are based on something like Electron. If those apps load code or, especially, display ads there's JavaScript running in places people aren't used to thinking about.
They knew of the issue since June. Now that the patches are out it'll be hard to regain the performance. I doubt they are able to issue a microcode update within the following months. Otherwise large clients such as AWS would have implemented that instead.
DigitalOcean: A Message About Intel Security Findings