>>22213

Guessing you were wrong.

>>22286

MAGAPill. He tweeted it. Thin iirc, he deleted it.

>>22302

You were wrong. And you never had a conversation with Q

>>22346

Server got overloaded from all the attention iirc

>>22401

I honestly don't remember WHERE I read that, tbh. It was awhile back, though.

>>22519

I actually had one last night I could only see the top line of. It was the one about how well you would sleep if you knew everything. An awesome anon posted a screencap for me. Could never understand why I could see he'd posted, but never could read it.

>>22521

No.

>>22603

Ummm. You DO realize that Q confirmed that, right?

>>22233

>>22719

>>22759

Nah, I just figured out why I couldn't see his post. I'd filtered someone + responses, and Q must have been responding to someone I'd filtered "ID+". Will have to rethink that for now and go back to filtering only "ID".

>>22759

Yes, but at this point, you have to refresh your screen after you filter. I've filtered "Lookie Lookie" in this bread for example. But I filtered him "ID=", because so many people were responding to him. So I wouldn't see all there responses and waste my time with all that, either. Betting it's why I couldn't see that one post from Q - He'd answered someone I'd filtered and the responses…