skysight-inc/HackerNews huggingface dataset:
Right. 50 pounds down here. It took 6 months but I have stayed keto and kept it off four more months since starting. Losing 6 pounds the first week was obviously water weight but wow, that is the way to start a diet.

I saw one good description of what is going on: You don't ever lose fat cells just the amount of fat each one stores. When you enter ketosis your cells give up some of the water they were using as place holders for the fat they are waiting to store. Thus the periodic "whoosh" that ketorers report. Every few weeks you notice you have to pee a lot and you lose a few pounds.
This is irrelevant. Before his death, Tesla told the driver that there was no issue with the autopilot feature. This likely contributed to his continued use of the feature. That feature, because of the same issue (which Tesla denied existed) killed him. And now Tesla is saying that there is an issue, and that it's his fault for using the system.

Whether or not it's a full self-driving mode, or if it's an assisted auto-pilot, or even if it was just some lame GPS navigation, is completely irrelevant. The bottom line is: there was an issue that was reported, Tesla denied it, the man died because of that issue, and now Tesla is contradicting themselves by saying there is an issue, but are deflecting blame.

At this point, Tesla is eroding the ability for anyone to put trust in their cars. What if you have a Model X and one day it unsafely opens the doors while you are driving on the highway, so you take it to the dealer but they say "nope, can't replicate the issue, your car is safe to use". Are you going to believe them? Why, when they've just confirmed that they have a track record of being wrong?

Oh wait, that already happened: https://www.reddit.com/r/teslamotors/comments/6giiao/my_mode...
I'm "hourly attentive" to email, or maybe "convenience attentive" if I'm waiting in line or something. For me, turning on notifications for email would eliminate the distinction between email and chat. I understand some people use it that way, but I expect lots of folks keep the distinction.
The problem with insider trading is that it creates perverse incentives. It, in itself, does not necessarily defraud.

If I work for Apple, and I sneak a glance at their balance sheet, and short its stock, I did not rob APPL shareholders. It's still illegal, and insider trading (Because otherwise, I'd have an incentive to actively sink the company, while benefiting from a short.)
> Is it, though? Autopilot has never in the history of those systems meant hands off controls, attention off driving. Pilots with their autopilots on in airplanes are still flying and watching gauges.

You are correct about the history of autopilot systems in planes, but when it comes to mass communication technically correct is not necessarily the best kind of correct. I wouldn't assume most people are aware of how autopilot systems work in planes.

Edit: just to make it clear, I don't believe this accident was caused by any confusion about the name. Rather, as pointed out by others in this discussion, I think the fact that the system works great for long stretches (some say they never experienced any problems) makes it exceedingly hard for drivers to remain alert. The brain's optimization tendencies are so strong that I think systems relying on people to stay alert when the action-effect-evaluation feedback loop is broken are inherently unsafe. My point is that with suboptimal messaging, Tesla is making it harder for themselves to keep the public on their side when tragedies like this occur.
Future Hacker News comments when Holmes peddles her new scam:

“You cannot hold that against her.”

“Most entrepreneurs experience failure.”

“She was fined by the SEC. What are you complainig about?”

“I’m sure she’s learned from her mistakes.”
I think the solution is to hold Elon Musk/Tesla liable for their misleading statements on FSD, Tesla Network, AP2 and their timelines about future capability.

Future promises if made should come with renaming the product to highlight its capabilities.
Well, does GM actually, officially allow users to cross arms in their car on live roads, or is it all artistic license?
Yeah, the git cli in its default settings is very hostile towards that information ^^.

Pull actually works the wrong way around – it merges the remote branch into the local branch and then pushes that as the new remote branch. So if you follow the first parent, you land in the pullers local part and bypass everything he merged.
Using Credit Cards to Travel for Free
Do you look at the keyboard or are you just a self-taught touch typist?
The issue with the statements from Tesla is that they seem to prioritize PR and obfuscation before actual relevant factual statements.

The fact that the driver received disengagement warnings prior in the drive is not very relevant to the accident per se. Might as well say the driver has received multiple disengagement warnings during his ownership of the Tesla. It is not relevant to the actual circumstances of the accident. Note that they do not say "he received disengagement warnings right before the accident and chose not to respond". Tesla instead says that his hands were not detected on the wheel 6 seconds prior to the accident. Okay, so thats the case, but obviously the Autopilot system allows that to happen, as disengagement warnings were not active at that time, therefore THE SYSTEM WAS OPERATING WITHIN ITS ESTABLISHED BOUNDS.

This leaves it down to, the autopilot system drove into the barrier while the driver wasn't paying attention, but was operating the vehicle within the defined bounds of the semi-autonomous system, but violated the parameter of "pay attention to the road and be ready to take control". He did not receive any system warning before the accident, he just simply chose not to correct the system behavior before the accident happened. Everything else is just trying to kick up dust and obfuscate the facts of the situation it seems.

The issue with Tesla's semi-autonomous system and to a certain extent, other systems, is that there is a poor boundary between system responsibilities and user responsibilities. This causes issues around the boundary where sometimes the autonomous system will accomplish something, but sometimes it can't and the user must. Because of this fuzzy boundary, I think its almost more important to invest into disengagement logic, equipment, and programming than pure self-driving technology. A good example of investment into this arena is actually GMs Super Cruise, which seems to have MUCH better user engagement detection and much sharper boundaries than systems like Tesla's
DaVinci resolve 15
If I am reading this correctly, there is one SI submission, SIKE. Microsoft is intimately involved, although it appears that Amazon, Texas Instruments, and Infosec have made major contributions.

https://github.com/Microsoft/PQCrypto-SIKE
Just took the words out of my mouth, thanks ^^
Im in a similar boat. I am not a touch typist and I can do around ~70-80 WPM, its never been a problem for me (been coding professionally for like 13 years and been coding as a hobbiest since I was 10 years old).

At this point I'm not sure what benefit I would get as I spend far less time typing now.

That being said, I almost want to learn just so I don't have to have this conversation anymore when this post inevitably pops up every couple of years.
Not really, that's how Windows works too since Vista.

https://msdn.microsoft.com/en-us/library/windows/desktop/aa9...

And it's what enables effects like this in Windows 10:

https://docs.microsoft.com/en-us/windows/uwp/design/style/re...

Disclaimer: I work for Microsoft
ART is a thing since Android 5.0 and it has become quite good.

Even the parts written in straight C and C++ code have issues in performance woes on Android, as everyone that has wanted to do real time audio on Android painfully knows.

The whole architecture has been a mess.
I think it's possible that keyboard usage is decreasing at this point. My nephew's elementary school stopped offering typing classes, however I'm amazed by how quickly he can type on a touchscreen!
How to spot a fake review on Amazon
They've just started sending out SLA credit notices:

-----

Hello,

On 2018-04-01 at 7:08 UTC, one of several storage clusters in our FRA1 region suffered a cascading failure. As a result, multiple redundant hosts in the storage cluster suffered an Out Of Memory (OOM) condition and crashed nearly simultaneously.

We have identified that you, or your team account, were impacted by this incident and will grant an SLA credit equal to 30% of your entire Block Storage spend for April, not just usage in FRA1. This credit will appear on your account at the end of April, and will be reflected on your April 2018 invoice.

We apologize for the incident and recognize the impact this outage had on your work and business. You can read the full detail of our public post-mortem here: http://status.digitalocean.com/incidents/8sk3mbgp6jgl

Thank you,
Team DigitalOcean
Please tell me where you work and how I can get a job there. Your work's culture is very rare.
There as rather simple technological solutions to achieve this company-wide:

Configure your SMTP server so that any email sent after 8pm is only sent to the other party at 7am; with a similar rule during weekend. [I am not sure how to perform this in practice with common SMTP servers, but there is not technological barrier here]

So employees can still "get work done" after hours, but they don't receive new tasks. In case of emergency, use the phone.

NYState could implement this in law. Emails sent at night to employees that are off-duty (i.e., not explicitly paid for night hours) should be blocked until the next morning. Much easier to implement than GDPR :)
From what I've read, GM is less confident about their system's ability to operate under as wide a variety of situations as Tesla's does. Yes, it operates in a hands-free manner, but does so only on well mapped uninterrupted divided highways, and even then it requires the driver pay attention. It does this by way of the IR lights and camera mounted in the steering wheel, which only allow the driver to look away from the road for a few seconds at a time.

Given the bad press that Tesla gets after any Autopilot driven accident, GM seems to have made a safe choice here.
Sometimes if I'm working on the weekend, I'll save the emails in drafts and send them out Monday morning, because while it's ok for me to work on my company on the weekends, I want to make sure my employees know that they are allowed to have a life too.

It’s hard to imagine sama saving emails in drafts solely for image rather than being responsive immediately.

What if a law forced him to?
I'd be down for an Erlang-like OS ABI (or, to put that another way, a Windows-GUI OS ABI, but for even non-GUI processes): just message-passing IPC all the way down. OS signals, disk IO, network packets, [capabilities on] allocated memory, [ACL'ed] file handles, etc: all just (possibly zero-copy) messages sitting in your process's inbox.

Of course, it's pretty hard to deal with a setup like that from plain C + libc + libpthread code, so OSes shy away from it. But if your OS also has OS-global sandboxed task-thread pools (like macOS's libdispatch)—and people are willing to use languages slightly higher-level than C where tasks built on those thread-pools are exposed as primitives—then it's not out of the question to write rather low-level code (i.e. code without any intermediating virtual-machine abstraction) that interacts with such a system.
Would be super great if anyone would help for instance with the README, as I'm no english native speaker. Other than that every kind of suggestion for improvement is greatly appreciated :-)
> You pass around objects instead of trying to parse strings and things.

That can't be very good for debuggability.
It seems reasonable to want to build a modern OS from scratch; Linux has survived and adapted remarkably well, but it has many aspects that are rooted in the past and just can't be shaken off. The world has changed a lot. I just hope Fuchsia remains truly open-source and doesn't become a power-play by Google.
I hope they'll add Walt
What if Smith and Wesson announced that their guns will update over the air and suddenly the bullets will become non-lethal and infact save lives as they'll include water from the fountain of youth?

Because I don't see much difference from how Elon Musk makes misleading and clearly false statements.
> You don't need to tell people to be polite (and you shouldn't). If someone isn't everybody will notice it.

Unless it's done in private. If someone is a jerk to me in private (over email or Slack or whatever), what do I do?

If I'm contributing to a project without a CoC and someone is a jerk to me, I'm much more likely to just contribute to a different project, or start my own fork, or just stop contributing to open source entirely.

Projects with CoCs have a stated procedure in place for dealing with abusive contributors. That's what the whole thing is about. Of course you shouldn't have to tell people to be polite, but that's not how the real world works. There are jerks everywhere, and more often than not they're going to express that in private.
Right, but you presumably aren't one of the stereotypical anxious busybodies the article is appealing to with the sentence I quoted. Anyone like that wouldn't disable the on-by-default push notifications, I'd assume. What am I missing?
Street Fighter may have disappointed fans of the series, but as an action movie I think it's pretty enjoyable.
I've made countless batches with my daughter and her friends.

One tip: instead of making a borax solution in hot water which can irritate the skin of some, use a contact-lens solution that has a borate-type preservative it in it. It might cost a little more, but it's a lot safer on skin and easier to handle (comes in it's own bottle with a cap).
Thanks for the feedback. We're still exploring all of these thoughts as we iterate and learn, so I don't have absolute answers here. Some thoughts, though:

> Yet another gaming community; it's very interesting how these continue to crop up but never end up sticking around.

We'll continue to see a lot of them crop up and die. I think we'll also see a lot of them crop up and succeed. Gaming is too big now for that not to be the case. The fundamental belief that drives this is that gaming teams will continue to be core to online gaming well into the future, and the question of if there will be a ubiquitous platform for their identity and team organization is more of a "when" than an "if" question, for me. Someone will crack that eventually, even if it's not us.

> You probably won't tell me, but how did you get funding?

Happy to share, there wasn't really any magic to it. We just explained the vision I described above and worked really hard to make something that a lot of people loved, and had some data to show that. I think a lot of investors know esports are big now, will be even bigger in the future, and they see the gap that we're trying to fill.
Now have the same team map other parts of the world! I bet these elements are not as rare as they are thought to be.

I grew up like ten minutes from where nine natural elements where first identified:

https://en.wikipedia.org/wiki/Ytterby

Pretty sure that place isn't globally unique, but the people identifying the elements were.
Exactly this. Assuming that shadow-profiles are derived on-demand, the only way to "delete" one would be to delete the datapoints it's built from.

We know that facebook can use contact info to identify clusters, right? Suppose that I don't have facebook, but a bunch of my friends do, and facebook has all their contacts' phone numbers. They can infer the circle of friends of "whoever owns phone number X" using just this info. This is probably not the extent of a shadow-profile, but I think it's a plausible stab at the underlying mechanics (repeat again with email, with browser fingerprint, etc).

In order to "delete" my phone-shadow-profile, facebook needs to remove my phone number from their internal copies of my friend's contact lists. They also need to keep a copy of my number in a "do not shadow" list, or else they'll just add me back in next time they scrape my friends' contacts. Armed with a such a do-not-shadow list, there's no need to actually do the deletion, rather than simply marking the deletion.

So, assuming my speculations of the nature of shadow-profiles are about right, the only way to really avoid facebook having one is to register your fingerprints with them, so they can tell which parts of their data are you, in order to know not to use that data to draw inferences about you.

That, or give up on drawing inferences between disparate data-sources at all.
Google also can't be convinced to carry a project through to completion and release /salty.
Well, the Tesla had the same amount of visibility and drove straight into the barrier. Victim blaming doesn't get Tesla off the hook.
Nice! This looks pretty good. I’ve been working on the CMS for a side project and have gone out of my way not to style or design anything (because I suck at it).

I was going to circle back around afterwards and find a good theme/template.

I did notice tables went off the side of the screen on iOS.

Looks swanky otherwise! I’ll see give it a swing!
Forking creates too many issues for general public adoption.
> So POSIX support is a given on most systems. Why replace it with something that breaks existing code?

POSIX says that usernames and uids can overlap, and if a program takes either, it should accept the other a well. And if something could be a username or uid, it should be presumed to be a username, and resolved to a UID.

Now assume you have a user "1000" with uid 2000, and a user "2000" with uid 1000... you can see where this goes.

And this is why the BSDs have broken POSIX compatibility and require uids to be prefixed with # when they’re used on the CLI.
I wouldn’t be as quick to blame the downfall of Zipcar’s quality on deliberate sabotage. I began using them in 2009 and even back then it was cheaper in a number of instances to rent a car for more than short periods.

Where ZipCar excelled (I haven’t used it for a number of years) was being able to not own a car and effortlessly get one for an errand or quick trip.

These days I rent far more often, and even being part of elite programs and being very experienced with the process it is still far more of a hassle than simply approaching a car you’ve booked online, tapping your RFID card and driving away.

I think ZipCar theoretically still has utility for that type of use-case.

A big drawback also was the inability to select a one-way trip. Sometimes you want to get somewhere and stay for a while, and it’s simply not cost-effective (or efficient) to tie up a car for 3 or 8 hours vs. just driving there.

I believe this is a use case that Car2Go addresses, although I haven’t yet used that.
You can't just blanket say everything is irrelevant because it doesn't fit your narrative. If he reported the system wasn't working, why would he continue using it especially in a known problematic area?
If the improvement is aiming for 2 years, what is it now? I understand that some of these things are broad and / complex, but dragging it out only dates the discovery process. At the very least, phase the projects.

That said, what about completion time? Can that be effected in some positive way? Or will it continue to be bid low and just keep tacking on the overuns?
Cruise Automation: Why our people matter most
It seems the underlying problem is that people who generally produce reasonable work productivity using email also likely are employed as salaried, overtime-exempt.

I don't think it is reasonable to craft a law saying you cannot communicate with your employees after hours. I do think it is reasonable to update the overtime exemption rules to allow for reasonable "time off" and that after-hour emails need to be compensated somehow, if the reading and responding to that email is required as part of your job. EDIT: And such regulation should also require disclosing to the employee that they are not required to read and respond to emails if they are not being so compensated.

I am also an executive, but definitely not to the level of your profile.
Came here to say exactly that. Cookies are only capable of tracking users across the web because giant companies have managed to dupe site owners into adding code to their site.
> But some bloat is the patina that all succesful systems take on over time.

What a nice analogy.
Many of those premises sound fine though. Jean Claude Va Damme mad three different movies with the plot of Bloodsport, which in the first place wasn't much different from Enter the Dragon. Plenty of people enjoyed them.

On the other hand, Rampage seems like something that's hard to work into a movie.
You're missing the point of reimplementing some or all of the standard libs. Similarly, disabling C++ exceptions and RTTI is a very common practice in gamedev.

Sometimes you reimplement a certain standard class (vector, string...) to adapt it to the very needs and usage patterns you have. Standard libs tend to be too general, plagued with allocations and other useless (in this specific context) behaviors that may negatively impact your performance/cache friendliness/memory fragmentation...

I agree a simple tiny game doesn't need all of these but when you need to squeeze all the performance you can there's no other option.

So please, do not just dismiss all the gamedev wisdom like that.
The Air Force and Navy both need (or want) a light, stealthy fighter-bomber. Historically, there's no good reason not to just make the Air Force use the same planes the Navy does. They just never actually agree on which plane they want and it's easier to let both services have their own way.

The only tricky part is that the Marines need a STOVL close-air-support bomber to replace the Harrier, and the Royal Navy needs a STOVL fighter-bomber to replace the Harrier since they don't have full-sized carriers. There's some commonality between those requirements and the Navy/Air Force requirements--there's some rationale for stealthy CAS planes, and your STOVL plane needs to be a full-featured fighter-bomber for the Brits to want it anyway--but STOVL is a lot more complex than normal horizontal flight.
This looks great. Can’t wait to try it out.
What do you mean the companies making the rules? Do you mean laws or rules like "you have to check your email after 5 pm"?
> There's a reason that most non-software industries (think aviation, medical, most car manufacturers not named Tesla) move excruciatingly slow when rolling out new features.

They do and I'm largely glad they do but I think you can go too far the other way, delaying advances that can save lives can result in more lives been lost because of the delay.

There has to be a middle point, you want new drugs (for example) reaching the market but with the risk minimised to a degree that is acceptable, you simply can't reduce the risk to 0.

All that said I'd be fascinated to read the assurance approaches that Tesla uses before pushing out updates to what is essentially a computer on wheels attached to batteries.
Intelligent men and intelligent women ultimately have to make a realistic assessment of their odds of meeting an intelligent partner with a compatible personality type, and come to the conclusion that they will ultimately either settle or die alone. I don't know any guys that I would consider extremely intelligent that haven't totally abandoned the childish dream of finding an equally intelligent woman. It's on par with never starting a career because you're expecting to win Powerball Lotto. Less-intelligent people literally have perfect intellectual matches everywhere they look, and they can realistically expect to find 'soulmates' that they can marry. Intelligent people are lucky if they can find an intelligent friend to really communicate with and someone else that they can tolerate long enough to marry and procreate with separately.