word, still haven't seen how useful the messaging will be.
I like ts because trump owns it ngl.. but there's stuff a place like this does that ts isn't.
I'm wondering if they are going to be partnering with someone like they did with rumble for that piece
imageboard. w/e. i'm drunk, fuckoff
if it is in the headpost, then you may want to read last bread to discern for yourself
this one rang muh bell. (snark ftw, kek)
>by kekbess who verified it on his own board when anons began reporting it
no.I had my board deleted.
I checked it here >>>/miku/249092
np. it worked out that that board is ded now. the posts are consecutive, kek!
or a sleeper
the creepiest part of this post is that he doesn't seem to understand that even saying that is like screaming"I AM COMPED AS FUCK"to any anon that has actually ...read the drops.
Especially the early qr ones where q did the tripless game.
where's the checklist? they are hitting them all.
>they are attempting to poison the well
>they acknowledge we are shifting the narrative, so they have to "sound like us" slightly in their posting so they can "pace" anons away from what we are actually saying
pretty much.
everytime i repost i get a few likes that i don't recognize. so i'll just keep staying the course :)
kek
q doesn't use tripcodes to auth. they us them as canaries.
eg- just because tripped q burned a trip here, does not preclude them commmunicating... at any given time.
they know we know the canary is dead and that's all that matters.
digits confirm, slippery slopes ahead
digits... kek...
test
oops
yep, all of the single whack ones are irrelevant to the convo
KEEEEEEEEEEEEEEEEEEEEEEEK
IT'S ALSO SECURE IN NAME ONLY, LIKE A RINO.
ahem.. i'm not retyping that.
>I meant in the context of tripcode generation anon
for a single whack, there are passcode generators omline. so in the context of tripcode generation and this discussion, they are a fucking joke that is bordering on resource wasting to even bring into the current discussion about the current tripcode breach.
>we have already tested with all the past single # Q passwords, looks like NO they do not change with salt rotations
no shit.
>well, a whole bunch of anons noticed their tripcodes change with that fucky situation on friday
no shit.
>should EVERYONES IP hash change when salt rotates?
yep
>is that standard practice?
do you think 8kun is the only site that uses salt? kek.
>IP address hasing uses the secure salt that actually" rotates?
on a non-comped site, yes.
they invited me to leave their comments a few days ago.
>Jim was being honest and they really did accidentally do it.
It still makes his opsec horrible because:
1) salt, no matter which server it is on, is single-use when used correctly. secops 101
if they migrated the dev salt accidentally, they should have
2a) left it that way and made a new salt for the dev server.
OR
2b) discard ALL hashes and start over, with a general announce.
3) you DO NOT save copies of the salt. ever. again, that is secops 101.
So it's really hard for me to believe this was not knowingly done.
dubs confirm, it is complete comped.
babylon bee is best bee
the network id is what will have the info. in the packets.
o7