And 63% of my traffic can't and won't support those open protocols. Can I count on you to pay for a few million people to change their phones and tablets out to the one you prefer, or are we still talking about people and a magical world in your mind?
And if you are going to provide a link to an article supporting your case, perhaps you should read it first.
"If you are going to use your phone for GPS in the car, get a mount for it and make sure you also consult Californiaâ(TM)s laws about where that can go (See CVC 26708) which is a 5â square area top center of your windshield for toll tags or a GPS device can go in âoea seven-inch square in the lower corner of the windshield farthest removed from the driver or in a five-inch square in the lower corner of the windshield nearest to the driver and outside of an airbag deployment zone, if the system is used only for door-to-door navigation while the motor vehicle is being operated.â
They obstruct your FOV much like the roof of your car does. You actually have to look very far upwards to see the display in google glass, so far up, they you are now more than likely looking at the roof of your car.
I think any lawyer worth $0.02 would get that argument thrown out in court. The law does not stipulate that the device must ONLY be capable of those things.
Most GPS systems are NOT illegal, because they fall under 27602(b)1. The only things that need an interlock are devices that conform only to 27602(b)5.
The law stipulates "installed", not permanently installed, nor professionally installed. Clipped, taped, or just leaning on the dashboard would be "installed" in the car.
On the flip side, wikimedia also pays bandwidth fees, and they can save money by sending videos using h.264 over the larger VP8/WebM format, likely a LOT (1000x) more than for any license fee.
Using h.264 allows for hardware decoding of the videos, which is much more power efficient than the alternative "open" codecs. Therefore, having wikimedia trying to force "open" codecs would cause all users to use up more bandwidth, consuming more electricity, which is generated (mostly) from burning coal, and polluting our planet. Why would wikimedia want to actively pollute our planet like that? Do you know how many people each year die or have their lives shortened due to smog and other airborne contaminants? Do you know how many of them are babies? What does wikimedia have against babies and why are they killing them like that?
There is abosolutely no reason for anyone purporting to provide open content to lock that content into proprietary formats.
Absolutely no reason, except: * Using less battery * Less studder/jitter * Better looking videos * Less cost in serving the content * Less cost in receiving the content (assuming a non unlimited "unlimited" plan) * Broader support
But besides the obvious less cost, better quality, easier to implement, you are right.
The h.264 is already lost, and at this point, I would venture, so is the next generation.
VP9 doesn't compete with h.265 -- It almost competes with h.264, but it is still worse than that. All the 4k video devices have already included h.265 hardware decoders because there isn't an alternative. No one wants to use VP9 when it will use 60% more bandwidth than h.265. Many don't even have internet connections that could handle 4k video using VP9, and even if it did, you'd hit your monthly bandwidth cap 60% faster. It's pretty much a dead deal unless google can pull some serious magic out of VP9 that they haven't shown yet.
And I would counter, HA, my phone works on all the other video sites, including Amazon (which that other one doesn't). Seems wikimedia is the one with the crappy site.
XBMC is an awesome Media Player if... you only have 1 user, and you only have one place you watch stuff, and that place is always connected through a local LAN, and everywhere you store media is available 24x7. Violate any of those, and things quickly go down hill -- all of which PLEX does quite easily.
Oh, and getting XBMC to share it's watched list across multiple devices running XBMC is a pain the ass or near impossible depending on what devices and what type of connectivity (if any) they have to each other.
A server that does the decoding is superior because it doesn't require all of your clients to be able to decode it.
Currently I'm using a Plex Server, and I have a number of clients that I use... iPhone 5, Android, PS3, Chromecast, Web, and Apple TV (via iPhone 5). It also supports offline syncing to the iPhone 5 and Android so I can watch media when I'm not at home, supports sharing of libraries locally and through the internet. It also supports multiple users, tracking each users watched list, so my wife watching something doesn't immediately remove it from my queue of things to watch.
XBMC while having a superior client interface, is a poor media server. FYI - XBMC also has a nice plug in for accessing plex media servers, which works quite well.
Slashdot Mirror
That's fine, just don't expect for us normal nonfreetards to donate to your sites if they don't work for us.
In addition to the other 3? Sure! Why not add h.265 as well and reduce their costs further?
And 63% of my traffic can't and won't support those open protocols. Can I count on you to pay for a few million people to change their phones and tablets out to the one you prefer, or are we still talking about people and a magical world in your mind?
So you are trying to say that you have the only android phone in the world that plays amazon prime videos? Cool!
And if you are going to provide a link to an article supporting your case, perhaps you should read it first.
"If you are going to use your phone for GPS in the car, get a mount for it and make sure you also consult Californiaâ(TM)s laws about where that can go (See CVC 26708) which is a 5â square area top center of your windshield for toll tags or a GPS device can go in âoea seven-inch square in the lower corner of the windshield farthest removed from the driver or in a five-inch square in the lower corner of the windshield nearest to the driver and outside of an airbag deployment zone, if the system is used only for door-to-door navigation while the motor vehicle is being operated.â
Except google glass doesn't swallow the entire pilot's field-of-view either.
They obstruct your FOV much like the roof of your car does. You actually have to look very far upwards to see the display in google glass, so far up, they you are now more than likely looking at the roof of your car.
I think any lawyer worth $0.02 would get that argument thrown out in court. The law does not stipulate that the device must ONLY be capable of those things.
That would be an incorrect reading of the law.
Most GPS systems are NOT illegal, because they fall under 27602(b)1. The only things that need an interlock are devices that conform only to 27602(b)5.
The law stipulates "installed", not permanently installed, nor professionally installed. Clipped, taped, or just leaning on the dashboard would be "installed" in the car.
Spending donations on bandwidth to cover the less efficient VP8/WebM video format doesn't help either.
Or perhaps they should change their mission statement to include being freetards first?
On the flip side, wikimedia also pays bandwidth fees, and they can save money by sending videos using h.264 over the larger VP8/WebM format, likely a LOT (1000x) more than for any license fee.
By "spy-phone" I assume you are referring to android and it's default to send everything you type into your address bar to google.
Using h.264 allows for hardware decoding of the videos, which is much more power efficient than the alternative "open" codecs. Therefore, having wikimedia trying to force "open" codecs would cause all users to use up more bandwidth, consuming more electricity, which is generated (mostly) from burning coal, and polluting our planet. Why would wikimedia want to actively pollute our planet like that? Do you know how many people each year die or have their lives shortened due to smog and other airborne contaminants? Do you know how many of them are babies? What does wikimedia have against babies and why are they killing them like that?
There is abosolutely no reason for anyone purporting to provide open content to lock that content into proprietary formats.
Absolutely no reason, except:
* Using less battery
* Less studder/jitter
* Better looking videos
* Less cost in serving the content
* Less cost in receiving the content (assuming a non unlimited "unlimited" plan)
* Broader support
But besides the obvious less cost, better quality, easier to implement, you are right.
And what browser is it that you have that supports WebM but not h.264?
The h.264 is already lost, and at this point, I would venture, so is the next generation.
VP9 doesn't compete with h.265 -- It almost competes with h.264, but it is still worse than that. All the 4k video devices have already included h.265 hardware decoders because there isn't an alternative. No one wants to use VP9 when it will use 60% more bandwidth than h.265. Many don't even have internet connections that could handle 4k video using VP9, and even if it did, you'd hit your monthly bandwidth cap 60% faster. It's pretty much a dead deal unless google can pull some serious magic out of VP9 that they haven't shown yet.
And I would counter, HA, my phone works on all the other video sites, including Amazon (which that other one doesn't). Seems wikimedia is the one with the crappy site.
Anything bad? As in taking up computer and network resources without authorization? Yes.
And I would have to totally disagree on that. A flat touch screen is the BEST interface for controlling media.
As does the plex app.
I tried ps3mediaserver, it was pretty bad.
XBMC is an awesome Media Player if... you only have 1 user, and you only have one place you watch stuff, and that place is always connected through a local LAN, and everywhere you store media is available 24x7. Violate any of those, and things quickly go down hill -- all of which PLEX does quite easily.
Oh, and getting XBMC to share it's watched list across multiple devices running XBMC is a pain the ass or near impossible depending on what devices and what type of connectivity (if any) they have to each other.
A server that does the decoding is superior because it doesn't require all of your clients to be able to decode it.
Currently I'm using a Plex Server, and I have a number of clients that I use... iPhone 5, Android, PS3, Chromecast, Web, and Apple TV (via iPhone 5). It also supports offline syncing to the iPhone 5 and Android so I can watch media when I'm not at home, supports sharing of libraries locally and through the internet. It also supports multiple users, tracking each users watched list, so my wife watching something doesn't immediately remove it from my queue of things to watch.
XBMC while having a superior client interface, is a poor media server. FYI - XBMC also has a nice plug in for accessing plex media servers, which works quite well.