skysight-inc/HackerNews huggingface dataset:
>Just to clarify, what should this update contain?

"We're working on it", possibly an ETA for a fix or some details. Technically it's fluff but people are not machines and the update is for people. We like the feeling that people are working on a fix, that people care and that the end is in sight. It makes the situation less stressful and, as for why Google should care, less stressed engineers won't bad mouth Google as much after the fact.
Fraud occurred, but it was not a fraudulent Bitcoin transaction. There is a big difference - though, I understand that the difference is likely lost on the average person, and that the average person places more value on centralized authority in financial matters.
For anyone familiar with reducing computational complexity in linear algebra, this is a direct corollary to reducing matrix multiplication to vector multiplication.

A reduction in problem dimension leads to an order of magnitude reduction in complexity.
ISO standards would be the least of my concerns given how common it is for implanted pet chips to migrate around the body and end up in the dog's leg etc.
Fair enough, the numbers speak for themselves.
What strikes me as interesting though is that the Surface uncovered a lot of people (especially students on my campus) willing to use tablets as a primary device. I'd bet that a lot of people would shift from Macs to iPads if they had a more comprehensive OS.
But hey, it's all spelled out in the policy, so don't say we didn't warn you!

Caveat emptor, folks.
I dont get that mentality either. None of that stuff is required for open sourcing a piece of software. High quality codebases are not born overnight.
While I support having a different view that goes beyond mostly postmodernist mono-culture of today's media, I also know some people who are both members of the IDW and who have had run-ins with Claire.

With the three academics who were behind the hoax articles in the feminist publications, Quillette had a three day heads up and played a much smaller role that she is implying in that article.

I also know someone that Claire contacted to write an article. After agreeing to write the article this person began to pen the article. Then, shortly they found out that two other people had been asked to Quillette to write the same article. Needless to say that didn't go over well, this person confronted Claire about it and decided to not continue with the article or to write for her.

It's a shame because while we really do need something that goes outside of the crazy mono-culture that tries to destroy all dissent, based on what I've seen Quillette, it runs the real risk of doing more harm than good for the cause.
I just have an ssh window and web browser open, both of which the iPad mostly handles fine. For me, it was a no-brainer because it's light and easy to travel with, and doesn't require 40 minutes of updates every time I open it (hello, Surface Pro 4, my previous laptop). Does it replace two 32" monitors? Nope. But I never had those when I was travelling.

I also draw and edit photos on my laptop. The iPad handles that fine. I have a Cintiq Pro 13" and it's a piece of garbage that made me hate drawing. I am glad it's gone from my life. The Apple Pencil is way better. (I hate Lightroom/Photoshop on the desktop, so I am trying to deal with Affinity. We'll see how that goes after I go on a trip where I take some photos.)

All in all, there are many tasks that can't be done on any laptop. That is why you can buy desktops. If the primary goal for your mobile computer is to not have to spend 40 minutes disabling Cortana, the iPad is perfect, which is why I bought one.

My only complaint is that Safari requests mobile sites instead of desktop sites. That is super annoying. I have a desktop-sized screen and a keyboard. Give me the desktop version.
My Pixel 2 running the Hangouts app transparently switches between home WiFi, LTE and xfinity WiFi (Comcast's attempt to make every one of their customers into a WiFi hotspot).

The Hangout connection doesn't drop. It may go fuzzy/staticy before the WiFi drops in favor of LTE but that's all.
The network effect is the only thing supporting a fiat currency like the USD - as evidenced by Krugman’s “men with guns” quote in the article.
It's only available on apple iOS and maybe Mac OS out of the box. Android is probably not going to support it; if Android does support it, it will be a long time before there's critical mass and early versions may claim to support it, but not work well, and it may be hard to selectively enable it, and we know many devices won't get the updates to fix it.

It's expensive to support on servers because (to my knowledge) there's not a good way to ensure related sub flows arrive at the same nic rx queue on the same server in real world load balancing situations, which is critical for performance.

Nobody else is doing it (other than Apple for Siri), so it's not clear what the benefits are.
what terrible actualized results

avoid anything to do with this trainwreck
As a long-time proponent of Bitcoin and other cryptocurrencies, I agree. Bitcoin is and was intended as a political tool. It may yet transcend that use, but it’s yet to be seen if that will be the case.
I mean, yeah, but Quillette is still a rag. It exists to exhaust people with the time, energy, and knowledge to debunk it so people without that will be duped by its arguments that only seem reasonable on the surface and one or two layers below, right above the trash.

Quillette is like a knowledge slot machine to people who want to be well-informed but don't have the resources to do it without leaning on others who do. It lures you in with surface plausibility.

I think you edited after my response below, so:

If your words are true, the entire thing is discredited. It feels hand-wavy, so do you have any examples or references? The article I linked above has supported references and links, and it's quite long. You're saying it's a complete fraud?
I’ll suggest considering whether entities enamored with centralizing ideals are more likely to fail to properly realize the robustness of a distributed system.
This video goes in detail about the Stadiums racket, and provide examples and numbers. https://youtu.be/xcwJt4bcnXs
As someone who's the same height (yay?) it's okay, it's really average around the world, you're not short, you're average for 95% of the world ;) (Also it's 5'10")

Having said so, may I remind you that the biggest predictor for your own personal wealth is the wealth of your parents, so you know.
Show HN: Split-screen Synchronization with FFmpeg
At a small enough scale and not in government-heavy states all of those are legal to do without any sort of license. When you start doing it regularly is when you need licenses.
According to NoScript, it's loading the map from http://www.arcgis.com.

EDIT: In the credits, they link to https://cesiumjs.org/
https://en.wikipedia.org/wiki/ZAZ_Zaporozhets#Second_generat...

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

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

https://en.wikipedia.org/wiki/GAZ-24

There were a few models concurrently of the two popular brands, but they were not great.
> There has always been head of line blocking in tcp, however H2 compounded it since it now impacts all requests to the origin instead of just a few requests in one of four or one of six tcp connections to origin.

I feel like you're conflating two very different things into "head of line blockings".

Head of line blocking in HTTP/1.1 was that HTTP/1.1 cannot transmit responses out of order, so a slow response "blocks" any responses behind it. HTTP/2 solves this by being multiplexed (effectively, it tags the requests & responses s.t. you can match out of order responses back to the appropriate request). This isn't necessarily that the network can't handle it; a request that might be easy for the server to handle (e.g., a static asset) can get caught behind one that is not (e.g., one that entails a slow DB query).

The other "head of line blocking" that I think you're getting at is just network loss or saturation. If the network can't deliver packets, I don't see how having 6 connections is going to help: you're going to have to wait for six different state machines to determine that the link is saturated, back off, etc.

Regardless, my understanding is that QUIC / HTTP/3 is still a multiplexed protocol; I would think it would behave very similarly. Nonetheless, Google's announcement of it backs up your claim[1]:

> Like HTTP/2, QUIC multiplexes multiple streams into one connection, so that a connection can serve several HTTP requests simultaneously. But HTTP/2 uses TCP as its transport, so all of its streams can be blocked when a single TCP packet is lost—a problem called head-of-line blocking. QUIC is different: Loss of a UDP packet within a QUIC connection only affects the streams contained within that packet. In other words, QUIC won’t let a problem with one request slow the others down, even on an unreliable connection.

But what here makes QUIC think that those other requests have any hope where the first didn't? To me, this approach seems like you're just spamming the link with packets and hoping for the best; those packets could just end up dropped like the other ones were. What makes QUIC think this approach will have any benefit? (It could, perhaps, if the link is just going to drop one packet and we can get right back to sending. I'm not sure that still conveys any benefit over TCP. Not saying QUIC is wrong, just that I don't see a decent reason to buy into it.)

(This whole thing makes me think there are two problems here: there's the actual network connection between two endpoints, and what its state is, how lossy it is, its PMTU, how much data we should allow in-flight between those two endpoints, etc. But then there is also logical streams, such as HTTP request/response pairs. It almost seems like to me any data about the link, such as PMTU/lossiness/window, should be shared between all TCP connections, and the individual logical streams should be otherwise cheap/easy to make.)

[1]: https://cloudplatform.googleblog.com/2018/06/Introducing-QUI...
When no one retires
Sounds like a bad fragmentation implementation. At 64KB datagrams you have to send over 4GB of data before you need to recycle an ID

Even if your packet ids are assigned poorly, on the receiving side Linux has a heuristic that takes in to account reordering to minimize the chance of reassembling bad packets. Basically if packets with the same frag id are too far apart then the whole datagram is chucked:

https://marc.info/?l=linux-netdev&m=113267833031122&w=2
This article talks about the issues but agrees there's evolution in certain places. It's harder to prove in others -

http://nautil.us/blog/is-poaching-causing-elephants-to-evolv...

It is very political, because if true, genocide's will evolve races of humans, and not for the better. People don't like inconvenient truths.

I at first doubted it was evolutionary from the headline, but it seems true.

It's what annoys me about memes about Christians and evolution. Not many people really understand evolution, like morons on a hot day talking about Global Warming deniers, we all just like to be smug, a human trait.
dynamic-codesigning gates MAP_JIT, which is what MobileSafari uses for achieving just in time execution for JavaScript. However, you can still have a “poor man’s” JIT by marking a page as RW, sticking code in there, then marking it as RX, which does not require dynamic-codesigning and can be done by apps not made by Apple.
I love OpenSCAD, but can't understand why it's so slow rendering. The viewer does it's own perfect render fast enough to pan/zoom/rotate, but rendering to STL is painfully slow.

It would be great to be able to switch to a slicing mode for rendering.
Do you have a reference for that?

I did a search for "Quillette Alt-Right" and I got a ton of articles from them against the Alt-Right, and comparing the extreme Left to the alt-Right.

It's Patreon-supported, is that alt-right too?
> It doesn't need profiles in mostly credible outlets. It needs a faulty backup and restoration plan and a power surge.

Who sounds like the church?
Spot on. This will be and is being used to justify a world of luxury for the 1% and a world of pain for everyone else who isn't "perfect".

I personally believe we should strive to create a better world for 100% of the population, not justify the shortfallings of the current mixed-capi-soci system.
IMO you will need to pivot to calendar-based activity that involves people on your premises ..
No, this is quite certainly a model/simulator for a digital quantum computer (implemented on top of a harmonic oscillator).

It is becoming a pet peeve of mine, but on most HN posts about quantum computing somebody always mentions some misunderstood statement about continuous variables. Yes, there are many interesting ideas around the use of harmonic oscillators (the older name for the vague and misleading term "continuous variables") to store data, but most of the time it is just one of many ways to implement the same digital computer.
> My only complaint is that Safari requests mobile sites instead of desktop sites. That is super annoying. I have a desktop-sized screen and a keyboard. Give me the desktop version.

Hold the refresh button you can reload the page as the desktop version
Can someone help me compare this with https://github.com/bevacqua/react-dragula and https://github.com/react-dnd/react-dnd? Which one is better, what are the pros and cons?

Which one would you choose to build something like https://trello.com, or https://dynalist.io, or https://nulis.io?
> You can plug an iPad into a giant external monitor using the lightning to HDMI cable

Or, on newer iPads, directly via the USB C connector. And apps can recognize that you have chosen to plug in a secondary display and suit their content to match on the other screen.
>Subject to Section 7.2

Which is the deprecation policy. (I mean I share your frustration with Google's what-appears-to-be-at-least haphazard policy of shutting down services instead of trying to gain traction. But, let's not misrepresent what they say).
>What’s interesting to me is that they didn’t simply nail her for buying and selling bitcoin without a money transmitters license. They also used the undercover agent to explicitly say it was drug money, ensuring worse penalties.

Creating crime to catch crime is pretty par for the course in federal investigations. The FBI is pretty well known to do it in terrorism cases. The ATF runs their botched illegal gun buying operations that create local crime.
Not the author, but it seems so; in the credits they link to https://github.com/puckey/freegeoip/
On a technical note, the Art Institute of Chicago images are being served using an API called IIIF, which allows you to scale, extract regions of interest, etc. [1]. There are about 1-2B images worldwide being served from museums and libraries using the API [2] and viewers that can work with the content from multiple institutions at the same time, for instance to compare two van Gogh self-portraits from different museums: http://projectmirador.org/demo/

[1] https://iiif.io/api/image/2.1/#image-request-uri-syntax
[2] https://iiif.io/community/#participating-institutions
Fry: What if I don't want to be a delivery boy?

Leela: Then you'll be fired...

Fry: Fine.

Leela: ...out of a cannon, into the sun
Good points.

> many cafes even close at 3pm

That’s far too close to a black mark against NZ coffee though. The weak, lukewarm, milky liquid that is served up elsewhere is deeply depressing. The stuff I want is best not consumed late in the day.
Not to minimize here (well, yes, a little), but this was a UI-only outage, from what I can tell. You could still create the pools from the command-line. It doesn't seem unreasonable to have a single, global UI server, as long as the API gateway is distributed and not subject to global outages.
Good point actually, I might look into this and see.
The preceding line is the imprtant part. Which is essentially

"Subject to the deprecation policy [which says that Google will give at least 1 year notice before cancelling services], Google may discontinue..."

In other words, at any time, google can give you a years notice.

(I work at Google, but am not a lawyer and this isn't official in any capacity).

Please don't selectively quote things out of context to give a misleading impression.
Is the thunder being generated? That's the most interesting part IMHO.
Get enough sleep.
> Google decided to fundamentally redesign HTTP to accommodate their own inability to impose any kind of discipline on their programmers

1) That is a ridiculous statement with absolutely no evidence to back it up.

2) The number of requests that Googles homepage does in order to load has _nothing at all_ to do with whether or not solving head of line blocking problems for the rest of the web is a good thing.
Using UIPanGestureRecognizer for gestures that should be recognized immediately on touch down is a common mistake I see a lot of people make. The problem is UIPanGestureRecognizer doesn't actually start recognizing until the touch has moved a short distance, and at this point, you can't recover the original touch location, only the location at which the gesture recognizer began recognizing.

The solution is to use a UILongPressGestureRecognizer with minimumPressDuration set to 0. With this configuration, it will begin recognizing immediately on touch down, allowing you to take action even before the user has moved their finger (or pencil).
Nice job cherry picking text.

> 7.1 Discontinuance of Services. Subject to Section 7.2, Google may discontinue
> any Services or any portion or feature for any reason at any time without
> liability to Customer.

Let's take a look at Section 7.2:

> 7.2 Deprecation Policy. Google will announce if it intends to discontinue or
> make backwards incompatible changes to the Services specified at the URL in
> the next sentence. Google will use commercially reasonable efforts to continue
> to operate those Services versions and features identified at
> https://cloud.google.com/terms/deprecation without these changes for at least
> one year after that announcement, unless (as Google determines in its
> reasonable good faith judgment):
>
> (i) required by law or third party relationship (including if there is a change
> in applicable law or relationship), or
>
> (ii) doing so could create a security risk or substantial economic or material
> technical burden.
>
> The above policy is the "Deprecation Policy."

To me that looks like a reasonable deprecation policy.
From https://strawberryfields.readthedocs.io/en/latest/quantum_al...

Here we will discuss several continuous-variable (CV) quantum algorithm examples that can be run with Strawberry Fields.

> It is becoming a pet peeve of mine, but on most HN posts about quantum computing somebody always mentions some misunderstood statement about continuous variables.

That someone is me. I’d love to hear what I misunderstand.

> the time it is just one of many ways to implement the same digital computer.

Yeah, what I’m talking about isn’t a digital computer.
I thought that 'subject to 7.2' meant that they can use the escape-hatch there 'substantial economic or material technical burden'? They can list anything under that.

I don't think it's wrong - they can deprecate any service they want to do whenever they want, unless people have paid for and signed a contract that says otherwise which I guess people aren't doing.

But the policy doesn't really guarantee anything at all does it, due to the reference escape-hatches? It might as well not exist?
This all seems like the fault of the marketing company forcing the OP to go through Upwork in the first place. But Upwork should be up-front about this from day 1.
Yt, ads, a bunch of services. Sure.
I don’t see anything about emulators in the App Store Review Guidelines, so I’d be interested in seeing anything that Apple has cited when they reject such software from the App Store. To my knowledge, this software follows Apple’s guidelines.
It was founded by Claire Lehmann, who worked for the Canadian far-right Rebel Media (RebelTV).

I don’t personally consider it alt-right, but i think someone viewing it that way is totally reasonable given her media background.
If you ever get a chance, I'd love to read a "making of" blog post -- how you started, what approaches worked/didn't, what you're measuring success against, and remaining challenges... Think it would be super-educational and fascinating!
If you are comfortable (mathematically) with the idea of "a gate" and "a qubit", then Wikipedia is surprisingly good at explaining what each new gate does.

Otherwise the standards reference that starts from scratch (prerequisites being linear algebra and intro quantum mechanics) is Quantum Computation and Quantum Information by Nielsen and Chuang. It is a very thick book and it takes a sustained effort to read it, but stackexchange is always eager to help. Preskill's lecture notes are amazing as well.

Regrettably, I do not know of a good book that does not have the prerequisites I mentioned.
Your first library has not been updated in 2 years, good luck using it.
Those are definitely all renders. I've worked on my share of prototype robotics. To get to the degree of polish they present, you'd need a heavy industrial behind you (see Fanuc or Mitsubishi or similar).
I am currently evaluating GCP for two separate projects. I want to see if I understand this correctly:

1) For three whole days, it was questionable whether or not a user would be able to launch a node pool (according to the official blog statement). It was also questionable whether a user would be able to launch a simple compute instance (according to statements here on HN).

2) This issue was global in scope, affecting all of Google's regions. Therefore, in consideration of item 1 above, it was questionable/unpredictable whether or not a user could launch a node pool or even a simple node anywhere in GCP at all.

3) The sum total of information about this incident can be found as a few one or two sentence blurbs on Google's blog. No explanation nor outline of scope for affected regions and services has been provided.

4) Some users here are reporting that other GCP services not mentioned by Google's blog are experiencing problems.

5) Some users here are reporting that they have received no response from GCP support, even over a time span of 40+ hours since the support request was submitted.

6) Google says they'll provide some information when the next business day rolls around, roughly 4 days after the start of the problem.

I really do want to make sure I'm understanding this situation. Please do correct me if I got something wrong in this summary.
This is a billion dollar business, if it can be made to ride on existing systems.

Imagine being able to plant, weed, and harvest strawberries from a center pivot. Huge.
Unfortunately the images cannot be downloaded from Google Art Project (original name).

It's irritating having to jump over complicated hurdles to get a seamless hi-res image capture from Google Arts. It requires some messing about, but I previously managed to grab about 100 high res images, but it took ages and was not easy. They printed out nicely in the end though, so was worth it.

A simple download link as seen on artic.edu would be appreciated but sadly I don't see Google providing this because they want people to remain on Google, logged in, while they view art.
> But a little known fact is that you lose all of ACID, meaning that a system crash can cause total loss of the database. Only use `MDB_NOSYNC` if your data is expendable.

Last I looked into LMDB, this was only the case if the filesystem doesn't respect write ordering, which depends on the filesystem. Otherwise you get everything but durability (i.e. ACI) If I recall, writes are ordered by default on Ext3.
Lovely, I'm particularly impressed with how fast the streams started. Biggest surprise for me was Kiribati and Saint Helena.
Newsletters You Need to Follow to Stay Updated with Crypto