skysight-inc/HackerNews huggingface dataset:
> "Users are your best allies. Empower users to action through meaningful feedback."

Interesting how that works only one way. If you are in need for some support from Google, then good luck trying to contact them.
Well, I try to at least drop a hint as to the right search terms when I do this, and an encouraging word. But IMO your issue is not my issue. I am not going to track your issue.

But if I have time I might try to point you in the right direction, in the right forum.
Guessing this wasn't intentional, though I'd be surprised if Google wasn't aware that Google Search was available and rolled it out without giving China a heads up.

As for China, can't believe they don't black list any TLD or sub-domain with Google in it; not that I'm for blocking Google, Google itself, etc.

Makes me wonder why someone doesn't just doesn't deploy it and give hints on "how to see beyond the Great Fire Wall"; fun fact, it's rumored that the average person has never heard of Tankman in China:
https://en.m.wikipedia.org/wiki/Tank_Man
When I was there, the University of Pennsylvania had coed dorms and coed shared bathrooms. It wasn't a big deal.
AMA with webpack Team
As an operations dude (or, at least, a recovering one) I've spent much of my professional life fighting post-deploy issues at the coal face, which almost always involves (when it's an app issue) digging into the code; even when we do that though, an important bit is observing what the boxes are doing in real time (we're not all dumb "INSTALL RPM AND RESTART" guys!) so we can explain impact and mitigate.

Usually, my goal then is to either:

1) Find a configuration / infra issue we can solve (best outcome for everyone)
2) Give the most info to dev to enable a code fix, and roll back/mitigate in the interim.

In the last few years, people have paid me lots of money to build these really cool ELK or Splunk log chewing systems for them, which I have to admit, are utterly useless to me. There are really great monitoring tools which give me historical graphs of stuff I usually don't care about too.. but... I, and most of the folks I run with don't really reach for these tools when we hit a prod issue as the first resort.

Lets say, hypothetically, a customer of mine has an issue where some users are getting timeouts out on some API or another. We got alerted through some monitoring or whatever, and so we start taking a look.

First step, for me is always login a webserver at random (or all of them) and look at the obvious. Logs. Errors. dmesg. IO. Mem. Processes. The pretty graph ELK tools can tell me this info, but what I want to look at next is easier to jump to when I'm already there, than trying to locate IOWAIT in something like splunk.

All looks good on the web servers. Ok. Lets check out the dbs in one term and the apps in another. You follow the request though the infra. Splunk or ELK can tell me one of my apps is eating 25,000 FDs but then what? I need to login anyway. Next on the list are tools like strace/truss, iostat, netstat and so on which will immediately tell you if it's an infra/load/config issue, and we go from there. Down into the rabbit hole.

The point I'm trying to make is; for me at least, the tools we're deploying and being paid well to deploy now like dataloop, newrelic, splunk and so on are actually useless for solving real-time prod issues (for me personally, and my crew, at least) because they only expose a very small amount of info, and almost regardless of the issue I'll need to be on the box looking at something unique to the problem to either explain the impact of it or to mitigate it.

As I said though, I'm a recovering ops person and I'm doing dev these days. I still tend to use print statements when I hit a bug; although since I'm now mostly doing Erlang, bugs are rare and usually trivial to track down.
This case shows the intel community lacks in the tech-smarts department
Guessing they mean the fairly common (around me) practice of a cab driver loaning their car to a friend or relative who may not have the correct licenses or carry the correct insurance.
Bulk Data and API for U.S. Congress
Bundling this with internet and cable is also a sneaky way to manipulate taxes.
Neither of which is very attractive to most people.

The author alluded to it, but domain-specific version control is more likely to capture history, especially since most people don't know it exists. Recent versions of Word, for example, record old versions, so we've got that, if we can still read Word documents.
There is, predictably, an integration to Pivotal Tracker:

https://github.com/concourse/tracker-resource

I'm not aware of any others. It might not do quite what you want - it's more about pushing the progress of the CI pipeline into Tracker than about bringing information from Tracker into the CI pipeline.

However, resources are fairly easy to write:

https://concourse.ci/resources.html

So if your task tracker of choice has an API (or a command-line tool!), it should be kind of easy to build an equivalent.
You can add a custom resource type (http://concourse.ci/resource-types.html) to add these integrations.

There's a Pivotal Tracker resource that does what you describe: https://github.com/concourse/tracker-resource
However this case matters because it closely resembles what got a developer pissed off enough at npm to unpublish hundreds of modules.

And the current changes don't help with the pissed off developer scenario much. Because a pissed off developer can simply publish broken versions of packages instead of unpublishing them, and still break the world.
> Your injuries could potentially be more than what your insurance would pay, thus your driving friend would be liable for the injuries.

I suppose that could happen to some, but my insurance pays for all care after I satisfy the flat out-of-pocket requirement.

I suppose my friend would be liable for the out-of-pocket cost, but that would typically be only several hundred dollars--a fair amount of money, but not much relatively speaking if this is a wreck that caused injuries.
Yeah, what's triggering those responses is a Reddit-tinged reaction to nuts and bolts investigative journalism as if it were somehow contravening a new Internet norm.
Not a good idea giving some form of level III consciousness to the robots.
I think some things can never lend themselves to the 'gig' sort of payment system because certain things aren't merely 'gigs'. This is especially true with the reference of SpoonRocket which seems to be fighting against another business (BiteSquad) for the same demand under food delivery/pick-up. Granted, the price of a restaurant cooked meal will be higher but when you're just hankering for a banh mi from Lu's Sandwiches you don't bother with something like SpoonRocket. It just doesn't make sense. As for the other examples, I can't say why they failed but I'm going to say there had to be some mismatch between factors of production and the demand/consumption of what's served/produced therein. I do think SV's would be startup darlings aren't taking a hint in this regard of doing good research on these matters but some things don't need 'disruption' if they're as old as time. Just a suggestion.
I wonder what the ettiquite is when sharing a ride like this? On a bus or in a cab there is no pressure to make conversation with the other passenger/driver, although sometimes they may be chatty. In this situation I'd feel pressure to make conversation with the driver, but what if I want to just read? Would that be rude?

If I found a good driver I would just deal directly with them because (a) I know they share my route and (b) I don't need to get to know them again each time I commute. That would be money off the table for Lyft though.

But I would not use the service because I have kids to drop off and also I may not finish at the same time every day.
This. It's an easy way to bend tax laws.
The service they provide is essentially a canvas. They go through great lengths to provide to the user the abstraction of a canvas. So this would be analogous to a chainsaw company selling a product named "Chainsaw".
As far as I'm aware there isnt any blkfront support in the recent changes, which would be needed for EBS.

Support for blkfront is not needed to get up and running with Xen though, so it makes sense to defer it until later and get the bootstrap going and then the devs can focus on the remaining pieces.
You could also have a conversation in real time, and not delayed by a second. Cell phone delay has made it impossible for me to carry on a meaningful conversation with anyone.

There's also value in having a phone number for a house or a family, separate from phone numbers of individual people. I don't want my utility company or my cable company having my cell number. But I'm not the only person that can make decisions about anything we might need to talk to them about anyway. The house number reaches both my wife and me. Cell #s can't do that.
How to write mathematics on Medium
>I am referring to the 85/101 merge near all the Google exits.

I've never stepped foot on the West coast, but I found this sentence really amusing! I guess I never realized the extent to which GAFA was embedded in the landscape.

(Nevermind this East-coast pleb. Carry on!)
Not the parent commenter but I can see how this would harm the product's image as you've stated. However, they're not forcing you to do anything. Technically, they're just saying they're not going to maintain their code anymore and it's up to you to continue or not.

It's as if you've gotten a lot of business to your small coffee shop because I've chosen to shuttle potential customers to and back from your shop. If one day I tell you I'm going to stop doing this, but you're welcome to pick up the slack, am I truly being unreasonable?
Disclosure: I work at Google on Kubernetes.

Please feel free to email me (aronchick (at) google) if you'd like to discuss this further (either P or GP post). We've seen a lot of this, and would love to help you out!
Well, the end of support for Windows XP in 2014 was announced in 2008. Windows Vista and 7 were available, and the Windows 8 launch was at hand before the date of his arrest.
But the text omits to mention Windows 8.1 which was announced by Microsoft in 2013, after the arrest but well before the Truecrypt announcement was published in 2014.

This could be because Windows 8.1 was only considered a relatively minor upgrade to Windows 8 by the author, or because it's existence was unknown at the time when the text was written.

This remains open to speculation, but it does not refute the possibility of a dead man's switch.
Anyone know if it can pull Caller ID from Google Contacts? That'd be a killer feature.
The problem is that trademark law pushes kik to be asses here. If you're not seen to defend your trademark publicly, you can lose it. So lawyers are constantly looking for trademark violations. And when lawyers find them, they usually start with legal threats.
The previous title was factually incorrect: it did not match the claims of the article. Even the OP admits it was a mistake.

https://news.ycombinator.com/item?id=11382412

The new title may not be great (as it's copied from the article, where it exists in the context of a larger series), but it's at least an improvement over one that was simply wrong.
Interview with FLIF Creator Jon Sneyers
I wasn't trying to patronize, I was making it a few seconds more convenient for you in this case (this was NOT a literal "LMGTFY" back-hand!). And I wasn't trying to proselytize. And I know that "what works for me" might not be "what works for you." I just know that individually, and especially on any programming team, this has been a practice that has paid off in spades AND "feels better" as well. YMMV, I guess.

I mean, there's a rational explanation for it: Your code produces states. What is a bug? An unexpected state. As long as you can contain/model ALL of those states, in your head, at all times, while working on the code, you can potentially write 100% bug-free code, at all times. But as soon as you cannot, then the tests will help contain the many possible states your code produces, and that your brain can no longer contain.

And unless you are infinitely genius, your code will eventually reach a point where you simply cannot model all of its potential states in your head (this goes manyfold on a programming team where everyone is sharing bits of the "mass state" the code can produce.)

Speaking of controlling unpredictable states and therefore bugs, FP often comes into the conversation as well, here's John Carmack on that topic: http://gamasutra.com/view/news/169296/Indepth_Functional_pro...
I wonder if this means they'll be actually working on improving Google Voice again after all these years, since it looks very much like this product bundles it. (The "ring your mobile" and "transcribe your voicemail" features.)
"casual users"

It won't matter given my use case of non-technical people snooping on computers or half-assed educators finding what I stashed on barely maintained PC's. I'm not speculating: they were fooled to the point they gave up trying far as I know.

"Of course you can make it even more interesting."

This is true. Your ideas are interesting. My brief foray into this sort of thing brought in a problem: compression passes applied at different points in apps and services. Your file might get modified at some point by a cheap storage service.

Also, the readers are lossy by design. So, these two things must be considered in any of these stego designs using multimedia formats disguised as actual multimedia. Plenty of methods still left.
Show HN: Steam bot to auto invite people to your groups
More or less with a number of caveats :)

Telco/ISP provided "VOIP" is often technically Voice over IP (as in the protocol), but regulations and implementation can be subtly different from VOIP (what people think of as Voice over the Internet AKA "over the top" or OTT).

ISP-provided Voice often comes with requirements for battery backup in the fiber/dsl/ata box so the user can call 911 during a power outage. There's also reporting requirements for outages that prevent a user from dialing 911.

Also, with ISP-Voice the VOIP part is considered a implementation detail so it can be given absolute QoS priority over internet traffic on a given last-mile link. This helps with being able to call 911 while someone leaves bittorrent open or whatever. OTT voip doesn't get that benefit (and that's not technically a net-neutrality violation).
Mine is Cable. Anytime the network goes down I have to put on headphones because I know I'm about to be inundated with 'Someone go get the cable!' and 'Why don't you check the cable?', and 'The cable is down!' and get briefly confused. The network's gone down more often than you'd expect.

And I haven't worked for Cable TV, but I have worked on things you play on TVs.
Why You Should Use Tumbleweed
Ah, gotcha. So if I'm following this line correctly, it'll need someone to write a wrapper that detects updates to .yml files and invokes fly?
This looks awesome! I hope to transition to it, handling Jenkins configurations is a huge pain.

Some of people also use their CI tools for running arbitrary one-off scripts (like deploys). Is this possible with Concourse? Currently we have a few Jenkins jobs that just execute a fab task that then does the actual work.
Hi, Tom!

> do it concurrently

Does ember renders concurrently?

> There is a huge gulf between "synchronously render a component in Node" and "asynchronously boot an app, marshall async data, render an async UI, and do it concurrently."

I dont think it is fair to say it that way. React implementation doing all this (except async/streaming rendering) is man-week at worst in existing medium sized project, and man-day for a new project with no pre-existing code.
Great Fire Wall is controled via malware, backdoors, network filtering, etc.; sort of like security firewalls, but only if compared to what a company might do to enforce their policies for what employees are able to use the Internet for. Paywalls are just a pay for access method for making money from content, and unrelated to the topic; meaning it's not like in China there a secret backdoor for the top government officials to see the real Internet; oh, wait, there likely is... :-)
I considered that but I'm worried that won't work with WebAssembly because it's a more memory-constrained environment. Your app may generate a ton of data in a frame and run off the end of the address space. I guess I'm probably just thinking back to asm.js where you sometimes only have 256mb to work with. I'll try this first at least since it makes stuff easier.
Erdogan is a disgrace for all civilized Turks! But obviously there are too many Islamists in Turkey to keep electing him!
Brilliant code != beautiful code. Dan Kaminsky called Satoshi's programming alien technology with regard to security.

I haven't looked for similarities but I'm guessing someone has already compared the two using Aylin's CodeStylometry work: https://github.com/calaylin/CodeStylometry
Of course! BigQuery export operations are free.

Although compared with other cloud technologies, BigQuery is incredibly cost-effective :)
Personally, I'm glad to see them using GitLab[1]. While GitHub vs GitLab may make fairly little operational difference for most projects, I do think that competition is sorely needed in the Git hosting space right now.

https://gitlab.com/sortix/sortix
Yes, flexbox is not supported in IE8 & 9, wrong spec in 10 and buggy in 11, therefore the 'terrible'. I'm talking in the context of websites that have to work on the open-web (where unfortunately a lot of people still use those versions of IE).

For contrast if you work against a framework like Bootstrap 3, sites 'just work' all the way back to IE8.
I'm sure they will find a way to pipe the deal through Ireland and offshore that profit
Your last line there is the key, and the filter by which we can see if that comic is worrying or wise.

HN has a rather brutal philosophy in flagging/downvoting items lacking substance and shadowbanning troll-ish folk; it seems to work ok and is usually not too sinister (and when it is, human intervention/moderation can often help). By contrast, large communities like states and national institutions can - with just a hint and a nod - inflict surprisingly chilling effects throughout communities of millions.

So where do we draw the line? I dunno. Whereever we draw it, it's got to be parametric with enough inputs to take into account at least the rough subtleties of the situation. Because the comic is right: I don't need to put up with an asshole's bullshit, but I also don't want to destroy them. Just, you know, tone it down a smidge and stop being a jerk.

I'm fairly passive. Normally I do that by ignoring them, changing the channel, or just avoiding the website. Rarely I'll actively flag or downvote (ugh, so hamfisted). And sometimes, I just go away if they take root. With high-signal web analytics, tracking, stats, and other social-buzz things, my avoidance may actually be logged and noted. Maybe I help starve out what I consider noise, thus boosting what I consider signal.

What if a lot of people in a community are just outraged? Or are very sensitive to easily become outraged? I think that's where things get underdamped fast, and where your worries come into play. My only thought is to starve it of energy 'till it settles down, but we've seen enough self-sustaining bullshit storms that I bet passive resistance doesn't work much anymore for that.

EDIT: speling
This was essentially Lyft's first idea right? I believe it was called Zimride?
Probably by emitting control sequences from the input files unfiltered to your terminal. Just guessing, but it's the one big thing that occurs to me when thinking of an unsafe pager.
If it walks like a duck, smells like a duck, and quacks like a duck, a court is very likely to call it a duck.
I love Ember. It seems to be one of the only sources of sanity and reason in this community.
I appreciate the reply and that what you mention is undoubtedly a major turnoff for many people depending on attitude to work/life balance and family, etc.

I guess I'd wonder whether SpaceX would ever intentionally target those people for "poaching" though given they're not a cultural fit to begin with? It would appear from the outside to be quite a self selecting situation?
"Pay because it's good" is the best content monetization model yet.

Glad to see this sentiment here.

If Patreon is too involved, content creators can also put a PayPal tip jar on their site:

http://micheleincalifornia.blogspot.com/2015/11/how-to-make-...
Agreed on second point - one of the first things we looked at when introducing node.js at our company was setting up a private in-house npm repository, similar to what many companies due in the Maven ecosystem to both store private packages and filter/proxy the global repo for outages, problems, etc.

It was rather hard and awkward, and there was no solution or support offered from npmjs-the-company. Some time after they introduced private (and hosted) npm repos as a paid offering, but this is still not what a lot of companies want. While perhaps I'm jumping to conclusions, a free in-house offering does not seem to be in their business model and therefore the community has suffered a bit.

(I'm aware of the unofficial projects for this)
https://cloud.google.com/bigquery/public-data/hacker-news
Anyone thinking about attending moonconf should take a quick look at their Code of Conduct:

No one at any events associated with Maitria, may speak to, touch, stare at, follow, or otherwise engage someone without their consent. Making jokes within earshot of someone you know (or even think) is upset by them is a violation of consent. Acting as though someone's gender is other than what they say it is is also a violation of consent. Doing things that people feel shitty about is often a violation of consent. Doing them more than once is even more likely a violation of consent.

http://maitria.com/coc

Given that Orwellian monster, I'd feel a lot safer at LambdaConf than Moonconf.
I was going to integrate my app with IFTTT, but after reading this post, as well as the responses from the CEO in this thread, there is no way I will ever in a million years integrate with IFTTT.

I think its an interesting train-wreck to take note of. And it is clearly a reflection of the CEO, who has consistently misunderstood or ignored the true complaints people have about this new direction, while half-apologizing for terms and blaming "communication" on terms that place absurd expectations on companies that IFTTT chose to integrate with, and now wants to reverse the roles of.

Meanwhile, maciej is doing everything right. Communicating with his users about what is actually going on (instead of lying to them as IFTTT has done), and doing so in a thoughtful and playful piece of writing.

Time will tell how this plays out. But I think if IFTTT's moral compass is willing to let this go public, if they think this is/was an actual good idea, their days are numbered. The PR around this change alone was horribly executed, in addition to the change itself being a big middle finger. Neither speaks to an understanding of their users or sites they depend on to integrate with.

IFTTT would be NOTHING without any other services to integrate with, and they chose to throw them under the bus.

You had a chance, IFTTT. But you revealed your colors, and now you don't.
They're using credits. It's called money.
chmod 500

Because it's certain he could execute as well....

(In fact, let's make it 510. The group can't read or write but they don't have problem executing either.)
Right, but why would this be the least of my concerns? What's the greater concern here?
When you said that, I expected 15, not 25.
Janet C. Phelan also wrote about him June 2015:

http://journal-neo.org/2015/06/12/paul-calder-le-roux-arch-v...
It's also powered from the central office, and doesn't require a local electrical power source.
Your own health insurance is one thing - compared to it, your liability in the event of an accident is essentially unbounded.