On further thought, I think this would need to be enabled on a white-list basis for crates (or crate trees, when the nested crates feature is implemented. I have a bunch of utility crates that allow be to group tracks in a way that is not useful for a global database (like "tracks for <friend>", or "broken files", or "recommended by <blah>"). These would need to be excluded. With nested crates, it would make sense to have the ability to include all crates in a tree (e.g. grenre:* or mood:*).
Some of those crates might be useful for me to keep and sync to a web service, but only if the service allowed private tags as well as public tags. I'll submit a feature request to musicbrainz for that, although I wouldn't be surprised if they consider it out of scope.
On further thought, I think this would need to be enabled on a white-list basis for crates (or crate trees, when the nested crates feature is implemented. I have a bunch of utility crates that allow be to group tracks in a way that is not useful for a global database (like "tracks for <friend>", or "broken files", or "recommended by <blah>"). These would need to be excluded. With nested crates, it would make sense to have the ability to include all crates in a tree (e.g. grenre:* or mood:*).
Some of those crates might be useful for me to keep and sync to a web service, but only if the service allowed private tags as well as public tags. I'll submit a feature request to musicbrainz for that, although I wouldn't be surprised if they consider it out of scope.