The FlickrAPI defaults to creating a local, hidden folder in the current user's home directory to cache its authentication tokens. This causes all sorts of headaches for unusual setups like datacats' docker containers.
Could the tokencache be disabled without repercussions? IIRC flickrapi would simply use an in-memory token cache.
The FlickrAPI defaults to creating a local, hidden folder in the current user's home directory to cache its authentication tokens. This causes all sorts of headaches for unusual setups like datacats' docker containers.
Could the tokencache be disabled without repercussions? IIRC flickrapi would simply use an in-memory token cache.