Runs a http server on localhost rendering you a simple, if stupid representation of your YouTube Watch History, available here.

To access this information yt_history uses the Google Data APIs. The program needs your OAuth2 authorization to operate.

Not much. See this G+ post for details.

• libevent 2.0.x: http://libevent.org/
• libssl from OpenSSL: http://openssl.org/
• libjson: https://github.com/json-c/json-c/wiki
• libexpat: http://expat.sourceforge.net/

For unit test(s):

• CUnit: https://cunit.sourceforget.net

For running the server you'll need Google Data API keys. See the Google Developers site for more information.

make

The makefile uses pkg-config for figuring out build flags.

Place your client id and client secret where yt_history can find them:

$HOME/.yt_history/client_id
$HOME/.yt_history/client_secret

Start the server:

./yt_history  [ -n ] [ -p <listening_port> ] [ -v [ -v ] ... ]

If you do not specify a port, one will be allocated for you. The listening address will be printed on the console.

• -v increases verbosity. Multiple -v:s more so

• -n disables https keep-alive. That is, we'll pass "Connection: close" with our requests and thus do the whole SSL connection negotiation separately for every request.

Point your browser at localhost. Your browser will be redirected to Google for authorization. When the browser returns we show a somewhat crude representation of your YouTube Watch History, unless the bugs get to us before we get so far.

Oh, no reason. Kittens.

Probably. I, however, can't.

Copyright (c) 2012 Jukka Ollila

Published under the GNU General Public License, version 2.0. See the LICENSE file for details.