From TT
JR - JB says not downloaded during Teams meeting
PD - DU moved the files to
JR - slow
PD - up to screen 5 into auto folder downloads
JR - from 6 what happened
PD - she wanted to put them somewhere easily accessible for her
JR - where PD - her work area docs/med/workarea
Fifer : osha beastie min. Here's the hing. If JR hinks it's mair important tae shite in IT #2's cornflakes than tae get ahead of the story ae why the disclosure procedure looked like a dropped kebab... then ah huv tae suspect that their ane witness had done them mair damage then shittin the bed instead ae doing proper disclosure.
JR - can you help with whether these we were looking at were accessed during your meeting
PD - after they were created, they were pulled at the time of the call
JR - sc sh 4 - dates rh column what are they
PD - creation of downloads
JR - date
PD - 16th may on the call 11:24-11:40
JR - comment on sc sh not taken during call?
PD - they were taken during call
CE - hello, I'm asking qu for SP, pick up first on quandry version hist dates showing creation 26th Oct. you say no tech explanation
PD -not that I'm aware of
Fifer : careful answer duly noted (peers ower glesses at screen)
CE - 1645 - sc sh of file location
PD - yes
CE - these html are useful at face value
PD - yes
CE - last portion of html gives creation date
PD - yes
CE so we look at this, subject toit bein editable, face value, that's the date
PD - yes
NC has deployed the Young Team. I think it's always good to give them a run oot, and it's quite possible CE has slightly better Tech Chops here.
CE - 1659 - these shots they purport to demo other similar errors going on
PD - yes, they highlight creation on 26th Oct in google, but genuine belief they were earlier, it's context.
CE - sync base explanation thats DU's explaination
PD - yes, in a forensic capacity i could
Fifer : (sarcastic posh voice) oooooh in a forensic capacity. Sorry mlaird, canny help masel sometimes ken?