Post Reply 
sidki's config set: 2005-06-09
May. 19, 2005, 06:13 PM
Post: #241
 
ProxRocks Wrote:edit:  ps - apparently, a LOT of people spell "it" as 'FireFox' and Mozilla got so "tired" of it that they put a tidbit on their website regarding proper spelling...  I didn't mean to offend by bringing it up...  just passing along "the word"...
GUILTY as charged --- and I promise to try hard to never repeat that error again. [beatdown]

However, ProxRocks --- I still do not like Norton AntiVirus or Norton Internet Security because either are the greatest resource HOGS on earth --- take that you Norton addict. Big Teeth

But I do LIKE Microsoft Internet Explorer because its far FAR far superior to any other browser out there for the things that I do :P Plus sidki's config and IE working to-gether under Proxo -- WOW!

Golly, I hope that my love for IE doe not sour sidki otherwise I may have to switch to Firefox. Hail
Add Thank You Quote this message in a reply
May. 19, 2005, 06:50 PM
Post: #242
 
I can't post there with IE6 anyway, even if i clear cache and put Prox into bypass mode...

edit: Nah, checking for config bugs in IE is fine by me, as long as there *is* something to fix.

sidki
Add Thank You Quote this message in a reply
May. 19, 2005, 06:56 PM
Post: #243
 
sidki goes the extra mile to not only ensure that his Fx works, but that "our IE" and Opera works as well... he may check more, for all I know...

well, "our IE" in a matter of speaking...
I use Sleipnir - a 'front end' to IE that has the ability to use the GECKO engine... (although I've disabled that for now - the last THREE (to the best of my knowledge) BROWSER "security issues" [most recent being ~5/11/05] that have gone public are Fx-related, not IE-related...)

and no, sidki won't force you to use "the dead fox"...
Add Thank You Quote this message in a reply
May. 19, 2005, 06:59 PM
Post: #244
 
ps - Fx is at 1.0.4... i keep the latest around for 'when' i do switch Sleipnir over to the alternate engine...
Add Thank You Quote this message in a reply
May. 19, 2005, 08:32 PM
Post: #245
 
sidki3003 Wrote:I can't post there with IE6 anyway, even if i clear cache and put Prox into bypass mode...

edit: Nah, checking for config bugs in IE is fine by me, as long as there *is* something to fix.
sidki, with your sidki_2005-04-02.ptron config I have no problems posting on the RB board using IE .... the posting problem only surfaced with the beta config .... so I do suspect that the beta requires a fix and only your genius can solve that! Hail Big Teeth
Add Thank You Quote this message in a reply
May. 19, 2005, 08:48 PM
Post: #246
 
Did you happen to make any changes to IncludeExclude-U on the 4/2/05 that may have not been carried over to the beta?

Just stabbing in the dark and all...
Add Thank You Quote this message in a reply
May. 19, 2005, 09:17 PM
Post: #247
 
Quote:Did you happen to make any changes to IncludeExclude-U on the 4/2/05 that may have not been carried over to the beta?
The only files I touched were the CookieValues.ptxt and Bypass List.txt.

In CookieValues.ptxt I only made changes that sidki makes mention of in the docs having to do with my IP address and FQDN.

Anyway I have reverted back to the sidki_2005-04-02.ptron config until sidki finds out what is wrong.
Add Thank You Quote this message in a reply
May. 19, 2005, 10:29 PM
Post: #248
 
Probably i won't find out. The problem is the POST URL.

Good:
Code:
POST /mboard/post.cgi HTTP/1.1
Bad:
Code:
POST //mboard/post.cgi HTTP/1.1

I don't know why, but it seems that i get the bad one randomly. The POST URL is declared with...
Code:
<form action=post.cgi method=post>
...and i see no filters that could interfere here.

If the 4/2 config is working there for you, good. If it's a problem with the beta, then adding...
Code:
ragingbull.lycos.com/mboard/(edit|post)
...or similar to the bypass list would be another option.

I guess that's all i can say regarding this issue.

sidki
Add Thank You Quote this message in a reply
May. 20, 2005, 03:59 AM
Post: #249
 
sidki,

re the CC filter could the url match field be changed to include search results
eg. http://castlecops.com/postlite61905-statistics.html

would this do ?
Code:
$TYPE(htm)castlecops.com/(forum-cat14|c14-|(check|f(orumx+|)|p(o+st(lite|p|s|x|)|)|t)[0-9]|modules.php\?name\=)
Add Thank You Quote this message in a reply
May. 20, 2005, 09:14 AM
Post: #250
 
That should work without problem. I wasn't aware of this URL type - CC filter posted here edited accordingly.

Thanks for the update.

sidki
Add Thank You Quote this message in a reply
May. 20, 2005, 12:48 PM
Post: #251
 
sidki3003 Wrote:
Code:
ragingbull.lycos.com/mboard/(edit|post)
Thanks sidki, adding ragingbull.lycos.com/mboard/(edit|post) to my Bypass list enabled posting on the RB board with the beta config. [rolleyes]
Add Thank You Quote this message in a reply
May. 20, 2005, 02:47 PM
Post: #252
 
Good news Smile!
Add Thank You Quote this message in a reply
May. 23, 2005, 05:25 PM
Post: #253
 
Hi Sidki:

I'm trying your lastest NAOKO 4.5 CONFIG -- SIDKI 2005-05-19 and must say the
speed improvement is awesome Big Teeth

The log window is more clear now and favicon solution is cool too.

good job man!!! Wink

Now a little request :P

Is about the display kill filter.

Could the display be smaller??

Try to explain it.

When I enable it lines like "&#8593;Link: AdD melodiasmoviles 300x50" break the page layout
and some pages don't return to the original when dissable.

Will be great if it only display the first part "&#8593;Link" and the rest in a tooltip like the bottom toolbar

Thank to share your config with us !!! Hail

There is not dead wich can eternal lie. Yet with strange aeons even death may die.
Add Thank You Quote this message in a reply
May. 23, 2005, 05:51 PM
Post: #254
 
The "&#8593;Link: AdD melodiasmoviles 300x50" is all relevant info...

The AdD tells you that an ad was blocked based on Domain (Dimension?)...
The ad was coming from melodiasmoviles...
The dimensions of said ad is 300x50...

Only the "&#8593;Link" part is an actual 'link'...
The rest are 'details' as to why the content was removed/blocked...


The 'display kills' filter is more for debug purposes, not for plain ol' surfing away...
You should EXPECT layout breakage in 'debug mode' - and the 'display kills' is basically a "subset" of 'debug mode'...


Hope that helps...
Add Thank You Quote this message in a reply
May. 23, 2005, 06:40 PM
Post: #255
 
I know it is relevant information, and is very usefull...

I only think that tooltip could give the same information without break the page.
With this solution the display kill could be allways enable or not...one personal decision [rolleyes]

For me would be very usefull enable it for normal surfing without "collateral damages" Big Teeth

but only a suggestion, If it's not possible I can't live without it :P

There is not dead wich can eternal lie. Yet with strange aeons even death may die.
Add Thank You Quote this message in a reply
Post Reply 


Forum Jump: