some while back i inserted an openoffice file into the wuala datastore.
somewhen later i edited the file with openoffice. then saved it inside openoffice. the file in the wuala data store has the new content and changes. but the timestamp in the wuala gui (win32) still shows the original filedates and timestamps for both inserted and last modified.
as you may or may not be capable of reproducing/following, the uptime graph of an avergae wuala user will roughly follow a y=1/(x+1)+10 shaped graph with asymptote at 100. so all those very dedicated sharers of storage can never range up to the 99.9% uptime they achieve since there is 1 month of presumed 10% online time. This does not really seam very fair in my eyes. aditionally, if someone has build up one year of 99% uptime and then goes on a vacation, he will 1. take an incredible amount of time to restore his 99% and 2. if he permanently has to take his server offline (for whatever reason), he will continue to get huge amounts of space while not sharing for very long. (significantly longer than a year).
I think it would be smarter to make the long-time average of maybe 2-4 month so that the online-time is only relatively temporarily influenced and users which stop sharing din't get humongous amounts of storage for such an extended period of time.