|
|
|
|
|
|
by maccard
2195 days ago
|
|
|
> I think after a year they could put everything in archive mode, but no, they deleted it with no easy export. I mean, it's still there. If it's that much of an issue, and the tooling has been made by the community, you're free to archive it now. At what point is it ok for them to say "hey, we don't want to pay to store the data/keep the codepaths to display/interact with this data" anymore? How many of those people were paying customers before this? I don't know the answer offhand, but if I had to guess, I'd suspect a small number of them. > That's not OK and I'm clearly very, very angry as a former user. I hope as a paying customer, you cancelled your subscription to them and told them explicitly why then. |
|
|
At the point when they make it super easy for the people to archive the data themselves. Code part is easy, PRs, issues and downloads are hard. See: Google takeout
> I hope as a paying customer, you cancelled your subscription to them and told them explicitly why then.
Not just even for me, I made my company switch to it, and we were also hoping support for mercurial in the future, but were okay with it not supporting mercurial in local deployments, we had our hg repos on bitbucket.org. When the news broke, I moved to GitHub and perkeep (for archiving all the JSON data that I painstakingly had to scrape), and my (now former) company found a smaller vendor that offered what BitBucket was supposed to offer but never delivered, only for 100x the price (although one-time, custom development for them).