As a recent ex-scientist (hint; I moved to software developer for the shorter hours and better pay), if we only had one problem to solve at a time, it would be much easier...

Yes

No.

Seriously though, probably not. It's experiencing a dip after it's initial surge of interest. It's not a roller coaster, or a rocket, it's a company. It will have ups and downs. Demand will fluctuate over time. It can experience market saturation (those of us who have now kickstarter-ed so many projects that we need to wait for some to finish before we pay for more).

Also; what's this nonsense about 50,000 projects and not getting near their total, as if that's a bad thing. It's not a magic money tree; most of those projects probably didn't interest people, so they failed at the first hurdle. That's not a tale of woe, that's someone being saved from spending months/years of their life developing a product that wasn't going to sell.

Have you ever tried telling a userbase that there's a problem with their browser and they should change? If you're lucky enough that they read the notice instead of just hitting reload a few dozen times then complaining it doesn't work, generally they'll tell you that it works elsewhere, and why not on your site.

It also presumes they can move browser; less of an issue with Safari, but we've had to put in work-arounds for IE6/7 for users who are locked into those browsers by their employer (who really, really doesn't care enough to change).

Oh, and unless you either don't have to support the users, or have a very generous allocation of support staff, telling 20-30% of your total users to change browser is going to involve the support staff being hopelessly swamped with related questions and issues.

> The day that you were able to tell what someone was running and make a decision based on that, we basically lost the point of a standard

Well, sort of. If the browser gets the standard wrong, and the options are:

1. It doesn't work for that browser.
2. Degrading the result for everyone.
3. Implementing a browser-specific work-around.

Which would you really prefer? Yes, user agent testing is heavily mis-used, but it's not the terrible idea it's made out to be.

I'll give you a specific example; we had an issue with file uploads with Safari over SSL. For some reason if the connection was kept alive, Safari would frequently start uploading the file but never complete. The work-around was to force connection close for Safari; it wasn't perfect, but it massively reduced the frequency with which the issue appeared.

When MPEG LA first announced the VP8 pool formation, a rush of companies applied to be in the pool, partly because everyone wanted to see what everyone else had. That gave way to some amount of disappointment. And by 'some amount' I mean 'rather a lot really, more than the MPEG-LA would care to admit.'

Eventually, things whittled down to a few holdouts. Those '11 patent holders' do not assert they have patents that cover the spec. They said '_may_ cover'. The press release itself repeats this. Then these patent holders said 'and we're willing to make that vague threat go away for a little cash'. Google paid the cash. This is what lawyers do.

That's why it's a huge newsworthy deal when companies like NewEgg actually take the more expensive out and litigate a patent. It is always more expensive than settling, even if you'd win the case, and very few companies are willing or able to do it. Google was probably able, but not willing.

We deal with this in the IETF all the time. Someone files a draft and a slew of companies file IPR statements that claim they have patents that 'may' read on the draft. Unlike other SDOs though, the IETF requires them to actually list the patent numbers so we can analyze and refute. And despite unequivocal third-party analyses stating 'there is no possibility patent X applies', these companies still present their discredited IPR statements to 'customers' and mention that these customers may be sued if they don't license. This is not the exception; this is standard operating procedure in the industry. These licensing tactics, for example, account for more than half of Qualcomm's total corporate income.

It's this last threat that Google paid a nominal sum to make go away. It's the best anyone can hope for in a broken system. If those 11 patent holders had a strong claim, it is exceedingly unlikely they would have agreed to a perpetual, transferable, royalty free license.

I'll add my own thoughts here, also posted at http://xiphmont.livejournal.com/59893.html

"After a decade of the MPEG LA saying they were coming to destroy the FOSS codec movement, with none other than the late Steve Jobs himself chiming in, today the Licensing Authority announced what we already knew.

They got nothing. There will be no Theora patent pool. There will be no VP8 patent pool. There will be no VPnext patent pool.

We knew that of course, we always did. It's just that I never, in a million years, expected them to put it in writing and walk away. The wording suggests Google paid some money to grease this along, and the agreement wording is interesting [and instructive] but make no mistake: Google won. Full stop.

This is not an unconditional win for FOSS, of course, the LA narrowed the scope of the agreement as much as they could in return for agreeing to stop being a pissy, anti-competetive brat. But this is still huge. We can work with this.

For at least the immediate future, I shall have to think some uncharacteristically nice things about the MPEG LA.*

*Apologies to Rep. Barney Frank"

>If you insist on recording in stereo though, you might do as they did, and record with a Mid-Side array and use a matrix to decode back to L-R, so you can control the stereo spread in post-production.

That would not have controlled the reverb; the space this was recorded in was a concrete floor with concrete walls and no acoustic treatment. Like I said, it was a tradeoff, and one that was successful if not perfect.

Oh! And 'linear' was completely wrong. I don't know how I braino-ed that in there, the [at very least perceived] distortion/noise tradeoff is not linear.

Right, and this is why dither is only applied to 'last-mile' audio intended to be consumed. Dither 'screws' you in other ways if you intend to use that audio in production, such as losing all the property of removing the distortion, yet still having the additive noise. But we're still talking about changes 100+dB down.

>Counter nitpick: Monty, as a professional motion picture sound designer, I cannot tell you how distracting it is to hear your voice constantly changing its pan across the stereo field :)

The audio was recorded with a stereo pair. It wasn't panned artificially :-) Look down a few comments for more about this, you weren't the only person to complain.

I think it's more "I want people to know why I do the stupid things I do." Latent fear of being committed.

As a nitpick, you get dithering losses _or_ quantization distortion, or a linear tradeoff between the two. You don't get the worst case of both on top of each other unless you screw up.

Without dither, worst case, all your 16 bit quant distortion products will be under -100dB regardless of input amplitude. I actually display the worst case in the video to make it easy to see. Quantization distortion aliases, and I chose an integer sample period so the aliased distortion would always land in the same bins after folding. If I hadn't, it would have spread out more and been even lower. If I had chosen a relatively prime frequency, the quantization distortion would have spread out across all bins equally.

My network is vulnerable. I know this, because it exists.

The question is how vulnerable.

I run Linux, not OpenBSD, so there's a greater chance that I'll get a zero-day attack sprung on my network. However we make that compromise because it's considered reasonable.

I run services we need, but each is a risk.

There is no such thing as a secure network, there is only a secure-enough network.

I do that for systems I maintain.

I've nuked systems just for looking suspicious, despite not being able to prove someone cracked them (half the binaries in /bin stopped working, I figure that's fairly damn suspicious).

Anyone who doesn't re-image a cracked system is unbelievably naive, and it will come back to bite them hard one day. Like hell am I going to take the word of someone who broke into my systems that they didn't leave a rootkit.

The same way you tax payments in any other non-USD currency.