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.
While Irene was busy stripping the leaves from my trees I was working on the feed generator. Somewhere along the way I managed to change it in a way that my borrowed Toshiba frame does not like — it reports ‘Connect to online service failed’ errors. <sigh>
Anyone else getting that on your Toshiba frame? (My Kodak frame is working just fine.)
I’m testing a new channel type to add weather radar images to your frame feeds. It isn’t ready for integration into the website but considering the weather on the ‘right coast’ I thought I would make this offer:
If you would like to have a weather radar image added to your frame drop me an email at framealbum at gmail dot com with your FrameAlbum username and your ZIP code. I’ll manually add it to your channels.
Those of you using the FrameAlbum DNS server to redirect your frame may have encountered a bit of trouble today. In this context ‘a bit of trouble’ means total failure of your frame to retrieve the feed from the FrameAlbum service. ;-( It may have exhitibed itself as a ‘DNS ERR; RSS invalid’ error, or simply ‘unable to contact service’ message.
I am in the process of building greater redundancy into the system and inadvertently mis-typed a password used by the DNS server to access the database server. We in the business refer to this as a ‘fat finger’ error. 😉
The issue has been resolved and the DNS server is back to normal operation.
I pushed some new code to the FrameAlbum website today. This is a small update to improve the messaging on the status of a channel. It will now inform you if the system was unable to find a matching username on Flickr/PicasaWeb. It will also tell you how many photos were added to a channel during the last update cycle.
As always, feedback is appreciated.
Digital Media and whatever else flows through my head…
Cookie Consent
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server