Cmon man, that one was debunked in 2006:
http://www.zdnet.com/blog/burnette/gplv3-myth-3-gpl-forbids-drm/354
Stall man hates in but so what.
http://www.zdnet.com/blog/burnette/gplv3-myth-3-gpl-forbids-drm/354
Stall man hates in but so what.
It's more simple then even that; first GPL doesn't forbid it, but second, the assumption here is that the core OS players and mediums handle it. As Mandriva, SuSe and others have pointed out, just because the OS level is GPL, add-on applications and overlays do not have to be. I don't think Amazon will make their custom skin GPL, and they aren't under any obligation to do so. As long as they leave the core, they are fine. So, to do this in an the OS, they just have to provide their own media player. That's it.Sam Posten said:Cmon man, that one was debunked in 2006:
http://www.zdnet.com/blog/burnette/gplv3-myth-3-gpl-forbids-drm/354
Stall man hates in but so what.
Originally Posted by Hanson /t/311127/can-amazon-stand-above-the-fray-and-make-sense-of-the-android-tablet-mess/120#post_3855779
So the long an short of it is that GPL doesn't forbid DRM, but if you use it, it will have to be made public like everything else. So if you include DRM, you will have to make the blueprints public, so to speak. That's an interesting deterrent.
Currently, Netflix will only stream HD content to phones that have the TI OMAP 4 chipsets. That's because the DRM is on the chip level, and bypasses the GPL issue:
http://androinica.com/2011/07/netflix-hd-certification-goes-to-ti-omap-4-first/
And here's another hat thrown into the ring:
http://www.androidcentral.com/samsung-announces-7-inch-galaxy-tab-70-plus
It doesn't look like it's coming to the US until next year. But if the Fire is all the rage by then, Samsung will not be able to sell this for a penny more than $249 (if that).
I'm no DRM expert, but I would think it's easier for people to bypass (vs outright break) the DRM if you choose software over hardware. If it's done in software, then there's more opportunities for the decrypted content to be grabbed somewhere along the playback chain before its final intended output. If it's done strictly in hardware, there may be virtually no opportunities for that depending on exactly how it's implemented.Originally Posted by Hanson /t/311127/can-amazon-stand-above-the-fray-and-make-sense-of-the-android-tablet-mess/120#post_3855791
Yes Matt, I understand your point, but if DRM were an easy software based solution, then why go to the trouble of have DRM on the chip level for HD video? I'm not that well versed on implementing DRM, but I assume there's something deeper than just software that needs to be addressed to have it working, at least on the video side. Kindle has DRM on its content, so you are correct that you can have DRM on Android as long as it's tucked inside of apps.
Originally Posted by Hanson /t/311127/can-amazon-stand-above-the-fray-and-make-sense-of-the-android-tablet-mess/120#post_3855791
Yes Matt, I understand your point, but if DRM were an easy software based solution, then why go to the trouble of have DRM on the chip level for HD video? I'm not that well versed on implementing DRM, but I assume there's something deeper than just software that needs to be addressed to have it working, at least on the video side. Kindle has DRM on its content, so you are correct that you can have DRM on Android as long as it's tucked inside of apps.
I guess one can keep one's entire digital media library on a big thumb drive or something toward that end.
I got excited at the prospect of adding storage via a thumb, but someone commented on a forum today that the USB port is only for transferring data direct from a computer. It won't draw from a thumb.ManW_TheUncool said:I guess one can keep one's entire digital media library on a big thumb drive or something toward that end. Not as good as having it directly accessible, but probably good enough for keeping storage hogging feature-length movies or similar off the rather limited internal storage. Not crazy about having to do that for music files as well though -- I guess one can just defer to one's smartphone or iPod or whatever other music player for that though that would kinda defeat one purpose for owning such a device...
_Man_
DaveF said:Google's reaction to Kindle Fire speaks volumes about its goals for Android. Kindle Fire is based on Android, and will run Android applications. Android has been struggling in the tablet space, so you'd expect that Google would be delighted to have Amazon on the Android bandwagon. But you'd be wrong. Let's look at the press release Google issued today to welcome Amazon to the Android family. Wait a minute, there is no press release. Okay, so let's look on the Google blog. Nothing at all. Maybe a tweet from Andy Rubin? Dead silence.
Originally Posted by Hanson /t/311127/can-amazon-stand-above-the-fray-and-make-sense-of-the-android-tablet-mess/120#post_3856998
We knew it was selling at a loss, but it doesn't look as bad as expected:
http://venturebeat.com/2011/09/30/amazon-kindle-fire-build-cos/
$10 loss per unit isn't that bad, but surprisingly, they only anticipate a $10 profit after digital purchases. Looks like it's a Trojan Horse to sell physical products from the main site more than a digital media platform.
Apps are also forbidden from using Google's Mobile Services (and in-app billing), which, if included, will have to be "gracefully" removed. In terms of actual content, Amazon has outlawed all apps that change the tablet's UI in any way (including theme- or wallpaper-based tools), as well as any that demand root access (it remains to be seen how the company will treat the root-dependent apps already in its store). Interested devs can find more information at the source link, below.