I've been tinkering with Python all day today... it's pretty slick. Just for practice, I tried to cobble together a tripcode decoder that would let you have "real" words in your tripcode as !WAHa and Sling and others do, and it actually came out better than I thought it would be. I'm aware there's already a program that does this, but if memory serves me, it's Windows-only and in Japanese besides. My script is kind of dumb in the way it goes about things -- it basically just tears through random strings until it finds one that fits -- but I've tested it repeatedly and it seems to work. If you'd like to check it out, nab it here:
http://www.anre.org/crap/detripper.bz2
Of course, you may need to modify the hashbang line depending on where Python is on your machine, and don't forget those execute bits, people... Use "-h" for help.
First person to ask how to get this to run on Windows gets pointed and laughed at.
Fyi, trip explorer is not the fastest anymore (though it does offer a gui)
MTY for ATI is multithreaded (like trip explorer) AND uses ATI stream compatible graphics cards.
Intel Core 2 Quad Q8200 @ 3Ghz is doing 13.8Mtrips/s, while the ATI 4850 is doing 63.75Mtrips/s
I'm currently trying a case sensitive seven character trip. I'll report back with the time it takes.
>>623
if you just output all tripcodes, you can generate tripcodes on one core and grep on another, instead of doing both on one core.
It won't be faster. It's more expensive to fill the queue between threads with generated tripcodes than it is to just filter them in the first place.
>>627
of course it's more expensive, but is it twice as expensive? you do get almost twice as much processing power that way...
but obviously the real solution is to filter them in the first place and do that in multiple threads or processes.
> of course it's more expensive, but is it twice as expensive? you do get almost twice as much processing power that way...
You don't use all of it, because the tasks are unequal (one is faster)…
> but obviously the real solution is to filter them in the first place and do that in multiple threads or processes.
…which is why you can should that, yes. OpenCL looks pretty convenient for this, it seems like it can be made to run well even without having to write bitslice algorithms.
virus
>>213
That doesn't work, as you need the des library that it's trying to include. It just gives you compile errors.
Kyon
testing
last testing@2
1
831
>>649,652-654
wtf is this shit? incompetent spammers?
>>655
You missed >>630-634,636-646,650-651.
For some reason this thread's become a retard magnet.
>>656
i think i just heard that someone wanted me to post ITT
http://github.com/astrange/tripper
Lots of minor cleanup changes just because I don't like my old code, no actual feature changes. forking (or rewriting it to be reentrant and threading…) is the obvious next step, that and being able to search SJIS strings.
fag
bump
test
boxxy
sd
,.....
'll even pretend to believe that you don't like furry for the ENTIRE thread
Hanstanding ?! Oh Yeahhh
Roni
dfdf
>>676-684
are people really that stupid, or is there some sort of broken spambot making posts like that everywhere there's any thread with "tripcode" in the title?
asd