bookmark_borderThe Smoking Gun

So, thanks to a PACER alternative, I now know Keith A. Becker (“Becker”) is absolutely guilty of prosecutorial misconduct in my case. In other words, I can now prove, with his closing argument from another case, that Becker knew he was lying in my case.

It’s important to understand exactly what misconduct occurred. First misconduct was obtaining a fraudulent search warrant for TB2 that was also void ad initio. (Void on its face because the magistrate wasn’t allowed to issue it on November 18, 2012.) This search warrant was fraudulently obtained because it based it’s “probable cause” on evidence Becker knew, or should have known didn’t exist. (As I explained in this post)

Second act of Becker misconduct concerns his use of that fraudulently obtained data to fraudulently obtain an indictment in Nebraska as explained in this post.

Third act of misconduct concerns his denial of malfeasance. As I explained extensively in this post, Becker knew he was caught in November of 2014 but instead of folding he doubled down.

Now, I’m trying to pin down the details of the conspiracy. As I noted in this post, the shills refuse to answer questions. None of the lawyers will answer my questions and the FBI is stonewalling.

I found this tidbit on the pacer alternative:

The judge has instructed you. It’s knowingly accessing with intent to view a computer disk of other material. What do we mean in this context? We mean [the] web server. That server was located here in Omaha. That sever had on it all the [contraband] images that were available on [the] website. That’s [what constitutes] the computer disk or other material.

And that the defendant knew that it contained [contraband]. Well, how do you know that? Well, you’ve seen the records of the defendant’s conduct. You’ve seen the screen shots of the site and what it looked like to its users and members. And you’ve seen what the defendant saw each day that he went and accessed these particular materials.

Now, again on the access with intent count [sic], ladies and gentlemen, you’ve got a guide. And your guide to these counts is [sic] Exhibits 5A through D and 6A though D…

5A through D are portions of that board data, the logs, that exist for the defendant’s conduct for November 18th until December 8th [2012]…

We’ve got a portion of Exhibit 5A broken up on the screen here. On the top part, we see the date and time. We’ve heard a lot about UTC, Universal Coordinated Time [sic]. It means the user took an action and that’s the time that the website recorded it…

We see the session identifier. Now remember the testimony of Special Agent Gordon, Special Agent Smith. A session ID is an individual, unique identifier for on particular session on the board.

What’s a session? Log-on to log off. One session, one unique series of characters just like you see on the screen.

Becker closing arguments 8:13CR105 Docket # 236 Pages 133 & 134

And I found this in my filing cabinet:

B. “Modified Tinyboard Application that Ran TB2” … 6. “TB2 servers apache access logs.” As we previously informed you via e-mail, Apache logs were not utilized to correlate website and NIT Data.”

Becker message to Howard on July 20, 2015

And I have this Becker quote from my withdrawal hearing:

And so the government was in control of the website TB2 and that means there are logs of activity from that website. That’s one batch of evidence. And some of the government’s evidence comes from those logs, including Apache logs which Special Agent Smith testified about at our last hearing. Then there is also information that is generated and collected via use of the NIT, and that’s a separate batch of information.

Becker statement on 12-16-2015

Now, combine those three quotes and compare them to the fact that Tinyboard doesn’t have any logs and you have a very easy perjury conviction. Now I’m trying to get exhibits 5A through 5D from the court and trying to get the shills to answer my questions (trying to hire a lawyer to ask them those questions on their stationary.

I’ll keep y’all informed…

bookmark_borderA Simple Analogy

  • Parking Lot = Tinyboard
  • Parking Garage = PHPBB
  • Cars = Browsers
  • Ticket IDs = Session IDs
  • Ticket Booths & Cameras = Computer Logs

OK, so when the cars enter Tinyboard’s parking lot or PHPBB’s garage, they’re issued a Ticket that has a unique ID number. This ticket also has location technology such that the ticket records its location when it stops moving. Camera’s take a picture of the cars license plates so the the booth can pull information about the cars entering the lots from the DMV and enter it into its logs.

So, for example, when someone driving a Ford Mustang enters Tinyboard’s parking lot, it gets a ticket with ID 100 and it proceeds to park in parking spot 2. So the ticket begins it’s log (ID 100 in Parking Spot 2). A similar circumstance happens in PHPBB’s garage, someone driving a Chevy Camaro is issued a ticket with ID 1000 and in proceeds to park on level 2 parking spot 10, so the ticket begins its log (ID 1000, on level 2 in parking spot 10)

This brings us to Mr. Becker’s second act of misconduct. Our Camaro driver decides he doesn’t like spot 10, and movs to spot 20. PHPBB’s ticket makes another log entry (ID 1000, Level 2, Spot 20). Our Mustang driver also moves from spot 2 to spot 12. BUT, Tinyboard’s ticketing system does something odd, it changes its ticket ID when it makes another log entry (ID 200, Spot 12).

So, imagine it was illegal to park in these places at the time the above parking occurred. When the cars leave, the ticket booths record all the information on the cards and ties them to the data linked to their plates. Now as explained above, PHPBB’s ticket booths are actually keeping business records and Tinyboard’s booths are not, they are collecting information solely to prosecute illegal parkers. So the ticket booth logs look like this:

Lot NameTicket IDTime InFloorSpotCar TypeTime Out
PHPBB100012:01:30210Camaro
PHPBB100012:03:20220Camaro
PHPBB100013:00:10
TINYBOARD10012:01:3012Mustang
TINYBOARD20012:03:20112Mustang
TINYBOARD30013:00:10

Now, if you happen to know how these ticketing system logs are supposed to look, you see a glaring anomaly with Tinyboard’s logs. The Ticket is changing its ID with every move, when it shouldn’t. PHPBB’s log looks legitimate, it says the Camaro got a ticket and parked in spot 10, then moved to spot 20, then left the garage about an hour later. Tinyboard’s log says the Mustang parked in spot 2, then left without registering, then returned and parked in spot 12, then again left without registering, then returned and left immediately. As anyone can see, that log is nonsensical.

Now, when you bring it to the parking lot’s prosecutors attention, he fails spectacularly at explaining the anomaly and you request all parts of the system to investigate. You find out that: 1) Tinyboard’s lot doesn’t have a ticket system and 2) the prosecutor installed the system solely for prosecution and 3) the prosecutor has destroyed the ticket booth and camera log computer!