short answer

No - without some more effort this is not a save procedure to simply sync all the configuration files below ~/.config.

detailed answer

This approach is limited through the following prerequisites:

• Dependencies to the installed applications, especially the plugin
  components of an application.


• Same file system structure on both systems.
  
  E.g. /home/Alice and /home/Bob
  will fail because a lot of configuration data use the qualified path
  and not the '~' reference to the user home directory.
  (In my .config directory 30 (of 92) applications are affected by this problem.)


• The network infrastructure may be different.
  
  E.g. desktop (with NFS, LDAP based user accounts) versus mobile laptop.



• You have to think about changes of configurations and collision handling.
  
  Because the data may be critical I would advice to use a version control system (e.g. subversion) as backend for storing the data.




• The config directories may contain volatile data not suitable for synchronizing:

  
  
  
  
  
  • lock file (e.g. chromium/SingletonLock) which should be excluded.
  
  
  • cache directories
  
  
  • ...
  
  

But give it a try and report your success and "lessons learned" :-)

I agree that the current situation below linux isn't suitable for working with multiple devices.

The problem is that most of the configuration data is stored in the file system and
either gnome, kde or freedesktop provide a network accessible configuration repository and an precedence schema for local an shared configuration data.

My workaround is that I try to configure as much as useful below /etc and share this configuration (via subversion).
This approach evolved currently to an inhouse framework of 5k lines of bash code and over 2000 data files. It handles currently 4 desktop, 5 mobile and 2 server machines.

For some of my own data below ~/.config, ~/.thunderbird (...) I use an similar approach.