Please log in. To create a new account, enter the name and password you want to use.
If you supplied an email address when you signed up or added a email later, you can have your password reset.
This user name doesn't exist. If you want to create a new account, just verify your password and log in.
This user name exists. If you want to create a new account, please choose a different name.
Enter the current email address you have registered in your profile. You'll get an email containing your new password.
You have no email address in your profile, so you can't have your password reset.
Password reset. Check your email in a few minutes
That account does not exist.
The email address specified is not registered with this account.
Delivery to this email address has failed.
I use resize almost every time, but it makes images look like crap in the browser, and doing it in advance (with a real resizer, not firefox's dumb one) would look much better.
Bandwidth is cheap, but it still takes 10-30 seconds for me to load most images (750k/sec line, but I usually get about 200k/sec here), and it still turns Firefox into a slow beast after doing it for a while. It ends up taking 400 megs of memory--even when no images are still loaded--and every tab click takes seconds to happen, and I'm not holding my breath hoping FF3 will fix this.
I guess the MD5 of the semi-thumb (still havn't thought of the right word) could be stored with the original post, so it could be checked on upload, too, though of course getting a good heuristic dupe checker is the real fix. (Has piespy released his image search stuff/tweaked imgseek? I wonder if anyone's working on integrating that for a dupe checker, I know there's been a lot of talk of it. I guess the GPL is why rq won't integrate it into trunk.)
I didn't understand "other problem"--what was the first problem?
If I can make it work with simple dupe checking, and nobody thinks of any more serious problems with the idea, would you consider it if I implemented it? (Seems like a fun day project, but it's not interesting to me if you won't use it.) It'd make the site a lot easier to use.
petopeto
Bandwidth is cheap, but it still takes 10-30 seconds for me to load most images (750k/sec line, but I usually get about 200k/sec here), and it still turns Firefox into a slow beast after doing it for a while. It ends up taking 400 megs of memory--even when no images are still loaded--and every tab click takes seconds to happen, and I'm not holding my breath hoping FF3 will fix this.
I guess the MD5 of the semi-thumb (still havn't thought of the right word) could be stored with the original post, so it could be checked on upload, too, though of course getting a good heuristic dupe checker is the real fix. (Has piespy released his image search stuff/tweaked imgseek? I wonder if anyone's working on integrating that for a dupe checker, I know there's been a lot of talk of it. I guess the GPL is why rq won't integrate it into trunk.)
I didn't understand "other problem"--what was the first problem?
If I can make it work with simple dupe checking, and nobody thinks of any more serious problems with the idea, would you consider it if I implemented it? (Seems like a fun day project, but it's not interesting to me if you won't use it.) It'd make the site a lot easier to use.