Cleaning Cached Blog Entries in Google Reader – Or: How to Remove Unwanted Posts from Google Reader

While I was working on my next article using Windows Live Writer, I’ve hit the “publish” button too soon and ended up with a published draft in my blog. I just went and re-drafted the entry, thinking everything was going to be fine. Unfortunately, I did not realize that Google Reader automatically caches everything it finds, and do not delete entries even if them have been deleted from their original blog.

After some researching, I’ve found out that if I published a new post with the same GUID as the unwanted entry, it would be automatically updated in Reader. So here are the steps to remove an unwanted blog post from Google Reader:

Removing an unwanted blog post from Google Reader

Step 1: Consulting Reader’s cache

Type the following address in your address bar, substituting yourblogname by your actual blog name:

Go to the page, then right click its content and select “View page source” or equivalent.

Step 2: Find the offending post

Find the string “” and notice the two numbers that come after it:

Those are your blog ID and post ID, respectively.

Step 3: Resurrection!

Copy and paste these two numbers in the placeholders of the following URL:

Finally, open this URL and watch your once deleted (?) blog post be resurrected from the dead. Update it or just leave it blank, set the post date to the future and publish it again. Voilà!


Update: Unfortunately, the original post title will remain as the URL for the entry. As you can see, this was going to be a post about Partial Least Squares Analysis. However, I’ll leave it as is to prove this procedure really works. Cheers!

Update 2: I made a simple application to browse and edit deleted blogger posts that have been cached by Google Reader. The program, together with the C# source code can be found here. The program uses the Google Reader API developed by Matt Berseth.

Google Chrome Bug?


It seems there is a minor bug in Google Chrome. Apparently, you can’t click links that are in the same horizontal line as the status bar that pops up from the bottom left corner.

For example, clicking the link marked with a red circle in the image below does nothing.


Well, this obviously isn’t a show stopper, but I think its a bug nevertheless.

On Google Account Security, Trustfulness and Dependence

Today I received a very strange email in my personal gmail address from gmail itself:

O seu endereço secundário, “my-personal-address”, está associado a:


Para efetuar login, clique no link abaixo.
Se você clicar no link acima e ele não funcionar, copie e cole o URL em uma nova janela do navegador.Obrigado por usar o Google.

Em caso de dúvidas ou preocupações em relação à sua conta, visite as Perguntas freqüentes (FAQs) do Google no endereço

Esse correio é apenas para envio de mensagens. As respostas para essa mensagem não serão monitoradas nem respondidas.

Which roughly translates to:

Your secondary email, “my-personal-address”, is associated with:


To login, click on the link below.

However, only the first address is known to me. I remember creating it to test a web project for a university class last year. But for the others, I have to ask: How did those people add MY personal email address as their secondary email?


I’m pretty sure my personal account is safe and has not been compromised. I switch (strong) passwords often and always take care when and where I insert my credentials. Could this be an error within GMail itself? I always thought GMail required secondary email addresses to be confirmed before they could be linked with an account.


I’m getting worried because I just realized GMail accounts often aren’t just email accounts. They are much more. They form the online identity for a lot of people. Through Google services, they hold financial, health, social and content information. They are often the primary identity in sites such as Twitter, Facebook, LinkedIn and many others. Gosh, I know business which run with GMail addresses. For some people, losing a Google ID would mean starting life over.

I think Google has acquired a lot of responsibility those days. And I hope they can handle it well and wisely, as I (and almost everyone else I know) trust Google to handle a lot of their personal data.


On a final note, I strongly suggest Google to start researching ways to identify people other than just asking passwords. I have to use 2048-bit cryptographic keys with unlocking pass-phrases to access my remote hosts; why would I continue using passwords – even if they are strong passwords travelling within SSL by default – to access my – much more important – personal data?

How Google Tricks Microsoft Into a Fake Competition


Or: The Most Overlooked Point In How Google Competes With Microsoft And Nearly Everyone Else Outside The Web

From the very principle, it was never Google’s aim to replace other browsing software such as Internet Explorer, Firefox or Safari with Chrome. In fact, what Google truly wanted, was rather to improve them.



Let me explain in simple words: Google doesn’t actually cares if you are using Chrome, IE or Firefox as long as you are using them to access Google. Didn’t you notice what happened after Google released Chrome? All other browsers adopted the concept of a JavaScript VM. All other browsers incorporated inovation from Google so now the Web loads faster. By adding competition and promoting the benefits of a secure browser architecture, Google has increased the momentum for further web-as-software-platform development. This will make sure not only Google and its services loads faster and look more appealing, but that it does so in every browser, for everyone.


Google indeed seems to have a brilliant plan: bringing innovation improving and exploring ideas and then letting everyone borrow its ideas improvements for free so it can profit while every other competitor wastes time and money improving their own products, thinking they are competing with Google. While, in fact, they aren’t: They are just building more room for Google to expand upon. And the Google Chrome Operating System is certainly part of this.

But note that, while those may be bad news for Google’s (virtual) competitors, for us, users, it means a lot more. It’s no doubt the Google Chrome OS will surely play a major role in the paradigm shift we are all living now, where everything is becoming web and being put in the clouds. Lets just wait for some real competition, let the technology evolve, and we shall all benefict.


Truth is: In the end, even if Chrome OS fails, it still a win. For Google, and for us.

A few Chrome thoughts


Chrome is obviously missing an undo close tab function. It is really annoying to mistakenly click “close tab” (the x button next to the tab’s name) while switching tabs. Also, I would expect Chrome to remember what I typed on a form whenever I go back and forth in a site just like Opera does.

On Opera, the only thing one has to do to restore a recently closed tab is hit Ctrl-Z so the tab magically reappears with all information one had previously typed in. It is true the browser can restore itself whenever it crashes, but this ain’t necessarily true for user-typed information. I think this, the lack for mouse gestures and good bookmark synchronization are the only major drawbacks for the browser at the moment.

Also, Chrome doesn’t seem to perform very well on old machines, such as the old 1GHz Athlon Thunderbird box I use when I’m back to my hometown on the weekends. Opera and Internet Explorer ran just fine, but Chrome is sometimes sluggish, specially with Youtube videos or with more than 5 tabs open. Bad news, since I like to start mid-clicking everything I find interesting, opening new tabs in the background for later reading. This is probably due to how Chrome manages tabs using separate processes, but is a drawback, nonetheless.

Last note: In order to get the dead tab picture, I googled for some random website and started middle-clicking it like crazy. After 10 or more clicks, one of the new tabs (only one) finally crashed, showing that picture. But after a few seconds, all my other tabs (including the Blogger’s post editor I was using to write this) began chaging to the same screen! I think those tabs processes aren’t exactly as separate as it seems!

Google Desktop on Windows x64


Google Desktop now offers a command line flag to force installation on 64 bit machines. Just install with

 googledesktopsetup.exe /force

If you don’t wanna deal with the command line, just right click the setup executable, then click “Create Shortcut“. Right-click the newly created shortcut, select properties, then add the /force to the end of the target path text box. Hit ok and finally double click it. Voilà!

Google Desktop used to work on 64 bit Windows (like Windows XP x64 Edition and Windows Vista 64 bit), but ceased installing some months ago. I have used Google Desktop normally on my desktop before, but I got surprised when a newer version went out simply telling me it wouldn’t install because Google Desktop wasn’t anymore supported on my platform, leaving me with no software at all. I don’t know exactly to which extent the “not supported” definition goes, but, for now, the software has been running just well. The Google Desktop Help Center reports that certain features may not work correctly, so you have been warned.

Nossa! O Google Chrome travou. Deseja reiniciá-lo agora?

Simplesmente não consigo entrar nas configurações do Chrome sem crashar o browser. Talvez seja porque estou rodando Windows XP x64 Edition, ou porque, logo na instalação, quando o setup avisava que estava prestes a importar as configurações do Internet Explorer, cliquei no link azul “Alterar preferencias de importação” [ou algo assim] e o setup simplesmente fechou e sumiu, sem mais nem menos.

Achei legal o espanto na mensagem de erro. Nossa! Ainda bem que é beta =P