Anonymous ID: 321d00 Jan. 9, 2019, 3:17 p.m. No.4685644   🗄️.is 🔗kun

>>4685598

And it’s only Jan 8. I suspect that number would likely be higher in a couple of weeks, if the shutdown continues.

 

The GOP is NOT /our party/

Anonymous ID: 321d00 Jan. 9, 2019, 3:23 p.m. No.4685730   🗄️.is 🔗kun

>>4685572

This is how it’s going to be, folks.

 

I think we need to pay close attention to GOP voting and make noise.

 

The House roll call website does its best to make compiling lists of names and congressional districts a pain in the ass, but it’s worth it: these MOFOs need to start realizing their voting record on important litmus tests of loyalty are being watched.

Anonymous ID: 321d00 Jan. 9, 2019, 3:45 p.m. No.4686064   🗄️.is 🔗kun

>>4685779

I seem to recall that all of the claims and counter claims were settled under the supervision of Hellerstein anyway. There was pressure to settle out of court.

 

The documents in layers 1 and 2 are exactly what you’d expect in the early stages of major insurance litigation - mostly casting around for responsible parties to stump up cash to offset the insurers’ payouts.

 

Every document I’ve reviewed quickly [most] treats the official story as the way it all went down. I expect little more from the balance of documents, but you never know.

 

I’d hope to see some papers questioning the manner of destruction and the identification of responsibility; but if such questions were entertained at any stage they’re unlikely to have passed across the wires or today be sitting on a server.

 

I doubt anyone has anything to fear from disclosure of these papers, which is why the hackers weren’t paid off immediately or otherwise sorted out.

Anonymous ID: 321d00 Jan. 9, 2019, 3:50 p.m. No.4686145   🗄️.is 🔗kun

>>4686038

No. Terrible idea.

 

Bill Still made a video last year setting out, rather well, the many reasons why the Article V procedure could lead to unintended outcomes.