skysight-inc/HackerNews huggingface dataset:
I am French but here is my take: I think you need to tell that your country (UK) has an income tax treaty with the US about taxes.

What it means is that you will pay your taxes in your own country (UK) instead of US.

I also think those links are relevant, but really filling the W-8BEN-E form is quite simple, I did it several times and never had a problem:

https://www.treasury.gov/resource-center/tax-policy/treaties...

https://www.irs.gov/pub/irs-pdf/iw8bene.pdf
There is a drinking water appliance in our breakroom that will not dispense water if it can not reach the internet.

This is not the world we should be engineering. Actually, I would say, this is not engineering.
The Personal Cloud is what we should be building for ourselves. Servers running in your closet at your house.
What I am talking about is things like this:
https://mail.coreboot.org/pipermail/seabios/2015-April/00902...
And this is where "software" diverges from "engineering". It's not a conspiracy, it's negligence.

Bugs happen in architecture, aircraft, etc. too. the difference is that the actual engineers are paid to have a precautionary approach -- and spend significant resources -- to actively prevent bugs from making it into the final product.

Amazon and your team has built a great product (I have one and make moderate use of it, have even considered building some skills).

But, you have planted a full-on bugging device in millions of people's homes. Done by a government, this would be cause for war or revolution. This is serious, and you need to treat it much more seriously than you obviously are. Every 'skill' does not require the same minimal levels of security and verification, some, like this one, require much more, or should be forbidden outright until such security can be properly implemented (and yes, this should probably include calls only to pre-configured whitelists, intent confirmation, etc. and to any manager that says "that's too inconvenient to the user", the response is "screw you, it's critical").

You call yourself an "engineer" at least twice, and claim that you take privacy "extremely seriously". The evidence from this incident and others noted in this thread indicates otherwise. Clearly, insufficient resources were allocated to figuring out the potential failure modes of a "call skill", and preventing them.

All due respect, but your team needs more of an engineering approach than you have. This entire "it's gotta ship yesterday" mentality in the software industry used to be just inconvenient. Now it's getting dangerous. Please help stop it.
It's unfortunate that a frequent response is "so what? who wants those jobs? I sure don't, so I'll decide for these other people who I assume need me to"

This is the thinking that leads to the shuttering of harsh garment factories in the developing world so the employees can go back to child sex work.
Not exactly. This maps shows insurance claims related to natural disasters, not incidence of natural disasters. Big states out west have very low population density as compared to spots east of the Mississippi. If a raging forest fire or severe storm happens on a big stretch of BLM land in Nevada, nobody's going to make an insurance claim about it.
Ah! I didn't realize there was a newer law. It seems dumb :P
It is the NTSB's goal to include all contributing factors in their investigations. Remember that the NTSB does not assign liability or make regulations, it simply serves in an advisory role. Their reports are as thorough as possible in identifying contributing factors so that safety recommendations can be made that address as many factors as possible.
I'm sad that I had forgotten about StumbleUpon, and now it will be gone. I found so many small interesting sites that way.
That was not my takeaway. My takeaway was that these are places where no one is, and thus there is not a significant amount of damage.
I always wanted to have an air compressor running every day on my otherwise quiet property.
I actually own an Iphone - why?
And rules out use on snowy roads.
It's not just that they knew it would bend. The document shows that Apple also knew that bending from normal use would detach the Touch IC chip and render the phone unusable. They secretly addressed this in later iPhone 6 runs ("after internal investigation, Apple determined underfill was necessary to resolve the problems caused by the defect") while continuing to charge affected users $350 (generously reduced to $150 after media attention) to fix their bricks.
Future engineers growing up today will read about this incident alongside the Therac-25 and the Tacoma Narrows Bridge.
Seems a bit more convoluted than in D.
I love stories like these. Reminds me of The Last Question by Isaac Asimov -- http://www.physics.princeton.edu/ph115/LQ.pdf
I recently stayed at a house which had an alexa device. In a conversation where I said the words light switch several times Alexa beeped and responded to me each time. I think most of us just believe Amazon when they say "Alexa responds to its name" and don't stop to consider the possible failure modes. We want to believe it can understand our words, when it's really just guessing. Over long enough time it's inevitable that it will misunderstand you and do something you don't want.

Still, I wonder how it heard "record this conversation and send it to someone on my contact list".
that is a very abnormal experience. Larry Wall has personally helped me with at least two junior issues over the years by just randomly answering in general forums.

FWIW perl6 takes extra special effort to be nice.
Depends on the country. I work in a secretive company that still discloses lots of financial and personal information, including CEO salary and private addresses of board members because local regulation requires it.
Yeah, not 300 a month in groceries, but you can write off your internet bill, you phone bill and all that.

Obviously if you can get an employer match for retirement and good benefits that's true, that's a huge part of compensation that's not taxed.
As a resident of Utah we have our own environmental problems.

https://www.sltrib.com/news/environment/2018/01/09/utahs-air...
What is this alleged 'conspiracy' story? An Amazon device recorded a private conversation and transmitted it to someone else, and it did so without the user's knowledge or intent. That actually happened.

How it happened is only relevant to the engineers who build and maintain the thing. I, on the other hand, could not care less how it happened, and the fact that it did happen is reason enough never to buy one of those infernal devices.
> I don't disagree, but the light ring is also important to know that it actually heard your command. Having it on all the time would make the UX much worse. Unless it was a separate light.

I see that, I think it would be best as a separate light.

I think product UX has drifted too far towards blank monoliths; I know I wouldn't mind a few more blinkenlights :)
Relevant xkcd [1]. The map would be quite a bit more informative if it was normalized by the value of all assets in each region. Population density could probably be used as a first approximation if such information is not [easily] available.

[1] https://xkcd.com/1138/
This is the kind of argument that seems really common and I find very annoying. So 'indoor plumbing' is obviously used to provide us with clean water, but the convenience aspect is the indoor part - you can have clean water from an outdoor communal well, instead. Similarly 'store bought bread' is food, but so is home made bread. I just cannot work out if the commenter was being deliberately obtuse or really misunderstood?
When compressed air energy storage comes up, it is always worth remembering PV = nRT, the ideal gas law. And then remembering that things are not ideal.
Are you confident this is still the case? I was watching CW shows on their website this week, and had to sign in with my cable provider to stream the full episodes. I've seen this as fairly hit or miss.
There are generally no job openings for engineers anywhere, because they all rely on headhunters and recruiters.

Try https://perl.careers/ for example.

I first heard of them from this slide deck that any developer, regardless of tech stack, should read: https://de.slideshare.net/perlcareers/how-to-write-a-develop...
> You couldn't drive a car if you had to constantly break [sic] because objects (such as people standing by the road) were being detected.

Yes, you could -- that's how I drive. Do you not? If I detect a mobile object that might be moving into my path, I slow down to give myself time to react until I am reasonably certain of safety. When doing so I take into account my situation-specific knowledge -- have I made eye contact with the pedestrian and do they know I'm coming? Is the dog on a leash and is the owner being attentive? Does the cyclist seem aware of my presence?

I would expect no less from anyone licensed to drive a car, be they human or software.
> However, the provisions of this section shall not apply to persons (i) wearing traditional holiday costumes;

It doesn't say I can't wear traditional holiday costume outside of holiday, so it should be okay to wear Halloween scary costume all year long.
For me, it's not a matter of performance, but rather of convenience. If I have a deeply nested component that needs to dispatch an action or access a part of the global state, I don't want to have to pass that all the way down through every other component in the hierarchy. The grandparent of a "Like" button shouldn't need to know the details of how it's implemented with regards to the global state, but it's forced to if you pass everything via props.
so why not hash with a very large salt and then throw away the salt?
It’s even worse. Sometimes the packages that the DRAM ICs are encapsulated in have minor radioactive elements in and alpha particles emitted can flip bits.

Interesting paper: https://media.blackhat.com/bh-us-11/Dinaburg/BH_US_11_Dinabu...
Indeed, I'm working on something similar: https://github.com/CtrlC-Root/mdcs
What else uses that?
Thanks, don't know how I missed that, I'll blame my phone screen haha.
I find it interesting that the author added an `isInteger` dependency then went on to not use it.
The ISA doesn't matter very much.

Meltdown is specifically Intel's fault.

Spectre is, AFAIK, inherent to out-of-order execution. So the original ThunderX is not vulnerable, ThunderX 2 is.
JS got a bad reputation from the pre-ES6 years. Before ES6 it really was a dumpster fire. It'll probably be many years before all that bad reputation can be redeemed as people slowly discover how good ES6 is.
The initial coverage was terrible and missed the point completely. So much "it was dark" or "the ped was at fault". I was disappointed, though not surprised.
>For home use you also have to consider that you're basically making a bomb every time you store energy in the thing.

No different than people who have LP tanks outside their homes. Or fuel oil tanks buried in their yards. Or coal bins in their basements. Or natural gas lines coming their house. Or pretty much any other storage method except a dam for your water wheel, but even that can burst and flood your home.
> So is a lithium battery explosion. So is a gasoline explosion. So is a flour mill explosion. So is a wind turbine explosion.

No, they're not all the same.

Compressed air, flywheel, flour mill - very dramatic events.

Lithium battery - much more mild, typically.

Gasoline - it depends.
That's the whole point, they are not being misleading about that, that is the plain, public message they are conveying. They're building chips on an ISA that competitors and partners can implement and extend, which is valuable because it keeps them honest (so they can't just abuse the customers for decades, knowing that competition with them is illegal).
> If the ability for Wikipedia to have a neutral article on a topic hinges on the existence of a single irreplaceable person with that level of dedication, then I think the right solution is to not have an article on the topic.

This kills the Wikipedia.

Unsurprisingly, there are orders of magnitude more people on the earth with some sort of agenda to push than there are people who actually care about having an unbiased and comprehensive Wikipedia, such that the good-faith Wikipedians are spread very, very thin. This is a shitty state of affairs, but it would be far, far more shitty for the Wikipedia community to just surrender to the post-truth dystopian future we find ourselves living in.
Hmm... They created random computer programs and say that one in 10000 turned out to be self replicating.

But that is just because they gave them all the necessaray tools to do so. So the program only has to 1) Set pointer A to its beginning 2) Set pointer B to somewhere 3) Copy from pointer A to pointer B 4) Increase pointer A 5) Increase pointer B. 6) GOTO 1

If you look at the actual instruction set they use, it's even worse. They served the opcodes needed for replication on a silver plate.

That does not count. You could just as well give the programs an opcode that says "copyMyself" and say that creating life is easy because many programs used that opcode.
This is why I unplug my Echo whenever I’m not using it.

Side note: why is it that after years and years of privacy breaches, there has been almost no support to use hardware switches for cameras and microphones?

I would feel 100000% safer using my internet-connected cameras and microphones knowing that I can turn off those devices independently of their host devices and that no hacker can monitor my cameras and microphones, even if they’ve rootkitted every device I own.
> assuming the fabs are using the same metrics

They're not. Nanometers are almost meaningless now.
Media companies fear and photographers love Richard Liebowitz
Yep. I left consulting after working on a project that was a Ferrari when the customer only needed a Honda. Our architect kept being like "it needs to be faster", and I'm like "our current rate would process the entire possible dataset (everyone on earth) in a night, do we really need a faster Apache Storm cluster?" :S

"Resume driven development" is a great term.
No particular single example in mind, but just going through random large leaks:

The Republican National Committee leak (https://gizmodo.com/gop-data-firm-accidentally-leaks-persona...) - all the involved companies which swapped data records to make up this trove would not have had the permission to have much of that data under GDPR.

World Wrestling Entertainment 2017 leak - the leaked data included home and email addresses, birthdates, as well as customers' children's age ranges and genders where supplied, and even ethnicity; there's simply no reasonable reason why they should have had data like that in the first place. It it hadn't be collected, it couldn't have been leaked.

Joblink breach (https://www.identityforce.com/blog/americas-joblink-data-bre...) leaked among other things birthdate and social security number. There's no good reason to ask the birthdate in the first place, and to store the social security number after you've run whatever verification they do (presumably it gets used for background screening).

The big point is that almost always data minimization would have reduced the consequences. Companies keep old data forever, and that creates extra risk; Companies ask for and store more data than they need and that creates extra risk; Companies buy and sell data that shouldn't be bought and sold, and so the data copied in multiple organizations and again, creates extra risk.
To be clearer: You do not need any "foreign tax id" because you will pay your taxes in your own country. The US IRS is not involved at all. What makes it possible is the tax treaty.
Because then the car would break every time anyone approached the car from an angle (which is constantly). Think every intersection ever, every time driving near a sidewalk ever. The car would be herky/jerky as crap.

They should have had it set to spike the breaks once collision was imminent though, that's (maybe) the biggest programming omission here.
The type system might be more powerful, my point is more that if you can bypass it and integrate directly with JS, then people will, and then much of that value is lost. Elm doesn’t have that problem.
"How do we fix bad laws when the wealthy are paying good money for those bad laws?"

The wealthy only account for a small percentage of the overall population. It is very easy to change the law if and only if people care enough to do so. But they don't. Because that involves work like protesting, writing to representatives, organizing community events, and maybe recalling mayors of congressional reps with votes of no confidence. They'd rather pretend to be outraged on Twitter, so that they don't have to actually do anything and instead watch Dance Moms or binge watch Netflix.

The fix is simple conceptually, but it is society's collective refusal to demand that laws be changed or for existing laws that are being broken to be enforced. If society really, truly wanted to fix the whole "paying good money for those bad laws" issue, it could do so relatively easily. But it's much easier for people to pretend it's not that big of a problem since things are relatively stable and people have what they need for the most part. Why rock the boat, right?

The problem isn't just the wealthy - it's all of us in our refusal to demand the law be enforced, as-written, without exceptions given based on wealth or size of the company/organization. Why was Wells Fargo, for example, allowed to just pay a fine for millions of fake accounts that were created which ripped people off? Those are clear cut felonies. If I opened a small, local bank and did that I'd be rotting in Federal prison right now, guaranteed. The only reason the employees that engaged in this and/or the Wells Fargo executives are not in jail is because society didn't demand the DoJ do it's damn job and indict them at the individual level. Hell, society at large didn't even withdraw their funds in bulk. Why would any retail customer hold deposits with an institution like that when this is a proven, admitted fraud, and was well-publicized? That's the real question. And it's the heart of the matter. And that's just one outrageous scam upon the people that comes to mind. There are many more.
ISPs. HTTPS Everywhere and net neutrality laws are both endeavors designed to mitigate ISPs from providing ad networks and/or collecting data on Internet usage.

Of course, Google claims they do this for your benefit, but if it was for your benefit, they'd need to stop doing the same things with tracking scripts. This is how you can tell they are pushing these to reduce competition, not to increase your privacy.
That's because there's no way its intention is to disrupt a soccer game.

That's Ukraine's intelligence sector's way of driving popular "regular Joe" attention to a security interest that they have (by misleading them about the purpose).

What's disappointing is that the VICE article bothers to repeat it.
> What amazes me more than anything else is the fact I'm still UNIXing for food nearly 40 years later.

It's both amazing and disappointing. It's amazing Unix is still used after almost 50 years. It's disappointing we never managed to come up with something better that was also viable.
Fulcro is a full-stack framework that's based on om.next. I've playing around with it for sometime and i feel that it makes the om.next query/mutation model much more easier to use and understand.

http://fulcro.fulcrologic.com/
Well, exactly. Nothing wrong with the sensors, and the classifier was getting consistent pings. This is the critical failure that led to the crash, as much as the shitty final-second emergency non-process.
Sounds far-fetched to me. If you are cleaver, you are also likely to get stuck in a coffee cup billboard or Eddie Haskell will trick you into insulting your Spanish-speaking friend.
Javascript has mutable datatypes and weak typing by default - that makes it easier to write buggy code than making it harder to do so.

To write nice JS, you have to be disciplined and very cognizant of what you're doing. And then you have to deal with the rest of the ecosystem, which is massive and of varying quality.

I recently ran into mutable date types in momentJS, which is a frustrating gotcha - it's not flip the table lose your shit annoying, but it's simply a non-existent issue in other languages.
Vi / vim.
LEARN ROBUST QT and C++ GUI PROGRAMMING: 2D GRAPHICS TUTORIAL
> You don't need to go back to the 19th century for that.

If you're white, you do.

It's easy to forget that today's industry is (still) built on slavery or near-slavery in the third world.
>Devices which are by design always actively listening and sending real-time audio to computers you can’t control

Oh, what devices are these?

>Devices that can be configured to do that, but which you have some control over ... and generally won’t, without some form of consent

Ah, so you mean like "Alex/Google/Apple assistant devices"?
You forgot the "evolution" part.

Also, I think most people would expect that "organisms" (as opposed to the more usual A-Life term "agents") are capable of homeostasis—that random bit-flips of their internal structure, or even another replicator attempting to "eat" into them, won't break their replicating ability. That's one of the (more implicit, oft-left-unstated) bars by which we usually measure whether something is alive. (E.g. it's the one that allows us to separate viruses from dormant bacteria.)
I'd love to go nuclear ... charge your phone once a year?
I love Purescript, but I'd be hesitant to recommend it to anyone without a Haskell background. There's a lot more to learn in Purescript, and I'd worry that it could discourage people who are new to the Haskell family of languages.

I'd advise starting with Elm to fall in love with the development experience and wonderful error messages, and graduating to Purescript when you need more power.
IR camera would probably make this simpler than a visible-light camera. You want to know if there are people in the room, you don't really care who they are specifically.
Still holding out hope for the 2016 Macbook Pro keyboard class action and subsequent repair programs.
I thought this was going to be sarcasm until I got to the end. It sounds like a project where the security would make it too much of a burden.
with significant fuzz factor, agreed. If i'm on the sidewalk and take a step toward the road, should it make the car jerk? Probably not, it's a hard call for passenger comfort. From another angle, think of subway tracks - the algo your describing would slow to a crawl as it crosses every station.
Criminally negligent.
> as an aside, do you know where I can find better documentation? The best I could find was a stack overflow post

https://kotlinlang.org/docs/reference/type-safe-builders.htm...

It's more designed to build DSLs or similar, so you'll find more documentaion/examples in that area of the docs.

> I think this issue with this is what happens when you combine DB transactions with async queries with errors and null handling? It seems like you have to combine 4 different mechanisms in order to do this (receivers, async/await, try/catch, if(null)). Is there some way to do this all with receivers? It seems like they don't really compose.

It's just a closure with a compiler-added paremeter. It can be nullable if you want and exceptions work the same as any other closure. If you want async/await you'd use coroutines. I think coroutines and receivers mix just fine, you'd just make the type a suspending lambda with receiver, but I've never tried.