yaseenkadir
commented
5 years ago Should we do this by adding a new field to our entities? E.g. mutable? Or should we just enable it at the table level e.g. all entries are mutable, all etches are immutable. Or add a field and enable toggling it per entity e.g. add mutable field and set it to true or false for each record.
My gut feeling is make journals and entries as mutable entities by default. But to add the field to etches. I can very easily see the concern that some people may want to delete an individual etch. Right now they are batched so we either have to encrypt each etch individually and send each one as an entity. Or continue sending them as a batch and allow editing them.
We need to add support for mutable and immutable entities on the backend. For example, an entry will be mutable because we can change the title.