You apparently kept the promise to fix the server (the "promise" was from the reject text which I don't get now). That "I'm broken but we promise to fix it" message was there a long time, long enough to consider the promise as broken as the server. A more specific message while you were fixing it explaining that you knew about it would have helped.
I am able to connect and sync files. However as I pointed out there was NO logs, no debug information, no way to find out what was causing the problem, so having it work apparently at random just like it failed isn't helpful. I still don't know what happened, if something like it happens again will it be something on my end or yours, or something else entirely. It also appears you require an insecure firefox to do the initial authentication (My extensions turn off the "allow bouncing anywhere else on the net via javascript or http redirects" feature which I had to bypass for your site). I don't see that mentioned anywhere near the top or in the FAQ which leads to more confusion - applets are normally self- contained and this one is not. That still needs to be fixed, even if it just puts up a dialog saying "Firefox will start now and you need to login via launchpad using openID" even if you have already created an account and the rest works. With it taking over the browser (without any warning or explanation), your applet looks like typical Microsoft Windows malware doing something to my computer or browser. So, yes, the server is fixed. Ubuntu One works for now, but the side (and I apologize for the slightly snide) comments still apply. Especially with something completely new, if you are going to do unusual things, or things might not work, it helps to know specifically what it is trying to do when it fails somewhere in the chain, or if you have confirmed server problems, put something on the front page saying so instead of having me and whomever else spend hours trying futile things. -- Can't connect - either web or client https://bugs.launchpad.net/bugs/480449 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
