More uninteresting information on Q's file naming convention:

AA18E55B-4CFD-4974-A479-37C7703ECC1D.jpeg

AA00D4A7-BF25-44EC-BB62-48819678C8B0.jpeg

A783B991-11D9-40D0-BD69-17FF6041E890.jpeg

A3589E21-85D1-4056-9DC7-553651D87D03.jpeg

A2735ADE-C628-42EA-855F-146700A8A886.jpeg

…

This is v4 UUID creation, the giveaway is the 15th character is always 4.(as opposed to UUID v1,v5) See UUID v4 in action here: https://www.uuidgenerator.net/

What makes this only minutely more interesting is that the UUID's are uppercase, against the standard:

>The international spec of 2008-08, itu.int/rec/T-REC-X.667/en, agrees with that RFC 4122: 6.5.4 Software generating the hexadecimal representation of a UUID shall not use upper case letters. NOTE – It is recommended that the hexadecimal representation used in all human-readable formats be restricted to lower-case letters. Software processing this representation is, however, required to accept both upper and lower case letters as specified in 6.5.2.

Q's filenames are uppercase. I could only find uuidgen on MacOSX that produces uppercase UUIDs by default, but uuidgen tool is not UUID v4. At any rate, these are unique and random UUIDs in Q file names and should not have any further clues or require further digging. The whole point of renaming files with UUID is to obfuscate origin. I wasted a few hours on this, wanted to save other anons the time.