Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Records could be edited at any time by any of several parties, …

I took an “Accounting for managers” course back in the nineties which included double entry book-keeping - we were taught to never erase a mistake but create additional entries to correct any error. You’d think something like Horizon would adhere to agreed standards of record keeping and have a signed and immutable event log at the very least.



Yep. I’m not an accountant or even a manager, but even I know that. Apparently the Post Office testified many times that the transaction record _was_ immutable, even though Fujitsu knew that records could be edited or even lost at any time. And it appears that their own customer service employees would edit transactions all the time, to correct perceived mistakes. And it would appear that this might even make the problem worse, as the Horizon system could fail to correctly merge those changes down the line. It could silently revert the edits or silently drop entire transactions as if they had never happened.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: