Ciphering the PR HTML

[Jon_King]

When I browse the PR data from Google's toolbar left in my internet temp folder I will see something like:

1:1:5

Or

1:1:5 /and then a Google category/

I have found the "5" to be the PR, but what is the 1:1 and what does the category string that follows mean? The category string is there only occasionally. Is there potientally other info I have not seen yet?

[Thundik81]

You find something link that :
- for google
Rank_1:2:10
FVN_1:54:Top/Computers/Internet/Searching/Search_Engines/Google
- for alltheweb & teoma
Rank_1:1:9
FVN_1:47:Top/Computers/Internet/Searching/Search_Engines

Explanation :
Rank_1:how_many_number_for_PageRank:PageRank
FVN_1:Category_in_DMOZ:Google_Directory

[b]Few other Facts[b] :
1. When you vote for a page with Google Toolbar, your query is [google.com ] for Vote UP and [google.com ] for vote DOWN.
I don't try but in theory you can use auto-refresh to increase your PageRank (like <META HTTP-EQUIV="refresh" CONTENT="x[minimum 1]; URL=http://www.google.com/search?client=navvote&vote=u&url=http%3A%2F%2Fwww%2Eyourwebsite%2Ecom%2F">)

2. You can find your PageRank and Category using this link :
[google.com ]
To know your website checksum look at your cache
Ex : for Google, today's checksum is ch=5455726090.
Also don't forget the final slash.

I don't search how checksum is calculated but it doesn't seem difficult

Mike

[Chris_1977]

Hi Mike,

Could you figure out how checksum is calculated? I think it not easy.

Chris

[Thundik81]

easy? if it was so simple, we would know how checksum is calculated.

in my previous post i just want to say that checksum algo isn't strong crypto. For example looking at few checksums in your internet cache, you can think :
- checksum is ch=dddddddddd (d for digit)
- ten digits would be a decimal form (so 8 characters in hexa)
---> 1. checksum is limited : only 4 294 967 296 possibilities
(Google has already more than 3 billions pages)
---> 2. checksum use a 32 bits algo (as one byte is eight bits) and you think naturally about CRC32.
---> ....

But it's just a idea which is inconsistent with facts. You think a lot but you search in the wrong way. The only way to solve checksum algo is by disassembling Google Toolbar.
First you will see that, in v1.1.66-deleon, :
- in HTTP request for PR, there is ch=5. So real checksum is the last nine digits. There is also ch=4 but it's not used yet
- checksum is computing from "q=info:" value. ASM subroutine is about 150 lines for "q=info:", "ch=" and "&freshness_check=3"

i don't have many time (i take my exams) but i promise you that i will look at look at following weeks

Mike

[GilbertZ]

I'm trying to change my encoding so that this thread will turn into english but nothing is working.

(YELLS into communicator) Scotty, please fix the universal translator tool. Jim, Over.

[Jon_King]

gilbertz,

Maybe this will help:

.model small
.stack 100h
.data
NotEnglishMessage DB 'This is Assembly not English Language', 13, 10, '$'
.code
mov ax,@data
mov ds,ax
mov ah,9
mov dx,offset NotEnglishMessage
int 21h
mov ah,4ch
int 21h
end

Compile with masm and run.

[BigDave]

What would be the interest in a proxy that would log the PR of the pages that you surf?

You would still have to surf all the pages that you care about, but at least you wouldn't have to write it all down. It should also keep you within google's TOS, as you would still be manually surfing the pages. But if GoogleGuy says don't do it, then I won't.

Of course it might be a nice addition to the toolbar to have a logging feature that you could turn on. It could tell you the PR and number of backlinks, but you would still have to surf manually