[mythtv] Implications of the new youtube API

[Bryan Haskins]

Really? Weird. From all the blog talk around it, it seems as though the
biggest thing is the neutrality of the content, and being visible in any 3rd
party player. How is it being accomplished without directly passing the
stream?

On Thu, Mar 13, 2008 at 8:27 PM, Kevin Kuphal <kkuphal at gmail.com> wrote:

> On Thu, Mar 13, 2008 at 7:20 PM, Bryan Haskins <ryuzaki90 at gmail.com>
> wrote:
>
> > What do you think this will mean for us? Since, from what I understand,
> > we can now freely manipulate/search/view videos however we please using the
> > API, it is now fully okay to get youtube working more directly (no scraping,
> > or anything) with mythtv. Has anyone thoroughly skimmed the new API, and
> > what it's capable of? I assume we can directly get a raw FLV stream from it
> > (as the big thing it boasts is playing videos in whatever client you enjoy).
> >
> > All of this, to me, means a custom frontend fro Youtube searches, and a
> > simple script to directly pull movie locations, passing it to internal or
> > mplayer.
> >
> > It's all new so I thought a good discussion would be great.
>
>
> If it's what I looked at a short while back when fixing MythNews for the
> YouTube downloading, it wasn't much different than the existing RSS feeds
> that they provide in terms of capabilities.  It still only returns
> information about referencing the embedded player, not downloading the video
> file itself.  At least that's what I gathered from the google site that
> described it and when looking at the results from the various queries.
>
> Kevin
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20080313/bfa8c3a4/attachment-0001.htm