Slashdot Mirror


AOL Blocks Links from LiveJournal

Evan Martin writes "LiveJournal.com is an open-source weblog site with over a million users, some of whom use AOL. Last week, AOL began blocking all HTTP requests with "www.livejournal.com" Referer headers. This is a common practice by image hosting sites to prevent off-site linking of their images and 'bandwidth theft'. However, in AOL's case, they're blocking everything, not just images, effectively breaking all links to any AOL member's site--but only from LiveJournal. To be clear: nobody on LiveJournal can even make a link to any AOL member site without getting a '404 Not Found' error. We've also heard reports of the same thing happening on AOL properties (Netscape, Compuserve). This concerns us because we have to deal with the support requests: it worked in the past for our users, and it continues to work for other sites, so our users think it's our fault."

Martin continues: "We've tried to contact AOL three different ways, all without success. We've also told our users to contact their tech support. At one point, an AOL staffer pointed out that FTP access still worked (which is probably because FTP has no "Referrer" concept), and so, as an interim fix, we're rewriting all HTTP URLs to use FTP on the AOL properties where that works instead. This means that users can again host their images on the AOL webspace they're paying for, but more importantly, it means they can simply link to their webpage.

We wouldn't be so upset if they were simply blocking images. Bandwidth use is a valid concern, after all, and we even provide step-by-step instructions for people to configure their webservers to prevent image "theft". However, because they're blocking all access, including regular links, this looks like it's either a mistake, or something more insidious (the conspiracy theorists have pointed out that AOL has just launched their own competing weblog product, also based on "journals").

Although CI Host sued AOL recently for being blocked, we really don't want to do that. We still suspect that this was all just a mistake, and hopefully, by making this public, we'll manage to get their attention, since all our previous attempts have failed."

12 of 396 comments (clear)

  1. Will this be what kills the referer header? by Anonymous Coward · · Score: 5, Insightful

    It's optional, so browsers don't need to send it. Mozilla/Firebird/etc (and Opera) can be easily modified to not send one, and the Google Toolbar could probably support blocking them, too (since IE isn't being updated). AOL is a big enough presence that this could have a significant impact on peoples' browsing.

  2. AOL and Blogs by zangdesign · · Score: 5, Insightful

    Actually, you may want to investigate whether or not AOL has gone live with their blog offering ( article here). If so, it may be viewed as an intentional act.

    --
    To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
  3. Well played... by tempest303 · · Score: 5, Insightful

    This is a really level-headed, well played move on LJ's part - primarily because they're following the universal principle of assuming stupidity before malice. ;)

  4. Why is it... by pongo000 · · Score: 5, Insightful

    ...that people bend over backwards to accomodate companies with draconian policies like AOL? If I were running an ISP, the loss of a few customers because they suddenly discovered they could no longer send e-mail to AOL customers through no fault of my own would most likely be offset by new customers who understand that the earth does not revolve around AOL. So they're blocking incoming HTTP traffic based on referrer? Are there not more pressing problems to attend to rather than trying to please the AOL gods?

    I'm not saying AOL is in the right. I'm simply saying that AOL (and companies like them) should be made to lie in the bed they make for themselves. Only when AOL customers start to be inconvenienced by AOL's own policies (rather than third parties patching together "workarounds" in a misguided attempt to protect the integrity of AOL) will they realize what AOL is up to...

  5. Re:F12 by randyest · · Score: 4, Insightful

    Well, if I were an AOL user right now (quite a stretch to imagine, I'm afraid), I'd be loving to check my contract to see if it provides for such limitations on user personal space. If not, I'd call to complain (I'd probably do that anyway, right before I called my new ISP). I know that my cable modem "free" hosted space included has a very specific contract that limits the monthly bandwidth usage, but does not mention anything about blocking access for links or clicks from other domains. I wouldn't be happy if they suddenly started returning 404 Page Not Found errors when anyone linked or clicked from foo.com.

    Maybe they can claim technical difficulties if called on it, or maybe the contract does let them yank their users around like this. I don't know. Does anyone here use AOL and will admit it long enogh to post a link or copy of the appropriate contract?

    Of course, there's the tinfoil-hat theory that AOL is planning to start thier own blogging service and wants to drag LiveJournal down from it's #1 spot a bit. Seems like a particularly blatant and non-clever way to do this though, or maybe that's the "beauty" of the whole ingenious plot? ;)

    Finally, I'm going to hope the /. editors checked this out somehow. I don't have AOL space. Can anyone else verify this is true and not just some EBKAC or hoax?

    --
    everything in moderation
  6. Re:Wait a minute by isorox · · Score: 5, Insightful

    My Libertarian side says AOL are free to do whatever the hell they want, it's their server. If you ask the AOL server for a page and it send you the goatse man, thats fine, thats their right. Vote with your wallet and dont buy their service.

    My more centrist side says this could be abusing a monopoly (or at least dominant position), OK they dont have a microsoft style monopoly, but they do have the monopoly over Joe Stupid.

    My cynical side says who gives a flying fuck

  7. Re:Wait a minute by infornogr · · Score: 4, Insightful

    I regret to inform you that all Slashdot comments are not posted by the same person. Not only are there different people on Slashdot, some of them have different opinions. It's a shocking revelation, I know.

  8. Referrer Header by Mrs.+Grundy · · Score: 4, Insightful

    I, for one, like the referer heading. It is useful to see where traffic is coming from and it really stinks that AOL is going to encourage people to mess with it, remove it, or spoof it. This will be the ONLY result of AOL's action. They may get a short break from livejournal links but people will work around it. The internet is about linking after all. If AOL want's to invent their own thing with their own rules they should make their own little private net like they used to have and they can remain one tight, happy, cloistered little clique. Of course if the referer header becomes useless maybe it would be a good opportunity to fix one of the most influential spelling errors in recent time and start using the refeRRer header instead.

  9. Re:Wait a minute by danielsfca2 · · Score: 5, Insightful
    Deep linking seems to be a totally different issue here. Your average AOL user who wants to place a link on their LiveJournal to "members.aol.com/aoluser" would derive little value from a link to "www.aol.com" or even "members.aol.com"!

    This is webspace that AOL gives its users as part of their paid service. When you pay for webspace, the general idea is that it supports these things called hyperlinks. It stands to reason that you or anyone else should be allowed to link to your website from any other website. Any deviation from this traditional behavior should be documented in their terms of service, and is very shortsighted and/or stupid, as it threatens the very nature of the WWW, much like restrictions/penalties on linking to sites that are deemed undesirable.

  10. Re:Quick fix for HREFs viewed by MSIE by jamie · · Score: 4, Insightful
    Dear God in heaven, anyone who does this is nuts.

    Load a javascript off the website of someone else you don't trust? Cmon now... let's just invite a stranger into your home to watch all your websurfing, or post the contents of your cookie file to your LJ.

    Anthony, I'm sure you're a nice guy and all, but would you trust a random stranger's javascript on every one of your webpages?

    (The space added to the URL you pasted in is added to every long word at the 50-character mark, to make sure idiots can't break your browser rendering by typing very long words into their comments.)

  11. Re:Solution: by carsont · · Score: 4, Insightful
    Don't use an ISP that is "broken". AOL has little to recommend it.


    Well, for one thing, AOL has been "broken" in many ways for many years, and yet they still have an enormous and loyal user base. So does Windows, for that matter.

    The problem is that for the average AOL user, who to put it bluntly is probably both too stupid to figure this out on their own and too lazy to read LiveJournal's explanation, it will appear just as likely that LiveJournal is "broken", not AOL. They will squeal "OMG WTF IT DONT WORK!!!!!1!!!11!!! :-(" and leap into the open arms of AOL's competing service. Whether or not AOL planned it this way is irrelevant.

    This is how the fragile and complex interoperability between pieces of computer software, which is opaque to most users, can subvert the workings of the free marketplace; if company A sabotages their product so that it won't work with company B's product, it is easy for customers to be fooled into blaming company B.

    Microsoft did this with their implementation of Java, and probably many other times. I doubt if this is some deliberate strategy on AOL's part, but the result will probably be the same regardless.
    --

    Ubi dubium, ibi libertas.
  12. Leave them feedback by BrynM · · Score: 4, Insightful
    You can leave them feedback regarding this decision at the AOL Feedback Page. Let them know that this decision will impact more than they expect it will and that you are disappointed with their actions. You don't have to be a customer. Most of us are technology experts who have influence on their potential and existing customer base. I've included my submission as an example, but please write your own.
    I find it disappointing that you are blocking content linked from such a popular site as LiveJournal based on referrer headers (see this slashdot discussion: http://slashdot.org/article.pl?sid=03/08/29/205724 2&mode=thread&tid=120&tid=187&tid=96&tid=9 9). I have recommended your services in the past, but that will stop now. Further, I will inform AOL customers whom I have recommended AOL to that their content is not available to sites that AOL seems to disapprove of for no stated reason.

    Changing your policy regarding this may defer my judgement about your "service", but your reputation has been irrecoverably tarnished in my view. Additionally your subsidaries, such as Netscape, will no longer be recommended by me.

    You may be thinking "Who cares? This is someone who isn't even our customer", but I have become the technology "guru" for over 100 people in my personal life and have input on technology decisions at my workplace. What should worry you is that for every peice of feedback you recieve like mine, there are hundreds of technologically literate people who will simply downplay or berate your services and will not do you the professional courtesy of informing you.

    Formerly Respectfully Yours,
    BrynM

    --
    US Democracy:The best person for the job (among These pre-selected choices...)