Today I am going to move the website to a new server as well as push updated versions of several of the back-room components into production.

Those of you already on the service (Thanks!) should notice nothing more than faster response from the website and less ‘wonkiness’ in the feeds.

The biggest visible change is the addition of ‘activation keys’. Activation keys make it much simpler to add a frame to FrameAlbum service.  These keys will be displayed on frames that connect to the FrameAlbum service but are not yet ‘owned’ by a registered user.  This replaces the image that included the ‘productID’ and ‘frameID’ values.  While these are very useful to me they are not so useful to the average user.

I’ve noticed that many folks that have registered for the service have not added any channels to their frames.  I accept that the website doesn’t exactly do a great job explaining how you go about getting pictures onto your frame.  I’m an engineer, not a user interface designer (as if that wasn’t painfully obvious to anyone who has tried to use the website 😉 ) – it makes perfect sense to me!  But, obviously, not to everyone.

Beginning today if your frame connects to the service but doesn’t have any channels programmed you will receive a message to visit the site and add channels. This is a very small step towards helping folks use the service.  I have a long way to go but at least you won’t have a blank frame and no idea why it is blank.

Shhhh. Don’t tell anyone but assuming all goes well today, I’ll be releasing the next batch of beta invites.  😉

Thanks for your support!

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!

I’m running the FrameAlbum service on a very modest server.  I limited all the channels to a maximum of 100 photos to reduce the load on the server.

I’ve moved parts of the service to a new, more capable server.  I’ve increased the limit to 200 photos to see how this new machine performs.  Assuming it performs well I’ll bump it up again in the near future.

Enjoy!