Update Jagger - Part 2

[Brett_Tabke]

Continued from
[webmasterworld.com...]

[Pico_Train]

Goohoosoft, trademarked already.

[TammyJo]

oooooooo, maaaaan! Why can't we just keep the allinanchor results. They are great on the 66.102.9.104 DC

[edited by: TammyJo at 7:37 pm (utc) on Nov. 4, 2005]

[helenp]

Christina I tried it and I got another url showing up for my domain doing allinanchor,
actually an site with my homepage in an frame,
but honestly donīt know what allinanchor means so donīt know if I should report it.

[jenkers]

hmmmm
sounds like we have a battle already - goohoosoft v yahooogle v microgoohoo.

[steveb]

Wading through the trolling, it is hard to believe anybody is confused unless they are too darn lazy to read Matt's blog.

There are no "pre-Jagger" results.
The datacenters in the 66.102.7.99 group are Jagger1 with a twist added yesterday.
The bulk of the datacenters show Jagger2.
Jagger1 and Jagger two are separate things. Jagger2 is not built on top of Jagger1.
Jagger3 will happen, probably, in the next 72 hours.

I believe Jagger3 was delayed because of the twist added to the Jagger1 results, which was clearly a very positive addition; and because of that batch of horrible results that appeared and was removed earlier this week, which was clearly a halfbaked thing that never propogated.

All datacenters are cooking, but not done.

===

The 66.102.7.99 fix yesterday more or less fixed a site of mine's Sept 22 problems, except for anything in two specific directories... the pages of which show at the very end of an allinurl:example.com site:example.com search. If you have less than 1000 pages perhaps you can observe this phenomenon with any partially healed domain.

[Yippee]

LOL microgoohoo... I love it.

[helenp]

[quote]
steveb said:
The 66.102.7.99 fix yesterday more or less fixed a site of mine's Sept 22 problems, except for anything in two specific directories... the pages of which show at the very end of an allinurl:example.com site:example.com search. If you have less than 1000 pages perhaps you can observe this phenomenon with any partially healed domain. [\quote]

Seems you are correct,
I had an redirection doing allinurl as result number 3, on 66.102.7.99 it is gone, however I canīt see the end, google only allows about 320 and I have 370

[giga]

[webmasterworld.com...]

I posted this earlier and no one replied. All of these datacenters are likely showing jagger 3 results or some brief glimspe of them. Our site was entirely non-existant prior to a few days ago, it suddently popped up in all of the below DCs. We are back on radar and looking strong. Anyone else confirm these centers? BTW according to Googleguys own posts none of the centers he listed for Jagger 1 or 2 are included in this list (I think**... I just came into this discussion very late in the game) :)

64.233.189.104
-gv: 216.239.53.99
-in: 216.239.57.99
-mc: 66.102.7.99
-ab: 216.239.63.104
-in: 216.239.53.104
-mc: 66.102.7.104 JAGGER 1 RESULTS (UPDATE)
www2: 216.239.57.104
-ab: 216.239.57.98
-cw: 216.239.57.105
-mc: 66.102.7.105
-ab: 216.239.57.147
-mc: 66.102.7.147

[JuniorOptimizer]

Giga, I have a number of horses back in the barn on those Data centers. It also shows pages I made in October on brand new sites ranking as well.

[Phil_AM]

Giga,

I believe most of those are Jagger 1 with "the twist" from yesterday morning. But who the heck really knows at this point.

I'm guessing Monday we'll start to see some stability, but as far as what going on right now, Jagger 2 and the Jagger 1 w/ "the twist" show pretty different results. That's if these DC's are Jagger 1 and 2 and J3 has not showed up yet.

All I know is that one of the two updates (J1 or J2) seems to have fixed a glitch that wiped out some of the 9/22 casualties.