An undocumented API has changed. Now can we stop overreacting?
How is the API undocumented?
Developers might also want to take note of the following:
Warning: The current Google Cast SDK is a preview SDK intended for development and testing purposes only, not for production apps. Google may change this SDK significantly prior to the official release of the Google Cast SDK.
Actually it does matter a great deal. A key difference is what happens to the money if the project is not funded to the goal level. On kickstarter if the project misses its goal, no money changes hands. On indiegogo campaigns can be set up as "Flexible Funding" and the hosts get whatever is pledged (minus 9% for fees).
From the Kickstarter page:
Why is Kickstarter funding all-or-nothing?
On Kickstarter, a project must reach its funding goal before time runs out or no money changes hands. Why? It protects everyone involved. This way, no one is expected to develop a project with an insufficient budget, which sucks. Remember you set your own funding goal, so aim to raise the minimum amount you'll need to create your vision. Projects can always raise more than their goal, and often do.
From the Indiegogo FAQ
What if I don't reach my funding goal?
If your campaign is set up as Flexible Funding, you will be able to keep the funds you raise, even if you don't meet your goal. If your campaign is set up as Fixed Funding, all contributions will be returned to your funders if you do not meet your goal. Flexible Funding campaigns that meet their goal are only charged 4% as our platform fee, whereas campaigns that do not meet their goal are charged 9%.
There is no longer term advantage to an apartment.
The people who bought houses six years ago aren't seeing any longer term advantage either. If they hold on to it for another ten years or so the value may climb back to 80% of what they paid for it. If they're lucky.
... and limit (either through new laws or good judicial common sense) tracking by law enforcement to the same sorts of situations in which they would otherwise install a GPS tracker on your car.
Hell no! Based on recent events I would want a lot more protection that just this.
Hate that last-minute slight swerve to dodge a thrown tyre-tread that I couldn't see until the swerve.
Here's a hint. You're following too closely.
...and they'll figure out a way to make the windscreen blue.
But the windscreen will only turn blue in the case of a crash.
For example, if you want to use your Gmail account with military-grade security that neither NSA can read, just install Penango in your browser and send messages encrypted - this solution is also used by US military and corporations. Penango does not hold any of your private information and/or your keys - so they can not be forced by anybody to give out your secret.. simply because they do not have it!!!! For more info, go to http://www.penango.com/
Except that penango is not really compatible with any current browser releases except Internet Explorer. Firefox is supported, but only up to version 20. The current release is version 23.
What about WebP?
Comparing WebP to APNG is like comparing Apples and Oranges. WebP is an up-and-coming web oriented image format from google. Part of the WebP standard mentions animation. WebP however does not currently have anything more than a sample implementation, and WebP will probably never be backported to older devices and software and may never be ported to a lot of software that already supports PNG. This means that if you start using WebP now you can expect a lot of people to not be able to view your images at all - whereas with APNG they will at worst simply see the first or fallback frame.
WebP solves different issues and has a variety of features, such as lossy compression profiles and filters that simply don't apply to PNG and will not be part of the simple APNG standard [though it could be noted these features and more were in MNG]. APNG and WebP are simply different, and though they solve some of the same problems they are not really competing formats. Ideally we'd like to see wide spread adoption of both formats on just about everything in the future - but we can have and use APNG right now.
What about MNG?
If APNG is a screwdriver MNG is a Swiss Army Knife with all sorts of little tools, one of which being a screwdriver head that is sort of awkward and difficult to use. MNG has a lot of compelling features that sound great but the reality is all these features made MNG difficult to implement. MNG isn't a simple [screwdriver] "frame based" format. Instead it has a bunch of small embedded tools [Swiss Army Knife] to create animations. For example it contains individual image objects/sprites and these are manipulated through some sort of animation instruction system that is embedded in the image - and variations of sprites are stored as delta fragments, and there's additional support for these fragments to be in transparent JPG which is a questionable standard on its own and seems self defeating in a PNG based standard...? If you want just a frame based animated image APNG does the job and is simpler, if you want a complex format that has individual image fragments and scripted action then SVG+SMIL is your solution; MNG is too complex to outdo APNG and too inflexible to outdo SVG+SMIL.
Advances in computation power alone will never break encryption. Ever. There is no boundary. An encryption can always just create larger keys.
Incorrect for the most part. First, algorithms that used fixed length keys, such as DES, can and do fall to increases in computational power. Second, even with algorithms that use a variable length key, improvements in computational power can break it. If I can capture an encrypted file today, it may be that in five years I can brute force that file open due to computational advances. There is nothing that you can do to increase the key length once I have a copy of the file. The important thing when choosing a key length is to make sure that by the time such an attack is feasible, the data protected is no longer valuable. The only exception that I can think of is a One Time Pad. No amount of computational power can help decrypt a OTP in theory. Implementation is always a different story however.
Adding features does not necessarily increase functionality -- it just makes the manuals thicker.