Thanks for the feedback. I'm on the CF Images product team.
We will allow the download of the original images, it is actually one of the next features coming up. Also we will introduce webhooks and Images Analytics next.
Thank you. If there's any other feedback you could take from this, please know that I've submitted a similar feature request for point #6, so that I could know the ID of the image from the direct creator upload. Without that, a malicious user of mine could possibly create many millions of images, and I would have no way of knowing who it was that created the image, and no way of knowing which images to delete or track.
I think Images could greatly benefit from having a tag/label system that allows you to decorate it, similar to how enterprise cache tags was implemented. That way, it is trivial to do things like "delete by user id X" as well as covering your use case.
Honour EXIF as well as sidecars for tags. Use one of the defined tag syntaxes and state which one you honour.
Approximate date in images is a huge issue. There's a range of ways to express uncertainty to date, not after. not before. circa. between. year good month uncertain. If you invested in this space, you could help simplify the thinking. Ramming it into specific YYYY:MM:DD:HH:MM:SS values is really bad.
Google is a bad actor here in photos: they don't re-index on tag modification except for very specific changes and its opaque and poorly documented. If you do better it has good qualities about market and mind share.
"it is actually one of the next features coming up" is one of the most annoying things I hear from enterprise companies that I have issues with. I have received this response and waited for the feature for over a year or have never seen it released at all.
Thank you for the response, but, at the end of the day, people are going to judge Cloudflare on how quickly and accurately they can solve these issues.
I assure you it's not just you. I see it from the other end as well. Not long ago I had a client shout "I don't want to hear about your roadmap!" and grab his team and walk out of a meeting. We really shouldn't have used that terminology there, since the feature they needed was actually already in beta test with a few friendlies, we could have added them to the beta test cohort on the spot, and demonstrated it in their account during the meeting.
(Personally, I'm kinda glad we didn't. They were without doubt the sort of customer we should have already fired...)
I can empathize with the customer here. I have also seen it from the other end, working for a large and slow SAAS organization. I see PMs always wanting to show the customer the "roadmap" because they think it somehow appeases the customer and calms their wrath. The wiser customers know that a roadmap is not a promise, and will take it with a huge grain of salt. I have grown to almost despise the word or mention of it. Quit with the meetings and compliance reviews and politics and just get stuff done for god's sakes.
This is exactly where that customer was coming from. Many many broken promises from their previous vendor about essential features "being on the roadmap" for 2-3 years without ever seeing the light of day. (And we knew that was one of the biggest reasons we poached them away.)
