Re:Microsoft is shutting down its Azure Blockchain Service
by haukem on Thursday May 13, 2021 @07:35AM
(#27140949)
You can also set up a git repository and prevent history rewrites on the central server.
Some third party could also offer this as a service.
Each entity can check this by doing a pull every minute in a cron job, which fails when history rewrite happened. If they detect this, their legal department can take some actions.
[ Parent
| on HN ]
Re:Microsoft is shutting down its Azure Blockchain Service
by ignoramous on Thursday May 13, 2021 @07:51AM
(#27141044)
Just because Encarta existed, didn't mean Wikipedia shouldn't; or because NFS exists, Dropbox shouldn't. They can be solutions to the same problem. In git's case though, it sounds more like a abuse of its underlying properties (not to mention, you'd have to block all git commands that can rewrite history).
Re:Microsoft is shutting down its Azure Blockchain Service
by yjftsjthsd-h on Thursday May 13, 2021 @12:53PM
(#27144407)
> not to mention, you'd have to block all git commands that can rewrite history
Okay, so use mercurial or fossil.