One thing that would IMO make Chord even better is if the delta for a removed action includes the full value as it existed before it was removed (and probably put it under the old_value key as it is for the updated action).
…Apropos, what is a “backend” in Chord, by the way?
(Also, at this point I’d think “state” is a better word than “context” but I understand that it would be too big of an endeavor to rename. And, what name is better is, for the better or worse, a highly subjective matter.)
Hi @dimitarvp, thank you so much for your thoughtful feedback, I truly appreciate it! 
Initially, I chose not to include old_value for the :removed action by default, instead offering the option to implement a custom delta formatter to adapt deltas to specific needs. However, after reflecting on your suggestion, I completely agree with you. Adding old_value to the :removed action provides greater flexibility and aligns better with the behavior of other actions like :modified. I’ll be incorporating this change in the next update.
Regarding your question, a “backend” in Chord simply refers to the underlying data storage mechanism, such as ETS or Redis.
As for “context” versus “state,” I understand your perspective, and you raise a great point. The term “context” was chosen to highlight the library’s flexibility and adaptability, aligning with its design goals. While “state” might feel more universally intuitive, “context” reflects the broader intent behind Chord’s functionality. I really appreciate your input, it’s always valuable to revisit and reflect on these choices.
Thanks again for your insights! Let me know if there’s anything else you’d like to discuss or suggest, I’d be happy to hear it!
Hi everyone!
I just wanted to take a moment to thank you all for the amazing feedback and suggestions you’ve shared about Chord. Your input has been incredibly valuable in shaping the library and making it better for everyone.
I’m excited to share that I’ve released version 0.2.0, which includes several key improvements:
time_unit configuration option for better control over timestamp precision (:second or :millisecond).Your feedback has truly helped refine Chord and inspired me to think about its future possibilities. I truly appreciate the time and effort you’ve taken to share your thoughts, it means a lot to me! 
I hope you enjoy the updates and find the library even more useful! Let me know if there’s anything else you’d like to see or discuss.