[JDEV] How is aol blocking ?

[Bill Ataras]

How is aol blocking? I can see blocking everything from jabber.com. But
blocking 100's or 1000's of IP addresses? No. So they're changing the
protocol. But how can they do this such that their legit aim client survives
and libfaim dies? Are they sending native code to execute in their aim
client? How can they tell libfaim is talking to them and not their own aim
client?



> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> Jens Alfke
> Sent: Tuesday, March 27, 2001 2:04 PM
> To: jdev at jabber.org
> Subject: Re: [JDEV] why the new version of the AIM Transport is
> stillbeing rejected by AOL?
>
>
> Dixon Canario <dixtigger at yahoo.com> wrote:
>
> > Anyone Knows why the new version of the AIM Transport is
> > sending this message isn't this suppose to be fixed or is
> > aol now doing to Jabber.org the same that they did to
> > Odigo.com ???
>
> The friendly folks at AOL late last week started blocking libfaim (used in
> gaim and Fire as well as presumably the Jabber AIM transport).
>
> Top of tree gaim sources (at sourceforge.net) generally have the latest
> workarounds. You'll have to dig into the oscar subtree, most
> likely. Last I
> heard there was a new block added yesterday but as of this
> morning gaim had
> a workaround. This tit-for-tat cycle is likely to continue since AOL has
> infinite resources to throw at it and no more reason to be interested in
> openness (courtesy of the FCC).
>
> "ALL YOUR BUDDY ARE BELONG TO US"  --AOL
>
> --Jens
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>
>