Comment Re:From the summary: (Score 2, Funny) 200
How do I mod +1 Redundant?
How do I mod +1 Redundant?
Me either
Also brightness should be measured in absolute terms (nits). One tablet's 50% is not the same as another.
Edit: the guy was not from the Economist, but it was used as an example.
That's actually a marketing trick of a kind of "false choice". I can't remember where I read this but they have done studies involving this and the example was given with newspapers. Basically the idea goes, if they offer 2-3 choices and 1 is very expensive, another very cheap but the third makes it seem like you are getting the expensive plan for less, you think it's a deal in your mind. No one is immune to this, so I'm not singling out you, we've all felt victim to this as it's the natural way our brain makes order.
Ah here it is, it was someone from the Economist:
http://danariely.com/the-books/excerpted-from-chapter-1-%E2%80%93-the-truth-about-relativity-2/
Ah ok, thanks
This is a decent code sample too:
https://code.google.com/p/adamkoch/source/browse/#git%2Fbitmapfun
From, here:
http://developer.android.com/training/displaying-bitmaps/index.html
(adam koch is an Android developer advocate at Google, and the code comes from the AOSP but is backported to use the support lib)
Not more, but not necessarily less. With a self signed cert, you cant verify the identity of the signer/cert. With the possibility of a compromised CA, you have (essentially) the same problem. (As far as understand it anyways).
What I would like to know is what (if anything) can be done to verify keys without a CA? I don't know that much about crypto, so am genuinely curious. Are there techniques to do this? (Diffie-Hellman-Merkle?)
ActionBarSherlock fills this role pretty well already, even with some added features. But this is good stuff nonetheless. The support library has always been a great addition to the SDK. It really helps avoid writing ugly wrapper classes, or the really ugly old technique of using reflection for API levels. I would like to see them add more widgets though. Such as TimePicker, CalenderPicker, etc. Some support for ORM, and better handling of Fragments, instance states, data persistence and Loaders (less black box-y).
Still it is nice to see the support library progress march on.
These sound helpful too:
Media
- Added TransportMediator helper class to manage media transport control, such as play, pause, skip and other media actions.
-Added DisplayManagerCompat for managing display output to one or more device displays.
Other changes
-Added WakefulBroadcastReceiver helper class for implementing a common pattern of detecting a device wakeup event and passing work off to a Service while ensuring that the device does not go back to sleep before the handoff is complete.
-Added two new APIs, commitContentChanged() and rollbackContentChanged(), to AsyncTaskLoader to help deal with background updates for data changes that are subsequently canceled.
http://developer.android.com/tools/support-library/index.html
If you like tinkering you might consider rooting and giving CM10 a try. Back when I used to do root & tinker there were ways, (once rooted, depending on the ROM), to block updates. Rooting is not everyone's cup-o-joe though, some prefer stock-like CM, etc., others like TouchWiz.
Also, nothing cheap about being prepaid.
Indeed what's interesting to me is the lack of a few anticipated things here. I havent followed closely but I thought the next update was going to be Key Lime Pie and was looking forward to a Nexus 5.
The new support library seems interesting though
You misunderstood the analogy (I think). "Free Speech Zones" were nonsense created by the government intending to hide and push speech they didn't like to irrelevancy. The definition of censorship is not the point, but rather the act of pushing things off to a dark corner effectively stifling the content/speech is what is comparable here.
Anyone can make an omelet with eggs. The trick is to make one with none.