My Google Reader Share Twitter (re)stream is being updated -- but the posts are coming from a rogue Feedburner bot. None of my Google Identities have control of this feed burn. I think I've run into a bug related to the (covert) Great Google Identity Integration Initiative (GGIII) of 2011.
What, you may wonder, is the Great Google Identity Integration Initiative of 2011? Why do I say it's covert (covert)? I'll provide some background before I give my take on this alleged bug.
The GGIII is covert, first of all, because Google hasn't named it, much less documented what's going on. Three Google articles provide some limited context (emphases mine) ...
After your Google Apps accounts are converted, your users will have access to most Google products. Previously, many Google products -- such as Blogger, Reader, and Picasa Web Albums [jg: and Feedburner] -- were available only in personal (consumer) Google Accounts...
... If any of your users have a conflicting account, they will be required to rename their conflicting accounts the next time they sign in to their personal Google Account...
... Any Picasa Web Album, Profile, or Wave usernames cannot be moved from an existing account to your Google Apps account
If your users used Picasa Web Albums with personal Google Accounts, they will not be able to reuse their old Picasa Web Album display usernames. They will have to sign up for new display usernames....
Reading between the lines there are two aspects to GGII ...
- Unification of usernames across Google properties where username is an email address. (example - firstname.lastname@example.org). So if this username is used for both a Google Apps account and a traditional Google Account then the two accounts will be unified.
- Tie all Google services to a Google Profile. This was recently mandated for all Picasa web album users, even paying customers. Not all customers were happy about this.
Phew. So, if you're still with me, this is what I think happened to a feedburner bot associated with email@example.com. That "identity" used to be split between a Google Apps domain (email, etc) and a true Google Account (blogging, feedburner). When I (carefully ) activated "More Google applications" for my Google Apps domain kateva.org Google merged two distinct identities that shared a single "name"
- firstname.lastname@example.org - Google Apps kateva.org
- email@example.com - Google Account
My guess is there's a bug with this process when a user has a Feedburner bot linked to a Twitter account using the Feedburner "socialize" feature. I think I have two feedburner services associated with firstname.lastname@example.org, but one of them is unreachable.
I doubt there's anything I can do, I just have to wait for Google to fix this. In the meantime I've posted questions with somewhat different angles on two forums ...
- How can I identify the feedburner source of a Google/Twitter integration connection? - Google Groups
- Feedburner configuration no longer accessible - Google Apps Help
-- fn --
 I expected problems. Since this is going to be mandatory in the next few months, including for our family domain where we have similar distributed identity issues, I chose to make kateva.org a test case. I expected bugs like this.
Update 1/2/2011: The problem stopped. I suspect it was related to another Google identity of mine, and so this is probably not a Google bug ... (see below)
Unfortunately, it is not possible to combine two accounts or to merge data.
Except that Google also tells us ....
Moving product data : Managing and using Google products - Accounts Help
... In most cases, it's not possible to move products from one Google Account to another ... This may change over time, so check back here for updates...
Right. Clearly, this is a flaming mess.
So what happened was that the feedburner configuration in my google (email@example.com) account was vaporized when the transfer process destroyed that account's data, but it took a while for the bot to die. Hence the duplicates.
This transition should be avoided as long as possible. If you do make the merge I suggest:
- Give the old account a new email address (you'll have to dig one up somewhere).
- Delete the old account after you've gotten all your data out of it and after you've ensured that any associated blogs have an admin user with the new identity.