Google Webmaster Sitemaps bug

Dear Google,
I have my blog at http://the100rabh.blogspot.com as you can see ;-). I was looking into Google Webmaster Sitemaps. Today I found that I was not able to see more than 100 inlinks to my page.
The main page link was this
https://www.google.com/webmasters/tools/externallinks?siteUrl=http%3A%2F%2Fthe100rabh.blogspot.com%2F&hl=en&bplink=http%3A%2F%2Fthe100rabh.blogspot.com%2F&sort=allsubdomain&num=100

The next link was this
https://www.google.com/webmasters/tools/externallinks?siteUrl=http%3A%2F%2Fthe100rabh.blogspot.com%2F&hl=en&sort=allsubdomain&view=&bplink=&num=100&bpmark=100,0,100,0,0&fwd=true

It was frustrating to see that clicking on the next link I went to the main inlinks page. For the time being I found solution as this

https://www.google.com/webmasters/tools/externallinks?siteUrl=http%3A%2F%2Fthe100rabh.blogspot.com%2F&hl=en&bplink=http%3A%2F%2Fthe100rabh.blogspot.com%2F&sort=allsubdomain&num=100&bpmark=100,200,XXX,YYY,0&fwd=true

Instead of clicking on next I make my own next URL. I just change that value of XXX in multiples of 100 with YYY being 100 more than XXX and you keep going to the next page....Google boys are you listening?

After giving some thought to the problem I have realized that the reason for this kind of behavior is a silly mistake on the programmers part. But I believe that the larger problem is because of the way Google gets and displays data. No doubt I am not the best in the business, but my common sense tells me that less I expose thing to be manipulated at the client end, more secure I am. In this case I did the same manipulation as I did to make a Greasemonkey script to get to the last page of the topic in an Orkut community. The script can be found here. Your comments are invited.

Comments

Post a Comment

Popular posts from this blog

[24th November 2024] Interesting Things I Learnt This Week

Image
1. AI Makes Tech Debt More Expensive - The core argument is that generative AI significantly widens the gap between codebases with low and high tech debt. Companies with clean code can leverage generative AI to write code much faster, while companies with messy legacy codebases struggle to adopt these new tools. This widens the gap between the two codebases, making tech debt even more expensive for companies with outdated systems. My Take : Legacy systems inevitably accumulate technical debt. A common analogy for this is the state of urinals over time: missed targets lead to increasing mess, keeps pushing people away from urinals and leading to more mess in turn. AI-powered coding tools could potentially accelerate the accumulation of tech debt. However, skilled engineers can leverage AI to reduce and even eliminate it. Ultimately, AI is just a tool, and human judgment remains crucial for making informed decisions. I hope AI will be used responsibly to drive positive outcomes. 2. Make...
Read more

[17th November 2024] Interesting Things I Learnt This Week

Image
 1. Booleans are a trap : Booleans, while seemingly simple, can introduce complexity and limitations into domain modeling. When used to represent complex states, booleans can lead to unclear code and potential errors. To avoid these pitfalls, consider using enums or enum sets. These approaches provide a more expressive and maintainable way to model complex states in your applications. My Take : I wish I had learned this earlier in life. When working with Google Docs, I realized the limitations of booleans. Expanding boolean-based behaviors often led to adding more fields, making the system complex. Enums would have provided a simpler solution. The problem wasn't just the booleans themselves, but also the need to pass them through multiple layers of the stack, often requiring additional parameters. Another important aspect of enums is the inclusion of an " enum not specified " state. This state explicitly indicates that an enum value hasn't been set, which can be usef...
Read more

[1st December 2024] Interesting Things I Learnt This Week

Image
1. C++ Pitfalls - this article, explains some of the pitfalls you can fall into when programming in C++ and shares their experience with them. This includes Operator precedence, Arithmetic conversion rules, Right bit-shift, Implicit conversions and Order of evaluation.  My Take : We've all read about JavaScript's quirks, leading to unexpected outputs. But let's remember that such behaviors aren't unique to JavaScript. Even languages like C and C++ have their share of ambiguities and compiler-specific behaviors. While it's tempting to dive deep into these intricacies, I've found that focusing on clear, consistent, and unambiguous code is often more practical. However, understanding these nuances is essential for any experienced programmer. It helps us avoid pitfalls and write robust, reliable code. Remember, mastering a language isn't just about writing "Hello World." It involves delving into its intricacies, including its counterintuitive and ambi...
Read more