Back to my page

Blog

Some issues with Facebook…


EDIT : Everything is now back to normal, Facebook and Netvibes are again working hand in hand without a glitch.

These past few days, some of our users have been experiencing difficulties connecting their Netvibes dashboard with Facebook. These issues include: signing up on Netvibes via Facebook Connect, adding a Facebook widget on a Netvibes dashboard and posting Netvibes links on a Facebook wall.

We are aware of the situation and are working closely with the Facebook teams to find a solution as quickly as possible.

We will of course keep you informed of any progress made towards a resolution of these issues. Thank you for your understanding.

Related posts:

  1. Facebook Meet Netvibes: Netvibes Introduces the Facebook Widget
  2. Netvibes now integrates Facebook Connect
  3. Facebook “Like” button now available on Netvibes
  4. Netvibes Introduces New Drag-and-Follow Facebook, MySpace and Twitter Widget
  5. Netvibes Announces Integration with Facebook Connect, Powering Personalized News Sharing for Millions of Facebook Users
  6. New Facebook Search & Compare Trends
  7. New Facebook Profile App for Brands & Businesses

Tags: , , , , , ,

This entry was posted on Monday, May 2nd, 2011 at 16:11 and is filed under QoS. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

Share/Save/Bookmark

4 Responses to “Some issues with Facebook…”

  1. #1 | Pablo_a_n | May 4th, 2011 at 08:42

    my flickr widgets are not loading, i have 10 in one tab and only 2 or 3 of them load. this is happening for a month. any solution?

  2. #2 | Pablo_a_n | May 5th, 2011 at 08:37

    today the flickr widgets started loading, did you do something or is it just a coincidence?

  3. #3 | Nick | May 13th, 2011 at 14:07

     The green issue seems sensible .. no point in making calls to your servers if the tab is hidden for a while. However, it does add an extra click to the experience, could it not wait for a mouse move?

  4. #4 | 218geek | May 23rd, 2011 at 10:03

    I still had that issue recently. Could that be cache or something?