Mike Chambers

code = joy

MXNA is back up

with 12 comments

New site and url is http://feeds.adobe.com. Redirects for old urls at (weblogs.macromedia.com) are not all in place yet.

Christian has all of the info.

Written by mikechambers

May 5th, 2008 at 8:39 pm

Posted in General

« FlashCommand for OS X updated to work with Flash CS3
Heading to Europe to Speak on AIR and Flex »

12 Responses to 'MXNA is back up'

Subscribe to comments with RSS or TrackBack to 'MXNA is back up'.

  1. Why was it even down to begin with? For a company as large and tech-savvy as Adobe I expect a PR machine to be cranking 24/7…

    German Bauer

    5 May 08 at 10:47 pm

  2. >Why was it even down to begin with?

    http://www.mikechambers.com/blog/2008/04/29/update-on-mxna-or-what-the-is-going-on/

    mike chambers

    mesh@adobe.com

    mikechambers

    5 May 08 at 11:07 pm

  3. Sure, every failure has its reasons.
    But still I have to second the first poster: we can expect Adobe to do much better than this.

    WinnieThePoo

    6 May 08 at 12:09 am

  4. Very good news. But they have not added my native (Ukrainian) language yet

    nouba

    6 May 08 at 1:47 am

  5. Excellent news. I hesitate to add to the chorus of whining in these comments, but .. any idea why my blog posts are no longer being aggregated? (I’ve waited, I’ve pinged …)

    Joshua Mostafa

    6 May 08 at 6:57 am

  6. Awesome. It performs a lot better now, for certain. I didn’t realize how much I used this resource until it was gone.

    Thanks mesh!

    Joel

    6 May 08 at 6:58 am

  7. Where do we ping once we have made post?

    cisnky

    6 May 08 at 7:26 am

  8. Great to see MXNA back, and the performance now is so much better!

    However, I have a problem with my feed (it is listed as ATOM not RSS a thus it is not parsed correctly). If now you guys are a little less busy, could you take a look at this? Thanks a lot.

    Bartek Drozdz

    6 May 08 at 9:50 am

  9. There is still some problem…

    I get the following error quite often

    Header Length too Large
    The requested resource
    /index.cfm
    does not allow request data with GET requests, or the amount of data provided in the request exceeds the capacity limit.

    I have to kill all browser instances and retstart after this .. else the problem persists
    though it does reappear shortly

    Thanks
    Thiagu

    ALAGESAN THIAGARAJAN

    8 May 08 at 5:23 am

  10. >Header Length too Large

    Yeah. This has been fixed. See:

    http://weblogs.macromedia.com/cantrell/archives/2008/05/adobe_feeds_upd.html

    mike chambers

    mesh@adobe.com

    mikechambers

    9 May 08 at 7:39 am

  11. Cool. Any chance we’ll see an update to the Macromedia News Firefox plug-in? Maybe it’ll go 1.0 with feeds.adobe.com? :)

    Chris Charlton

    11 May 08 at 7:00 pm

  12. markme.com’s Firefox extension was taken offline. :(

    Chris Charlton

    7 Jun 08 at 11:36 pm

Leave a Reply