We introduced a human_readable_serialization option in RUST-1687 as a fallback for our possibly-breaking bug fix to force non-human-readable serialization in all of our API methods. However, we don't think this is an option we should maintain in the long-term for the following reasons:

• There are many places to keep track of and configure human_readable throughout the code which creates a larger maintenance burden for this option.
• Most users are not concerned with the way their data is represented in the database as long as it properly round-trips through the driver.
• Users who do care about the format of their data in the database can write custom serialization/deserialization logic to handle the formatting themselves.

Rather than support this option outright, we should deprecate it now and remove it in the next major release to give any users who are affected by the serialization fix a workaround while they fix their code.