Why Google PR is quirky -- Google PR bug

Recently I have been informed that the PageRank provided by pagerankstatus, a Firefox extension is different from official Google Toolbar. Since, I have been slightly involved with the development of this extension, I have studied the reason behind it.

Example

Target site: http://benmccann.com/
Pagerankstatus's PR: 4
Official Google Toolbar's PR: 0
Reason: Google's bug

Analysis

Pagerankstatus
What pagerankstatus requests: ...features=Rank:FVN...
What Google returns: Rank_1:1:4
Official Google Toolbar (IE)
What Google Toolbar requests: ...features=Rank:...
What Google returns: Rank_1:1:0
Official Google Toolbar (FF)
What Google Toolbar requests: ...features=Rank...
What Google returns: Rank_1:1:0
Google info XML file: ...info:...
PR inside XML file: 4 (This might be the right PR. Same as of pagerankstatus.)

Conclusion (Google bug)

Official Google Toolbar has downgraded the category/directory option; that's why now not sending "FVN" as "FVN" is for category. But, Google is supposed to return same PR for "Rank:FVN" and "Rank:", but returning different results. Let's hope, Google will fix this bug soon.

Comments

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...

What's wrong with delicious.com?

The recent UI changes of delicious.com is quite confusing and smells suicidal phase. I have noted that, after Joshua Schachter sold it to Yahoo!, it's going crazy changes. Probably, it's because a Yahoo! company now or Engineers don't get the real idea? Some crazy moves: del.icio.us to delicious.com change; probably to reach countries that censor .us TLD? delicious.com to www.delicious.com; unjustified Perl to PHP switch; why? for:handle geekish way to share to separate box; crazy but ok. Looks like, the new Yahoo! guys don't know how to make it a cult following like how twitter popularized @handle Recent broken UI

Technology prediction for 2018

Bubbles of bitcoin, blockchain, machine learning, deep learning, artificial intelligence and more People usually appreciate me for my predictions on technologies. As I already noted our team will quickly hit the edge case for any use cases and that's supposed to be the reason for my better prediction rate. And so, here are my predictions… Bitcoin bubble When Bitcoin became talk of the town/industry, I informed my boss and colleagues that I find no real use case for this digital currency--except in underground markets like drugs, etc. In fiat currencies, there is at least a way to take legal route, in case, if you've transferred the money and not received the goods. But, in Bitcoin, this is not possible at all as it is not a legal currency. So, if there is no trust, the chances that other person can cheat you by not sending the goods and or not transferring bitcoins after receiving goods. My stand above vindicated by the article Ten years in, nobody has come up with a...

R. Rajesh Jeba Anbiah

Search This Blog