Shutting down Ubuntu One file services
blog.canonical.com
blog.canonical.com
For a service that we were suppose to be syncing our lives to, that seems like a really abrupt, customer unfriendly ramp-down.
I would have expected something more like:
1. April 1 - no new accounts.
2. May 1 - can no longer add files to your existing account.
3. May - Dec - nagged/reminded constantly to pull your files down.
4. Dec 31 - All accounts closed, data "erased"
5. [BONUS] March '15 - Data actually erased to provide a few months of emergency
recovery for the few folks that didn't know and are emailing frantically that
their family photos are up there.Not that it changes things a lot, but two months is definitely better than one. They probably have data to back their decision.
EDIT: I misread the post, there's not difference. Sorry for the noise.
Disclaimer: not an Ubuntu One user.
Regardless, for an online backup/sync service, I think a very compassionate ramp-down plan is on the order of 6 months with a few secret months of emergency recovery in the cases where people "forgot their child birth pictures were on there!" and the like.
If it wasn't a "backup your life" service, sure, a more aggressive ramp-down is fine... but for a service that tried for a few years to convince you to stick you life in it, I think it's overly aggressive.
I can't imagine their burn rate is _so high_ that it is not something they could have funded for a few extra months.
Anyway, just my opinion... a few of you have pointed out "how long does it take to move your data?" -- sure, if you are paying attention, have a stable/non-metered connection in a 1st world country and are always ontop of things the moment they happen... you are right, a few days maybe.
I am thinking of that small 10-15% of stragglers that miss the emails, miss the announcements and legitimately have important information sitting in One and don't realize it's gone until too late.
I'm pre-emptively feeling compassion for them :)
The biggest cost here is to the Ubuntu reputation. They stand on the promise of LTS releases: with the quick timeline for removal of support from what could be a critical piece of customer infrastructure they signal that they are willing to sacrifice relationships for convenience.
Looks like the last time files were changed was Sept of 2009. Obviously, I haven't used it since then.
The vast majority of the packages in Ubuntu (more notably in the LTS releases) are all custom patched by Ubu-devs. Rather than taking the raw package and pushing it through, they have a semi-opaque method of testing, patching, and then releasing to the greater community.
I've tried several times to get an 'in' so that I could help with the process, but it seems to me like a 'club hangout' where outsiders are slightly discouraged. :(
I don't think we purposely discourage people to participate, though I can understand getting lost in the process can be confusing.
So there's definitely a community and it takes time to learn the rules. But there's lots of ways to get involved and if you take the time to understand the issues and then have ideas on how to improve the processes you'll be listened to - Ubuntu is ultimately a community.
You can find out more on how to contribute on the Wiki http://community.ubuntu.com/contribute/developers/
I think this is an unfortunate perception. There's an active sponsorship queue, and nominated people run shifts to review and accept outside contributions. All contributors need to do is submit a suitable diff, and subscribe the sponsorship team to the bug. See https://wiki.ubuntu.com/SponsorshipProcess for details.
If you are willing, please help!
Where outside contributions tend to fall down (IMHO) is understanding and thus compliance with existing processes. For example, outside contributors tend (again, IMHO) to underestimate the consequence of regression in stable releases. Or they contribute patches that should really go upstream, and underestimate the extra overhead and community harm of independently maintaining these patches just in Ubuntu.
> Rather than taking the raw package and pushing it through...
The reason is the risk of regression. https://wiki.ubuntu.com/StableReleaseUpdates describes both the process you describe, and the rationale for it.
Where upstreams have sufficient QA and release process to sufficiently minimize the regression risk to existing users of a stable release, an exception can be granted so that the updates can just be pushed through: https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExc...
I'll share my story: I help maintain a 3,000+ node Puppet config for a school district, running Ubuntu 12.04 on various laptops/desktops. Part of our config used XFCE's weather widget on a panel. A few months back, the widget stopped working, as the API's url had changed. I had tracked down the issue independently, and even found that newer versions were released for 13.10+, but alas- no backport for 12.04. I tried to investigate how to test and sponsor the package to get it backported for the LTS, but after nearly a day's worth of digging, I gave up.
Conversely, on my Arch tech station, the XFCE widget was updated many times in between, with many bugfixes and other updates.
> The reason is the risk of regression.
I can appreciate it. It makes sense that one would want the software to be as tested and stable as possible.
However, it seems a bit disingenuous to me that the developers of the various software packages are not the 'final say' in the development. Sure, the patches might only affect a specific version of Ubuntu, but as a Developer- I would prefer to fix the issues myself.
I hope that makes sense- I'm not trying to paint Ubuntu's update method in a poor light, I just can't quite grasp the full scope of why it's done that way.
Ubuntu is supposed to integrate and add a QA layer on top of upstream packages. Just pushing any so-called stable release of upstream packages isn't going to improve the situation, even if it might in specific cases.
Personally, I don't see a way out. The very fact that a distro is an agglomeration of independently released packages means that there will be breakages like the ones you describe, because every package has its own concept of stable release, development cycle, feature deprecation, old version support, and so on.
My experiences fixing the resulting brokenness and occasional unbootability is why I first claimed Ubuntu/Debian on my CV.
I think it stems from the 'Linux' way of doing things, which is to give as much information as possible, I like it, but I can see how it's off putting to some people.
There's the icon overlay sure, but not a popup or anything.
As a near 100% RHEL/Fedora user I am always wondering if there is anything but a material difference between apt and yum?
From using Ubuntu extensively a few years ago they seem to have near identical feature set?
Apt/dpkg is also a lot more careful about its treatment of configuration files. Debian packages generally ask questions during preconfigure, build a config file, and then run out of the box. But if you already have a config file it will either be left alone or ask you to resolve the merge.
http://unix.stackexchange.com/questions/634/what-are-the-pro...
dpkg -S /some/file # tells you what package provides that file
dpkg -L some-package # lists all the files provided by a package
apt-get search <regex> # lists all package names matching <regex>It's apt-cache search, and it searches full descriptions, not just package names.
Atleast some of it is momentum from being first. APT was the main reason I jumped ship from Redhat, but that was before yum.
As a dev I still love dpkg-buildpackage way more than rpmbuild.
I'm a proponent of RHEL/Fedora, but still, Ubuntu can upgrade from LTS to bleeding edge fairly easily. Try that with RHEL.
My experience has been to have trouble with both bleeding edges, Fedora or non-LTS Ubuntu. I don't freak out though, as I know the purpose of the bleeding edge is to suffer the bugs so the RHEL/LTS folks of the world don't have to. That said, using a release backward from current for Fedora or non-LTS Ubuntu usually is pretty stable, supposing you're on your game enough to upgrade before repo EOL.
/endrant
Meanwhile, my own experience with the Red Hat family is with CentOS, which is either kept artificially out of date for security reasons ("bleeding edge" is well-named, generally) or else I only ever saw poorly-configured old versions. So I don't know enough to compare it, but I'm comfortable with the Debian family so I'm sticking with Ubuntu.
What is that based on exactly?
I've set my phone camera pics auto sync to all my devices. All my music and photos are backed up with Ubuntu One. When I upgrade my OS version, I sync all important files here. When I switched jobs late last year, my music was instantly available at my new office. When I'm working and I need a file on my Windows machine, I just throw it in Ubuntu One and switch keyboards.
I'm disappointed by this, but not surprised. They haven't been doing anything with the product in a long time.
I had hoped that just meant it was a stable product.
This being said, it did have its warts (for example sometimes when uploading a file the app hung for no reason; there was even one time when I had some files reverted to an older version).
I understand their decision and I think it is better to discontinue a service than to keep it running without improving it. I guess it's time to switch...
What do you mean? I used it for years on both Ubuntu and Fedora, never had an issue.
The web interface gives a progress indication, so why not the native application? It's very very poor.
Ok, so do users really rely so heavily on Ubuntu One? If so, then why do you shut it down? If no, then why do you say they rely on it?
I believe they don't rely on it.
"The Ubuntu One file services will not be included in the upcoming Ubuntu 14.04 LTS release, and the Ubuntu One apps in older versions of Ubuntu and in the Ubuntu, Google, and Apple stores will be updated appropriately. The current services will be unavailable from 1 June 2014; user content will remain available for download until 31 July, at which time it will be deleted."
1.5 months? Really?
From the article:
> Additionally, the free storage wars aren’t a sustainable place for us to be, particularly with other services now regularly offering 25GB-50GB free storage.
In other words, they can't compete with Dropbox, Box, SkyDrive, Google Drive, and whatever flavor of the week is next week. It's a distraction, so they're focusing on making the OS better and getting out of the cloud storage business.
They can probably tell that there are people who rely on it (active usage logs and all that), and to those people this is a Big Deal. But those are also the people that would be underserved by U1 going forward, so it's best if they get out now.
Out of the 4 of our peers you mentioned, two are sizable companies in their own right but are dedicated to their essentially one product, and the other two are products produced by giant mega-corporations that have room for product teams as large as us, Box, and DropBox put together.
It ain't easy, being cloudy.
I wonder what they'll try next.
http://www.networkworld.com/community/blog/linux-profitabili...
Ubuntu has gone for consumers (home users, home servers), where nobody else ever managed to build a profitable and sustainable business in the Linux world.
Do you really find it strange that some users could rely on a service, but that service is also not worth continuing?
>If no, then why do you say they rely on it?
Which is more likely to be wrong?
1) There exist users that rely on Ubuntu One
2) There are absolutely no users that rely on Ubuntu One.
"We will calculate the refund amount from today’s announcement, even though the service will remain available until 1 June and data available for a further two months."
Very respectable.
I'd rant more, but hey this is free software so I'll just switch to another distro.
viva la divergence.
Maybe automatically encrypt and backup all text files in the home directory by default, and for free. Restore encrypted backup from Ubuntu One every time a user does a reinstall or upgrade. Charge users if they want to throw in media files or binaries.
A rather bad track record for software that is there to prevent you from losing data :/
On top of that, also the backup process itself was unbearably slow... I really wanted a backup tool built upon inotify, so now I'm using Crashplan (it's not open source, but at least it works on linux)
Ubuntu is really terrible at that.
The price cuts from Google last week were clearly an offensive move in this space. One of the best ways to refine a market is to run it at sustainable loss and watch those that cannot compete die off. Credit to Canonical for failing fast here. I hope they decide to reassess the situation and provide tooling for a BYOCS[1]-esque abstraction. This'll permit users to roll their data from one cloud storage company to another as they all start dropping off.
As a somewhat related aside: where is amazon in the consumer commodity SaaS world? No email, no calendar, no storage (albeit they do provide mp3 storage). Do they just have no interest in providing these user services?
[1] Bring Your Own Cloud Storage
I wish all companies would open source code they don't use anymore.
I mean it really doesn't cost anything pushing your old code in a github repo or something.
> Additionally, we continue to believe in the Ubuntu One file services, the quality of the code, and the user experience, so will release the code as open source software to give others an opportunity to build on this code to create an open source file syncing platform.
So you might expect that they are (or will be) preparing for an open source code release shortly. A move with class, BTW.
Can anyone explain to me why every cloud drive is using their own proprietary protocols to do the same thing? Why we have to install a different client for each vendor? That's one thing that annoys me greatly, and I'll never use Dropbox as long as its syncing tool is proprietary.
Does anyone else remember when companies were proud that they were the custodians of a file format? Once things went to the internet it seems like that stuff is no longer important to companies.
No. When was that?
Even though cloud syncing is simple enough that dozens of companies have reinvented it, the companies don't feel any obligation (as I personally feel they have) to open up these protocols.
I agree, but I don't agree that they used to. Most formats were and have always been proprietary. Open formats are and were an exception, and they were poorly supported by the industry at large. Yeah, we had Open Document, but the biggest Office suit didn't support them.
Similarly, ownCloud has an open protocol for syncing, but most vendors don't support it, just like they didn't used to support open formats unless they were forced to by their popularity. It's nothing new.
With cloud syncing we have a few open alternatives, you mentioned ownCloud, but there's also git annex, and clearskies (btsync clone).
But those are all community projects. No corporate support. At least in the OpenDocument days you had Sun as the corporate owners.
Why does DropBox not feel some responsibility to step in here, as the industry leader? This is a company that was launched on HackerNews. You are like us, why does this not bother you?
Yeah, but that still happens. There's the W3C and the WHATWG, of course, but also formats like Opus (Xiph.Org, Skype, Mozilla and others) and protocols like OData.
At least in the OpenDocument days you had Sun as the corporate owners. (...) Why does DropBox not feel some responsibility to step in here, as the industry leader? This is a company that was launched on HackerNews. You are like us, why does this not bother you?
I think you're being a little unfair to Dropbox here. You should remember that Sun was in a very different situation: they weren't market leaders, they were users and the main vendor (MS) was asking them so much to license Office, that it was cheaper to flat-out buy StarOffice. And then opening it up was certainly socially beneficial, but it was also a way of pulling some power from Microsoft's hands and making it easier for Sun to avoid licensing their suite.
Dropbox, on the other hand, has no clear business case for opening up. They'd be adding a lot of risk to their main and only product, and for what? Good will?
I'm not saying they shouldn't open up, but I don't think we should judge them too harshly.
By the way, I'm very doubtful of the idea that HN has a whole has an ethical position on opening up. I'd say the mainstream position here is "we like open source if and when it benefits us". Which is why you see plenty of open source libraries and programming tools, but very few open consumer software. Proprietary SaaS is the mantra around here, not FOSS applications.
Plenty of companies have been jealous custodians of their file format to prevent interoperability.
Amazon's S3 interface seems to be widely emulated by cloud storage providers. Although that's very far from a complete sync solution.
I'm not sure your argument applied at the time. As technology makes progress, today's competitive advantage is tomorrow's commodity.
In any case, consider the people who pay for Dropbox today. What proportion of these people don't use integrations or services on top of the basic sync service?
Why is that troubling? Why should a service provider open source the software that they use for providing the service? You're not 'receiving' the software code of the server parts -- providing the storage functionality -- but are just using that.
In this case, the Ubuntu One client software and protocol libraries were already open source, and their statement suggests that they will also be open sourcing the server software code shortly.
As another example and similar case -- server software code that implements the storage functionality not available as open source -- is this quote on Tarsnap:
> While the Tarsnap code is not distributed under an open source license, Tarsnap contributes back to the open source community via bug fixes and enhancements to [...]
In these cases, the storage parts implement the competitive advantages for the provider. Now that Ubuntu One is stopping to leverage that competitive advantage, it remains a classy move to open source their implementation.
That's not true. The code must be checked for licensing issues; certain parts may depend on components they don't intend to release, or on third-party ones they can't release. It must also be checked to make sure it doesn't have any security implications (credentials, information about internal architectures, etc). Finally, releasing it may expose them to patent attacks of which existence they might not even be aware.
Then hopefully that code isn't in the same repository during develoment, but as a separate library. Everything else makes no sense.
The open source code can be useful even if it doesn't run without the library you didn't release.
> or on third-party ones they can't release.
Again, I hope for you, you didn't check in this stuff in your main code repository.
> It must also be checked to make sure it doesn't have any security implications (credentials, information about internal architectures, etc).
If your code has hard coded credentials you should probably start by firing your developers. As for the architecture part, if you need to do security by obscurity you're doing it wrong anyways.
> Finally, releasing it may expose them to patent attacks of which existence they might not even be aware.
Not for canonical, they're based in the UK and there are no software patents in Europe :)
But okay, that might be an issue for some US based companies.
Edit: IANAL, the situation might be a bit different in the UK than in the rest of europe, so I might be wrong: https://en.wikipedia.org/wiki/Software_patents_under_United_...
Besides, let's say that you're a product manager who's responsible for allowing the release of that code. You know that generally all those best practices are followed, but there were a few dozens of employees touching that code, and some might not even be at the company anymore. Are you really sure that none of them put sensitive stuff in there? Are you willing to bet your job on that?
If you really want an answer to that: Yes, I would. Even if there are credentials in there, I'd expect them not to be usable from the public net, but only from lan/vpn.
Yes, I'd risk my job for that.
Software patents are not entirely avoided in the EU, just to be clear. Quoting a little from an essay I had to write, although “programs for computers” are excluded by Article 52 of the European Patent Convention (1963), inventions that include an inventive step and solve a technical problem by the utilisation of a computer program have been upheld on appeal, for example in the case of Microsoft Corporation (data transfer with expanded clipboard features. T 0469/03 - 3.5.01, (URL now dead : http://www.epo.org/law-practice/case-law-appeals/recent/t030...) They might tell us that computer programs can't be patented, but their courts say otherwise - including states involved in the upcoming European Patent (for those unaware, currently EU states choose which European Patent Office patents to accept, the European Patent will synchronise all states except Spain and Italy). Actually the situation in Europe is quite similar to America - software isn't part of their patent legislation literature either; but such patents have been upheld repeatedly.
You should have been OwnCloud, not a Dropbox wannabe.
Pity this didn't work out financially for Canonical, and too bad for those users that came to rely on it (but this is the issue with pretty much any service that you don't operate yourself).
2 months continued service and another 2 months data access. It could be worse but it is a long way from the best you could wish for. 12 months to 2 years after the announcement would be what I would hope for from a big company winding up a service
Between various bugs, shit that just plain doesn't work, cancelled projects and now Ubuntu One, it seems Canonical likes shooting themselves in the foot... Maybe if they had actually marketed Ubuntu One and made it better they could be a Dropbox competitor. Then again, maybe they just don't have the expertise to make half of this shit work.
No wonder SUSE is a billion dollar company, Red Hat a multi-billion dollar company (with over a billion in yearly revenue), and Canonical a trust fund baby...
Ubuntu one felt like an experimentation from Ubuntu to bring some money in, in hope to somehow contribute money to fund itself for lack of a better business model. It makes sense to kill the experimentations that don't bring enough profit while consuming precious resources.
The spec is amazing, including client side encryption, fully anonymous, no single point of failure, no way for the network to be censored or shut down etc.
If interested check out [MaidSafe.net](http://maidsafe.net) for overview, and if you want to talk code join us on maidsafe-developers Google Group. It's launching soon and it would be fantastic to have a Ubuntu One government as one of the first apps!
Are there any good open-source self-hosted options that I could run on my little box at home? Preferably something that doesn't require a special setup or deployment on a server.
I could imagine there are file-sync solutions that just need an operable SSH account somewhere and merely automate the use of rsync to do the transfers, watching files and taking care of conflicts.
However I'm very grateful they decided to opensource it, at least I have a hope to keep implementing it.
Surely I will like to open source it, is just a 17Kb script that keeps listening and add a permission layer to create directories
>Our strategic priority for Ubuntu is making the best converged operating system for phones, tablets, desktops and more
If Ubuntu One wasn't of their strategic priorities, then certainly they didn't have their priorities right.
That said, I was never one to pay for DropBox or Ubuntu One because their pricing was just a little too expensive. The free tier got me enough space to share a few random files, and if I needed more than a few GB's, I've got my own infrastructure for that.
Any other good alternative, maybe FOSS, except Dropbox?
All open source, too. https://github.com/owncloud/
Check out http://owncloud.org/ for the full info on getting it set up! :)
And same is lack of differential uploads (change a single byte in a gigabyte blob, get the whole gigabyte re-uploaded).
I guess a server OS is also not a strategic priority. Oh well. What is a good Debian-based server OS that is a bit more up-to-date than Debian (and also a strategic priority for its developer)?
https://tools.google.com/dlpage/drive/?hl=en
"Running Linux? Stay tuned - Drive for Linux isn't ready just yet."
That's my .02€
[1] https://www.indiegogo.com/projects/ubuntu-edge [2] http://www.v3.co.uk/v3-uk/news/2323882/dropbox-valued-at-usd...
One time I needed to make something around 5 GB publicly available, and since Dropbox's free plan was too small, I used Ubuntu One.
Only after two days' worth of painful, oft-restarted uploading did I discover they require logging in to access publicly available files.
This is a mercy killing.
What are other alternatives to Ubuntu One? If they are smart, the partner with dropbox.
Check out their main page as well: http://owncloud.org/
Are people who have Ubuntu One installed being notified? I backup with Ubuntu One and haven't got any 'imminent shutdown' messages.
At least that's what people on HN say every time other companies launch something new.
Maybe companies are just capable of doing things we like and don't like and our liking them is just a cognitive bias of our historical cherry-picking of good things over bad.