Gabble wastes a lot of network I/O on disco caps replies whenever we sign on, and to work well, MSN CMs need to cache a bewildering variety of tokens. Perhaps we should relax the "CMs shouldn't write to disk" constraint to allow CMs to write to $XDG_CACHE_HOME (defaulting to ~/.cache), as long as they only write data meeting the definition of "cache" (i.e. the user can delete random files at any time and the CM will not be adversely affected, except by wasting some network I/O).
Gabble writes to $XDG_CACHE_HOME. I think this constraint can be considered relaxed.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.