And if they do a good job, they will push competition. This seems like a common theme with Apple. They come into a fractured mess of a product sector and make a good show of it. This is good news, car infotainment is terrible.
Plus maybe cars will be able to launch actual angry birds at each other to express road rage.
Not sure if trolling but that's not really what trivial means in this context.
adjective: trivial
1. of little value or importance.
synonyms: unimportant, banal, trite, commonplace, insignificant, inconsequential,
Think "the average airspeed of an unladen swallow". "The atomic weight of cobalt"
ISPs are not peers though, they are endpoints. The "equal data" argument only works between two backbone/transit providers. ISPs are requesting that data be sent to them. they don't get to request the data be sent to them and request that they also be paid to receive it.
Also what makes you think you only pay for upload? That makes no sense. Though I agree in that bandwidth caps are bad -- though mostly because they are generally misleading advertising.
1) it's the ISP's users requesting 30% of the internet traffic, not Netflix. The ISPs aren't peering at all, they are the termination point. They aren't providing a service to Netflix, or to anyone else on the internet for that matter, except their customers.
2) It's the ISPs responsibility to provide enough network infrastructure to their customers. They don't get to hold hostage their users as a product to be bought by Netflix or other content providers.
3) Netflix offers Open Connect CDN
ISPs can directly connect their networks to Open Connect for free. ISPs can do this either by free peering with us at common Internet exchanges, or can save even more transit costs by putting our free storage appliances in or near their network.
https://signup.netflix.com/ope...
I think there is a fundamental misunderstanding of how peering arrangements are supposed to work that is being exploited by the PR departments of ISPs.
Well, there aren't really any apps that satisfy all of that. Open-source, secure, video and mobile. Thought the post I was replying to did not specify mobile (although that's WhatsApp's main platform I guess). But the Point I was trying to make is that WhatsApp didn't satisfy those requirements either. It wasn't open, nor secure.
Anyways. there is Xabber for Android -- but I don't think that has video. Also many Android users use Google Hangouts / Talk etc for chat and video, but that is not open-source. There seem to be a number of other XMPP clients for Android but I don't know enough about them.
Also, FYI that Wikipedia link covers lots of apps -- both desktop and mobile (including WhatsApp).
Scratch that, looking through the links, even one of the AOSP browsers is affected.
Some distributions of the Android Browser app have an addJavascriptInterface call tacked on, and thus are vulnerable to RCE. The Browser app in the Google APIs 4.1.2 release of Android is known to be vulnerable. A secondary attack vector involves the WebViews embedded inside a large number of Android applications. Ad integrations are perhaps the worst offender here. If you can MITM the WebView's HTTP connection, or if you can get a persistent XSS into the page displayed in the WebView, then you can inject the html/js served by this module and get a shell.
I think it's that it gains the permissions of the app hosting the webview. This isn't really browser related AFAICT
Was WhatsApp ever secure or open? Wasn't it just a proprietary wrapper for xmpp?
There are other jabber/xmpp/jingle clients out there. I'm not sure what is the best client but pidgin works well for most things IIRC. Miranda IM may also be worth a look, or Adium. All three are a GPL or similar license I think.
"If I do not want others to quote me, I do not speak." -- Phil Wayne