Since Adobe makes it difficult to contact them to inform them of poor quality products, I'm going to post here. Apologies if this is not the correct avenue, but I guess that's another complaint for another day. I would like Adobe to be aware that the content in their Stock library is often of very poor quality. There are numerous cases of repetitive images with only slight differences, where the contributors are clearly just trying to squeeze out more from one image. But also, some complete garbage being returned in search results. The following image is a good example of something completely unusable and unprofessional. Image #522730440, which, inexplicably, is a PREMIUM image. https://stock.adobe.com/ca/images/a-group-of-workmen-sitting-at-a-construction-site/522730440?asset_... There are a few other issues I could mention with the Stock library, but that's a start. Adobe, can you please remove the low quality images from the library? Such a waste of time scrolling through pages of unusable images.
Adobe customer care is not difficult to contact. Adobe customer care can be contacted by beginning a secure chat session at https://helpx.adobe.com/contact.html?rghtup=autoOpen. Pop-up blockers need to be disabled, you need to accept cookies! If the chat window fails to open, or is non-responsive, use a different device and/or browser to start the interaction.
Support phone numbers may be found here: https://helpx.adobe.com/contact/phone.html. Kindly note that phone charges may apply.
For support via Twitter:
(see also here: https://community.adobe.com/t5/creative-cloud-services/how-to-contact-adobe-support/td-p/11875703 or here
Important: Adobe does NOT contact you unsolicited by e-mail or direct message. If you get contacted by direct message from a person, claiming to be an Adobe employee, look at that profile and look, if they bear the “Adobe Employee” marking under their name. Adobe support does not use Skype to give you support.
If in doubt, ask the forum.
Thank you for reporting this. Our content review team is looking into this issue.