Looks like it was just a server configuration issue with slashdot.  For a
while, they weren't accepting HTTP 1.0 connections, only HTTP 1.1.  But it
seems to be fixed now, and slashpluck seems to be working fine again.
-- 
Jason Day                                       jasonday at
http://jasonday.home.att.net                    worldnet dot att dot net
 
"Of course I'm paranoid, everyone is trying to kill me."
    -- Weyoun-6, Star Trek: Deep Space 9
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list


Reply via email to