Yep. For me, the core struggle was having a `redis_id` attribute. Immediately set off some flags that I'd be explicitly allowing Redis to bleed through, but simply naming it `:id` seemed like it would cause major headaches down the road if someone wanted to use multiple backends or migrate to a different backend where an id is implicitly managed by the storage system.

I don't have a silver bullet for this one. Best I can come up with right now is renaming `redis_id` to something more generic and allowing the user to override the id generation via an optional proc or something. Obvious concern there is maintaining uniqueness if we allow users to override the source of failure id generation.

I'm definitely open to suggestion/dialogue/pairing to try and tighten this up.