Hey Xarn, apply this patch!

--- progscrape.py    2010-07-26 13:42:46.000000000 +0200
+++ /tmp/progscrape.py    2010-07-27 11:00:18.991885078 +0200
@@ -299,8 +299,14 @@
 
 
         if verify_trips and len(tripv) > 0:
+            # We get 403 with long URLs
+            # if too many trips to check, fetch the whole thread
+            tripv_url = read_url + thread[0] + '/'
+            if len(tripv) < 200:
+                tripv_url += ','.join(tripv)
             try:
-                hp = urlopen(read_url + thread[0] + '/' + ','.join(tripv))
+                hp = urlopen(tripv_url)
 
             except:
                 print "Couldn't access HTML interface to verify tripcodes.",\


This will solve the 403 errors.

>>31
Hey, that's like a less readable, slower version of Xarn's, except that it's not as easy to distribute over a cluster, suffers from NIH syndrome, and doesn't compile.

slower
not as easy to distribute over a cluster
doesn't compile
Obviously false.

less readable
Completely subjective.

NIH syndrome
I don't think that means what you think it means.

>>39
Completely subjective.
Hello, FV.

>>39
It's slower because they both use OpenSSL's DES_crypt, but Xarn doesn't wrap his in superfluous crap, doesn't unnecessarily generate a completely random string (with associated function calls; the attempt at inlining doesn't actually inline those functions) for every iteration, and doesn't use regexes by default.

It's not as easy to distribute over a cluster because processes are just easier to distribute than threads. That's a fact of life.

It doesn't compile because it inexplicably doesn't use POSIX regexes.

Readability can be subjective when comparing, say, K&R indentation to Sun indentation. It isn't when comparing K&R indentation to whatever ridiculous Lisp-wannabe style that piece of shit uses.

As far as NIH syndrome goes, random number generation is one thing C has a plenty of options for, but he still chose to implement a silly knock-off.

It's slower because they both use OpenSSL's DES_crypt, but Xarn doesn't wrap his in superfluous crap, doesn't unnecessarily generate a completely random string (with associated function calls; the attempt at inlining doesn't actually inline those functions) for every iteration, and doesn't use regexes by default.
there are very good reasons for generating a random string. this has been discussed extensively on other boards. the fact that your compiler is shit doesn't mean that every compiler is.

It's not as easy to distribute over a cluster because processes are just easier to distribute than threads. That's a fact of life.
you obviously didn't look at it:
Usage: %s [-c] [-p processes] [-t threads] [regex]

It doesn't compile because it inexplicably doesn't use POSIX regexes.
pcre is faster and more useful than any free implementation of posix regexes.

As far as NIH syndrome goes, random number generation is one thing C has a plenty of options for, but he still chose to implement a silly knock-off.
name one that's as fast as that and has a period at least as long.

>>42
Are you trying to become the new FrozenVoid?

>>43
Are you?

>>43
At least FrozenVoid was entertaining. Hotaru is just petty and obnoxious.

>>42
name one that's as fast as that and has a period at least as long.
No, no, that's not how it works - you're meant to do that, otherwise you're just pulling ⁶⁶arguments⁹⁹ out of you're anus.