MXNA is back up

mikechambers May 5th, 2008

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.

12 Responses to “MXNA is back up”

  1. # German Baueron 05 May 2008 at 10:47 pm

    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…

  2. # mikechamberson 05 May 2008 at 11:07 pm

    >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

  3. # WinnieThePooon 06 May 2008 at 12:09 am

    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.

  4. # noubaon 06 May 2008 at 1:47 am

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

  5. # Joshua Mostafaon 06 May 2008 at 6:57 am

    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 …)

  6. # Joelon 06 May 2008 at 6:58 am

    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!

  7. # cisnkyon 06 May 2008 at 7:26 am

    Where do we ping once we have made post?

  8. # Bartek Drozdzon 06 May 2008 at 9:50 am

    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.

  9. # ALAGESAN THIAGARAJANon 08 May 2008 at 5:23 am

    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

  10. # mikechamberson 09 May 2008 at 7:39 am

    >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

  11. # Chris Charltonon 11 May 2008 at 7:00 pm

    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? :)

  12. # Chris Charltonon 07 Jun 2008 at 11:36 pm

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

Trackback URI | Comments RSS

Leave a Reply