| Time |
Nickname |
Message |
|
00:20
🔗
|
JesseW |
the blocking worked at passing the bitly claims that were stuck; trying unblocking for a sec, then reblocking to see if that works well |
|
00:20
🔗
|
JesseW |
unblocked |
|
00:21
🔗
|
JesseW |
and blocked again -- we'll see how this goes |
|
01:49
🔗
|
|
toad1 has joined #urlteam |
|
01:50
🔗
|
|
toad2 has quit IRC (Read error: Operation timed out) |
|
01:57
🔗
|
|
VADemon has quit IRC (Quit: left4dead) |
|
04:43
🔗
|
Atluxity |
Anything I should do? |
|
04:46
🔗
|
JesseW |
Atluxity: I dunno. |
|
04:47
🔗
|
JesseW |
Atluxity: whatever research/experiments you can do to see what the reputation of your IP range is, would certainly be informative. |
|
05:39
🔗
|
|
W1nterFox has joined #urlteam |
|
05:44
🔗
|
|
WinterFox has quit IRC (Read error: Operation timed out) |
|
05:56
🔗
|
JesseW |
hm, it doesn't seem to be anything specific to Atluxity; unblocking |
|
05:56
🔗
|
JesseW |
I'll try just lowering the queue sizes on bitly and tinyurl *more* |
|
05:57
🔗
|
JesseW |
tinyurl is already at *5* and still complaining. wth |
|
05:59
🔗
|
JesseW |
maybe they're doing honeypots? |
|
05:59
🔗
|
JesseW |
but it's not that -- other claims seem to be going through fine |
|
08:56
🔗
|
|
JesseW has quit IRC (Leaving.) |
|
13:16
🔗
|
|
VADemon has joined #urlteam |
|
13:58
🔗
|
|
W1nterFox has quit IRC (Remote host closed the connection) |
|
17:15
🔗
|
|
chazchaz has quit IRC (Read error: Operation timed out) |
|
17:20
🔗
|
|
chazchaz has joined #urlteam |
|
17:20
🔗
|
|
svchfoo3 sets mode: +o chazchaz |
|
17:37
🔗
|
|
JesseW has joined #urlteam |
|
17:37
🔗
|
|
svchfoo1 sets mode: +o JesseW |
|
17:40
🔗
|
|
JesseW has quit IRC (Client Quit) |
|
18:34
🔗
|
|
VADemon has quit IRC (Read error: Operation timed out) |
|
20:09
🔗
|
|
will has joined #urlteam |
|
21:19
🔗
|
|
dashcloud has quit IRC (Read error: Operation timed out) |
|
21:23
🔗
|
|
dashcloud has joined #urlteam |
|
21:23
🔗
|
|
svchfoo1 sets mode: +o dashcloud |
|
22:58
🔗
|
|
WinterFox has joined #urlteam |