skysight-inc/HackerNews huggingface dataset:
Wow, this is a really informed comment.

To add to this, as a software engineer, while thinking through Smule's AutoRap app and the Shred Video app, I couldn't help but think that they could both probably benefit from a similar method for detecting (or synching with) beats, chorus, etc. Even though this sort of audio posterization (I'm not sure what it's really called) is not entirely novel, it's probably a reasonably tough problem to solve. If I had to guess, I'd guess that this aspect is what Smule's case is based on.

FTR: I hope Shred Video wins, because, based on the Business Insider article linked herein, Smith seems to be, IMHO, a huge bully.
Also, I changed the resolution from the default 1280x800 to 1440x900. Makes text feel right size-wise, and also makes more room on the screen.
IMHO, your legal counsel provides advice, but that's it. You're already sitting on the receiving end of bullying with an existential threat, so there's a strategic choice (talk/don't talk) with risk on either side.

As a founder who has taken on a legal threat from a big-corp before, know that bigger companies are in the habit of being bullies like this, because they get away with it far more than they should, and they might not even realize how stupid it is. Big-corp's lawyers are simply incentivized to rack up billable hours, legit or not.

But when you can make it clear to big-corp's strategic decision makers that there's far less upside than they expect (including that they have practically zero chance of winning anything), and far more downside (including that they will really look like idiots in front of their customers, their employees, future strategic partners, etc), big-corp usually calls off its lawyers and moves on to the next person on their hit-list. They're usually rational enough not to pursue negative-ROI activities for very long simply for vengeance. If the threat of going public isn't enough to make them back down, it's ugly, but you've got to follow through.
I don;t think they passed this by legal. If they did, they aren't listening. Publicly airing dirty laundry while in the middle of a suit is a dangerous tactic. It doesn't take much to tack on new claims.
It isn't "government," it's a handful of politicians who've been bribed (legally, by way of campaign contributions).

Want to stop this from happening, and make our elected officials more responsive to the people who elect them? Fight for campaign finance reform. That one fight will do more to "fix government" at all levels (i.e. make it responsive to the people) than just about anything else.
The statistics are at http://www.rita.dot.gov/bts/sites/rita.dot.gov.bts/files/pub... .

Eyeballing, it looks like 10 fatalities per 100 million passenger train-miles and about 1,300 injuries per 100 million passenger train-miles.

That's indeed ~1 injury per 100,000 passenger miles. And "Passenger fatalities and Injured persons include passengers on trains only"

Looking at http://safetydata.fra.dot.gov/OfficeofSafety/publicsite/Prel... , for 'Annual Report 2012 – Preliminary', Table 1-3, and picking 2010 as representative:

41 non-fatal conditions for Train Accidents
Excluding Highway-Rail Crossing (HRC) Incidents
112 non-fatal conditions for Highway-Rail Crossing (HRC) Incidents
1,213 non-fatal conditions for Other Incidents, Excluding HRC

I can find that "Other Incidents" means "not train accidents or crossing incidents" ... but I don't know what that means. Knife fights in the observation lounge? A high incidence of getting drunk, falling, and knocking oneself on the head? Do the European numbers use the same categories?

If we leave out that large but unknown category, it looks about 10x safer than the numbers sandworm101 gave. Still worse than Germany by a factor of 5.
Yes. We have open positions for C engineers.
Not being blackballed for any Government contracts?
Best Instagram Analytics Tools for Measuring Brand Engagement and Effectiveness
Close; it's (I think) the third incarnation.

Fun fact: the third incarnation is much worse than the second, which EFF/FFTF vigorously (and, I think, dishonestly) campaigned against.

Virtually nobody who campaigns against these bills ever takes the time to read them, despite how remarkably easy it is now to read not only the bills but the amendments it collects as it goes through the legislative process.

And still, as you can see on this very thread, most of what we get in the way of commentary is stuff about how this is being "snuck past the American people" --- as if 85%+ of Americans wouldn't automatically favor anything with the word "cybersecurity" in it.

(I was ambivalent about CISPA, and am not ambivalent about CISA; CISA is a bad bill. I think CISPA's opponents bear some small responsibility for that badness.)
The ideas contained in this book and Causality have been a huge influence in my decision of what to focus on learning as a data scientist. Very much recommend it even if you feel like the book might be too dense for you. It definitely was for me, but I still got a lot out of it.
Smartphone backlash: the mobile that gives you your life back
4 colors is the maximum required for planar graphs. It's trivial to construct non-planar graphs that require an arbitrary number of colors.
Or a variety of other reasons that we can, like that reason, simply make up.

The funny thing about your made-up reason? It's actually forbidden by statute in the very bill we're discussing.
Are there any plans to add application hosting along with this offering? Specifically, it could be useful to have a shim application that has direct access to the data without traversing the Internet, to minimize what needs to be transferred. For example, if used for a backup application, each day's incremental delta may be in one archive, but a periodic operation would be to move files from one archive to another. Or a full system restore may be pulling some data out of multiple archives, and a "shim" app (running within Backblaze's data center) would eliminate unnecessary transfers out.
Yes, but the bandwidth is not really needed. PCI-E data compression is a thing. You only lose like 10% performance when comparing ExpressCard (4Gbit) to native PCI-E

Sources:

http://forum.techinferno.com/diy-e-gpu-projects/6578-impleme...

and specifically:

http://www.3dmark.com/3dm/4476434
Hi Paul thanks for your comments.

In the code comparison, the 3rd party will also be able to look at methods (in addition to code copied directly). We're more than happy to include proprietary methods in the review.

On stealing "ideas," do you have some advice here? Smule has never specified what ideas they think we stole. What do you think is our burden of responsibility in proving we did not steal ideas our opponents won't even specify?
For something of a litmus test, the most recent Ford Fiesta model advertised better-than-actual gas mileage numbers. To mitigate the issue, Ford sent checks for the assumed loss of money to owners for the lifetime of the vehicle (which amounted to a couple hundred dollars). I imagine VW will only be required to make up the assumed loss of value of the vehicles unless the states intervene (California and NY are notorious for this).
Unfortunately, most people upset about this issue right now will still obediently walk into the voting booth next November and vote to re-elect public officials (or at least the next candidate from the same party) who supported this. Unless you're willing to put your vote where your mouth is and thus make it clear that actions have consequences, nothing will change.
Isn't it a bit early to call this frivolous?
If you can dump the code in your car, then you can boost your own car's performance by circumventing the laws yourself. That's one of the reasons this software is locked up, (as I understand it, anyway)
Latency is way to high if I had to guess.
as well as https://blog.ycombinator.com/on-the-shred-video-lawsuit
Previously, Google has been getting negative feedback for not giving a grace period in the event of an imminent update being released to patch a vulnerability. As a result, they added a grace period to prevent such situations from happening. In this instance, Cisco, the vendor, communicated that they would not want to use the grace period and published the vulnerability on their own website despite Google communicating that they could have waited.
Just google, there's massive amounts of industry data. One term is "insertion cycle", another is "loss of force". A typical soldered PCB connection will always last longer than a comparable mechanical one. (comparing cheap to cheap and exotic to exotic, so no fair comparing a corroded solder joint in a throwaway greeting card to the backplanes in an FA/18).

I don't know of a good overview but here's a specific example: http://www.mouser.com/pdfdocs/Molexlga2011brochure-3.pdf

The term "Mechanical Durability (min.): 30 cycles" means that this socket is only guaranteed for 30 insertion/removal cycles and they don't specify a lifetime. Is that lower than you were expecting? Making connectors is hard!

Amusing that my comment is factual and at -1.
Doesn't this mean that the Oculus Rift can now run on notebooks? that's a pretty big deal and means they might sell a lot of these!

[1] Oculus Rift specs http://www.slashgear.com/final-oculus-rift-specs-revealed-fo...

[2] GeForce GTX 980 outperforms GTX 970: http://gpuboss.com/gpus/GeForce-GTX-980-vs-GeForce-GTX-970
I had the same feeling when I read how they told Mark to keep the laptop.

I wish you guys all the best and hope this gets sorted out soon.
Australian Banks closing down the accounts of Bitcoin businesses
I'm always so paranoid of this at any of my employers so I go through great lengths ensure everything is separated. It's a lot more work in terms of managing your stuff, but can simplify situations like these. I always keep my work and my personal projects completely separated. Separate machines, separate repos, separate accounts and I don't do personal stuff at work. My goal is to have a clear separation so if either of us decide that our contract isn't working; it's as frictionless at possible. While I applaud the fight for what's right, there is no doubt that a legal disagreement will take time away from building the product that your users want.
Seriously, right? Too bad your father or uncle probably needs to already be a longshoreman and vouch for you in order to get into this old boys club.

The port strike earlier this year was over the crazy health benefits these people receive - Obamacare was going to force them to start paying tax on their absurd benefits, and the longshoremen didn't want to.
Just an extreme example of bad PR.
Oracle is exactly who came to mind when I was typing out my reply :)
It's pretty normal for any expertise to be limited to a 'small minority'. All it takes to expose trickery like this is for that small minority to do their thing and then write lay-man comprehensible press releases. This is how a lot of stuff gets exposed and for the most part that does not seem to require in-depth understanding of the nitty gritty details by the un-informed, even though they may be directly affected. (In this case: by higher fuel bills to date, reduced re-sale value and possibly a forced significant drop in performance).
I wonder what the thermal budget looks like. I can't imagine that it can run at full crank for an extended period of time.
> It will take probably two years for the case to get fully adjudicated...

During which time many prospective investors, partners and customers won't want to touch you with a 10 foot pole.

> ...and the legal recourse for preventing frivolous lawsuits like this is insufficient.

To be honest, this doesn't look like a frivolous lawsuit, even if this goes to trial and is adjudicated in your favor.

Your post indicates that you and your co-founder quit your jobs at Smule to start Shred. In your post, you detail the differences between some of the technology behind Smule's products and your own, but it is clear that Smule and Shred are in the same general space as far as technology is concerned.

The intellectual property assignment agreements most employees sign cover inventions, processes, discoveries, etc. that are made or conceived of during their terms of employment. They often contain language referring to "the present or reasonably anticipated business" of the employer.

While none of this means you can't leave an employer to start a business in the same space, matters like this can be incredibly messy. If you believe that your defense will be successful because you can prove you didn't steal code outright, you are being incredibly naive. It's not that simple.
I don't think this is comparable to the Osprey for the following reasons:

* the osprey's idea intent was VTOL to horizontal thrust via an adjustable wing+rotor....

--- This has NOTHING to do with feedback to external terrain

* The osprey began dev WAY before pretty much ALL the tech that would be needed to accomplish this (in scale and at low cost) even existed

* the problem the osprey was solving was NOT this....

I am note refuting your point:

"Typically in hot LZ it's in your best interest to not land." -- as this is valid...

But that does not discount the desired functionality of being able to land on non-flat surfaces in a manner which doesn't require the pilot to have gobs of flight experience and training for such a landing.

------

Let me propose a thought experiment (which I can be sure the military has already explored):

Imagine a craft that is a replacement of a helicopter in ~45 years.

It should be an airframe/device that has a set range of capabilities: it is robotic enough to land on uneven surfaces to a given angle. It can autonomously land in level or non-level surfaces... it can be sent away/recalled as a drone (drop me here - go to 25K feet and hover for an hour, then land at spot X and retrieve me - unless given further orders), it should be able to work as a swarm from fewer pilots (i.e. one pilot driving N units - either in a trailing, above, or remote vehicle/cockpit)

It should be able to have smaller advance, trailing or escorting drones tied to its safety.

it should have a body-unit (like a shipping crate) that it can either detach and leave - or come back and pickup...

the smaller escorts can swarm in groups of 6 or 4 to pickup and carry off said body-units should the main lifter be compromised....

/speculation
I wonder how I do this as a home user.
Is it ethically wrong for a woman to drive in Saudi Arabia?
You can swap out your tires for known good ones just before the MOT too and swap them back afterwards. Laws can always be circumvented, but that does not make such circumvention any less illegal and when caught the penalties tend to be quite serious.
Don't you think this will be absolved with a review of Shred Video's code/methods vs Smule's code/methods? And isn't it telling that Shred Video is more than willing to submit to such a review, but Smule has not yet acquiesced?
Turing to roll back pricing for Daraprim amid controversy
I don't understand what you are trying to say. My point was that energy can be saved. I guess I tend to think more abstract than you. For example, population could be reduced by dropping a nuclear bomb - boom, energy saved. (I'm too lazy to go into details of population control here...).

That's of course not the solution I propose, it just abstractly proves the point that energy can be saved. In fact, as you mention with the washing machines example, the majority of people seem to get by on very little energy (even less than is required to power a washing machine).

All I said is that saving energy is another option, besides building more nuclear power plants or burning more coal.

And you seem to have missed that washing machines are not the major factor in power consumption that you make it out to be.

"it will never be enough to significantly impact the the total energy used in the world"

People will simply use all the energy they can get (even if you build lots and lots of nuclear power plants). That doesn't imply that they couldn't get by with less.
How can you steal an idea? There is little to no protection for ideas. More tangible information may have a lot of protection, but ideas are more-or-less fair game.
Why did you specify liberal governments (is this not something all governments do?), and put it in quotes?
Are you trying to say emission laws are unethical?
I get the whole leaving on good terms, really. But this whole "hey, we just want you to keep the code and answer questions for our other engineers" aspect really ought to have set off red flags.

Pro-tip, hand write a nice letter to your boss/colleagues on your way out. Bingo, no burned bridges, and no risk of law suits for holding on to company IP.
So far as we know†, CISA has virtually nothing to do with PRISM.

CISA enables information sharing only in the context of "cyber attacks" (a term defined reasonably precisely in the bill). Essentially, what CISA says is that companies can run intrusion detection systems (like they already do) and then share the alerts with DHS.

PRISM is, as far as we can tell from the leaks, a tasking system for FISA 702 warrants. FISA 702 warrants can pertain to any foreign intelligence target. They have virtually unlimited scope (as does foreign signals intelligence as a whole).

I think this is a distinction with a big difference, but leaving that difference aside: the mention of PRISM is clearly an emotional appeal, and sets the tone for the rest of the open letter.

CISA is also at pains to avoid the sharing of PII (again: since CISPA, and the Rockefeller bill before that, these bills have been intended essentially for IDS alert sharing). It also does not shield companies from liability for sharing information via FISA 702 requests: the only liability protection CISA sharers get is for information shared to prevent cyberattacks.

† Given the little we know about PRISM, that is.
I think that has been specifically mentioned in some of the articles as the 970 is the minimum required GPU.
As with his Chernobyl interest, I believe he's focusing on how a nuclear disaster causes seemingly permanent loss of human habitat. This includes emotional upheaval, lost personal identity, and lost way of life, as well as the loss of future places of dwelling. In that focus, I believe he does a good job.
I wonder what their stack is. I can't readily determine that, which might just be a function of working too hard today. I don't have time to search for the info. (I was specifically wondering if they use Hadoop.)
Seeing as how I'm the guy that used to do the checking, I humbly disagree.
Completely agree. We ourselves were very conscientious to never do anything Shred Video-related on any Smule machines, and did not build anything Shred Video-related until after we'd terminated our full-time employment at Smule.
"Ideas" isn't a form of IP that can be stolen. Did you patent anything? Have you appropriately protected these ideas to qualify for any sort of tradesecret protections?

(ps. Don't answer. This is the sort of thing to be discussed with an attorney behind a closed door.)
Being able to use AWS spot instances for long running batch processes would be great. We have some bioinformatics analysis jobs that take days to complete and this could cut their cost by ~80%.
From the Python docs:

https://docs.python.org/3/

Extending and Embedding
tutorial for C/C++ programmers

Python/C API
reference for C/C++ programmers

... right between "Distributing Python Modules" and "FAQs"
>Low sulphur fuel is 4x the cost.

It's more like double the cost. Your point stands, though.

http://www.bunkerworld.com/prices/port/nl/rtm/
> They are abusing it, specially as workarounds for constraints that cannot be expressed in the type system.

That doesn't sound like abuse to me, as long as the exposed interface remains safe.

> some Rust devs are using it for anything they assume isn't logical safe.

That sounds like an objection to the scope of what Rust defines as safe. Unless you mean to imply there are reasonable, Rust-safe ways to rewrite the transgressions. In the former case I have to disagree. It would be nice if we could prove more. But you can't prove everything.

I haven't seen the ICFP talk but I might watch it later if you can link to a video. I've skimmed that discussion before but you will need to point out your objections—IMO it is great that Rust devs are having that discussion.
The only time I heard Jeff Smith was in Stanford Podcast[1]. I listened to every podcast on Stanford (DFJ Entrepreneurial Thought Leaders lecture series) and particularly remember Jeff Smith because I thought he came out wrong from the talk. His statement "Palantir is evil" because they hired a guy who smule was trying to recruit. Seriously you are giving a talk to inspire future entrepreneurs and use that to bad mouth someone who is not even your competitor?

PS: I have no relationship with Palantir. It just really bothered me that someone would use that opportunity to bad another company.

[1]http://ecorner.stanford.edu/authorMaterialInfo.html?mid=2992
(The point comes at the end as a reply to last question).
We're talking about emissions...
To me, this story has analogues to the analysis of the space shuttle Challenger disaster. The engineering report indicated the O-rings were a risk, but the report was not clear enough or strongly-worded enough to effect change. The mission went forward unmodified with fatal results.

This story is a strong argument for physical access controls. The computer could have been placed inside even something as low-tech as a locked cabinet, with only the people who knew what they were doing granted access. While the DEC Engineer should not have made assumptions, the assumptions he made were assumptions any reasonable individual might have made.
> Also, check out the ESP8266 chip, it doesn't have a BTLE onboard but it does handle the "SOC with low-power wifi" thing.

I know all about it. Still won't run on a coin cell.

Nobody will build a 2mW WiFi chip until Apple forces somebody to build it. Then EVERYBODY will rush to build it. Then EVERYBODY-1 will go bankrupt when Apple doesn't use their chip.

It's the Zen of Hardware.
I doubt go to C calling conventions are going to be the slowest part of calling tcsetattr(). Using ioctl() is being difficult for the sake of being difficult.
Real-Time (Not Turn-Based) Chess
Scuba and skydiving are the exact type of hobbies where if you make people interested, then you can get a lot of very expensive follow-up business. You won't get most of them hooked up; and if you make the first experience a lousy one because of Groupon pricing issues, then you won't get any of them hooked up, but in general if your business current weak point is excess capacity and a need to bring in new people to the hobby (since your current customers are doing it as much as they can and won't do more), then a deeply discounted first trial is pretty much the main way to do that.
Two new accounts created within the same hour, with a single comment each, on a post that isn't on the first few pages of HN, both of whose comments contain two exclamation marks as their only punctuation? I think you might be right to be suspicious..
I've always gotten a response back from David Schmidt within a couple days of contacting him. Try again?
Quirky has filed for bankruptcy
What Does Your iPhone Know About You?
Using the syscall interface is a lot faster in Go than calling to libc, because the system libc is going to expect large stacks and so you incur the overhead of a stack switch when you switch out of M:N threading into the C world. I assume that's why Go calls syscalls to begin with.
Ayup, but until then I need a gateway to talk to the outside world. If I don't have a phone, then that's WiFi.