There's one thing I don't like about this line.

A common advocated RQ pattern is to create many `Queue()` instances, since they are light-weight objects. This makes the Queue constructor require network access. Maybe we can change this to be done implicitly once the queue is used? That way, creating queue instances will still be a fast operation (not requiring network access), until they're actually used to write to, of course.

Besides, I don't think trying to read from a Queue should put it on the list anyway.

Thoughts?