codefined

This seems to be one of the problems with USB-C implementations, barely any of them seem truly compliant? I remember this comment from a week ago[0]:

> In watching the evolution of USB-C over the last few years, it seems like it's extremely hard to implement correctly with the huge number of modes, alternate modes, and power delivery in the spec. > When you connect two USB-C devices today, you have almost no idea what is actually going to happen, which device is the master, and which way power will flow.

[0] https://news.ycombinator.com/item?id=16706803

It appears that the current figure is sitting around 10 vehicle deaths per billion vehicle miles travelled.

Which seems unbelievably low. I'm getting these figures from this Wikipedia graph[1]

[0] https://en.wikipedia.org/wiki/Transportation_safety_in_the_U... [1] https://en.wikipedia.org/wiki/File:US_traffic_deaths_per_VMT...

Being naive here, wouldn't a massive help be to not focus on detection of DoS/DDoS attacks but instead to focus on validating that IP addresses come from within the range of addresses being served by the ISP?

It strikes me that this would prevent a massive number of amplification attacks.

Honestly, I feel this would happen to most systems that have the following properties:

- One size fits all, (clients can only run one language, JS, so it has to fit many use cases).

- Popular (JS seems to be the most popular language at the moment, having beaten Java on most scales in the past year).

- Not owned by a corporation, (whilst probably a good thing, this does lead to "design by committee" issues.

- Backwards compatible (in all this time, only a minimal amount of breaking changes).

I'm not sure if this post is sarcastic or not, you realise he's giving away something like 99% of his money?

This comment assumes you're being sarcastic. "Halon's Razor" as a concept is pretty popular, it's not that out of the ordinary to expect for you to know (especially if your peruse this site). Add to this with the fact that you're on a computer, you can select the text, right click --> search on <engine> in probably under 3 seconds to find out what it is means that it's fair just to type the phrase and not have to add on the adage that it represents.

The fact there are no pads or helmets actually makes Rugby safer. In American Football people rush into each other at almost full speed, which can lead to serious brain damage. In Rugby, if you were to rush into each other at that sort of speed you would become seriously injured, so brain damage isn't as prevalent.

Can confirm, Chrome stable / Firefox stable on Windows 10.

I imagine the cost of the data, in this case, is negligible when compared to the cost of salaries and benefits for employees working on it.

Considering they have the ability to pick from thousands of hospitals and universities (the latter being where they actually got the data) they probably have a fairly large amount of leverage to keep the costs low.

I feel like Google have the power behind them to try to at the very least data mine the free text data for information. Possibly they even have enough sway to convince doctors and other individuals towards a form that is far less random, or at least to provide a platform to share information between patients. Note that NLP seems to have come a long way in five years, who knows where we'll be in a decade or more.

In terms of incorrect records, I'm not sure this would be a major problem over a large dataset. Making this up, but I imagine the range of errors is fairly random across all fields and with enough data you can always identify an approach that appears to save a life more than some other approach, even if the diagnosis is incorrect.

Although I totally agree with you that this is going to be an enormous challenge for Google, I feel like it would be underestimating them to assume this has very little hope of succeeding.

Isn't that a logical move? Allow a single department to both gather and act on the information, rather than disparate departments that have to try to work together?

The issue comes from the fact that I don't really want to have to download gigabytes of data over my network.

Especially not if I just want to quickly check my messages from a web browser.

E2E encryption fails on a large number of subjects when it comes to a chat application such as Slack.

One of the simplest issues I can see is the search functionality, something I use daily in Slack and would sorely miss not having. Elasticsearch requires access to the contents of a message to index it (basic requirement).

Another thing that would become difficult would be adding people to a group, although my technical knowledge in this area is perhaps not massive, my thoughts are that if a user can join a group with another key, surely a Slack attacker would also be able to add their own key?

I'm sure there are many other things that ensure Slack cannot be E2E encrypted since it stops a significant amount of the logic they can do (they would become a dumb proxy), similar to why Google hasn't gone E2E.

How is that different to any other advancements we've made? C is slower than assembly. Python is slower than C. Programmers will continually pick higher level programming languages since it's easier.

I keep on seeing people complaining about Electron here, but it's brought about an age of hundreds of thousands of applications that have compatibility across OS' to do very specific tasks.

I just feel that the ~80MB memory usage and large file size (30-60MB) is inconsequential in modern computing.

Many over-arching issues come from using a language that isn't designed for your use case. For example, writing any programs that require speed to be your goal are not programs I'd recommend Python for.

Other languages also have advantages in certain areas, e.g. Node.JS lets you reuse the same code on the server-side and client-side, something which is great for those wanting to right games that require the server to simulate them and the client to run them.

Even if the language is rarer, say C or C++, there are still many circumstances where it is better to use those than it is to use Python.

I do not foresee any language to be able to be easily usable in every use case, the generality itself would be a drawback for specific user case. There is a reason there are currently dozens of popular programming languages out there.

That's an interesting question. Speed climbing[0] is for 100% vertical climbs and seem to attain speeds of 6,000+ft/hr rate of ascent for only a minute. Over 30 minutes, people are very close to climbing a kilometer in vertical height[1]. One of the fastest times that author found was 0.568m/s (6708.6614 ft/hr), with an elevation of 16.4 degrees.

I'm going to assume it's roughly similar for 60 minutes, as well as 30 minutes.

[0] https://en.wikipedia.org/wiki/Speed_climbing [1] http://www.irunfar.com/2012/04/the-30-minute-kilometer-a-loo...

I've had this with a large number of media.ccc.de pages (which seems to be popular on Hacker News recently [0]), but they all seem to load slowly.

It seems odd since this post only has 6 points, which suggests it's not down to the Hacker News effect. Plus I'm geographically within a hundred miles of where the IP resolves to (195.54.164.138).

Anyone else loading slowly?

https://news.ycombinator.com/from?site=ccc.de

False & true aren't great terms to use for an "either or" question.

This seems oddly specific, am I missing something?

I'm not sure, my opinion of Webpack is completely different.

We used a ~20 line configuration file found on Gist to replace our ~400 line gulp build. It resulted in better optimisation, less hassle and "Just Worked™".

We wanted to add a few more things to our configuration, literally just took running `npm install some_package`, followed by requiring it in the webpack configuration.

It might be against terms of service, but I very much doubt it's illegal.

Ten minutes of Googling shows nothing about running servers from my home being illegal.

How would they know you're hosting a server? I mean, practically speaking a server is just a computer you leave running 24/7.

Please could you provide some evidence of your statement, otherwise I don't think it's quite true.

Personally, I'd suggested cmder[0]. It's much more light-weight than MobaXterm and doesn't require installation.

[0] http://cmder.net/

I think the issue is that with the rise of VPNs, you're now looking at >1% of users being from a mislabelled country.

There was a report they log when you open apps, close apps, change state, etc. But as far as I know no backdoors have been found that are specific to OnePlus (and not bugs in Android)

Cool project! Since this seems like something you've created yourself, can you share what stack you used to support both iOS and Android?

I quite like this[0] article on what AWS products should have been called.

[0] https://www.expeditedssl.com/aws-in-plain-english

This is for FB messenger, not FB posts. Messenger has no such rules for no pornography. Plus, this allows them to be proactive, rather than waiting for people to report posts.

As someone who has just spent the last 15 minutes escaping to HN from Rust due to reference errors, this was amazingly useful and actually helped me fix the error I was getting.

Isn't this incorrect? The developer edition appears to be built from the beta version. You get some alternate switches turned on, such as extensions no longer required to be signed & other stuff, but none of it is specifically new.

Considering there are limited use cases for pointers moving at different speeds in other fields, no, I wouldn't say it would be easy.

The idea itself, once you hear it, instantly makes sense. But having the ingenuity to thinking of it during a stressful period shouldn't be used as a measure of how good a candidate would be for a position. Especially considering there are hundreds of different ways of approaching such problems.