> Calling .get() on a dead server returns None on failure, the same thing that is returned when there’s no value.

I suppose they were doing a .get() to check if the server was still up, and assuming None meant "there are no values to get, but the server is up". If .set() works in the same way (silently failing) they were essentially using /dev/null as their task queue. :)

Yeah. It's a cache, it says so in the name. Why would you make not-a-cache on a cache protocol and library? In-sane.