That's pretty much where I am with all this. My reasoning:
•We all know that redactions coming out of the FIB have been flagrantly excessive for years and, often times harmful to the public interest.
•Therefore, someone, or a group of persons who are responsible for creating those redactions must [logically] be performing, and/or ordering those redactions to be made. Most likely imo, a boss directing underlings.
•Federal govt. career employees are notoriously difficult to remove from their jobs without overwhelming evidence of wrongdoing to support any employee removal efforts.
Based on the above ideas, I can imagine a scenario whereby certain FIB employees have deployed "cut&paste redactions" to expose the fact that some redactions are excessive, not required, and violate protocol criteria.
Something like this as an example:
Embedded FIB swamp boss tells employee: "I need you to redact XYZ, off of these files, and pics- no questions, Capiche?" FIB underling: Sure thing boss. ... proceeds to 'follow orders' by redacting with "Cut&Paste redactions," ensuring that questions will be raised, and evidence of wrongdoing by embedded Swamp Boss will finally be exposed.
May “cut and paste” was part of the plan.
Of course it was. Thats why DOGE got rid of the Adobe licenses, kek.
That's pretty much where I am with all this. My reasoning:
•We all know that redactions coming out of the FIB have been flagrantly excessive for years and, often times harmful to the public interest.
•Therefore, someone, or a group of persons who are responsible for creating those redactions must [logically] be performing, and/or ordering those redactions to be made. Most likely imo, a boss directing underlings.
•Federal govt. career employees are notoriously difficult to remove from their jobs without overwhelming evidence of wrongdoing to support any employee removal efforts.
Based on the above ideas, I can imagine a scenario whereby certain FIB employees have deployed "cut&paste redactions" to expose the fact that some redactions are excessive, not required, and violate protocol criteria.
Something like this as an example: