|
I understand you're wary of breaking parts of Amazons functionality as we don't know what's going on there. I also understand your concern that future changes by amazon could break functionality. However:
1) I've tested the logic and scenarios I listed above and they work. I can do further testing before providing a patch, including other scenarios if you wish.
2) We're already exposed to the risk that future changes could break functionality. We're putting a random ASIN into the file, which currently enables last page sync to work- there's no guarantee this will keep working.
3) The current interaction between calibre mobi files and the kindle sharing/sync is significantly broken- of the three functions listed above only one will work at a time. This isn't intended as a criticism of calibre- it's amazon behavior. However I can't change amazon, but I can change calibre. If I've told calibre that a given non amazon book is the same as a given amazon book, then all of these functions can be made to work.
Regarding your specific concerns: a user generating MOBI files for submission to Amazon's DTP platform will not be linking the book to an amazon book using the metadata plugin, so behaviour will be as current. I'm not sure what the issue would be with the cross user notes?
Why not let the user decide on whether to include the linked, via a configuration option on the mobi output? Leave it off by default, and let users who want the full sharing/sync functionality turn it on?
I'm happy to implement, test, and maintain this. I think it would be of value to kindle users.
|