skysight-inc/HackerNews huggingface dataset:
USB 3.1 Gen 2 plus display is not the same as Thunderbolt. TB is basically straight PCIE. Can't just combine data and video and call it Thunderbolt. Plus 3.1 Gen 2 is only half the speed of TB3.
Yes, that's an option -- the simplest option would be a single overlay network, with the node-node tunnels encrypted using IPSec or similar (https://github.com/coreos/flannel/issues/6 or https://www.weave.works/documentation/net-latest-how-it-work... or https://github.com/projectcalico/felix/issues/997). I think this would be tricky to configure in GKE though.

With a secret-per-pod, your key material lives in in the etcd on the API server, and gets mounted in a tmpfs on each pod that is given the secret. Only Pods in the Secret's namespace can access the Secret, so if you have RBAC configured correctly it should be possible to lock this down tightly to only the code that needs the Secret. (I'm not sure how to do this in GKE; I'm currently treating each cluster as a single security domain).
> What’s the first thing anybody does when they get a second computer? That’s right, set up a kerberos domain

tedu is a funny guy
This is good advice but I think it downplays the seriousness of government insolvency and the repercussions with respect to investing.

The worst case scenario for millenials is not just getting 3/4 of our promised social security; it could be far worse.

To wit, the national debt increased from ~$5 trillion to about ~$10 trillion on GWB's watch (doubled). It increased from ~$10 trillion to ~$20 trillion on BHO's watch (doubled). DJT has promised massive new spending on infrastructure, increasing funding for border patrol etc, a massive military buildup, no changes to SS or Medicare, and massive tax cuts - so it is reasonable to believe we are still on track to double the national debt again within the next 8 years. That is something not unlike exponential (and BTW that "national debt" is just the level of outstanding treasury debt; the actual unfunded future liabilities are much much higher).

To cover the massive debts of the government (and maintain the stability of the economy and society) massive amounts of new money will need to be created to monetize government debt. This has already started, as the base money supply in the US has quadrupled since 2009. Velocity is low so we don't see the inflation (except in things like stocks, bonds, fine art, and tech startups) but DJT's Keynesian wet dream should get velocity up at least long enough for inflation to start showing up in the real economy, and even that doesn't get the snowball rolling, it is unreasonable to believe that velocity will stay so low forever and that the new money will not start flowing through the economy.

In any case, in such an environment bonds will get savaged and there will be great economic dislocations. A simple index-fund based asset allocation between US stocks, bonds, and international stocks is not necessarily going to work in the next 30 years as it did in the past 30. Past results are not guarantees of future returns.

That said, I think taking 15% of your income and sticking with a strategy that you are comfortable with is great advice. The best way to get rich quickly is to do it slowly indeed. But investing in the near-to-medium term might get interesting, just sayin ;)
Golang Self-referential functions and the design of options (2014)
Also, and I'm not an astrophysicist, but I believe going fast _relative to Earth_ doesn't make it any more or less likely that you're going to hit anything. Moving at .998c relative to Earth and hitting something that is stationary relative to Earth is the same thing as not moving and being hit by something going .998c relative to you.

EDIT: Right, as chris_va pointed out, we're all traveling at .998c relative to something out there.
That is great in theory but it throws out all of the deeply rooted tooling that reports and aggregates http status codes across the service architecture. It is nice to be able to tail the apache log and see the status. In your situation I would need to have an additional system that uses application details for similar purposes.. you can do it as you describe but there is a cost! It is also against convention, which increases the custom tribal knowledge that people working in that system have to acquire. By the time you "outgrow" http I assume you'd have custom metrics and logging/tracing, but I would not suggest it as a good place to start.
There are better algorithms for bootstrap intervals that you perhaps should look into. Better in the sense of quality, not speed.

Google e.g. "interval BCa"
Many Google APIs were created before this guide. New APIs published at https://github.com/googleapis follow this guide. Having the same API available via both REST and gRPC is very valuable, as gRPC often provides 10x performance.
But that'd still be transpiled code, right? After getting rid of flow it will be exactly same minus the type annotations. Same cannot be said about typescript considering various language features and syntactic sugar TS offers. Will it run? Yes. Will it feel that it was written by me? That depends.
There's a Steve Jobs Theater but no Steve Wozniak Engineering Complex? Ow.
The Essence of Mobile DevOps to Destroy Silos
According to this paper, you can travel around 0.5 c before the radiation caused by colliding with interstellar hydrogen kills you:
http://www.scirp.org/journal/PaperInformation.aspx?paperID=2...

"Going slow to avoid severe H irradiation sets an upper speed limit of v ~ 0.5 c. This velocity only gives a time dilation factor of about 15%, which would not substantially assist galaxy-scale voyages. Diffuse interstellar H atoms are the ultimate cosmic space mines and represent a formidable obstacle to interstellar travel."
I use GitHub only to see if someone has a side project and their interests. Never to judge their code quality. I use GitHub to store code when I'm experimenting or teaching someone else.
If we had a near-perfect hydrogen -> helium fusion engine, why would we want to stop at 2,000 saturn V rockets of mass? Hydrogen is cheap AF.

Also why would we only want to stop at helium, why not fuse any further?

Also why would you want to stop at 1g acceleration - why not 1.5g or 2g, say? Surely living in 2g environment is okay for that period?

However presumably there is no good reason for us to go there. Just because there are planets doesn't make it worth the trip.
This is interesting because the disk activity LED is covert, not clandestine. There's no need to try to hide the activity; communication is buried in the normal busy activity of the hard disk.
If you make the fuel on Mars it will take less effort to get it into orbit. It's also a bit further up the suns gravity well.
I'm talking about establishing a self-sufficient colony somewhere other than Earth. We have a major crisis on our hands. And few are even willing to consider let alone research and confirm that we're talking about an extinction event much sooner than we thought, maybe on the order of just a couple years out. Problem is, we don't know. Bigger problem is, we're not doing anything about it.
HTTP has some very useful status codes, which convey standard conditions found in most apis: 200, 201, 400, 401, 404, 403, 406, 429, 500

Also note that not all APIs will be used be developers. Often it's someone less proficient with programming, and you can't rely on them to check the content of the return message. Help them help themselves by making curl (or whatever) bitch when there is an error.

It takes a bit more work to design an API that works over multiple transports, but a good framework, such as Servicestack.net if your in .Net land, mostly does it for you. By advocating 200 for all responses you're basically reverting to SOAP and WCF (Windows Communication Foundation).

Each to his own though, and for internal stuff, it might make a lot more sense.
> Is it plausible for anything we'd build to travel .998c and survive the journey?

The first half is actually a bigger problem than the second half.
It's simply another form of trolling. If they could get people to debate about the moon landing then they will pull out the same crap.
4 separate front-page posts about this on H/N so far..
"Why not 80% of the price of the comparable Intel part?"

1. Because Intel is about to significantly drop their prices in response to Ryzen.

2. Because AMD really wants to immediately hurt Intel's revenues as badly as possible.

3. Because AMD has such an uphill battle to regain mind share that it really needs to release a product that makes people realize that AMD now has the superior perf/$ product, beyond any doubt. If Ryzen was only priced 20% lower than Intel, many people/OEMs/etc would not be motivated enough to go AMD.
You've no idea. But for the first step, I need to find one or two very truthful physics grad students / electrical engineers who feel some responsibility for Earth or saving themselves. You wouldn't happen to know someone?
Current discussion - https://news.ycombinator.com/item?id=13705055

It would be awesome if we could add a filter to HN to strip the Medium tracker hash so dupe links don't go undetected.
Is there information already on how the short distances between planets would affect G-forces felt on surface?
ScaleFT founder here.

We're actually more focused on issuing certs to authenticate SSH and RDP clients, similar to what Google, Facebook, etc do. We keep track of the host keys for those services, and use them for key pinning, but we don't look for other X.509 certs on servers where our agent is installed.
HAHA. This discovery currently occupies 3 out of the top 4 spots on HN.
I didn't miss it. I just think way more information is necessary in order to understand whether or not it's a positive or negative. As originally implemented, it doesn't appear to be in any way dishonest.

My understanding of the article is that the service fee wasn't originally optional. It was a static 10%, required, service fee. No information is given about how much of that fee goes to workers, meaning it's entirely possible that all of it does. It doesn't go to _the_ worker who delivered your groceries, it goes into a common pool that is distributed across all workers.

If 10% is enough to break the barrier into a living wage then this could be a positive change. Workers no longer have to fear having a "bad night" where they have 5 runs to get a single $10 items vs a "good night" where they have 3 runs to get $200 worth of groceries.

They made it optional and mutable when their workers protested.
Is it possible there isn't an asteroid belt to be concerned about?
What they describe is not REST. Nowhere in this document mentions hyperlinks, a strict requirement of the REST architectural style.

The best analogy would be a simple web page, which usually contains hyperlinks that a client can follow to discover new information. Unfortunately, web developers' understanding of REST ends with HTML, and they re-invent the wheel, badly, every time they create an ad hoc JSON-over-HTTP service.

There is a standardized solution for machine-to-machine REST: JSON-LD [1], with best practices[2] to follow, and even some formalized specs[3][4]. To Google's credit, they are now parsing JSON-LD in search results, which is much nicer to read and write than the various HTML-based micro-data formats.

On a related note, REST has nothing to do with pretty URLs, naming conventions, or even HTTP verbs. That is to say, it is independent of the HTTP protocol, but maps quite naturally to it.

[1]: http://json-ld.org/

[2]: http://json-ld.org/spec/latest/json-ld-api-best-practices/

[3]: http://micro-api.org/

[4]: http://www.markus-lanthaler.com/hydra/
Earth is 4.5G years old, and the earliest undisputed microbial life fossils are 3.5G years old, so that gives 1000 million years.

But we can also say that Earth was cool enough for liquid water 4.4G years ago, and there are some findings suggesting microbial life already 4.1G years ago. So only 300 million years, at maximum.
Revolve around. Sorry, had to.
Forget Normalize or CSS Resets
A year generally refers to the time something takes to make one revolution around its closest star.
HTTP Method DELETE. Payload: empty.

I know DELETE is not supposed to have any payload, but using PATCH is awkward if you have to delete multiple resources based on a query or a filter. You need to specify a 'delete' action as part of PATCH request which means the payload model has to be different. Just awkward.
Because it increases the chance that they'll need to resort to crime to survive. It's the same reason that the pervasive policies against hiring felons increase recidivism rate. Once they've paid their debt to society, we need to actually forgive them, or it's much harder for them to rehabilitate.
I believe I read somewhere that the 3 engine landing burn could loose one engine for LEO missions and such, but don't quote me on that.
Here's the 1990 USENET announcement of "archie".[1] This wasn't a full text search engine. It just collected what it got from "ls".

"Alan has a set of shell scripts that automagically calls
up some subset of our list of servers each night (to keep
load down on any one machine) and do a remote 'ls' on that
machine. We cycle through the entire list in about a
month, so no entry can be more than that old. For what
it's worth, we currently know of about 210 sites."

Archie allows anyone to rlogin into one of our machines
and query our archive lists. Another one of my guys, (Bill
Heelan, whe...@cs.mcgill.ca) wrote a bare-bones front
end, which allows people to login, get a help message, ask
for a specific string (using ed-like regular expressions)
or get the contents of a specific archive server.

Currently, archie is pretty brain-damaged. The files are
stored as flat ASCII files and the "prog" command just
launches a "grep" with the appropriate arguments. Future
plans (once we get the latest start of semester out of the
way) is to add a real database (we've compiled postgres
(sp?) and Alan has started to code the program to parse
the raw input).

So that was Archie. That's like a library shelf list, or Active Directory, not a search engine.

Long before WWW search engines, there were computerized keyword and catalog databases. The US National Library of Medicine (MEDLARS) and Mead Data Central (later Lexis/Nexis) were early big ones. Big libraries also had online catalogs by 1990.

AltaVista was the first big full-text search engine. AltaVista was in the old telco building behind the Walgreens in Palo Alto. where PAIX is now. AltaVista was built as a demo of DEC Alpha servers. It was the first data center built telco-style, on open racks with the cables overhead. This was because they had the racks in place, but it became a trend.

[1] https://groups.google.com/forum/#!msg/comp.archives/LWVA50W8...
The earth moon distance is tiny, and the G-Forces are hard to directly measure.
What's wrong with begs the question? It's a regular part of my vocabulary and I'm a southern American.
very good read, but not really about web/http/rest API's.
> Also, and I'm not an astrophysicist, but I believe going fast _relative to Earth_ doesn't make it any more or less likely that you're going to hit anything.

OTOH, given that it is (like most of the stuff around it) orbiting the center of mass of the Milky Way Galaxy, shouldn't Earth be moving relatively close (within a very small fraction of light speed) to the speed of most of the interstellar dust, etc., in its immediate galactic vincinity, such that moving at 0.998c relative to earth is also moving at a very similar fraction of c relative to lots of other things you are going to potentially hit on a journey from earth to a nearby star system?
Can I own my identity on the Internet?
"
You can call anyone anything you like... what you don't have control over is how they feel in reaction. Assuming you identify as a man.. how would you receive someone that always referred to you as a female, and I mean always not just as a one-off joke type thing. I'm going to take a guess that you would feel worse than "censored"."

Basically, imagine having Dr. Cox calling you Shirley every single day, even though you hate being called girl's names. A lot of it boils down to 'Don't be a dick'.
I Ignored Trump News for a Week. Here’s What I Learned
> you had a near perfect hydrogen -> helium fusion engine,
it'd take about 6 million tons of fuel (about the mass of the Pyramids of Egypt or 2,000 Saturn V rockets)

That is assuming constant energy consumption to sustain 1g, but unfortunately that's not the case, the closer you get to the speed of light, the more energy you'd need to sustain 1g, and this becomes unrealistic long before you are anywhere close to the speed of light.
Basic auth is great. It lowers the barrier of entry, to anyone with a browser.
Not all users of APIs are developers.
How to quantify product market fit
do we think Intel will drastically drop prices on middle and high end chips?
I hate to always post links to Greg Egan, but he's sort of the XKCD of SciFi - if there's an out there concept, he's usually written a book about it. In this case Incandescence:

https://www.amazon.com/dp/B0070YQOHW

Top review has the best summary: "Egan's story is set in the galactic core, inhabited by a race known as the Aloof, because they seem almost indifferent to any attempts at communication from the Amalgam, the loose network of civilizations that inhabit the rest of the galaxy. However, they do allow thrill-seeking members of the Amalgam to enter their transportation network, digitizing themselves for transmission at the speed of light across the galactic core, instead of the long way around it."
Build stadiums on a couple of old oil tankers and accompanying cruise ships?

Is there any country that matters that doesn't have easy water access? Russia?

Also same deal for Winter Olympics since there's a lot of water up there?
That is not talking about the age, but about the possible life span, into the future.
I suspect you meant definitely and not defiantly.
To put that 60 years into perspective: It was 66 years between the first powered airplane flight and landing people on the moon.
My friends and I were joking before that Olympics that organizing it was just writing a bunch of letters. To Wimbledon for tennis courts, to FA for Wembeley, etc. Others were probably building from scratch.
> It is not right given our current values.

Citation needed.

> stand up for what they believe is right

That isn't my belief system, hence the disagreement. Do I have to stand up for what you think is right?
It looks like it can be very good, but doesn't integrate with Simple and Robinhood. :(
Whenever I see someone who labels people that criticize Trump as 'liberal' I automatically label them as 'dumbass'.
I argue about words for a living, so I am always happy to hear competing interpretations.

However, here it is pretty clear to me, and likely why he deleted his post, that he meant "we should just ignore it." Which I don't think is a particularly defensible position.
Best of luck, I all ask/need from them is to keep their free tier available, don't be another mandrill please!
It's just never been clear to me what HATEOAS is really supposed to be good for. Sure, a client can follow the links in an automated fashion, but how is it supposed to know what the resources actually are and which links it needs to follow, which resources it has to create or modify, to actually accomplish anything?

The general idea of returning links to related resources and/or actions is fine and good, but the rhetoric tends to go further, to ecompass claims like the API being "self-documenting" or amenable to a universal client. It always seems to me that this Big Idea of just presupposes the existence of a "smart" client that can really understand the links, one that there doesn't seem to be much sign of.

GitHub's API proudly notes its use of hypermedia and URL Templates in its responses, but I still have go read the documentation to decide what link I need to use, and what needs to fill into those variable slots in the URLs. The template doesn't do much for me that text in the documentation saying "these GET paramters are accepted/required" wouldn't just as well.
Labeling a service fee a service fee isn't a dark pattern. Nothing about "service fee" makes me thing it's going to the driver.

Also, per the article, the service fee wasn't originally something that could be changed. It was a static 10%. Neither you nor I have enough information to know if 10% is enough to pay drivers a living wage. Maybe it should have been 15% or more but there is no way for me to know.

I am, however, very confident that a service fee that goes into a common pool and is paid out across all workers is a better solution than customers tipping.
Our experience, from having gone that route internally and externally (e.g. with JSON-RPC), is that it ends up not paying off to have that separation.

From the client side, developers shouldn't need to worry about what piece of your stack was at fault. They want to know if it's your fault or theirs/their user's. And if it's their fault, how to prevent it or fix it. Both HTTP and gRPC are flexible enough to encode that information.

From the server side, it complicates monitoring in practice if errors are propagated encoded in the response body of a "successful" RPC. With reverse proxies and other things in place, the complication increases, and many people get unhappy.

W.r.t. migrating clients to other transports, the client library should hide that (we haven't done that always right in the past, but we do now).
LOL -4 karma on that one.
I'm easy to find.

Finding someone local to you, well, you'll have to ask around.

But how do you know if the recruiter is qualified to assess coding skills?

>> Pretend you're a team leader interviewing a junior coder.
Your speed doesn't affect the laws of physics you experience.
Herpes Virus May Be a Trigger for Autism
Nice, clear article. I've always been impressed by the usefulness and clarity of Stripe's documentation. I should pay more attention to their blog.
1. There are a lot of them (seven).
2. They are all Earth sized.
3. There are a lot of them in the habitable zone (three).
4. Even those not in the habitable zone could contain liquid water under certain circumstances.
5. This star is insanely close-by (39 ly).

Basically, if you're looking for a second Earth, this is an incredible gift. Even if we don't find a second Earth among these seven planets, they could tell us a lot about the likelihood of life around red dwarf stars, which is significant, because the vast majority of stars are red dwarfs. That's in addition to the information they can probably provide on planet formation and makeup.
A really clever abstraction...

We used it to good effect in go-ipfs: https://github.com/ipfs/go-ipfs/blob/2e116b40eb7ea41564c3371...
Possible, but cross-section for collision is way way smaller in the Earth-Mars system. Cross-section goes as r^-2 so the closer the bodies, the 'way better' it is.
That's not depressing. It gives us a moral imperative to transplant Earth-origin life onto every somewhat concentrated mass that we can reach.

Then we can wait a few billion years, and the universe will likely have generated a superior successor species which can then re-seed over everything we had previously tilled, and then some.

And they'll all be rubber-forehead aliens to one another, because they'll be billionth cousins, a few million times removed.
Make development great again – A Python story