Threaded Mode | Linear Mode

ProxoDent · (This post was last modified: Nov. 16, 2009 06:36 PM by ProxoDent.)

(Nov. 15, 2009 10:43 PM)sidki3003 Wrote: ... i was actually hoping that the plethora of posted bypasses could be trimmed down to the essentials.

<snip>

For everything else there is the user exceptions list.

When I first began posting the bypasses for Live.com, I really envisioned leaving them as strictly user exceptions.

But, if you'd like to include a few that might pass your criteria, I'd suggest the following set of three exceptions as it fixes a lot of the functionality without overburdening the Exceptions list (the two e-mail-related ones really must be included as a pair if included at all):

Code:

# General site issues:

# Fix broken links caused by URL untangler (site is almost completely unnavigable otherwise); and 

# Fix  embedded 'bottom' display which otherwise is presented at BOTH the top and bottom of the site's pages

[^/]++.live.com/&(^([^/]++mail.live.com/mail/*Inbox) )$SET(0=a_noprint.a_rdlink.)

# E-mail issues:

# Fix inability to read e-mail messages

[^/]++mail.live.com/mail/*InBox    $SET(0=a_adscr.a_noprint.a_rdlink.)

# Prevent 'loading' message from hanging when opening e-mail module

[^.]+.hotmail.com/mail/&gfx[0-9]  $SET(1=adkey_j:0.)

-- Side-issues and questions: ------

I used 'a_adscr' in the exception:

Code:

[^/]++mail.live.com/mail/*InBox    $SET(0=a_adscr.a_noprint.a_rdlink.)

when 'adkey_j' works as well. I'd generally like to use the method that applies the most restrictive filtering while still allowing things to work, but in this case I couldn't easily make up my mind. Any thoughts?

Also, for my personal use, I have abandoned the two e-mail exceptions recommended above in favor of these items placed in AdKeys-J.ptxt:

Code:

~adsToFire$TST(uDom=live.com|hotmail.com)&$TST(uPath=/mail/*)

~adsMinActions$TST(uDom=live.com|hotmail.com)&$TST(uPath=/mail/*)

~ads$TST(uHost=gfx[0-9].hotmail.com)&$TST(uPath=/mail/*)

I do not see that this method gets used much (if at all), but it seems to narrow the culprits down nicely without having to broadly bypass the entire AdKeys-J.ptxt file. Any thoughts here as well?