Fzzr

Timely, the first new beta in years just came out. There's a lot more content to go before it's a complete game, but there's lot of fun to be had. Contributions welcome!

Time to advise your friends to be extra cautious against phishing attempts.

This is like the circle of life for startups, I swear. Next up will be "legal services for someone interfering with your disruptive business model as a service".

Tow trucks work that way too.

I was more interested to see that it dropped btrfs. I wonder what pushed them away from it, in the end.

Unfortunately, the First Amendment does not protect against private action, only government restraints on speech. Other mechanisms like anti-SLAPP laws might help with that, but either way that's a lot of legal effort to publish some benchmarks. Intel also operates all over the world, so they could eg. sue a Britain-based branch of some media outlet that also publishes the numbers if the laws there are more in their favor.

The license can't restrict third parties from sharing benchmarks, which is why it puts the onus on the user not to allow third parties to share them. If some news site was to publish benchmarks without disclosing the source, Intel would first have to take them to court to force them to disclose who provided said benchmarks. That's as far as I can see it directly impacting sites that don't run their own benchmarks. That said, the sites that do run their own benchmarks would be on the hook. Sadly, even if this is unenforceable, the potential legal battle to have it declared so would be scary enough to quash some criticism.

This really makes me doubt if I should buy Intel products in the future (to the extent that I have a choice). If I can't get performance information because Intel has something to hide, I'll have to look elsewhere. Really, this is sufficiently distasteful behavior to make me avoid Intel even if the products work just fine.

I see it as a step towards integrating more (or in this case better IMO) things into their ecosystem. Consolidating Hipchat with Slack is a step toward that.

Woah, this is huge. Atlassian is really going for the "everything a tech shop needs" gold.

I regularly send this to people where ever I work. Never stops being relevant.

True. REAMDE (same author) is more on the nose, but I also didn't enjoy it as much as a book. Really, Neal Stephenson just doesn't do books with only one major focus.

Cryptonomicon is probably what you're looking for.

Correction: I'm not sure Apache 2 and GPL work that way. IANAL and please read the licenses yourself (and consult counsel if needed).

Explicit probably saves a lot of time in court, and helps with global consistency. More importantly, Apache 2 and GPL 3 include reciprocal patent grants. They work similarly to the React patent grant, but unlike that one they go both ways. In the React one, only you lose access to the patents if you sue Facebook, but Facebook can sue you fine even if you contributed to React. Under Apache 2 and GPL 3, no one contributing to the software can sue anyone for patents infringed as a result without having their license revoked in its entirety (copyright AND patent).

GPL 3 adds an anti-patent-treachery clause not unlike the Apache 2 clause.

React Patent Grant Version 2: https://github.com/facebook/react/blob/b8ba8c83f318b84e42933...

The license granted hereunder will terminate, automatically and without notice, if you (or any of your subsidiaries, corporate affiliates or agents) initiate directly or indirectly, or take a direct financial interest in, any Patent Assertion: (i) against Facebook or any of its subsidiaries or corporate affiliates, (ii) against any party if such Patent Assertion arises in whole or in part from any software, technology, product or service of Facebook or any of its subsidiaries or corporate affiliates, or (iii) against any party relating to the Software.

Apache 2 Section 3: http://www.apache.org/licenses/LICENSE-2.0

If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

GPL 3 Section 10 (See also Section 11): https://www.gnu.org/licenses/gpl-3.0.en.html

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

Edited for spacing

Today in "headlines that would have been April Fools jokes ten years ago"

That's a fair guess. It was more a "maybe some of them want time off without getting above average interview offer spam". Overall I think it's a good thing too.

Yes. If it was set up from outside it has the feel of imposing a job hunting strategy on people without their involvement.

Interesting, was this set up by someone from soundcloud or independently?

I've never heard of such a thing for engineers, but I have heard of it for production line workers. (eg. assembling servers and PCs)

That's definitely one of the possibilities. 100,000 years is an order of magnitude longer than all of human civilization thus far, and we're trying to spook people all the way that far in the future. Who knows if even the "humans dislike asymmetry" assumption will hold up that long?

One of the afterthoughts in that document even suggests that the most likely reason people would leave the place alone would be when people die of radiation sickness after breaking into it anyway. It just takes one group of really determined people with a decent amount of time on their hands to destroy the markers and everything else. If asked me how long I would guess until that happens, I'd say less than 100 years. If not then, how about if it's so scary that a religion arises that considers the area to be the home of an Adversary of some kind and destroys it in a holy war?

Also posted above: http://www.wipp.energy.gov/picsprog/articles/wipp%20exhibit%...

Yes. They're considering everything from pictographs up to the level of hostile architecture. The proposed message includes instructions to update the message in the language spoken at the time, in the hope of helping the message endure for generations more.

Obligatory: This is where the second image in the article ("this is not a place of honor") comes from. It's also briefly summarized in the last few paragraphs. Worth a read on its own.

http://www.wipp.energy.gov/picsprog/articles/wipp%20exhibit%...

I stand deceived and now corrected. I'll do better next time.

Nothing, he was just selected (based on who knows what criteria, they don't need warrants) to be scanned. Whether or not they actually cared about the sensitive data on the device, he still lost control of it long enough for it to be copied or compromised.

Luck and skin melanin content have an interesting inverse relationship when it comes to these things...

Yes. Recent (this administration) policies allow for demanding passwords etc. at the border. There was an incident where a NASA engineer lost control of sensitive data as a result https://www.theatlantic.com/technology/archive/2017/02/a-nas...

It's not paranoia. Welcome to 2017.

Edit: It's not like they're scanning every cell phone that enters the country... but they reserve the right to.

That was under Josh Paetzel, who also left (unrelated to the Corral stuff). Most of that same team is still there, though.

There were lots of reasons why Corral failed, including poor choices of technology (MontageJS, p9fs), unfortunate engineering decisions (tons of unmaintainable wheel-reinvention, tons of backward-compatibility breakage), and poor planning (eg. documentation and localization ignored from the beginning, constant design changes). Jordan (departed CTO) would seem to have fallen on his sword and left, and the remaining executives (including returning CTO [and founder] Matt Olander) made the ruthless but understandable decision to cut their losses. They're re-focusing on the existing stable project with the intention of bringing in the the coolest features of Corral incrementally rather than all at once. Kris Moore has a solid record with PC-BSD/TrueOS and has been managing FreeNAS 9.x for some time. Only time will tell if FreeNAS 11 will live up to what 10 could have been.

The growth refers to the enterprise version of the current (9.x) product line, which is legitimately growing. It's just that 2+ years of engineering effort on the successor was thrown out two weeks after that PR.

I did once. Didn't work out, but it was worth a shot.