4 ms·
Yes, this is a lawyers version of a patch to fix bugs that programmers sometimes introduce. A couple of years ago I used DocuSign on a contract, and the PDF “c
by kube-system 7y ago
Yes, this is a lawyers version of a patch to fix bugs that programmers sometimes introduce.
A couple of years ago I used DocuSign on a contract, and the PDF “copy” I was emailed as a receipt had different terms than the one I actually signed.
Luckily I did not object to the discrepancy, but I would have wondered what would have actually happened if I did.
- gumby 7y agoWhat?? Is this public? Have others reported this happening? That would be a huge issue!
- kube-system 7y agoLet me clarify by stating that I am not necessarily claiming that there is/was a software issue with DocuSign. There are also some big procedural differences between signing a hard copy and the way most electronic signature systems work. I could have been fooled by the user. Regardless, I am sure there has been a version of a some document signing software somewhere that had a bug with immutability. Now paper documents aren't immutable either, but you couldn't accidentally change one with a bad where clause in a SQL statement, and casual attempts will leave evidence of the change.
- gumby 7y ago> Now paper documents aren't immutable either... BTW this is why numbers in contracts are often written “1 (one)”: because in the age of pens it was easy to change “1” to “10” or “4” or “one” to “none” Also why checks do this — checks are actually simply contracts, which were standardized in the US a bit in the 1920s (you’d get a check form, fill in your name and the bank name, then the amounts, etc; current check design With preprinted bank info dates back I believe to the late 1960s.