@pawelreise sorry - been thinking about this but it seems like a challenging problem and all of the proposed solutions have some problems. it seems like the overhead of keeping `location_ids` on users and `user_ids` on locations could get us into problems down the road. and that's before we start worrying about changing location paths and the implications that has. also as we've mentioned we've been really trying to avoid adding new couch views wherever possible.

if we moved locations to sql or elastic search would that make this more tenable? i realize that's a lot of work but just wondering if that would solve this in a cleaner way.