skysight-inc/HackerNews huggingface dataset:
And yesterday Australia announced that it will be pushing ahead with an ISP level data retention scheme in the name of fighting terrorism [0]. This is after last year explicitly asking for feedback on the proposal to retain Australian's internet history, and receiving countless concerned letters from the community (along with security agencies who were pushing for data retention) [1].

I suspect in a decade or so that we will also have a similar chart as this post [2].

[0] - http://www.zdnet.com/abbott-brings-on-mandatory-data-retenti...

[1] - http://www.aph.gov.au/Parliamentary_Business/Committees/Hous...

[2] - Only an order of magnitude smaller due to our population difference.
Read the post; apparently Zend doesn't make deep array copies in some circumstances.

The quote from the spec is "Unlike conforming deferred string copy mechanisms discussed in §§ that must produce the same observable behavior as eager string copying, deferred array copy mechanisms are allowed in some cases to exhibit observably different behavior than eager array copying."

Note the phrasing "observably different behavior".
If you move to one time zone, dates get complicated as well. You may have meetings scheduled on separate dates but in the same business day. Birthdays: they're now the afternoon of one day and the morning of the next.

Furthermore, while travelers may not have to change their wristwatch to account for the local time, they still would have to grasp "what time the locals do X." This may be more difficult for people to reason about if they can't easily draw on their expected scheduling from "back home." Simply knowing that 8:00 to 5:00 is a common work-day will no longer be easily translated, as it may be 11:00-20:00 one place and 05:00-14:00 somewhere else.

In any case, people are creatures of habit, so they tend to fight change. So I don't foresee this ever happening, regardless of whether it would solve some problems (and debatably it may cause as many problems as it solves).
UI - of course the UI thread should not be blocked in handling IOs. My point is, move these IO actions to another thread; the code in that thread is good old synchronous/threaded code.

heart-beat - yes we'll need concurrent threads for handling concurrent requests in the blocking world; the question is whether this will result in too many threads, which depends on the application.
I think you're right, the headcount reduction number would most likely be conservative. But what I can imagine is that the overhead of administering multiple programs (some overlapping) is larger then just the salary and benefits costs.

Something like a more wood behind fewer arrows ... applied to government.

I'd like to see somebody else run the numbers on the "overhead" like a group of independent economist (eg. not me).
That might be ok if that's what happened, but it doesn't actually. You sign a contract which says something like "The employee will perform the duties of a software engineer to the best of her/his ability"; it's basically up to the boss to decide what those duties are on any given day.
Ok, we'll put it back.
The initial Operation Torpedo seemed rather strictly targeted ("Pedoboard"), and those are the cases working their way through court.

The Freedom Hosting malware came later, and it's not clear whether there even was a warrant or not, since it all appears to be still secret. To argue whether the warrant was sufficiently particular is impossible to say. I can concede that was too large a scope, but that defense can't really be made until there's a defendant.

Was it even the same malware in both operations?
> that can be solved by writing everyone a check, regardless of their income level.

I believe that is an explicit part of the definition of "basic income." One proposal I've read is that it must be applied for or opted into somehow, so wealthier people can simply refrain from accepting if they choose.
Hence my last point at states being better able to deal with issues in a more localized matter.
In case anyone is interested in the random number, `2862933555777941757`, but didn't catch it while scanning the PDF, it is shared with the "64-bit Linear Congruential Generator" [1]

The author specifies that if the key is larger than 64 bits, then it should get a 64 bit hash for use in input. But I wonder, supposing the compiler or processor handled higher bits in a single register and we had a need for it, would this algorithm handle a change of the magic number without a problem? Where would one look for such numbers?

[1]: http://nuclear.llnl.gov/CNP/rng/rngman/node4.html
>The transaction is quite simple: you spend $X, you get $BOOK. Perhaps later you spend $X2 and you get $BOOK2.

I believe this has analogues to how Jack Welch says (paraphrasing) "At the end of the week when the you have your paycheck, you and the company are even"-- implying that there is not further obligation. I find this hard to believe on a professional level. If I am a key person on a team, I have an obligation to give no less than 2 weeks notice, and probably much more if I want to remain in good professional standing w/ the company I work for (eg, more notice for small companies) . Why? Because despite the lack of contract and resolutions, there is more at stake than just what is stated on paper, there is reputation, business continuity and implied continuations in the relationship.

I see it similarly with an author. Yes, there has been a transaction that takes place and is complete. But if GRRM wants to keep relationship and reputation intact, then there is more to the picture than money in and book out. There is the way the customer feels when they hear the series is cancelled, for example.
But on the positive side for single-payer healthcare, there's no upper bound on how much you get to consume, subject to medical necessity.

The problem is that medical problems are financially bimodal: they tend to be pretty cheap (take some antibiotics) or incredibly expensive (you need dialysis or you have a brain tumour).

So unless you have some sort of useful insurance plan that covers people and minor dependents for less than what you're getting in basic income you'll end up with the problem of people who are unable to get serious medical conditions treated. And making medical treatments universally accessible is part of the point of most single-payer healthcare systems.
Oh that's very convenient, thanks. As another person replying said, I only migrated from 2003 a few months ago (don't ask) so I still have a lot of new quality of life features to discover :)
Everything faded into mist. The past was erased, the erasure was forgotten, the lie became truth.

-- George Orwell, 1984, Part 1, Chapter 7
I looked into Interactive Brokers in more detail and you are correct that their fees are extremely low. They do not seem to charge a hidden "spread" fee, which is they usual method that forex traders hide their fees.

Based on some googling, there are secondary fees to consider such as minimum monthly fees and wire transfer fees, which might make it more or less attractive than alternatives depending on conversion amounts and regularity of transactions.

You mentioned that you use Interactive Brokers. Are you a Canadian citizen living in Canada that transfers money into and out of an Interactive Brokers account, exchanging USD and CAD?
Funnily, before clicking on this link, I was expecting that the author would suggest that instead of discrete time zones we should have continuous ones, e.g., no matter where you are, it's always noon when the sun is highest. You know, just like it used to be pre modern times, and I was kinda curious how the author thinks he could pull something like that off in a completely different society.

Instead, his suggestion is pretty much the opposite: instead of discrete time zones, let alone continuous ones, the proposal is to have one static time zone globally. Strange that the headline calls the current system "impractical", as the disadvantages of a single global time zone are kind of obvious (see the comments here on HN).

I suppose, the current system is a good compromise that tries to address the disadvantages of continuous and static models.
It's like, slightly better than it used to be. But let me take this opportunity to evangelize for Ninefold. http://ninefold.com

Ninefold is, from my experience, everything you'd ever want from Heroku and much more (which in turn means much less). Far more simple UI and implementation, and extremely passionate and responsive dev team.

Please try out Ninefold if you've ever said "fuck you Heroku" like I have so many times.
Daily Mail has great photojournalism. I wouldn't trust anything textual from there, their reportage sucks.
Ha. michaelochurch almost literally wrote a book about the Gervais Principle, see his 26-part blog series on the topic: http://michaelochurch.wordpress.com/2013/08/06/gervais-macle...

And I don't think there are really any Losers destined for Cluelessness. The Clueless are the people who don't understand office politics, or think they can climb the career ladder simply by working hard and being loyal employees (not through strategic social climbing). Losers are people who understand and see the ladder there but choose not to be social climbers. They gossip, do crossword puzzles, punch out and go spend time with their kids. There are lots of Clueless destined to become Losers once they get burned out and realize what's up. Once you've learned that you can't unlearn it.
Data Visualization and D3.js Newsletter – Issue 90
Screencast: Starting a new Ember.js App
i'm in favor of something like a basic income, and my reasoning in part comes down to something very much like that in the article - we are already subsidizing people, and we're doing it badly with political overtones, so let's just get rid of the crap and make the system work.

I'd like it to go hand-in-hand with other sanity measures, like eliminating the gov't agency habit of foolishly spending their "leftover" money at the end of the fiscal year to avoid budget reductions the next year. It's a clear demonstration that the money isn't needed, and I'd rather see an ordinary citizen get to decide how that money is spent, because the gov't is just throwing it to well-heeled contractors who don't really need it.
5 reasons you should be using Sass today
If you have an Automatic and want to use both, this will be a no go since each will need to use the OBD II port in your car.
It would be cool if python could support date/timestamp literals.

I've implemented something similar in a query language I wrote, where dates are represented similar to ISO 8601 format:

d'2014-12-01'
t'2014-12-01 12:52'
t'2014-12-01 12:52 PST'
t'2014-12-01T12:52:20.0820Z'
t'2014-12-01T12:52:20.0820+08.00'
Open letter to the MEDUNSA community
>Concurrent programming is hard because "concurrent programming" usually means "concurrent programming with mutable states and imperative control constructs"

people have trouble even with database transactions - the simplest "imperative with mutable" concurrency model around. The simplicity comes in particular from well-defined hierarchy of objects and locking semantics upon them. No wonder that programs with concurrency, especially written in OOP languages where mutable state hidden, spread around in really disorganized way and de-facto inter-mixed with code, is just a mess. The article mentions Netbeans - yep, UI OOP models are among the messiest.
$50 might be the best price on offer, but I would consider it infuriating to pay a $50 tax to the bank on each and every pay check on top of the 3% currency spread they probably already charge.

$1200/year in bank fees just to get paid every two weeks? It's real money in comfy western Europe, in Brazil it's surely a fortune?
Well as someone in their target group (or maybe not, as someone above remarked, I don't know) I did find it juvenile. What's wrong with saying that? Or do I need to carefully construct everything I say with 'this is just my opinion' etc - this is just an off the cuff report from a first time user to help these guys out, I don't think it's reasonable to expect I'm going to be all touchy feely.
7 lucky best practices for managing and sending secure web push notifications
There are only 2 hard problems in Computer Science: naming things, concurrency, and off by one errors.
Good document, also, http://www.mit.edu/~viveck/code/Research_files/fbdof-1.pdf covers broader topics including FulL Dux.

Simple laymen's explanation, the transmitter wave form is fed back into the receiver but inverted so it cancels out the transmitters signal. You can think of this like noise cancelling headphones in reverse. With noise cancelling headphones you sample outside noise and invert it to cancel that. Here you sample your own signal and invert it and add it to the received signal and the inverted signal cancels out the transmitted signal. This technology has been around a while but the DSP technology is just now really getting good enough for it to be practical.
We're exclusively Linux at the moment, sorry.
Many of the "secondary" nets cover specific things, like food, housing, or healthcare, rather than just "money". It's harder to cut through those, though not impossible.
"There's a dilemma though - if the application code is writing bytes to
the response body with blocking write(), isn't it tying up a thread if
the client is slow?"

There are TCP buffers. If it gets full ya maybe you'll wait a bit but it's thread vs rope relative to blocking a whole big roundtrip data exchange while blocking a thread. Nobody really tunes the write buffers because it doesn't slow down our apps. That is not the case with calls to remote services.

Note that TCP buffers are pretty big so the chance of the thread blocking while writing are very low.
It seems like such a waste to use async libraries in many Java applications and I wince at the thought of a mainstream application framework adopting CPS. In the techempower benchmarks Netty beats Servlet by only like 3%. Maybe if you are serving millions of connections you will get your money's worth but I think a synchronous API in the application stack is the right answer for almost everything. Even Play framework with Scala which takes most of the edge off is still needlessly complex compared to say, Dropwizard code. You have to remember not to block, and be sure all your libraries don't block either. Why pick up that burden if it is not totally necessary?
Alaska distributes oil royalties to citizens of the state. If the wells suddenly dried up, so would the checks.
Yes, if you have light-weight threads, there's no question that threaded programming is better than async programming. But we are talking about heavy Java thread, and whether its cost is so high that we need to avoid threaded programming. I think the answer is no, generally.

Also, the discussion is in the context of imperative programming.
Those who control the present, control the past and those who control the past control the future.
There was a Mad Magazine article that said that you know you've made it as a successful movie director when critics started finding symbolism in your movies that you'd never put there in the first place. :)
Block Together: Twitter block list sharing
Ebola Red Alert ‘Unprotected’ Man Within Feet Of Nancy Writebol
Maybe I'm looking at this from a different perspective. Some implementations do not require any response.

For example if I have a honey pot that collects random events, the clients can just send the data to it without expecting a result (IE: I don't care if it's successful or not) and honey pot is not expected to write any sort of response.

Clients send data and move on.
Your post is impossible to follow. You jump to point to point without rhyme or reason many of which aren't really justified (even on a casual basis).

Here's just a few of the points you try to make:

- You don't think cellphone-driving laws work unless there is a cop literally with you 24/7.

- You think this device minimizes distracted driving (?)

- You think cellphone usage while driving is going to increase regardless (?)

- You feel that because cellphone usage while driving is going to increase (unsupported) and that Navdy is less distracting (unsupported) that Navdy is an improvement (?)

If you believe this stuff then you have to at least try a little tiny bit to justify it. Those are pretty far out there opinions some of which aren't really supported by the admittedly limited data we have.
Yes, even if your language/framework have great abstraction over async, it is still something that the programmer must be aware of, and must be reasoning about all the time. It's just easier doing sync instead, at least for the C-family programmers.
The Metrics displayed in the new Dashboard focus on the characteristics of app execution on Heroku, rather than internal instrumentation of the application. Hopefully that's useful in providing more visibility into tuning applications on the platform.
So many keyboards! What you (and I) missed at Keycon 2014
I remember in the first weeks of JTV when the crew would hold a weekly BBQ at their apartment, so that people would have something interesting to watch. It was fun to go up there and joke with Justin about his shenanigans for the week while watching Kyle build ever smaller portable rigs.

I'm glad that that crazy idea ("I'm going to live stream my life and people will watch!") has turned into the best live streaming gaming site on the internet.
In 'Sherlock Holmes' Rights Dispute, Conan Doyle Estate Slammed Again
People always react to new RF technologies with "SHANNON'S LAW!!!" and ignore the fact that Shannon's Law refers to channels, not frequencies. If you create a new channel through active interference, you get more bandwidth.
Money doesn't buy you faster hardware, but it can buy you more hardware. A lot more money can buy you a lot more hardware, and that can make a difference. They may have been doing stuff on a million machines that 'normal' researchers were only dreaming of, not because they didn't know how to do it, but because they did not have access to a million machines.

It is similar to what gives Google an advantage. Even if you can write a web crawler that is faster than Google's, it is unlikely that you will be able to crawl the web faster than Google does. That also means your statistical translator likely is worse, your homonym disambiguaties is worse, etc.
That's almost by definition. If you take all the money currently being spent by programs targeted at the poor/needy and redistribute it among the entire population, the average amount that a poor person would receive will decrease.

Attempting to do that would be political suicide. "You're taking money from the poor and giving it to the rich!" The only realistic way something like a GBI would be implemented were if there were means testing involved.
"Perfectly acceptable" doesn't reach the standard of type inference and feedback that you can get with modern IDEs for their supported languages. Visual Studio gives far more feedback for LINQ than SQL, and it's damn more useful for debugging queries.
You are right that single payer has a number of theoretical advantages, and I never meant to imply that single payer healthcare was prima facie 'bad'. I was only attempting to point out some major differences between single payer healthcare systems and the basic income.
game publishers also have paid twitch for front-page visibility during release hype.

I have a feeling they pay quite a bit.
Suggestion: rename arrow.now() to arrow.localnow() to make it even clearer that it does not generate utc. I've run into this mistake many times with datetime.now() vs datetime.utcnow()
Russian Gang Amasses Over a Billion Internet Passwords
Seems like as a good a time as any to refresh people's ideas on Java. There is a user-thread implementation for Java. It does require instrumenting the bytecode, but it does work. http://docs.paralleluniverse.co/quasar/.

I'm looking at the port of Quasar to Clojure as my sole reason for looking at Clojure over Erlang.
The flawed system in this question is the machine, not the time zone.
Do you have any experience working in a business that does a lot of international trade? My experience is that they convert to local currency ASAP.
I will just make my raw observation and prediction that the reach into certain community for certain use case is likely to have little success. For example, if you want to travel between Flushing and Chinatown, or between Brooklyn and Chinatown, or between Queens and Chinatown, there are specific "bus station" for people to wait at. For car service it's also a single phone call and you can get a quote within half a minute. There is usually a single number you dial and you can get a quote on the ETA so you can wait at home and go on the shuttle van when the time comes. The reason technology hasn't beaten this old school system is because of the low cost to run and the low entry to barrier for both the business owners and users. Typing can be quit slow and ineffective and sometimes Internet access is just not available.

It's basically a community lock-in. So a Uber-like clone will have to break this "monopoly practice" not by just translating the app, but actually knows how the community works.
We started out with limited, then everybody started advertising unlimited because they never thought anyone could use a ton of data. Then things like torrenting and Netflix and YouTube came along, and now everyone's using a lot of data again, so they're re-introducing data caps.

Of course, data caps are ridiculous in concept. It's not like they go out and dig up infrastructure when it's not in use. It's their anticompetitive attempt to put online video services out of business and reinvigorate the outdated and overpriced cable/satellite TV model.
These revelations are too new to be from Edward Snowden, Glenn Greenwald and Bruce Schneier suspect a second leaker.

https://twitter.com/ggreenwald/status/485081861119832064
Every discussion that doesn't confront the actual math of how it would work is silly.

300M * 10k = 3 Trillion Dollars

This is greater than the total revenue of the Federal government in 2013.
no big deal, but everything else looks great.
We mostly operate the OS X and Linux hosts using the same or similar tools; Ansible for automation, ssh / rsync / git for getting files onto hosts, and an automated network installer that fills the same niche as the one we use with Linux.

All of the core infrastructure is shared between OS X and Linux systems -- same DNS caches, NTP servers, etc. -- so there's no additional work there.

There are some things that are a little tougher to do on OS X. The userland utilities are different (and anything GPL is trapped on GPLv2 versions for all eternity, such as bash and rsync), and sometimes we have to work around that or build local packages.

Ansible doesn't really know about things like launchd processes or cron jobs, and OS X has nothing analogous to useradd, so we had to write some modules and implement branching in common playbooks to handle tasks in different ways on Linux and OS X.

Ultimately they run Unix, and once our environment is deployed onto a server you don't really notice the operational differences on a day to day basis.