Every function in the vimeo module maps to an endpoint in the vimeo API, including this one. Moving it to another module seems wrong from that point of view.

Hmm, I know! I'll make a decorator, `vimeo_task` that marks the function as a celery task AND handles retrying the method. Then I can just apply it to all the vimeo functions so that you can either call them directly or schedule them in the job queue.