bhcentral

I plan on testing the waters on byte counting for my cloaks and see if that helps in the ban war.  I load content dynamically so getting the page size is no problem.

The thing I need ideas on are what to put in the comments of the 404 or 500 page I show them (them being anything that isn't a bot or serp ref). 

I thought about putting a generic ToS or Privacy in comments and adjusting size as needed....but that seems like footprint to me.  Technically though, footprint shouldn't be a concern assuming I catch every bot (yeah right)  Applause

Another option I thought of was having a message like "Internal Error Parsing Page @ AKJNSKDJANSA(*S^(*&Y(*&AHSDAS&ApplauseTYA*S&"  and generate it randomly.

Thoughts?  Ideas?

perkiset

BHC -

I'm not sure why you're worried about bytesize if you're passing back a 40x to the (which? Surfer? Engine?)

But that's not the issue...

What kind of delta are we talking about here? A couple K? Perhaps an on-page JS that loads a variable with a "checksum" hex number... obviously a random one. You could even divvy up the number of bytes you need to add into several lines of:

var bytecode += '0aec1b2424001a';

and such.

Another option might be to use a hidden div with randomized tables. I did this for a while and it worked great. Randomize the number of rows, randomize the number of cells, randomize the amount of "hex chars" in each cell until you get what you need. That'd pass a DOM test nicely as well...

bhcentral

So avoid using comments? 

The reason I want to adjust size on 404 / 500 pages is to get past the google toolber checksum...not that I am sure that this is really used for anything....but just in case.

I'm confident my redirect is only occuring on real searchers.  But if I am showing a 404 and 500 to everyone else but a bot and they have the toolbar that could easily red flag the site.

Not worried about hand jobs either...nothing you can really do about those....just wanting to work on my flying under the ban algorithm.

perkiset

Gotcha -

Re. comments: I do not know how the HTML parsers count them - that's the only issue (perhaps). Just like when you compile code, comment lines/blocks are not included in the total lines, I have no idea if comments are counted, although I suspect that they are in the first analysis for a simple byte count.

Excellent test to perform - and a comment would actually be the easist of all to spoof size-wise. So I guess I am not saying to avoid comments, only that I don't know how they'd play out for you. As a cloak strengthening exercise I'd *personally* use another mechanism, but then, I'm a well known irrational paranoid Applause

bhcentral

Since this is just for the benefit of a toolbar I think anything would work.

If they get smarter in the toolbar (omitting empty tables, comments, blah blah) I would think a simple windows IIS compiler error repeated for about every xxxx line of code would look okay:



quote
The page cannot be found
The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.
--------------------------------------------------------------------------------

Please try the following:

Make sure that the Web site address displayed in the address bar of your browser is spelled and formatted correctly.
If you reached this page by clicking a link, contact the Web site administrator to alert them that the link is incorrectly formatted.
Click the Back button to try another link.
HTTP Error 404 - File or directory not found.
Inte

rnet

  Information Services (IIS)

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Please contact:
MySQL error:  database unavalable.  Resource not found at line: 212

MySQL error:  database unavalable.  Resource not found at line: 296

MySQL error:  database unavalable.  Resource not found at line: 345

MySQL error:  database unavalable.  Resource not found at line: 405

MySQL error:  database unavalable.  Resource not found at line: 515




And so on and so forth until you fill the need.  User would probably be fooled and not think anythings up...hey..it's windows Applause

perkiset

Ooooh I like that one... divy up the delta by the size of an error message and add a small line of hex to cover the remainder...

Nice! That's you're bogey I think. You could also add some kind of hexdump information at the end to handle the remainder.

bhcentral

The icing on the cake:

quote
Loaded in 12.12135165468484321 sec.


Adjust the decimal to fill the exact number of bytes  Applause



perkiset

Nice. That's about as straight ahead as it gets!

And think of the awe you will inspire when you can calculate the page dispatch time down to 330 dignificant digits!  Applause

bhcentral

Page loaded in 1.234555555555555555555555553452345832740582348597342085732049857039847502398475 secs

Applause

perkiset

"It's so biiig!"  Applause

bhcentral

dim faketime as int1024


keep getting a compiler error  Applause

perkiset

... you're kidding, right?

bhcentral

no...it keeps giving me some strange "Are you out of your fishing mind" error  Applause


Applause

perkiset

Applause Applause Applause

If only my compiler had such a sense of humor...


Perkiset's Place Home   Politics @ Perkiset's