This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-20
Channels
@beders https://hk.saowen.com/a/6b7a98d508424e6f3ea79e64a50506a349468a22003437db33f2f3a39b589cc9
Looks like a mirror from @val_waeselynck’s blog http://vvvvalvalval.github.io/posts/2018-05-01-making-a-datomic-system-gdpr-compliant.html
I’m not a lawyer, and I’m not speaking on behalf of the Datomic team, but this seems to mangle a lot of Datomic’s value for a possibly questionable goal in the face of a rapidly evolving legal area, which may actually not require anything of the sort.
@U064X3EF3 maybe you would think differently if you worked in the EU, this stuff is getting pretty tangible there :) . In any case, I felt it was important to make people aware of this option so that they don't consider Datomic's immutability a deal breaker.
I also disagree about it mangling a "lot" of Datomic's value, from experience, and I tried to articulate that in the article (criticism welcome). As a comparison, IMO you lose much less power by adopting this approach than by moving from Peer/On-Prem to Client/Cloud.
Finally, from a non-legal standpoint, I will add that I witness every day the temptation to abuse the data of our users within my company, and I want to technically enforce its protection - who knows how things will evolve, especially once I'm gone?