skysight-inc/HackerNews huggingface dataset:
THIS NEW PEN DIGITISES Your NOTEBOOKS AS YOU WRITE IN THEM
Umm... It's 50/50.
React unminified is ~660kb.
If you want to get technical, ASCII is a single-alphabet substitution cipher.

Remember, lawyers have tried asserting that copying to RAM is copyright infringement.

http://newmedialaw.proskauer.com/2008/08/20/ram-copying-an-i...
Game of Thrones Season 6 Can't Wait. :)
A valid point. Haven't used it for bulk (automated?) testing, as I personally never find myself running more than once instance at a time while debugging.
I've Had Enough and Today Everyone Has the Phoronix Premium Experience
Illuminating the Effects of Light Pollution
I had the same thing the other day. I figured maybe it was because I was in incognito mode (because logging into half of Google's properties with uBlock and Privacy Badger enabled doesn't work). sigh
At work, we use master as you describe, and follow gitflow for feature and bugfix branches.

For release-to-customer products, we have a release branch, eg: release/1.2.3, and as part of our CI build, that number is automatically picked up and used in the product itself as the version number.

For our cloud/SaaS/single-instance stuff, we have a 'staging' and 'production' branch, and typically have 3 environments (dev, staging/test, and production) all of which are continuously deployed. We typically just do fast-forward merges to bring staging and production up-to-date with master.

In both cases, when a developer is working on a new feature or fix, we want them to base off master.. which is the latest fully-integrated build, though it hasn't passed QA. If they worked off a production/release branch, we'd continuously have to deal with conflicts as by definition they're basing their changes on out-of-date code.

A 'develop' branch could work for some of our small stuff, where typically production/release isn't far off from master, but for our main stuff we do a 2-3 month release cycle, so master usually has quite a lot of changes that aren't in release.
> This is complete nonsense.

I don't just mean in getting federation to work. I mean building a good network that is response to updates and adding features. A network that does not make further devlopment almsot impossible.

> If you don't build in mitigation to this problem from the beginning, it will never happen.

I would disgree about that. I think an incremental approche can work. I guess we will see about that.
Yes, there's a good chance the the spike and drop in high-end digital camera sales represented a one-off replacement of the high-end film camera fleet with digital.
To me this just screams scam, I personally wouldn't want to attend a conference where speakers are paying to participate because likely it will just be more of one big marketing experience controlled by people that paid to get their content up there. We get enough of that through the sponsors and booths at a conference, the speakers should be presenting balanced talks on specific subjects.

Traditionally (from my experience), speakers are invited or apply based on a topic and are not asked to pay any fees. The conference costs are covered by the conference attendees, sponsors and booth fees.
since reddit works fine in smart phone's webbrowsers, why we even need an app?
YOU WANT QUALITY?
For international readers, in US English 'table' means 'postpone', whereas in British English it means 'to present for discussion' which has almost the opposite meaning!
I like how you made the header in a modern design and as soon as you scroll or go to a different site it just looks old.
You mixed some straw-man objections ("Facebook is evil") with one that's important and legitimate.

People are right to be cautious with closed source crypto. It has a long and sordid history of turning out to be snake oil, terribly implemented, or outright backdoored.

Given the people involved, though, and all the scrutiny the Axolotl protocol has already withstood, WhatsApp looks trustworthy.

It would be better if the source code were available for inspection, and even better if it had a deterministic build so that people vould verify that what's installed on their phone was actually built from that code.

Rolling out usable end-to-end encryption to a billion people is still a huge achievement and we owe Moxie, Trevor Perrin, and the whole WhatsApp and Open Whisper Systems teams our thanks.
So far spending a day (or two) onsite and working on something together with the team has been the best option for me.
You:
- get to see what people are, how they work and what they do
They:
- learn whatever they need about your skills

So it's a win-win.
That's what they tell me. I honestly didn't feel like it mattered, my mom and I are ISTJ for instance and we get along/work with a pool of such random EN* it feels like you pull these letters out of a bag.
No, you want them to build up.

Tax will be levied on the value / rental income of the unimproved land---not on a fixed charge per area. (There are some ways to use auctions to set these taxes automatically in an economically efficient way.)

See eg http://www.economist.com/blogs/economist-explains/2014/11/ec... or https://en.wikipedia.org/wiki/Land_value_tax

Very beloved by economists.
This is just a PR puff-piece for a couple of security companies that monitor the "dark web". Not much substance here.
I go by what the IPCC states. As poor as its past performance has been in refining the science into accurate predictions, it is by far the best source of "scientific consensus" we have. And there have been many papers published over the last 20 years claiming a whole number of things.

James Hansen has been wrong so many times in the past, I'm not sure why anyone still listens to him. And if you have any feel for the data at all, several meters of sea rise in 50 years should strike you as nearly impossible. There's certainly no strong (or even weak) evidence for this.
This is more an artifact of how our data is currently organized more than anything else. It's on the list of things to fix once the guts of the whole system are set up.

We track height and weight (as well as a few other characteristics of a persons physical appearance) to give attorneys more data points on how to distinguish two people who have different names. Who knows, it might also be relevant to a case someday.
Using the Google's own reverse image search to break an image-based captcha. Simple, but brutal.
A lot of people fail to even consider the consequences of possible breakthroughs in disciplines that helps discover more breakthroughs.

Cascading discoveries are already hard to think through very far, but discoveries that accelerate the pace at which we make discoveries make the whole thing very chaotic.
Yes, and consequently the platform should not (and in practice does not) receive declarations of high security in its default state. Ignoring PRISM, this is true of every major smart phone platform as they all have remote install and update abilities that excepting Android aren't generally straightforward to disable. Argumentum ad populum is not an excuse for doing something even when you know it's wrong.
Not that it can become much worse than it already is, though. The current reCAPTCHAS are already "fuck this shit"-inducing on Tor.
Like I said, none of us take it seruiously. But the places that hire using that which we've experienced have been top notch in most ways; I think to a point it's okay to just let them satisfy themselves with their little tests.
I think that's an amazing feature. It does the same thing for Soundcloud playlists.
I would say encryption is somewhat of a red herring. It is the introduction of similar surveillance policy that is quickly becoming widespread, I don't even think Hungary is an early adopter here. The sources even citing roughly 'granting powers other governments already have' and establishing an agency TIBEK with similar access to data (without warrant IIRC) as common 3 letter agencies. They even use the same terrorism/ISIS/Brussels/France reasoning.
I guess in the end everyone can pick their surveillance point on the safety - freedom graph.
Are these governments really spending all day spying on us?
Jailbroken iPhones or Androids that have an accessible filesystem would give access to the installed executable.

Having this, Whatsapp would be subject to having their app disassembled and checked against the source. Sure, they could modify the executable, but it's a PR liability for them.
Experts should be paid - marketeers should pay
... or do not play God at all. (Edit: This is also an ethical choice)

Just drive safely. Keep your distance and be very good at reducing your own speed as fast and as safe as possible.

Even in this hypothetical it will certainly help reducing the speed as the motorcycles will have a better chance to react.
You mean what mobile phones have done to cameras, gps navigators, handheld gaming, personal music players and other things that required dedicated devices in the past?
I like this idea. A friend of my co-founder created something similar, albeit with key differences, for politics (AppleCart). They are seeing some great success so far, you may want to reach out to them.
Living on a narrowboat is a very niche way of life even in the UK, and they have far more mobility and much lower densities than any form of dense urban living could.
What I think is and is not better about .Net OSS these days
The other way round, the more they arbitrage me, the more I buy dear (they front run me and push the price up).
Thanks for the thoughtfully considered response :).

Regarding security with redis. Did you read the docs here? https://www.elastic.co/guide/en/logstash/current/plugins-out... Logstash does support Redis Password auth (as does Filebeat). Regarding the encryption with redis point, seeing as Redis doesn't support SSL itself, are you using spiped as the official Redis docs recommend?

Regarding the two queues, I would like to clarify that you can do this with the:

Filebeat -> Logstash -> Redis -> Logstash -> (outputs) technique.

If you declare two Logstash Redis outputs in the first 'shipper' Logstash you can write to two separate queues. And have the second 'indexer' read from both.

It is true that if one output is down we will pause processing, but you can use multiple processes for that. It is possible that in the near future we will support multiple pipelines in a single process (which we already do internally in our master branch for metrics, just not in a publicly exposed way yet).

Regarding JVM overhead. That's a fair point about memory. The JVM does have a cost. That said, memory / VMs are cheap these days, and that cost is fixed. One thing to be careful of is that we often times see people surprised to find that they get a stray 100MB event going through their pipeline due to an application bug. Having that extra memory is a good idea regardless. We have many users increasing their heap size far beyond what the JVM requires simply to handle weird bursts of jumbo logs.
Right, but you can use caching / service workers to solve the network time, but there's nothing you can do to speed up the initial javascript load time.
no it's foolish to trust something that hasn't been independently reviewed. How can EFF recommend something that hasn't even been subjected to an independent security audit?
There have been at least two game-changers since then.

The first is high-ISO: my Canon 40D can take a good picture at ISO 800, but my Sony NEX-5N can take a good picture at ISO 12,800, which is basically pitch black - think dark room by the light of a television. You can shoot available-light pretty much anywhere, particularly in combination with the image-stabilization tech and superfast lenses that are now available. Some of the newer sensors will get a good image up to 102,400 and can capture up to 409,600, which is just nuts. That's "dim moonlight" territory, basically night vision.

http://www.sonyalpharumors.com/amazing-sony-a7s-low-light-te...

The other is phase-detect pixels on the sensors. Previously many cameras had to use contrast-detect autodetect, where the camera racks the lens and samples the image for peak contrast on the target. Only SLRs had phase-detect autofocus, which was much faster and more accurate but required a separate set of sensors. But now they put phase-detect pixels right on the sensor, so you can get small cameras with fast/accurate focus.

Not the camera itself, but lenses have also come a long way in the last 10 years. Superfast f/1.4 primes and f/1.8 to f/2.8 zooms are now faster, sharper, and cheaper (and the idea of a f/1.8 zoom was unthinkable 5 years ago). On the high end Sigma's Art series are simply fantastic, and Samyang is raising the bar on low-end lenses too.
IE has the cheating husband problem. He says he'll never do it again, buys you nice things, hell, is even nice to your mother, but in the back of your mind there's always that latent fear that he'll cheat on you again.
How to Develop a Microservices Pipeline
WW3 CAN WE TRUST,CAM MORON,CLING TON OBI ONE CANSHIT,AND DE ELITE CROOKS -
Project Manager/Scrum Master

I’m passionate with delivering a high grade product within the limits of schedule and resources. For the last 3 years sucessfully managed over 10 projects with 7+ team members. In work use Agile methodologies and phylosopy. 5 years ago started as a QA Engineer, so I understand the mean of « quality ».

Location: Dnepropetrovsk, Ukraine

Remote:yes

Willing to relocate: yes

Technologies:PM/Scrum Mater

Résumé/CV: https://ua.linkedin.com/in/anatoliylazarev

Email: anatoliy.lazarev@gmail.com

Thanks
What if Apple is Wrong [about privacy]?
Burr Encryption Bill – Discussion Draft
Intro to Machine Learning and NLP with Python and Weka
This is not an article, it's ad.
In addition to tiers, I think there are dimensions. Mainly:

1: security against targeted surveillance from criminals or state-level adversaries. (= spying targets).

2: security against mass surveillance. (= finding targets)

I think it's possible to have Tier 2 system that is Tier 1 against mass surveillance. Individual connections don't have to be proofed against state level actor targeting individuals. It's enough that the whole system works in a way that makes mass surveillance too expensive.

In fact, I think this kind of security is enough to ease most concerns against government surveillance.
I use vlctube https://greasyfork.org/en/scripts/1783-vlctube to not only download youtube videos but to also use vlc as default player, there is a huge performance boost, I no longer hear my cpu fan when playing a youtube video.
smart phone displaced cheap camera market with image quality that is "good enough" for every day photos. especially those that will only be used digitally. they did the same thing to hand held voice recorders. how is this "completely insane" ?
I have thought about this problem and like your goals. Like @rkho stated, re-scanning is a pain. Perhaps if you could somehow get buy-in with the grocery store: the store sends an electronic copy of the bill that can be processed; have a program read the bill.
Why not use an SSH tunnel as a SOCKS proxy? Would save you a few steps there.
Good points, though... Some of the best known, and as a result watched races are the ones that had wrecks; my opinion.

Personally, I don't watch races, and do either street racing, long distance, or bad weather driving; which is it say that I don't care for race tracks personally.
The answer to almost all of these hypothetical problems is "hit the brakes". Speed is the main killer in automobile accidents, it's a power law. Just a small reduction in velocity can have a dramatic impact on the survivability of an accident.

What about the question of whether to swerve into traffic to avoid a kid who ran into the street from between two parked cars?

Answer: you were going too fast to begin with. If you're travelling anywhere that this is a possibility, your maximum speed should be less than 20mph. A collision at that speed is almost never fatal. That speed also allows almost instant braking.

The fact that autonomous cars will be driving so slow and defensively in the suburbs will perhaps be the biggest cause for the coming backlash against them.
It's a weak strawman, though. He isn't literally saying that, but is trying to discount those who complain about closed source by comparing them to people who are apparently anti-iPhone. Then again, maybe that's exactly what you mean and you'd be right -- normally that sort of tired strawman would be dead.

It really is incredible to see tptacek discounting the closed source, completely unaudited nature of this product. A company is saying "we have total end-to-end encryption...trust us", and to believe that you trust the binary that is on your device, that it is managing keys properly (there is usually a fine line between usability and security, and usability usually wins), and you trust that they don't misuse your messages when they pass through their server. They control every aspect of the conversation, and are fully capable of completely undermining your security at any moment (if not already). In practice it's not terribly unlike the widely discredited JavaScript encryption approaches.
Scientists Stored These Images in DNA–Then Flawlessly Retrieved Them
You appear to be saying that you had the opportunity to use cannabis when growing up, and managed to refrain from turning in to a stoner. That's how I read this comment - my apologies if I have misunderstood you.

I am going to assume that you grew up in a country where alcohol was available to teenagers, to a greater or lesser extent. And yet you also - presumably - managed to avoid turning in to a raging alcoholic.

Despite the availability of drugs and alcohol, you managed to avoid becoming a slave to either of them.

The mere availability of drugs (of any kind) will not immediately turn your children in to stoners, alcoholics and junkies. The causes of addiction are deeper than that.

As you said, you know what it is like to be a teenager. Teenagers experiment with various things that adults would prefer they avoided. Given that fact, let me ask you this:

Assume your children are going to drink underage (it is statistically likely that they will). Would you prefer them to drink a) a bottle of beer that an older friend purchased on their behalf, or b) a jar of moonshine, which was homemade without any quality control, and might contain adulterants?

This is not a rhetorical question, or a snarky one - I'm genuinely curious as to which you would prefer.

> My point is that I don't want my kids being turned into stoners and that the law should be on MY side, not the guy pushing drugs on them.

You seem to be saying that your children will be turned in to stoners if cannabis is easily available to them. Given that alcohol will be available to them, do you worry that they will turn in to alcoholics?

If not, why not?

If so, are you also campaigning to return to the days of alcohol prohibition?
I love cdnjs.com but check out npmcdn.com
This is certainly true for the optical sensors. I wonder what the long term effect is of shining a bright LED at a small patch of skin like that?
I didn't see anything in the first HPC Wire article about Moore's law not being dead. All they really said was that HPC was a useful tool to continue improving processor performance:

"Without supercomputers, we wouldn’t be able to understand what it takes to continue the march of Moore’s Law, and without this understanding, we wouldn’t be able to create more powerful supercomputers. This symbiosis is at the heart of the relationship between Moore’s Law and HPC."

As for the second HPC Wire article, this sums it up fairly well:

"What you see is that the performance per core has taken a dramatic hit around 2005-2006, but it was compensated by our ability to put more and more cores on a single chip"

Increasing the number of cores on a CPU is not the same as keeping Moore's Law. We could keep doubling transistor count every two years if we could keep doubling the silicon wafer size at the same time. Moore's Law only really makes sense if you consider it as doubling the number of transistors within the same wafer size.
Wat. Fuck the camera thing. that is insane.
Another option is figure 8 racing.
Thanks for the comment.

i) Data portability is a key feature for us. As the excellent comment above noted users have been burned by fairly complex and locked-down in house CRM systems so we are doing our absolute best to make sure that the data can be accessed and ported in an easy way.
ii) This is an interesting idea, especially with regards to evidence, care to elaborate a bit more? Do you think there is room for something beyond the regular database to track these case features?
I believe 'babel-root-import' works on windows (haven't tested myself). It's a lifesaver if you are already working w/ babel (which I am).

It really saves time when you forget what nesting level you are at, and are trying to get to some other folder. I can easily remember my absolute paths, but always forget the amount of "../../.." I need. It's also nice to be able to copy imports from your "src" folder to your "test" folder, and just have them work (which they do when using absolute paths).

This is an interesting take on that idea (using symlinks instead of transpiling).
HN as you mentioned
ProductHunt
BetaList
Techcrunch

Waiting for others to expand the list:)
The classic hedge fund used to be able to find niches in the market where they could make money - and the good ones used to be able to do it well.

They could do things other money managers couldn't - short stocks (i.e. hedging against a fall, hence their names), better analysts, investments in more diversified instruments, early HFT.

They would often take a fee of two and twenty - that is to say 2% of the money you lent them (every year), plus 20% of the profit they made from that money.

If you gave them $10 million, they'd take $200k as a fee every year, then 20% of the profit they made. So let's say they made you $1 mill a year, they'd be paid in the first year $200k fees and $200k performance fees.

However nowadays there's millions of them, and almost all of them lose money as there weren't that many profitable niches to begin with, and a lot of them were lucky anyway (survivorship bias).
There's really not much of a difference, except that WhatsApp allows you to verify the fingerprint and will notify you if your chat partner's public key changes.

WhatsApp doesn't force to you meet your contacts, and there's no "signing each other's public keys" involved at all.

There are two levels of authentication or verification - with iMessage, you only get the first one:

- The first is WhatsApp telling you "Hey, this is +555 0100. Their public key is 12345. Once upon a time, I sent an SMS to that number, and the device with this key was able to read a code in that message. Looks like the owner to me. Good luck! PS: I might be lying."

- (Optional) You compare the fingerprint by meeting in person or communicating through some other secure channel. This will ensure that WhatsApp is not lying to you¹, and that you're actually encrypting messages with a key belonging to the recipient (and vice-versa).

¹ Unless your client has a backdoor, of course.
Get tired of theses posts which are not content but barely ads for their products.
The human brain needs about twenty watts, fits in a compact package and outperforms computers on a variety of tasks. Squishy wetware is pretty far from computronium. I think we still have a long way to go before we hit fundamental limits.