On the technology behind UbuntuOne: iFolder, mono and all that jazz…
Well… keeping myself to the technical side of things. I know the following about UbuntuOne:
- It is one week ago I heard about it for the first time after blogging about iFolder, weird eh?
- I found the O’reilly UbuntuOne link after googling Ubuntu One. Comments on blog posts rock!
- A lot of people have been ranting about it, and others just discussing it
- Too many blogposts, bugs and mailing list threads about it for me to link to any of them. I am actually kind of done with that discussion. Business is business! Freedom is freedom!
- The client side seems to be free software and based in mono (since it seems to use the iFolder client code base, although this might be wrong as this mono assumption is based on a comment on my blog.
- I like the idea of having iFolder or part of it at least in Ubuntu as I have expressed in previous entries since I dream of dropping that box in my own server or servers, since simias, the iFolder server side, actually might even support p2p tech now
So now, let’s wait and see how people start using the mono argument against UbuntuOne (even if it ends up being wrong)… People have too much time available for ranting.
Meanwhile those interested or involved on the technology behind UbuntuOne (client and cloud) please drop a comment and let us all know more. I want to know it all. Thanks in advance! 🙂
And yes, I got an invite. Yes, I have signed up for the service. Yes, it rocks! Yes, I still want my own server to do the same (or similar) thing.