1 / 20
Decoding The Puritycpl Leak: Understanding The Data - cc6aetx
2 / 20
Decoding The Puritycpl Leak: Understanding The Data - j7pfj3a
3 / 20
Decoding The Puritycpl Leak: Understanding The Data - nrthlpb
4 / 20
Decoding The Puritycpl Leak: Understanding The Data - k5qroz2
5 / 20
Decoding The Puritycpl Leak: Understanding The Data - nlaf5ip
6 / 20
Decoding The Puritycpl Leak: Understanding The Data - 8xvgt2q
7 / 20
Decoding The Puritycpl Leak: Understanding The Data - hcjxzxp
8 / 20
Decoding The Puritycpl Leak: Understanding The Data - eboqocr
9 / 20
Decoding The Puritycpl Leak: Understanding The Data - 9gdpkoe
10 / 20
Decoding The Puritycpl Leak: Understanding The Data - bmhoiy1
11 / 20
Decoding The Puritycpl Leak: Understanding The Data - le7wb4k
12 / 20
Decoding The Puritycpl Leak: Understanding The Data - gl1nqaz
13 / 20
Decoding The Puritycpl Leak: Understanding The Data - djhfqi0
14 / 20
Decoding The Puritycpl Leak: Understanding The Data - szkypko
15 / 20
Decoding The Puritycpl Leak: Understanding The Data - m7364ys
16 / 20
Decoding The Puritycpl Leak: Understanding The Data - 7osttvl
17 / 20
Decoding The Puritycpl Leak: Understanding The Data - gg1qxzw
18 / 20
Decoding The Puritycpl Leak: Understanding The Data - s5zo85h
19 / 20
Decoding The Puritycpl Leak: Understanding The Data - sz6t0yf
20 / 20
Decoding The Puritycpl Leak: Understanding The Data - ttx5862


While i know some members of the dtg community are checked out of discussion on the lab leak, i have been enjoying following the various threads of the story and was pleased to hear.