skysight-inc/HackerNews huggingface dataset:
I certainly can. These kinds of takeovers occur all the time.

https://www.internetsociety.org/blog/2018/04/amazons-route-5...

https://www.itnews.com.au/news/china-systematically-hijacks-...

https://www.theregister.co.uk/2018/11/13/google_russia_routi...

My first experience with BGP hijacking was accidental and not malicious - and over twenty years ago now: I dropped Sprintlink off the East Coast US for several hours. If LE had been active, I could've taken over any Sprintlink-hosted (or downstream) SSL cert simply by performing challenges to LE. If people aren't doing this out of China and Russia I'd be surprised.

LE might mitigate this with multiple checks (across multiple private links) but it currently doesn't do this: LE checks my challenge only once.
> So when you see the reviews of your own paper, there are the exact same challenges for anonymity and ugly consequences as you’re pointing out.

Yes, and this already happens (hence the grudges I was commenting about).

> How does maintaining secrecy for the per-paper improve the situation with respect to “frank and honest” reviews?

By increasing the uncertainty. If I am 95% confident it is you who screwed me last year and 50% certain this paper I got now is yours, I will look at it with a harsher attitude than if I'm only 20% and 20% certain.

If you were to publish all reviews then researchers would have much more information to convince themselves that it indeed is "that guy".

It is sad, and I personally despise it, but that's what it is from my personal experience.

PS: I quit academia after getting the PhD, and this was among the reasons for me to quit. The other major reasons being that I don't want to keep relocating somewhere else in the world every 2 years until I'm in my 40s-50s, I don't like the overselling and result dishonesty in general, and I actually enjoy working in industry too).
MSFT charges 30% to developers as well:

https://docs.microsoft.com/en-us/legal/windows/agreements/ap...
It is odd that you mention this, unless your name is Karl and were at lunch last Wednesday :-), because it came up as something that companies with big cash hoards might actually be thinking about. Consider the notion that at some point a feasible fusion power plant design becomes "known". Then its a question of money to build one or two or 10. And a company like Google or Apple, with a large cash hoard could jump in, build some plants, power their infrastructure on their own plants and sell excess power to the grid, we even gave a name to the company "Google Power and Packet" :-).

The conversation came up because I was trying to fathom why a company would sit on billions of dollars when they could make more billions with it. This idea, that the future will have sudden insights that will take tremendous capital to exploit to create unassailable leadership positions, is not one I had considered. Fusion power, space opportunities, Etc, might be areas where things suddenly create an entirely new need.
Incubation Program: Seeking Startups in the Aged Care or Smart Building Industry
Coordinated development could help wind farms be better neighbors
It's AES: Anything the right length will decrypt to something.
IIRC, the whole transition of Facebook from web app to iOS app was a complete fiasco, from a user perspective.

It was at least a year, perhaps more before the app was usable. It would take minutes for a single page to load in the app. People hated it with the intensity of a thousand suns.

I think you dodged a bullet not getting on board that train wreck.

My guess is that Facebook only decided to go mobile-first when it realized that a phone is a much better personal data slurping device than a stationary desktop computer.
Sorry, I read your comment before my coffee and misread "native compilation" as "static compilation", so I'm conflating two distinct things.
I’m sorry but to me this just looks like Stockholm syndrome all the way.

The approach suggested for Go 2 under bargaining is basically a reverse try-catch at best and a Visual Basic “on error goto” at worst.

Even in their own attempt to explain why try catch is bad they effectively admit it serves a common use-case: A common use-case not handled by Go no less.

This lacking also puts the burden on the programmer which will have to manually handle each and every error, by himself, everywhere, one by one.

Even worse are the priorities given in the language: checking for errors is cumbersome, while ignoring errors is easy.

I’m willing to be proven wrong, but my immediate guess is that this in general leads to more buggy code, not less.
It's pretty useful for libraries, as you don't have to do anything, but still get type safety benefits. It also has really good tooling. If you use anything like ES Lint, then TypeScript does a similar job but is a step up in quality.
While i am a fan, we took it up a notch by allowing users to upload their UI and we write the supporting code using A.I. https://crane.ai/
You can, but this package is very low-level so chances are that it's not a direct dependency for many end-users. A lot of popular modules that may be using this module also don't pin dependencies or don't use lock files so that's one problem. A second problem is that when a npm package is transferred to someone else and then a new version is published, there is nothing notifying you that the package in under new ownership. A third problem is that sometimes users might delete their lock files and re-install dependencies when they encounter some versioning issue and are looking for a quick fix without realizing the implications of doing that.
"We hope that the release of this landmark data set, the largest-ever collection of fully sampled MRI raw data, will provide researchers with the tools necessary to achieve even greater acceleration factors"
I think there's something there for sure. The ability to rewrite the Kanji correctly probably wouldn't be there (I believe it follows a strict pattern?). I was messing around with Arabic for a month and was able to memorize written words and what they meant but could not reproduce it if I wanted to.
Code Shelter, collective of developers that helps maintaining abandoned projects
If this ends up being the right design for fusion, it may be the most weirdly shaped human artifact, where the shape is fundamental to its operation and not decorative. It's far more complex than a mere turbine blade or venturi. Or can anyone suggest a weirder one? (Define weirdness as the Kolmogorov complexity of the shape, within the precision needed to work properly.)
Yeah, being available for a symbolic price with source code has a certain appeal versus the alternatives.
Unless I'm misreading, the point of the quoted text isn't to dispute whether that's true. It's specifically to point out that the 2016 election discussion isn't relevant to whether an Assange trial today would be a bad thing.

If Assange is tried by a Trump DoJ, it almost certainly won't be tied to the 2016 election. Rather, it would be for any of Wikileaks' earlier actions - projects like Cablegate or Collateral Murder. Congressmen have already called for Espionage Act charges over those releases, so it's not a hard outcome to imagine. That would open up a range of alarming questions about handling of classified information, where current practice favors openness and disclosure but the legal situation isn't entirely clear.

Narrowly interpreted, transmitting or even linking to classified materials violates secrecy laws even after those materials leave classified control or become publicly accessible. New York Times Co. v. United States set a precedent in which journalists are not prosecuted for handling or publishing leaked materials. Alongside Branzburg v. Hayes and Lovell v. City of Griffin, which extend press rights to citizens generally, it creates a general presumption that only the actual exfiltration of classified material is prosecuted. But NYT v. US was decided narrowly on prior restraint, and no strict protection for publishing already-leaked classified materials exists.

Convicting someone for publishing classified materials which someone else leaked to them would effectively destroy this protection. Convicting a non-resident non-citizen on Espionage Act charges would create a bizarre situation in which interference with United States military actions by any party anywhere in the world would ostensibly be a capital crime in the US.

Those are the concerns at hand. No matter how guilty someone might be of a specific charge, it's still a serious problem if they're convicted of something unrelated which should never have been a crime.
Please elaborate extensively on the evidence the shows Russia to be complicit in election meddling. I've been watching endlessly for some hint the Russia was a compelling force in anything related to the 2016 election. And the same goes for the alleged Wikileaks connection to Russia, because all I've seen is unwarranted speculation and conjecture in this regard.

Personally, I'm waiting until all the cards are revealed before I solidify my opinion on this.
> By increasing the uncertainty. If I am 95% confident it is you who screwed me last year and 50% certain this paper I got now is yours, I will look at it with a harsher attitude than if I'm only 20% and 20% certain.

Ouch, that’s a good (and depressing) point.
I had to lookup "opinionated" to make sure I understand this statement correctly...

Forth is on the contrary very opinionated. When you want to implement something in Forth, you have to take into account it's very limited ability to support complexity. Which forces you to think about the problem until you can code a simple enough solution for Forth.

It's a severe limitation, but it's one of the rare cases where a limitation is actually a feature. Forth forces its opinion about simplicity on you and that's a good thing in my opinion, because people tend to underestimate the exponential nature of complexity growth: adding a parameter to a procedure at least doubles the amount of unit tests you have to perform on it; add three parameters and that's a 8x the tests.

But it also makes Forth far less fit for task where handling nightmarish complexities is the main topic. If you can't cut the Gordian knot, you lose.
Fixing our inverted retina would be one of the low hanging fruits:

>The vertebrate retina is inverted in the sense that the light sensing cells are in back of the retina, so that light has to pass through layers of neurons and capillaries before it reaches the rods and cones. In contrast, in the cephalopod retina the photoreceptors are in front, with processing neurons and capillaries behind them. Because of this, cephalopods do not have a blind spot.

https://en.m.wikipedia.org/wiki/Retina
You can simply read the "tweet" from the websocket in Devtools :-D
https://i.imgur.com/Z3669oi.png
The cost of the operating system + ecosystem needed to compile is so enormous, it increases income inequality.

A low income person is excluded from developing for Apple. Established, middle-upper class and corporations are the only people that can afford to develop for Apple. Apple is effectively widening the gap between rich and poor.
I love these guys, steadily working through the issues, making steady progress. I think with a slightly different diverter design they could claim to have the worlds first plasma cannon :-).

Pretty insanely complex machine, and really awesome results. Congrats!
Microsoft dethrones Apple as the most valuable US company
What was he compensated with in exchange for taking on responsibility? Without compensation the contract by which he takes on responsibility is not valid.
> If the rich wanted Mars or lunar bases as “escape hatches”, there are dozens of multibillionaires that could singlehandedly fund Musk’s estimated $2-10B price tag for the completion of the entire BFR development program while still retaining 50-90% of their net worth.

This is a bit of a naive view of how wealth and capital expenditure works.
> Linux has a giant user base, a giant installation base, and a giant pool of talented devs willing to take on unpaid work.

And also important: It even has a giant number of paid maintainers, for who this is their main job.

For those the incentive to continuously maintain things is different than for someone who gets nothing expect more work out of it.
Me too please. Email is in my profile :)
I wonder if you could use the DNS resolution cache itself to do the reverse lookup. As long as the DNS cache lasted at least as long as the TTL, it should work.
I get the feeling this is something they always wanted, but the software business model had to catch up to that need.

Thinking back to my first job as an EE in the early 90's, I clearly remember the new owner of the company who had been a CFO in his previous life, trying to figure out a way to move our hardware sales to a leasing-type model. His experience as a CFO led him to the conclusion that larger companies would prefer to bill items to OpEx rather than CapEx for just the reason you said.
>Personally, I see Elm as an interesting development in such a direction, i.e. humane FP language, with the author relentlessly striving for simplicity

Red is another language that is or was striving for simplicity (or resisting the complexity that seems to be the norm in tech nowadays). In fact that was supposed to be one of its main goals. I felt sad when they went down the ICO route for funding, though.

Not sure how FP-ish Red is, though. Rebol, which Red is based on, is supposed to be homoiconic. I like Rebol and Red.

The size of the Rebol and Red interpeters (and Red is a compiler too) and the size of the Red EXEs are quite small, which is another plus. Much smaller than some other languages.
Actually, what you linked states different amounts depending on application type and/or other conditions:

The Store Fee is:

i. Thirty percent (30%) of Net Receipts for: (a) all Apps and In-App Products made available in the Store and billed to Customers on a non-subscription basis, and (b) all Games (and In-App Products in Games).

ii. Fifteen percent (15%) of Net Receipts for any Apps that are not Games (and any In-App Products in such Apps) that are billed to Customers on a subscription basis.

See also this blog post:

https://blogs.windows.com/buildingapps/2018/05/07/a-new-micr...
AFAIK (at least here in Italy) the "standard" is M 30 x 1.5 mm, so the actual thermostatic cartridges are generally that size.

The document you posted (which is very nice BTW) indexes all the existing valves so it makes IMHO the (actually problematic) situation seem worse than it is (because the actual diffusion of this or that type of valve isn't taken into consideration).

Check this:

https://support.tado.com/hc/it/articles/212050583-Con-quali-...

basically all M30x1.5 are not listed as they are directly compatible.

Then, 11 most common types are listed, and for the first 6 ones (the most common among the non-M30x1.5) the adapter is included.

From personal experience (anecdata, so take it with a grain of salt) the "standard" M30x1.5 + Danfoss + Giacomini + Caleffi cover really nearly 100% of what people can find in their home.

These other guys here say that a basic set of adapters cover 90%:

https://www.youtube.com/watch?v=u5KOMFlDbhE

https://s3-eu-west-1.amazonaws.com/common-data-files/static/...
> Why would someone update to a new version of a dependency if they don’t trust the new maintainer?

They didn't know there was a new maintainer, let alone that they didn't trust them.

> In my world, you should have a really great reason to update a third party dependency—“there’s a new version” is not a sufficiently good reason.

Because new versions come out with bugfixes _and_ security patches all the time. In my world (which I'll be clear is not npm), I update all my dependencies to whatever backwards-compat latest version there is, to get advantage of any bugfixes or security patches without having to spend time being aware of every possibly applicable bugfix or security patch. If I spend a day hunting down a bug that ended up having already been fixed in an upstream dependency and I wouldn't have even been subject to it if I had updated... that was a wasted day.

Also if I regularly update, I get security patches without having to have spent time being aware of every one.

This all applies to indirect dependencies (dependency of a dependency) along with direct ones too.

Some of these issues are general to any kind of dependency system. But the particular balance of trade-offs changes in different ecosystems. One thing that seems to be somewhat special in npm is how _small_ and _numerous_ the dependencies are. Npm ecosystem is built upon a large number of very small and discrete dependencies. This has advantages, but the big disadvantage that it becomes very difficult to 'manually' keep track of them, and easy for a bad actor to sneak something bad in.
Operating system program starts user program.

User program does not start operating system program.

Job done.
Dave Winer:

http://scripting.com/stories/2007/04/04/coexistingWithPlatfo...

Sometimes developers choose a niche that's either directly in the path of the vendor, or even worse, on the roadmap of the vendor. In those cases, they don't really deserve our sympathy. It's almost like a game of PR, there's no way you're not going to have a fight on your hands.

Further discussed by Joel Spolsky

https://www.joelonsoftware.com/2009/06/10/platform-vendors/
Freckle is hiring a Designer to help K-12 students grow
I know this is true when the debt is issued by the currency issuer & denominated in that same currency, such as in the case of the United States.

Is that also true in the case of say, Italy's debt denominated in Euros or Illinois state debt denominated in USD? I have been meaning to read Steve Keen's work on this
And touchid. Still sore about that. Maybe I am just too old but the iOS platform died for me as an option the day they yanked touchid out of the iOS ecosystem.

I know this is pure speculation but does anyone think they may bring it back if they can do it under the screen? Also waiting for them to add mouse support to ipad. I am convinced this will happen in a few years (prolly not tho).
>You are getting a significant title bump that moves your career forwards.

The title bump rarely moves your career forwards.
Do you think anyone would publish open source software if it was possible that they might be held liable by people who used services or software which included that code at any future date when they had no say in how their code was used??

Really you think that's realistic, given the astonishingly heavy presence of open source software?
Perhaps slightly unrelated. We've been using the eQ-3 Max radiator heating system (from the article) in our house for three years now to control our radiators on a room-by-room basis. Connected with OpenHAB 2 [1], this has been a great experience.

Given the low price of each radiator controller, the engineering is top-notch. Mesh network works all of the time, the batteries last for multiple years and the installation is relatively painless.

This is one of the few IoT solutions that 'do-not-suck'. No calling-home to China, no unexpected updates and upgrades, no complicated install process.

[1] Openhab Website https://www.openhab.org/
> In Go, if a function returns an error you have to explicitly handle or suppress it.

If a function only returns an error, or if it returns both a value and an error and you care for neither, you can absolutely ignore them entirely.

And when you can "suppress" an error and still access the value, it's not really impressive.
IMO Kylix was always pretty half-assed. The Lazarus project is what it should have been.

https://www.lazarus-ide.org/

But your point stands. Their ridiculous licensing ended any chance they had of mainstream adoption.
Pattern Recognition and Machine Learning [pdf]
There has got to be more money in Linux than Windows since the majority of servers are running it. The problem is Linux doesn't see user experience as anything that is necessary. When it does (ubuntu, et al) it thrives....but many of us have been waiting since the 90s for everything to "work" on Linux without having to screw around.

People love it when things just work and for many of them Apple and Windows do just that.
Anyone became extremely annoyed by the constant "breathing" of Amazon Polly?
I think this is the crux of why Apple trades at such a low P/E, sure they make tons of money, but their product line is very concentrated and not diverse at all. Microsoft has tons of product lines, and if one is suffering others usually do ok, or excel. Windows has struggled for the past decade or two, and what picked up the slack? Office 365 and Azure. I suspect when those cool off, Windows and devices will pick back up. Microsoft is built better to handle cyclicality. That's not to say Apple isn't a great company, or even a bad investment, but I do understand why Apple has fallen so sharply, and relatively speaking, Microsoft has had a marginal correction relative to its peers.

If you assume we might head into a recession due to the trade war, Apple has never really had to go through that with their current high end product line. The iPhone was introduced in 2007 and was early cycle even during the financial collapse. It will be interesting to see if the business cycle greatly hurts their sales. I think that's what so many are worried about. Especially when we have their vendors cutting forecast (and yes there have been some crying wolf over the years, but eventually the wolf will show) and Apple being less transparent about unit sales. I suspect they will see a fall in sales when we do enter a recession, but I am encouraged that they have such control over their supply line that they won't get stuck with inventory gluts, like...uh Nvidia.

I mean back a few years ago Microsoft had a massive write-off from hardware...and that's not even a fraction of their business, imagine if Apple had to write off a ton of hardware, it would be brutal. That seems unlikely though, as I said, they seem to have a good handle on their inventory.
Why would there be any cherry picking? There are a number of people in this thread (and also many downvoters) who apparently believe very strongly about this stuff.

Why can't they point me to the exact evidence that convinced them? And while you are one of the better ones "the references are somewhere in this one book" is not very helpful. People are busy, you need to make it as easy as possible for them if you actually care about convincing them.
Even though the fine is low, at least this stuff is starting to get some attention and offenders are getting fined.
The problem with BCI, eyegaze or speech control systems is how slow they are. There can no delay in a fast paced game: https://www.youtube.com/watch?v=qTfa0gh2WVg
Looks curious, thanks. Nevertheless it (or a part of it) has to become a part of the CPython standard and get switched on by default at some point for the quality of the ecosystem code to start increasing by means of more Python coders being gently pushed to type-mindfulness. I also couldn't find a flag that would rise warnings when a value of a non-matching type gets assigned to a variable with a defined type hint yet allow everything else - IMHO such one would be the most useful.
Think Google is safer. Plus just rolling out their robot self driving taxi service and already growing faster.
> Especially given that Dominic maintains hundreds of packages

> maintains hundreds of packages

> hundreds

How can a single human reasonably and responsably do this? This number alone demonstrates how sloppy and inept the Node.js community's practices are.
Nice! I would like to move the goal post a BIT further, and also have annotations of case law that actually used any of those clauses.
This is one reason why you don't depend on trivial libraries you can roll in-house and maintain yourself. Shame on people perpetuating the "depending on is-array or left-pad is totally fine" ideology.
Hugely Popular Android Apps Have Been Committing Ad Fraud Behind Users’ Backs