 | | Re: Very strange server behavior today
|
|
As a follow-up to the original announcement, I would like to let everyone know that the "visitor" who basically jammed the NNTP service came back this morning. Since nothing else seemed to help, I had to block out his or her IP range entirely from (...) (17 years ago, 25-Aug-08, to lugnet.admin.general)
|
| |
| | Re: Very strange server behavior today
|
|
(...) One solution would be an FTX enabled news reader. There is no reason why a news reader could not process the FTX. Another thing a customized Lugnet newsreader could do is post via the web interface. I don't think it would be too tricky to get (...) (17 years ago, 25-Aug-08, to lugnet.admin.general)
|
| |
| | Re: Very strange server behavior today
|
|
(...) I've solved the read vs. unread issue by reading LUGNET via RSS & Google reader. There's not enough traffic on LUGNET to prevent me from reading it via RSS now (the traffic has dramatically dropped since Peeron introduced the RSS feed). And I (...) (17 years ago, 25-Aug-08, to lugnet.admin.general)
|
| |
| | Re: Very strange server behavior today
|
|
(...) Thanks for your suggestions (all of you) - actually an FTX-capable news reader might be something we'd need an idea of the actual demand for. I'll take your suggestions into account and we'll see what we can make of them. There are also some (...) (17 years ago, 25-Aug-08, to lugnet.admin.general)
|
| |
| | Re: Very strange server behavior today
|
|
(...) The easiest solution would be to convert FTX in NNTP message files into HTML; most NNTP browsers understand embedded HTML. And then rewrite the web-posting modules to convert FTX to "safe" HTML (ie. rejecting JavaScript injection or other (...) (17 years ago, 25-Aug-08, to lugnet.admin.general)
|
