The fast-export --anonymize item is interesting. I've used a few tools professionally that I've been unable to feasibly report some bugs for, because any time I

The fast-export --anonymize item is interesting. I've used a few tools professionally that I've been unable to feasibly report some bugs for, because any time I produce a log file (or whatever) it's filled with file names or email addresses or function names or code snippest or paths or whatever. Or if it's an example file, it contains copyrighted information that one can't just go giving away to 3rd parties. Had there been some kind of anonymization option, on the other hand, there'd have been no problem. As it is, I just have to produce some hand-wavey bug report, that's as accurate as I can make it - that then presumably gets put on the shelf with all the other random unclassifiable oddities that nobody has time to look at properly. Because they're too busy dealing with the bugs that actually came with data. (Of course, sometimes the data itself is the problem, and then this wouldn't help. Then other times, the system in question has faulty RAM. This wouldn't help with that either.)