Custom Query (1145 matches)
Results (268 - 270 of 1145)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1109 | fixed | XDG_CACHE_HOME should be pointed to a local directory | davidben | |
Description |
The XDG base directory spec defines several variables including XDG_CACHE_HOME where applications are supposed to stuff cache data. There aren't all that many that create cache data of any significance, but browsers do. Google Chrome (and unbranded Chromium builds) uses it. Firefox does not, but they already split their profile into local/remote halves for Windows. I intend to shepherd a patch in Firefox to put the local half into XDG_CACHE_HOME. Debathena should consider pointing XDG_CACHE_HOME to something local. That would get local cache in Chrome for free, and same with Firefox once the patch goes through. This would also fix issue #329 as urlclassifier3.{sqlite,pset} are also part of the local profile. So are the offline cache and startup cache. (This would not fix #1107 as Thunderbird does not treat ImapMail? as local data.) This isn't explicitly stated as the intention in the spec (not that rigorous reading of a spec is remotely meaningful for desktop APIs), but random searches on Google do suggest that NFS homedir and local XDG_CACHE_HOME are common. It's conceivable that bad things will happen with an app running in two concurrent logins but each sees different caches, so it's probably worth testing a few things. (Then again, I suspect they all already break on concurrent logins anyway.) |
|||
#1107 | fixed | Thunderbird syncs entire Inbox locally by default | jdreed | |
Description |
Thunderbird thinks you should have a full local copy of your Inbox for "offline use" (you know, for when you have to disconnect your Trumpet Winsock SLIP connection to make a phone call, or something). This is a terrible idea in AFS. It can be limited by message age or size, and we should consider doing so. |
|||
#1105 | worksforme | The MIT Software menu is maybe broken? | jdreed | |
Description |
We should either fix it, or remove it, but it's basically unusable now. This is sort of related to #541 and #662. |