I've been working on this for a while, but essentially, with secure tripcodes, if you get to know the user and the site's salt for secure trips, you can get it.
My Tinychan tripcode was ##Espeon. Seriously, with secure tripcodes, it's more commonly a word than a jumble. Vanity trips (@155,957, (Born this Way !dLadyGAgAA)@155,955 (!JuMPb0dbaE)) are harder, though.
protip !!pMmAiEwOm joined in and replied with this 15 years ago, 30 minutes later, 38 minutes after the original post[^][v]#155,984
Yea. Duh.
hamfist !!mtq555+/1 replied with this 15 years ago, 4 minutes later, 42 minutes after the original post[^][v]#155,987
My trip is ##boner
(Edited 26 seconds later.)
!!mtq555+/1 joined in and replied with this 15 years ago, 16 minutes later, 59 minutes after the original post[^][v]#156,007
wat
!!mtq555+/1 joined in and replied with this 15 years ago, 50 minutes later, 1 hour after the original post[^][v]#156,097
123
naimj joined in and replied with this 15 years ago, 24 minutes later, 2 hours after the original post[^][v]#156,115
my trip was #pizzaday
Anonymous K joined in and replied with this 15 years ago, 34 minutes later, 2 hours after the original post[^][v]#156,175
@155,960 (vocalon !!jdS+H4VgV) > but essentially, with secure tripcodes, if you get to know the user and the site's salt for secure trips, you can get it
If you know the method the site is using to create secure trips, then sure. For instance, if the site is using the standard crypt() to generate trips you can get an example of the site's output for a sample input (let's say #password secure trips to JF9JC7Shec) and then try to brute force the salt by encoding "password" with different salts and looking for a match. Then you would still have to run a dictionary attack, search, or whatever over those trips to find the user's trip.
If the site uses some unknown or batshit insane method to generate secure trips, then you would have to find out what method they were using to generate them before beginning an attack on the password.
ltamake !3vZ7A06glM joined in and replied with this 15 years ago, 2 minutes later, 2 hours after the original post[^][v]#156,178
Dictionary attack, mang.
notamake !3vZ7A06glM replied with this 15 years ago, 6 minutes later, 2 hours after the original post[^][v]#156,185
ltamake !!onnLC5KY8 replied with this 15 years ago, 25 minutes later, 3 hours after the original post[^][v]#156,194
Wololo...
New trip then.
vocalon !!jdS+H4VgV replied with this 15 years ago, 1 minute later, 3 hours after the original post[^][v]#156,195
@previous (ltamake !!onnLC5KY8)
What was it before?
Anonymous K replied with this 15 years ago, 5 minutes later, 3 hours after the original post[^][v]#156,196
@156,194 (ltamake !!onnLC5KY8)
Don't worry too much. I've known that one since you were using it on t4c. (and maybe back on 888?) I'm not about to run around impersonating you.
ltamake !!onnLC5KY8 replied with this 15 years ago, 5 minutes later, 3 hours after the original post[^][v]#156,197
@previous (K)
I know. I've had that tripcode since about TC 2.0 (when I first started tripfagging). It needed to be changed anyway. ;P
dreamworks joined in and replied with this 15 years ago, 5 hours later, 8 hours after the original post[^][v]#156,319