>>16521604 (pb)
I am 100% willing to be wrong about the previous 3 posts, anons, can we verify on another board that the salt (and therefore Q's trip) is the salt before Q made the new posts?
Where is the external confirm from DJT?
Source it? If the salt changed, than Q's trip should have too. Someone link to the other board where the trips are common… my tagging system is lagging… ah.. https://8kun.top/pen/res/1052.html
End of bread post, not playing by established rules… no DJT confirm… BV/BO we need some clarity, can you see when the salt changes? Cuz if it just changed AGAIN, and Q posted on the old trip… that's a no go. The trip should change and Q should follow the established protocol.
TY understood. Anons, the ID you get changes every bread, even when your IP does not. That is because there is an additional salt, that changes every bread I assume. but a board owner can see the thing that the ID gets generated from, which is what a board owner can see, and that is your IP hashed with the salt. What this anon said is his ip hash is now back to where is was on the other "new" q posts… indicating that again, these are not legit. Correct anon?
Also… "establishing comms" and then "established" with no DJT 0 deltas.
ah, checking… and I cant test directly keep getting 404 when I use ##something in the name field of https://8kun.top/pen/res/1052.html
cap on salt change
Keep pretending Q doesnt have many trips, each because the salt changed, each needing external verification. Whitelisting just means allowing a tripcode on a board that no others can use a trip on.
This is too obvious. Nobody is buying it. No external verification. Dan posts a babyfist.