P: Provide preference and preset syncing via the cloud (Presets, Preferences, Workspaces, etc)

I would not be at all happy with simply saving and loading. That's already easily accomplished using backup software and plugins. Syncing is not so easy and would definitely be a great addition!

I would definitely want BOTH! It wouldn't be a problem to implement both. Just as you for sure want to be able to do it without synching there are those (a lot) that for sure want synching.

I'd be happy with preset saving and loading, rather than full syncing. Syncing is often a very difficult problem to solve, but wouldn't have much benefit over saving and loading for me (or maybe saving, loading, sharing).

There should be a choice. Something like this maybe.
(not put in any particular order just typed it out)

1) I want to synch to the cloud.
(the cloud being whatever service that is implemented)

2) I Don't want to synch to cloud, I ONLY want to export.

3) I synch to cloud but would like to export my settings at this time.

Maybe??
What do you think?

Let me second Ian's proposal. Being able to export everything to a given location (desktop, for instance), then let user copy and move the files to another machine, then import from there needs to be present for non-networked areas. The Cloud service is a plus, but should maybe not be the default behavior.

@8452758 - you may use Drop box and not want to change, so what about the people who use Sugar Sync, Windows Live, Amazon S3 or one of the many other sometimes better cloud syncing tools? Should they all move to Drop Box to save you any hassle?
And as you obviously have and use an Adobe ID, what's the issue anyway with another login you already use and maintain?
Besides at the moment DB is a bit crippled as you cannot tell it to sync a bunch of different folders scattered around your various hard drives, it can only sync from within the single DB folder and its subfolders. There are workarounds, some fiddly and some dangerous and which differ depending on which OS you are using, so it really isn't that suitable anyway.
And why use a third party who may go out of business or change their terms of use excluding other companies using their service. Particularly as PS for example can already interact and share files online, so why even use a 3rd party tool?
The whole point of this feature request is to make life easy for people, not fiddly with geeky faffing around with 3rd party software. Which most users will have no interes in.

Re: the security thing--I can understand how there might be a concern regarding the integration of a CSLive account and a dropbox account if I had to tell Adobe the login credentials for my dropbox. I was thinking something much simpler.

Try this idea for its worth:
I can establish a setting in Photoshop, defining where I wish to keep my Adobe Presets. Maybe it's in the Adobe folder, maybe it's in my dropbox. That setting is stored as a Photoshop preference, *and* in my Adobe CSLive account, if I'm signed in.

Now, any time I go to another computer, I have several options:
1) For computer 2, set up Dropbox and tell that instance of Photoshop to point there. This keeps all presets synced so that changes on computer2 are re-acquired on computer1 by virtue of the machines having the "same" preset folder.
2) I sign into CSLive on computer2, and it notices that it should sync to dropbox and links up automagically to the configured instance of dropbox running on computer2
3) I sign into CSLive on computer2, but it does *not* have dropbox, nor do I want to/have permission to install it for any applicable reason. CSLive sees that I should sync with dropbox, and asks for my dropbox login credentials (not stored by Adobe--used to connect to dropbox). As I change presets, or close Photoshop, these credentials are used to re-upload my prefs to DB and then are wiped away.

I think that covers all use cases of needing to have Photoshop on multiple machines that you may or may not have complete control of. Right? And ost of it is accomplished by letting the prefs folder be variable. he extra coding work would be with the last bit there--sending a folder up to DB (which I assume there's an api for)

I am all for being careful about security but I am not sure how putting presets on an third party server is going to be any kind of security problem. Aren't presets just text files with pre-defined values for existing variables? Isn't there already some sanity/safety checking within LR and PS that validates these files? If so why is is a problem where they are stored? If I'm missing something I would be glad to be enlightened.

So if Adobe wants to provide a new service for this that would be great, but I already use Dropbox for other data and would rather not have to configure and maintain yet another special login/service that is functionally equivalent to what I already have in place.

David,

I think there are two levels of interest here. The first is being able to share the presets, etc via a cloud based service. The second is one where the sharing would take place within a closed network. As Jeffrey has already intimated, the first will almost certainly fall foul of the policies in place at quite a few corporate and governmental bodies. The second much less so. Therefore, if you do decide to take the idea forward (actually one that Joh Nack has been championing for years), I would ask that Adobe keep in mind those who have no option but to work within closed networks.

My original request is to be able to easily export and import settings with all the various benefits that will accrue. Syncing via the net is icing on the cake. I also agree that being able to choose exactly what bits need syncing is important too.