PlatformsFacebookPhotos

useSherlockPhotoPredictionMutation

Domainphotos
Kindmutation
doc_id8975911135844322
Path/api/graphql/
Sendsinput
Readssherlock_photo_prediction.top_categories, sherlock_photo_prediction.virtual_taxonomies
Called fromuseSherlockPhotoPredictionMutation
reaev_c00a0898155fe51669981d0310887e094b1fc17734525a087f1d5dcfab9ef057

Seen 54 time(s) in 16 run(s).

ActionOur stepTimesStatusTookAfter step startErrors
publishUploading 5 photo(s)30200875–1551 ms4730–9792 ms—
publishUploading 2 photo(s)4200789–913 ms6550–8179 ms—
inspectstep 14: snapshot2200946–1004 ms1195–1197 ms—
inspectstep 16: type e23222001388–1881 ms7266–7268 ms—
inspectupload: before.png handed to the file chooser22002272–2835 ms4801–4803 ms—
inspectstep 10: type e2322200886–889 ms6956–6959 ms—
flowupload: photo1.jpg handed to the file chooser42001071–1354 ms5511–7105 ms—
flowstep 7: fillRole textbox "…"42001426–2739 ms7868–7872 ms—
hostsetLocation: 'Mountain Top, Pennsylvania' is suggestion 2 of 942001071–2739 ms686837–707190 ms—

What it does

Facebook's image model reads the uploaded photos and suggests categories (sherlock_photo_prediction.top_categories: "Household" for our rubbish-removal photos). Sent as multipart form data, about 1 s each.

What our machine does with it

Nothing. The publish machine picks the category from the listing, not from this suggestion.

What can go wrong

Harmless, but telling: Facebook classifies every photo, so photos that do not match the listing's category are visible to it. Keep photos and category consistent.