There are some capacity problems with the feed reader occurring intermittently. I will be working to put a fix in, but you may witness some problems here and there. So sorry for the inconvenience.
So the feed crawler problems have been solved and I have put the site back up in a demo location for testing purposes. If you are reading this, feel free to try it out on
Since its ‘beta’, holding off reblogging / reposting elsewhere would be appreciated.
For those of you who know what it was, I have removed the badge blurb in the About section for now. It wasn’t used very heavily and I am trying to whittle rososo down to its bare minimum in an effort to ease the transition to a different code framework. When this transition is succuessfully made, I hope to start rolling out some new features.
Now added to the About section is a shameless grovel for Paypal donations. In addition to fronting the hosting costs, I have already and will continue to devote a fair amount of my personal time to maintaining and improving the site. Anything would be appreciated, but of course not expected.
Please let me know any problems you encounter or feedback you may wish to provide at email@example.com.
I hope to be rolling it out to rososo.com very soon.
Thank you all for your patience and interest in Rososo. And thank you Kyle for all your help with the crawler rewrite.
The crawler is trying to conserve as much bandwidth as possible and Marco’s verbose description field is throwing this effort off…
It’s clear this is being dumped from the Tumblr ‘Description’ field, but It’s also got his google analytics tracking code buried within which seems superfluous. Just sayin’.
I’ve managed to create an entirely new, lean crawler however testing it has proved tricky. I’m juggling this work with paying work so its unfortunately taking a back seat to that at the moment.
Happy New Decade all.
So sorry for the long downtime and associated, unacceptable radio silence on my part. We are turning over a new leaf here at Rososo and hope to be up and running soon.
A bit of background on the crash:
Rososo has a crawler that has to go check your feeds every X minutes to find out when they have last updated. To do this, the previous crawl method was relying on 3rd party tools to fetch the entire feed and parse for a date changed.
As Rososo grew, the number of feeds did as well and this old method was consuming TONS of bandwidth just to read out a single date.
This method has been entirely scrapped and a new feed reader is being written from scratch. It will be lean and mean and hopefully will allowed for continued growth of the feed base.
Stay tuned. I will try to keep a pulse here from now on.
Thank you for your continued interest in Rososo.
I am currently trying to get to the bottom of a mysterious cron job problem (a cron job is the thing that runs automatically in the background to keep the feed updates current) .
Until I resolve it your feeds may update sporadically - I am sorry for the inconvenience.
A major change to the feed crawler was just pushed out. Those of you who have written in to ask why some feeds were not being reported as updated should hopefully see many, if not all of them accurately displayed now.
The new crawler has 3 ways to try and get a feed and its latest update. Unfortunately there are some poorly formed feeds out there that do not contain a publish date and consequently cannot be crawled by Rososo.
Thanks to all of you for the reports, please continue to let me know if any feeds are not updating. I will do what I can to try and make them work.