Great.
Not it's:
>Ha ha Q dropped on QR
VS
>Ha ha Q dropped on HM
When it should be call your shot no doubt about it 0-delta verification or bust.
Watching the legacy of the whole Q operation go up in smoke like this is both funny ha ha and funny sad.
But, mostly the latter.
Yeah, I'm going to work my way towards the ha ha side of things.
If the Real Q and Q+ dgaf that it's devolving into the absolute state of all absolute states then why should Ii?
I myself have no interest in competing Fake Q LARPs especially when everyone is shitposting them non-stop via TOR now.
Deltas are bound to accidentally happen.
Rock solid verification or GTFO.
Even @Q has moar cred these days since at least he's on PDJT's site and is bffs with Dan, Kash, Devin, etc.
So, legit verification + @Q saying bye bye you don't need me anymore since the real thing is back is what will do it for me.
>no possibility of a white listed trip
Concur.
The whole whitelist thing has been a farce.
It's just a who can TC post on this board/site and who can't process.
And CM's supposed magic whitelist that would allow Q to bypass the Salt after a rotation is the most cringe of all.
If any bypass code for Q exists it's that hey man just enter password123 and I'll hardcore Q's TC for you special custom TC code.
The current bread on QR is Comms Absolute Panic time.
The banhammers and deletion vacuums have been deployed.
Don't miss out must see TV....
None of the Q's flying all around lately have been worth a shit compared to OG Q.
Including Jim's hardcoded TC Q.
Salt/Tripcodes and Whitelist Basics
Salt/Tripcodes
Think of Salt as a TC generation engine.
You supply it a password and it outputs a unique string.
If the engine changes (rotation) then a different string will get generated by your password.
That string is what displays when you post using a TC.
Whitelist
This is just a listing of TCs that you allow to post on your board.
If your string is in there you're good to go.
If not then you can't post using a TC there.
Custom Tripcode Logic
That's what Freddy Crip said is in place to be used if the site admin wants to.
It's what I think they're using to get Q's old TC to display.
Basically, when a special password is entered it will use a hardcoded TC that they setup to be the same as Q's.
Now they could do that obviously without touching the Salt at all since it's a hardcoded process.
But, on Friday they rotated the Salt.
Why?
These people are stupid.
OR
They wanted to lock out Real Q from using his normal pwd/TC in case he logged in right away and called them out.
Either way, if they hadn't rotated the Salt like they did they never would have been busted so easily.
So, thankfully they did it for whatever reason.
Here's the deal.
They don't know Q's password.
So, the only ways to keep Q from getting the old TC is to:
Lock everybody out of the Salt process so only their hardcoded TC is used.
Rotate the Salt so that Q's password won't generate the old TC.
Comms Baker.
Prolly still has the record for most breads baked, but maybe Gerbil is closing in now.
Had many classic board war battles with OSS and some of the rest of us that frequent this board.
Kekbee's bff (I kid, I kid).
Then there's this anon.
I dgaf if new Q is a MOS op in a desperate attempt to set things up to J6 everyone here.
The breads are flying again so everyone should give new Q a giant thank you.
I vote to get rid of it entirely.
Ok, here we go.
The claim now (days later) is that 2 Salts were maintained.
Old one just for Q workaround.
New one for everyone else.