This. Just because the Apple TV (at the least) supports YouTube-styled encodes, doesn't mean we have the obligation to support them. The audience for the Org's hosting is generally PC users anyway.BasharOfTheAges wrote:Why would we want to enable the macfags? I don't get it. Shouldn't they be forced to suffer the downside of their proprietary lock-ins? How else will they learn?
The general point of why people use Local hosting is for the standard quality encodes - encodes which are meant for playback on a PC, where screen resolution is not a concern. The Local server has always been meant to store one and only one copy of the encode, if not video (re-edits discounted), and this topic has come up before, just maybe not with this latest iteration. It always gets shot down.
If you're really that concerned about iWhatever users, then just make the main encode compatible with it (or do what you already do, and host them elsewhere). To me that's just sort of like pissing into the wind, though, since so few people would really care about it, and think of the benefits you'd be losing, encode-wise, trying to support them. It's just not worth it, IMO. If they really want to have the stuff on their Phones and digital music players (what do you mean they're for playing music?), there's plenty of conversion apps out there, and they should already be pretty familiar with them if they're used to using those devices for practically everything anyway.
