Hi Dom,
I saw your earlier post in here and took a chance hoping youād see my concerns. You did. In all sincerity, thank you greatly for taking the time to respond. Most companies have these forums simply as echo-chambers to give users a false sense of resolve (or at least a place to vent). Clearly, this isnāt the case with PLEX and based on your reply, I can see PLEX is committed to their users.
As a result of your reply, frustrations aside, I speak highly of PLEX then as I do now for your teams ongoing commitment. Thank you.
That said, I did want to reply to your email. Since formatting always seems to be a challenge on all forums :), I broke this into 3 key sections below.
##1: Resource Prioritization/Data Monetization ##
@āDom Cā said:
Just to be absolutely clear - this is just not true. If you choose to use the autotagging feature then small thumbnails are temporarily stored on Imaggaās servers for analysis - https://support.plex.tv/articles/234976627-auto-tagging-of-photos/ There is no selling of your data, metadata or anything else.
1. My point was this⦠Why not commit development resources to fully baking existing core functionality rather than chase new features which will just lack more core features or create more work when existing work needs to be completed? Iām guessing it took a non-trivial amount of development resources (probably 10x of simple basic functionality weāre asking) on both PLEX and Imagga teams to implement photo-tagging that a fraction otherwise could have gone to fulfill existing user requests.
2. Aside from my key point (resource allocation), reading Imaggaās privacy policy, it seems to read as if they can do whatever they want with our data, thus my comment. Perhaps PLEX has individual B2B terms with Imagga that supersede the āwe can do whatever we likeā terms they have posted publicly?
3. At present, Imagga privacy policy does seem to be a bit of a āPrivacy Casinoā. In other words, if you play (i.e. upload data) you are effectively gambling with your privacy at your own risk. This includes but is not limited to their ability to monetize users PII or Non-PII (Personally Identifiable Information) data.
Per https://imagga.com/privacy:
1. "However, although we make efforts to protect your privacy, we cannot guarantee that the Service will be immune from any wrongdoings, malfunctions, unlawful interceptions or access, or other kinds of abuse and misuse."
2. "In any case, as long as you use the Service, we will keep information about you, unless we are required by law to delete it, or if we decide to remove it at our discretion."
3. "At times, we may anonymize your Personal Information so that you cannot be individually identified, and provide that information to our partners."
4. "We use anonymous, statistical or aggregated information and may share it with our partners for legitimate business purposes"
ālegitimate business purposesā = We (Imagga) have the right to sell your data if we want to, even if we donāt exercise that right today - we can and will.
All of the above appear to be proverbial āGet out of jail freeā cards. āJust trust usā is what weāre leaning on absent of additional terms that otherwise supersede this language - thus the driver and concern I raised.
5. If photo tagging is truly a cost driver for PLEX, and not a revenue source, then I commend PLEX and stand corrected on PLEX monetizing our data as this is not usually the norm, but make no mistake, as written today, Imagga has the right to monetize our data from what I see written in their āsmoke meets mirrorsā privacy policy. I want to be wrong about any data being sold or monetized (outside of PLEX if youāre not doing this), so if something exists to the contrary, please help me see where we have protection from PII or Non-PII data being monetized given the statements from Imagga above?
- Again, to be clear, monetization of data in and of itself was not my primary concern provided itās disclosed and done correctly. Resource prioritization is the concern.
##2: Slideshow Speed##
@āDom Cā said: Iām hoping we get this added soon. Itās in our backlog of work and a few recent forum posts have certainly raised its priority.
Thank you for this!!! This is big.
##3: Bulk download photos##
@āDom Cā said:
Bulk download photos
Also in our backlog - but dumb question so I can add more context to the issue, what do you need this for? Do your family want to use another service/print them?
Iām sorry to hear itās not working for you, especially at what sounds like a horrible time.
Thank you for the condolences and concern. That means a lot to me. 
To your question for context - use case is such that photos are an emotional experience and families and friends look at photos together and **as @āScott the Linguistā conveyed in his post, folks want to take action on photos after they view and favorite them **- In many cases those actions are needed in bulk. Those actions need not happen in PLEX, but having the ability quickly export the photos in bulk to do so elsewhere is key - otherwise itās pointless to use the photos feature in PLEX if youāre only to have do so elsewhere and repeat the entire viewing process.
With photos (and even other content for that matter) organization and content export are the key pillars of success to accomplish most use cases
To PLEXās credit, you have organization NAILED - hands down.
However, content export is what is sorely lacking in photos and itās the key enabler so we can take our action outside the PLEX platform. In my case, our family needed to collectively pick from 6,000 photos and export a subset to make a video slide show with music synced (thinkā¦VEGAS/MovieMaker/FinalCut Pro, etcā¦)
Additional context - In my case, my father passed away and I wanted to put together a video slideshow to memorialize his life with our family I scanned in 6,000 photos over 3 days prior. Once the A/D conversion was complete, viewing and picking from the 6,000 photos of course was going to be a family effort and of course, PLEX has been good at most everything else, so it seemed like a natural fit.
**So the entire family sat down using our NVIDIA shield and 70+ inch TV with PLEX as the client (not server) and were wowed at first, until I couldnāt find a way to speed up the slideshow **and my non-tech inclined family kept getting annoyed asking āwhy is this so slowā¦can we speed this up???ā as **we had 6K photos to view and after an hour of searching, realized this basic function was ācoming soonā several years back. So, like everything nowadays, I switch into āworkaroundā mode.
THIS IS ONE OF MANY REASONS BULK DOWNLOAD IS NEEDED ā> āWorkaround modeā for no slideshow speed = Scrolling in thumbnail mode, all of us viewing the photos, āheartingā the photos we liked. We marked 500 photos. I made the naive assumption I could export these in bulk (even if 500 pop-ups in Chrome - which is an easy fix to workaround) from the āfavoritesā album that creates. So as you can imagine, when I found out I couldnāt even export the photos we invested an entire afternoon viewing, needless to say I was going to miss my deadline to submit the proof for viewing and test the next morning at the funeral home.**
So to the suggestion of individual download⦠As Iām sure you know, clicking download is frustrating when you have to do that 500 times in addition to waiting for screen transitions and other cutesy stuff. In the end, I got up at 4AM the morning before the funeral and downloaded all 500 photos individually one by one and probably missed a few along the way. Add that to resetting my workflow outside of PLEX to make the movie (since I didnāt have what I needed up front - time cost is compounded).
The consequence of PLEX not having the bulk download feature was me being late to the funeral home for the early family arrival. Because of this, to take my mind of more emotional matters, I kept thinking⦠At what point will be people learn the consequences of seemingly harmless decisions and deferring āboringā but critically needed functionality code work?
An ounce of investment in time from PLEX upfront pays 10x dividends to your users the end. 20 hours (generous) of DEV work by PLEX would save humanity 100K+ hours annually (or perhaps millions depending on user base) of manual work or the enormous frustration and heartache of realizing theyāre SOL last minute like happened to me. Saving time for users without creating trade-off, is how real value in product development is generated. Not by feature quantification, hence my comment⦠If you canāt do it right, donāt do it at all.** The backlog of problems it creates only drives long term unsustainabilty (beyond job security) with overall workload.
In any event, I thank you and do appreciate you pressing for these key pieces of functionality as well as taking the time to listen and respond. My sincere hope for everyone if ever faced with this situation is they donāt face the same level of frustration and heartbreak I did.
Best regards