What's the problem?
juxtapose includes its Flickr API key in juxtapose.js making it visible to all users. In spite of this disclosure account security should not be at risk.
However, there are two other issues that might arise:
According to https://www.flickr.com/services/developer/api/ key usage is limited to 3.600 queries per hour. Sharing your personal key across all juxtapose users may lead to exhaustion of your quota resulting in denial of service.
What's the problem? juxtapose includes its Flickr API key in
juxtapose.js
making it visible to all users. In spite of this disclosure account security should not be at risk.However, there are two other issues that might arise:
I would suggest to either remove your Flickr API key and see if it's needed at all. Otherwise I would enable users to specify their own API keys.