Where very sorry…
Our main server suffered from a power-dip. The datacenter where it is hosted failed to provide continuous backup power so it went offline around 16:00 (GMT +1).
We had to do some repair work so it took longer than expected before it was up again.
All systems are back online now.
It seems that some feeds didn’t get through. We’ve updated the parsing capabilities to be even more forgiving to non-rfc compliant feeds!
One of the things we’re busy on is the wap version of Rasasa. Right now we’re finished with creating access to your personal Rasasa Masterfeed. You can check how it works with the Wapsilon online wap-browser-emulator. Expect more to come… (control your Rasasa account through wap, receive wap-push messages instead of partial-text SMS)
Let me know what you think!
It seems trickmcsneak snatched the first available Alexadex Rasasa shares before we could get to it…
But as he/she is a member of the TechCrunch group and they’ve explained their strategy I have good hope there might be more shares available soon 
We’ve changed our favicon to 
instead of the mobile thing. The mobile thing was too much aimed at only one end-point of your newsfeeds. So now it’s a “… a little birjdee toold mee …” thing. It will tell you what’s up, where ever you are!
Some people already noticed that Rasasa can flll your inbox quite rapidly.
We’ve added a mail-frequency-choice-option to the Account settings, from now on you can decide for yourself how often Rasasa can send you an email about newsposts if you’re not online. We’ve set the default to 12 hours.
We’ve started this blog to, well, blog the development of Rasasa.com. As we are just beginning the public Beta stage, there’s lot’s of issues coming up.
We will be trying to update major issues immediately and are keeping feature requests for the Beta2 release at the beginning of june.
