Received: by 10.101.63.2 with SMTP id q2mr138086ank.48.1314301799487;
        Thu, 25 Aug 2011 12:49:59 -0700 (PDT)
X-BeenThere: youtube-api@googlegroups.com
Received: by 10.101.204.19 with SMTP id g19ls2506186anq.5.gmail; Thu, 25 Aug
 2011 12:49:39 -0700 (PDT)
Received: by 10.101.63.2 with SMTP id q2mr137730ank.48.1314301779128;
        Thu, 25 Aug 2011 12:49:39 -0700 (PDT)
Received: by 10.101.63.2 with SMTP id q2mr137728ank.48.1314301779093;
        Thu, 25 Aug 2011 12:49:39 -0700 (PDT)
Return-Path: <je...@google.com>
Received: from smtp-out.google.com (wpay10.hot.corp.google.com [172.24.198.10])
        by gmr-mx.google.com with ESMTPS id v10si1099789anq.2.2011.08.25.12.49.38
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 25 Aug 2011 12:49:38 -0700 (PDT)
Received-SPF: pass (google.com: domain of je...@google.com designates 172.24.198.10 as permitted sender)
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of je...@google.com designates 172.24.198.10 as permitted sender) smtp.mail=je...@google.com; dkim=pass (test mode) header...@google.com
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77])
	by smtp-out.google.com with ESMTP id p7PJnbWv006981
	for <youtube-api@googlegroups.com>; Thu, 25 Aug 2011 12:49:37 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta;
	t=1314301777; bh=HFYYCxiM2nDYd+Lsua+jR9xZ9gE=;
	h=MIME-Version:Date:Message-ID:Subject:From:To:Cc:Content-Type;
	b=uKzXkl4UHk3POOrJM9P+iKKtfiWYyzfvaRbwblu8wZn7ZtLI7g4ONM55sYRzce7mA
	 LMPP2yFaQXzZyFHghKIuQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=mime-version:date:user-agent:x-google-web-client:
	x-google-header-order:x-http-useragent:x-google-ip:message-id:subject:from:to:cc:
	content-type:x-system-of-record;
	b=nQX1NvFWzDMK+ejWUcVBiNGF9L1M3Zuqs55cNbhKEWRI708IHetCXFhhPRjUmrecN
	Mc0jkTsTlaWlE4JpxjQRw==
Received: from gwj22 (gwj22.prod.google.com [10.200.10.22])
	by wpaz13.hot.corp.google.com with ESMTP id p7PJnaW6006701
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
	for <youtube-api@googlegroups.com>; Thu, 25 Aug 2011 12:49:36 -0700
Received: by gwj22 with SMTP id 22so3339472gwj.27
        for <youtube-api@googlegroups.com>; Thu, 25 Aug 2011 12:49:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.135.25 with SMTP id m25mr43333ann.9.1314301776747; Thu, 25
 Aug 2011 12:49:36 -0700 (PDT)
Received: by x11g2000yqx.googlegroups.com with HTTP; Thu, 25 Aug 2011 12:49:36
 -0700 (PDT)
Date: Thu, 25 Aug 2011 12:49:36 -0700 (PDT)
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8)
 AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.854.0 Safari/535.2,gzip(gfe)
Message-ID: <ce7946e6-b319-440f-b6ff-382b5a4cf...@x11g2000yqx.googlegroups.com>
Subject: Auth Tokens & Unlinked YouTube Accounts
From: Jeffrey Posnick <je...@google.com>
To: YouTube APIs Developer Forum <youtube-api-gdata@googlegroups.com>
Cc: youtube-api@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
X-System-Of-Record: true

We have a new blog post up at

  http://apiblog.youtube.com/2011/08/auth-tokens-unlinked-youtube-accounts.html

That contains some important information for developers using AuthSub
or OAuth. Existing tokens that were generated for YouTube accounts
that were not linked to Google Accounts will become invalid on
Wednesday, August 31.

There are a number of important details in the post explaining exactly
what that means, so please give it a read.

Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev