-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Optionally never write personally identifiable information to metadata files #2640
Comments
I've already had the idea of adding options to add, modify/change, or remove metadata fields to the existing Something like this: {
"name": "metadata",
"delete": ["thumbnails", "preview"],
"set" : {
"is_blocked" : false,
"is_favourited": false,
"is_watching" : false
},
} |
It's possible there's an edge case where, for example, one site has But until someone runs into that this should work perfectly! |
Just realized you said this was an idea and not already added Gonna go get some tea to wake myself up |
Couldn't you just remove metadata fields with custom content format? |
This has been implemented quite some time ago, but I never got back to this issue and I'm also not sure if this implementation is any good. It's needlessly verbose but rather flexible because of that. f3de6b7 and 0c73914 add two additional "deviantart": {
"postprocessors": [
{
"name": "metadata",
"mode": "delete",
"fields": [
"is_blocked",
"is_favourited"
]
},
{
"name": "metadata",
"mode": "modify",
"fields": {
"is_watching": "\fE False",
"custom_field": "{index!s}-{extension}"
}
},
{
"name": "metadata",
"#": "write metadata"
}
]
} |
Sometimes when sharing archives of accounts, the metadata can snitch to people what account you're using or if you're following the person and whatnot
Since this would affect so many extractors it should probably be added as a postprocessor
A basic implementation of the idea:
Of course the hard part is getting a list of all metadata keys that can be used to identify you
The text was updated successfully, but these errors were encountered: