FrameAlbum is a victim of it’s own popularity.  The tiny server I have running the service isn’t up to the task now that there are several hundred people on the service.  This is the reason that some of your frames are reporting ‘invalid RSS feed’ or ‘cannot contact service’ or similar messages.

My bad, sorry about that.

The server I’m using is based on Amazon’s EC2 service.  This matters not to most of you but will be interesting to the .5% of you that are are geeks like me.  The ‘tiny’ instance type is a small fraction of a ‘real machine’ and when someone else on the same physical machine as my instance runs something heavy it takes away from me.  Well, it seems that someone is almost always running something heavy on the same machine as the FrameAlbum service.  As a result, the service is a bit wobbly.   I’ve tried stopping/starting the server a few times to get on a different physical machine but the problem persists.

I’m moving the service to another machine that is not shared.  This will cause the service to be a bit bumpy for the remainder of the day but will result in a much more stable and responsive service.

Thanks for your support and patience!