HN user

jan_nan

3 karma
Posts0
Comments4
View on HN
No posts found.

Very strong opinions about this. As someone who grew up on the internet and who prefers to browse it read-only without an account, with self-deleting cookies, ideally using some of the amazing third party front-ends out there for the likes of YouTube and co, this announcement is a bit of a "fuck you" to my way of life. Obviously a VPN will go some way to navigating the immediate effects of this but I worry for the larger eddies this might create towards a broader acceptance among platforms of enforced user identification and verification.

Also, YouTube is one of _the_ premier platforms for education. Many schools use it directly, and I'm sure every kid today with an itch to learn has found a serious part of their identity through the educational YouTube channels out there that IMO do such a better job than equivelent media a generation ago did.

TV devices are a hot mess to support from a streaming perspective, they each come with their own quirks that mean some perfectly-in-spec encoding and packaging techniques will result in a failed playback on some models of TV. Once a TV device _is_ supported, that support has to be maintained typically for more than a decade until usage of that model falls so low that dropping it from support can be justified.

It would be prohibitively costly to produce per-device renditions so instead there is one generic rendition produced for "all smart TVs" and another one for "UHD capable smart TVs".

Traditional TV manufacturers all work with the BBC to get their devices certified, which is a requirement for carrying the iPlayer app and comes with legal agreements that asset that a device _will_ be able to playback BBC content for as long as it's supported.

Because Apple like to Think Differently, they opted not to align with the entire rest of the TV industry in standardising on MPEG-DASH spec. They instead require all developers to stream video using the HLS protocol. As UHD content on iPlayer is geared exclusively for smart TVs, and all the other smart TVs support MPEG-DASH, the UHD workflow simply never evolved the ability to target Apple's TV devices.

toki! sina toki pona tawa mi. mi musi mute a!

mi kama sona pi toki pona kepeken lipu mute. ilo YouTube li suli tan ni. mi ken toki lili, taso mi ken ala sona e sona suli. mi wile e tenpo mute tan kama sona.

mi toki insa e ni: mi toki kepeken toki pona anu toki kepeken toki Inli kama toki pona.

mi wile e ni: jan ante li lon ni li toki kepeken toki pona anu seme? me kama awen e sona.

jan pali li sitelen e toki sitelen tenpo pini. jan ali li sama. tan la, mi sona ala!

English: I wonder if there are other people on Hacker News who know toki pona? I myself am still learning it.

I see the author of this site is using the old sitelen (glyphs), as is usual for most in the toki pona community. I don't understand why the new glyphs aren't used more.