Under the hood
Useful2 Signal4
Sync records survive an unfamiliar transport name instead of being thrown out entirely.
What's wrong with this entry?
Anonymous. No account, no email.
What
The field naming how a bundle travelled changed from a fixed choice of two values to any short string, normalised to "row", "direct" or "unknown", with size caps looked up per transport. A newer server transport now passes through an older reader instead of invalidating the whole record.
Details
- The laptop side refuses to write a journal note whose bundle normalised to "unknown".
- The same note gained an origin field that only survives the round trip as "folder".
Evidence
sync journal note is not one its reader would accept, or rides with rows
Strings lifted out of the shipped bundle, so the claim above can be checked against them.