skysight-inc/HackerNews huggingface dataset:
I usually have the opposite problem: I'll consider myself a friend of a person, but that person thinks I don't like them. A common side effect of being factual/honest, unfortunately.
Google study shows unwanted software worse than malware
A Day in the Life of a Software Tester
No, you're describing something much closer to the patent system which is not the same as Open Source and even further than the Free-Software-As-Defined-By-GPL view. The latter explicitely requires all changes to be available to the user of the software, but doesn't require anything at all regarding the original developer(s). That those developers get the changes back is purely a demonstration of the company's goodwill, or it may also happen because the original developer also happen to be using the modified version, but that's not always the case (example: set-top boxes with modified Linux version. If you're not using one, you're not entitled to the modified Linux kernel, even if you are a Linux contributor)

You're saying that the aim is to prevent somebody to make money on your work. This is absolutely not the goal of Open Source or Free Software. There is no issue in somebody else getting rich by using your work. A rough summary of both would be:

* Open Source: Stop reinventing the wheel every time. Somebody writes an implementation of a javascript interpreter, and everybody who needs one just uses it instead of writing one from scratch. If they find ways to make it better, they share their knowledge so that others can build on top.

* Free Software: As a user, I want to be able to understand how the software works, so I can fix it myself or ask somebody I know and trust to fix it if it's broken, or improve it if there are ways to do it.

The commercial side is neither seen as positive or negative; it's completely orthogonal to the question. My personal opinion is that I don't see why I should prevent somebody to earn money based on my work. To think that a software is enough to make a business and you could have made as much money as them if you just sold it is misunderstanding the domain. If they're better at it, why would I prevent them ?

Note that regarding Open Source and Free Software, I don't have a problem with any of those views. It's just important to understand the difference in philosophy if we want to understand why both styles exist and why some might choose one "side" over the other. I'll agree that in practice both styles are largely overlapping.
Linux MP3 player able to modify the sound with Tuna.js API
$12M in Sales: Our 1H’16 in Review
Well yeah but if all Google knows is when you're getting push notifications about email, then that's a lot better then them having all your email. I mean, there's a good chance that the person who just emailed you is using Gmail so they still have a lot of your email even if you don't use it at all. It's all a trade-off.
Respectfully, I disagree. One doesn't need the knowledge of a systems administrator to use free software instead of proprietary software. The Debian OS ships with lots of free software to do practically everything you'd ever want to do on your computer.

We are 90% of the way to a "Stallman-style" world being a realistic possibility for the 'average user'. Only a few key applications are missing or under-represented, which should be seen as an opportunity for new developers to cut their teeth on some valuable projects.

There's more to it than an intelligence gap. There's a propoganda issue where people are being convinced that the subject matter is "too advanced" for them, which is a lie that would-be masters tell the people they wish to enslave. (this has been going on for centuries). But the intelligence gap does play a role and can be traced back to our neglected public education system and the greed of free market capitalism.
Imperva Report: http://www.imperva.com/docs/Imperva_HII_HTTP2.pdf
> I don't know the polite way of saying die in English, in Japanese, we have a special polite word for the emperor's death

In Osaka I saw the expression, "emperor Hirohito succumbed". I found the euphemism quite entertaining at the time.
When to use Scrum
I thought you said your friend liked you?

that.. is not.. my friend!
Survivor bias. For every correct prediction you had 100 wrong predictions, and I'd venture it's the same today.
There's no way of answering this without people perceiving that I am "attacking" mu4e.

Let's just say that mu4e gets its efficiency from memorisation (e.g. hotkeys) and a quirky way of working ("all organisation is a query"). Gmail and FastMail get their efficiency from standard UI elements that most computer users will already know how to use, and discoverability is via UI elements not manpages.

mu4e undeniably has a maximum higher speed. But you'll spend a lot of time fighting the tool until you reach that nirvana.
This is an anecdote but it fits what I've observed over the years. Most of the really good friends that I have (white) are recent immigrants from Europe. North Americans tend to be more individualistic and this colors their interactions with others. Basically with Europeans, I tend to feel less like I'm being used or that I'm stuck in a quid-pro-quo situation.
I disagree. This is how you end up with messy code that needs constant refactoring. Making time to come up with a composable design shouldn't be that difficult. It usually isn't.
I like how this article frames it as an issue about the 'free movement of capital.'

In a lot of instances 'free-trade' agreements exist to help the mega-rich, this seems like a perfect example.
But in the end won't most of the sent emails still go through Google's servers, thanks to the ubiquity of Gmail?
One of the first things I was taught when I did my first Scrum Master course was that scrum is just guidelines. Teams are self-organizing and need to do what works for them.

Most of the criticisms in this piece can be resolved by team members adapting processes so they work for the team.

I've also encountered most of those problems in non-agile, non-scrum teams as well. Instead of obsessing over points, it's hours.

Meeting hell can happen anywhere. Good employees will tell their managers when meetings become an impediment. Good managers work to fix it (and pro-actively try to prevent it).

I always find it odd when somebody complains that sprint goals need team buy-in to change. Why is that a bad thing? Adjust and move on. Sometimes things don't go as planned, sometimes they go well. Hopefully, it all averages out at the end.

Anyways, I guess I view scrum (or any other methodology) as a loose set of guidelines, not strict rules that must be enforced at all costs. If management is forcing the rules, even when they are becoming impediments, that's a sign of a management problem that is unlikely to be cured by a change in methodology.
They have quite a vast network of turbines. During some of the most windy days of the year, they produce more electricity than they consume. I'd say they also tend to do much less shipping by truck than many other countries.
Just goes to show that there is a large and emerging market that Uber has yet to corner [1]. Interestingly, this thread [2] mirrors my experience with and view of local taxis in Nairobi/Kenya [3, 4, 5].

[1] It’s Already Over And Uber Has Won [https://www.buzzfeed.com/johanabhuiyan/its-already-over-and-...]

[2] https://news.ycombinator.com/item?id=12199721

[3] The race for Nairobi’s taxi market [http://savannah.vc/2014/03/26/the-race-for-nairobis-taxi-mar...]

[4] Uber Battles Locals for Future of African Taxis [http://www.wsj.com/articles/uber-battles-locals-for-future-o...]

[5] Nairobi’s taxi hailing startups: too much of a good thing [http://disrupt-africa.com/2015/06/nairobis-taxi-hailing-star...]
As I've been teaching myself rust this point has been hammered home hard. It's really eye opening to see all the copies plainly represented in code and the lifetime checker is really good about highlighting where you should be making a copy vs sharing a reference.

I haven't reached the stage where I can write performant Rust yet since I've only recently started to truly grok the borrow checker but I can see how longer term it will be easier to figure out how to make my code performant since the all the information required is front and center. It will be interesting to see whether that promise holds for rust code as the community matures.
Upcoming changes to KDE version control infrastructure: SCCS
Yeah, that's how I read it, too. Given that there is no actual article, the headline should be changed to "Relaunch of Destroy All Software" (which I think I would have ignored).
> Anything else we can do

Use natural resources more efficiently by way of better technology and/or import natural resources from the rest of the solar system.
This happened to me. I think on some intellectual level I understood that work friendship wasn't terribly authentic and based on the politics of getting ahead. Then I was on the receiving end of some very dishonest politics and it really opened my eyes on how terrible some/many of the people here are and people I've had unbelievably good relationships with will turn on you in a very aggressive manner instantly if they think picking the other side will gain them more benefits. Fairness, truth, etc didn't matter to them. Holy cow, I just couldn't believe it.

Ironically, this has made me appreciate the people who are openly jerky at work. At least they're open with the biases. There's probably something to be said about white collar workplace culture's default of "aren't we all just friends and teammates?" It seems to empower only the worst political players. At this point, I'd probably rather work with a bunch of jerks who are open with their biases than a bunch of 'office friendly' people who are only friendly because it serves them. There's a certain level of honesty with the jerks.

I also see this in myself. I've learned how to play up false modesty and the whole "Aren't we just pals" attitude, and I don't like it now that I'm self-aware of it. I don't know if I'm ready to become an full-on office jerk, but I'm probably half-way there now and life seems a lot easier when you're more open with your biases and honestly accept that most of your coworkers are adversaries, not teammates. I'm sure I'm more disliked, but disliked by people who would just turn on me anyway if push came to shove. I also invest much less mental energy into trying to be everyone's buddy and instead focus that on the work itself, anti-burn out strategies, leisure time, my creative projects, planning my next career move, etc.

I used to laugh at the grumpy gray-beards in IT. Now I see where they are coming from. The sooner the automation/robot revolution comes the better. Work is a zero-sum game that best serves the extremely dishonest. I don't know why we're so worried about moving into a post-work and post-scarcity society. The status quo is pretty terrible if we're being honest about it.
I often have the impression that the term "technical debt" is just an euphemism to avoid admitting that someone in the team has produced poorly thought and poorly written code.

I'm not sure I ever found myself in the position of writing bad code just for the sake of speed - I surely wrote tons of bad code because I didn't know how to do it better, or because I didn't have the requirements clear from the start, or because of bad design and planning. But to get a feature out quicker, no. If anything, it seems to me that writing bad code requires more time than writing clean and elegant code.

In the end, "technical debt" becomes a way to shift the blame from your own (the team's) inadequacy at planning, designing and developing, towards supposed time constraints that always lie outside of the team's responsibility.
Is there significant legislation that only benefits doctors at the expense of everyone else?
Only legislation that's designed to protect their customers comes to mind right now.
I'm pretty ignorant about economics, but doesn't this assume perfect competition? For housing that's probably a reach (depending on the location) given the possibility of limited supply and near monopoly power of real estate owners in a given area. Maybe other areas can't be considered due to other factors like proximity to work, lack of public transit, etc. It seems hard to guarantee that these kinds of things work out as planned except in optimistic conditions.
because if you run your own mail server apparently you have a 50/50 shot of having literally none of your mail ever delivered.
Ohh a Matt Levine post, so I guess the top 10 comments will be people recommending that everyone subscribe to his daily news letter:)

On a serious note....

> Engineers at Sydney-based Metamako LP and Exablaze Pty. Ltd., and Chicago-based xCelor LLC are rolling out switches that take around four nanoseconds—four billionths of a second—for messages to transit from one side to the other, sending data from exchanges to electronic traders.

Wow, can anyone shed some light on how they time this? What sort of clock, I'm assuming its some fancy hardware that you use to benchmark at the 4 nano second level? Or do you just claim this and assume that no one can prove you wrong?

As to Bitfinex, on the weekend a few friends and I were batting around ideas on how to reliably trade bitcoins without having to worry about being robbed by the exchange^H^H^H^H^H err worrying about the exchange being hacked and passing their mistake onto you.

The top ideas we had were:

- only trade on US domiciled exchanges, the US government tends to poke their nose into everything and this is one case where you benefit.

- phone the exchange before you start trading. If you can't get someone on the phone, that's a very bad sign:)

- Similarly, if the C level executives of the exchange aren't well known and always around at the regular bitcoin industry conferences then that's a bad, though this fails the Mt Gox test.

- we tried to figure out if you could pull the coins out each night and put them back in each day, but even then, you'd run the risk of the hack happening while you had coins held by the exchange.

But we came to the conclusion that there just isn't any sane way to trade bitcoins currently where you can eliminate "exchange risk". If anyone does know of a way please let me know.
As a person who values good design (and has spent what many would think way too much for a table lamp), I don't see this law as totally absurd: they are basically putting design and works of art (think paintings, pictures, novels) on the same level.

The real problem is that copyright law is flawed, and terms should be reduced, both for designs and for works of art.
Having read Carnegie's "How to Win Friends and Influence People" recently, long after I had heard of people recommending it left, right and centre I came to the conclusion that the book says more about the person who reads it and finds it revelatory than it does about society itself. If you believe the world works as the book lays out, it becomes a self-fulfilling prophecy.
You have to keep in mind that the majority of drivers use a sort of mental auto-pilot, which is why most car accidents happen in the first place.

Only someone who is aware of the dangers introduced by how their peripheral vision will be affected is going to have the foresight to "focus on the road". Other people are going to slam into the person in front of them. That's my prediction anyway, I might be wrong but let's wait and see.
or even a second site to fail over to?
When your only proverb is a hammer everything starts to look like a hammer.
Software is split into a few overlays. Each overlay is filesystem slice, some overlays may have intersection. They are merged in specific order to get the final filesystem. Some overlays may be version-related (v1, v2), some environment-related (test, live), some may contain specific device configuration. Ordered overlay set forms an update stream. (That's just terminology we use, I do not want to teach somebody how to call things right)

Initially client knows only own hardware ID (which is just sha256 of part serials, MAC, etc.), and registers itself on server, which is allowed only from trusted networks. During registration client receives unique HTTP client certificate. Later administrator approves registration and assigns client specific stream. Stream may include sensitive information, like unique credentials to access some other services. Some overlays, which are not secret, like executables, 3rd party libraries, OSS stuff, are just rsynced to save time and bandwidth, but others like configuration and credentials, are downloaded over HTTP with client certificate authentication. Overlays are merged on client side in memory and applied in semi-atomic way (series of file moves within partition, not writes or other I/O in between).

There are a few other requirements, like log if devices tries to register second time, log if device tries to register from non-trusted network, log every update attempt, successful or failed, etc. And this is of course just brief overview. For instance, administrator approving registration is not a single person, but group of administrators, each with different permissions on streams. Client cannot download stream of some other client, and cannot get any information on overlays used by other clients, etc.

I do not see any way generic updater [framework] (not only TUF) to fulfill my requirements not causing more problem, than solved.
The new Internet generation should really read Haraway's cyborg manifesto
It is, deliberately and self-consciously so. The Register's approach to journalism spoofs traditional British tabloid broadsheets, and shares much of its humorous aesthetic with the satirical magazine Private Eye.
Some MUAs are pretty slow. It isn't hard to do better than a few of the MUAs I've used, and webmail often is better just because more people use them so more optimization has gone into them. I think this is the main one.

Webmail often has a really fast pipe to the email storage, which means it can get the headers faster and then extract only the parts it needs. Webmail is not required to use IMAP (though many do) an optimized protocol can offer advantages.
> the goal of ideas like these is to reduce income disparity

Except when they're not. That's the point of this article. UBI is one of those ideas that can be all things to all people depending on the details.

For example, say you set it at a level that could sustain an able-bodied person temporarily but needed supplementing for comfort. Say you then remove all other state funded payments. That's UBI.

For example, say you set it at a level meant that most people could comfortably live off it and was topped up where necessary e.g. disability payments. That's UBI.

Of these, the first is, arguably, purer UBI. It'll also do very little to reduce income disparity.
Security, Spam Filtering, Better web interface, native apps, two-factor auth, DR, etc.

These are just some of the reasons.
Gmail scans your email to show you ads. That's how Google makes money from it. Fastmail doesn't show ads, you pay them money to do your email. Moving email off Google could also be a move towards not putting all your eggs in one basket. I think there's a valid incentive to move away from Gmail.

That, and all the complications that running your own email server brings with it. If you read the article, the author explains it very well.
This is both true and important, but I think the author was aware of it, and is willing to sacrifice that privacy for convenience (note how they moved from a private mail server to Gmail, then FastMail).
So there is no innovation whatsoever in the clothing industry? No real nice piece of clothing?
If demand for shelter doesn't change, and supply for shelter doesn't change, what's pushing the price higher? Supply of money only affects prices when it can change demand or supply.
I find points far more useful than time based estimates. The trick is to use points like categories and not try to treat them as 1 point = N of something.

During my training the analogy was to categories of dogs based on size. So like a Chihuahua is maybe a 1 and a Great Dane is maybe an 8 (and there's 7 categories of dog size between them.) But a Malamute might also be an 8. Even though it's shorter than a Great Dane, it weighs maybe the same because it is more thickly muscled. But neither of those dogs is equal to 8 Chihuahuas.

The point being that if you categorize stories like this, treating point values as categories rather than as 1 point = N of X, then that makes pointing a lot easier and a lot faster as your team builds up a methodology (what categories your team uses and what they mean is up to you, it doesn't matter as long as you are consistent.)

This leads to meetings taking less time, and leads to a more consistent velocity than if you do something like 1 point = 2 hours or 1 point = something else rigid.

If SCRUM doesn't work for your team by all means you should abandon it. But, to me, it sounds like his team is using it badly. It sounds like they are being really rigid, and it sounds like a few adjustments could lead to a lot more happiness. But maybe not.
This is an often repeated fallacy, but Australia doesn't have the equivalent of the National Security Letter, by which they can coerce any company to do what they want without the right to disclose such breaches. The NSA is also the worst adversary you can get. I doubt Australia's agencies are as competent or as well financed.

Also, no security agency is above the law, but the problem with the NSA is that the US law does not apply to non-US citizens. Us foreigners, the ones that the NSA are supposedly targeting, have no way to fight this through the judicial system and we have no representatives to call or vote. But choose a service provider closer to home and things change dramatically.
I have to wonder if the employee stock options were worth anything? Most telling is that Walmart decided to throw ~$300M at the founders "and others" to retain them. Does that mean, in this case, that the founding team is the only one who walks away with a payday?

And to be clear, this isn't a cynical musing. I'm genuinely curious to see how this worked out for them.
Ask HN: Are you using any outside/third party help to build a web/mobile app?
If so, what type of app are you building, how close to production ready was the work you received from the outside help, and how much did you pay for their services?
AMD RX 460 benchmarks
One also sees the little 1990 peak. That's when inefficient east-block power plants started to be turned off and be replaced by more efficient versions. Other countries did not have such an easy way to increase overall power plant efficiency.
In cash? Really?
The article cites a study from a business management class of 84 people.

That seems like quite a small sample, and I wouldn't expect business management students to be representative of the population as a whole.

It might still be true, but it's probably a bit early to write off all of your perceived friends as shallow fakes.
> you usually don't create data

I think the creation of new data is the whole point, actually. Even at the lowest level, aggregation of data is still new data. Deriving insight by the use of more sophisticated methods is also creating new data. Arguably, all data is derived so just because a data engineer distills large data sets into smaller ones doesn't mean they don't create new data.
I see technical debt as being that code you haven't written yet. You just ignore the errors from misaligned data instead of writing the date sanitizer. You monitor and hand-reboot processes that leak instead of finding the leak/automating the reboot. and so on.
Try getting your mails from your self-hosted DO server into the inbox at Outlook, Gmail, Yahoo etc. The big mail providers have it all relatively sewn up - anything coming from the likes of a random VM provider like DO will end up in 'spam.'
Privacy != anonymity
Some US work visas are country specific. What passport do you hold?