Since there’s 78 pages, I’m guessing at least 1 ambiguity per page? Anyways, it’s dreadfully big.

I tried to leave a comment, but it doesn’t seem to be showing up there.

I’ll just leave it here:

too tired to look into this, one suggestion though - since the hangup seems to be comparing an L and a 1, maybe you need to get into per-pixel measurements. This might be necessary if the effectiveness of ML or OCR models isn’t at least 99.5% for a document containing thousands of ambiguous L’s. Any inaccuracies from an ML or OCR model will leave you guessing 2^N candidates which becomes infeasible quickly. Maybe reverse engineering the font rendering by creating an exact replica of the source image? I trust some talented hacker will nail this in no time.

i also support the idea to check for pdf errors using a stream decoder.

If you have nvme use secure erase first.

the only appreciating asset I own are the several 1-2 TB SSDs I have lmao

my direct supervisor has showed me what information he has access to w.r.t. wireless client information, such as client position.

My first thought would be how that is even possible, but given the fact that we record the location of each AP install, this makes a lot more sense.