Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #470591 > unrolled thread
| Started by | DFS <nospam@nospam.com> |
|---|---|
| First post | 2018-10-04 10:08 -0400 |
| Last post | 2018-10-10 10:36 -0400 |
| Articles | 20 on this page of 158 — 15 participants |
Back to article view | Back to comp.os.linux.advocacy
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-04 10:08 -0400
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-04 08:51 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-04 13:50 -0400
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-04 11:59 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-04 21:23 -0400
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 08:12 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 08:21 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 09:55 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-05 13:51 -0400
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 11:16 -0700
"Path:" is the only line that's never fake. Jeff-Relf.Me @. - 2018-10-14 01:41 -0700
Re: "Path:" is the only line that's never fake. "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2018-10-14 11:16 -0400
Re: "Path:" is the only line that's never fake. Steve Carroll <frelwizzen@gmail.com> - 2018-10-14 08:38 -0700
Re: "Path:" is the only line that's never fake. snipeco.2@gmail.com (Sn!pe) - 2018-10-14 16:40 +0100
Re: "Path:" is the only line that's never fake. "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2018-10-14 11:43 -0400
Re: "Path:" is the only line that's never fake. snipeco.2@gmail.com (Sn!pe) - 2018-10-14 17:12 +0100
Re: "Path:" is the only line that's never fake. "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2018-10-14 12:23 -0400
Re: "Path:" is the only line that's never fake. snipeco.2@gmail.com (Wader of Doom) - 2018-10-14 18:01 +0100
No one can do "a perfect forgery" of my posts. Jeff-Relf.Me @. - 2018-10-14 14:29 -0700
Re: No one can do "a perfect forgery" of my posts. "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2018-10-14 17:33 -0400
Re: No one can do "a perfect forgery" of my posts. snipeco.2@gmail.com (Sn!pe) - 2018-10-14 22:47 +0100
Re: No one can do "a perfect forgery" of my posts. "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2018-10-14 17:53 -0400
Re: No one can do "a perfect forgery" of my posts. snipeco.2@gmail.com (Sn!pe) - 2018-10-14 22:58 +0100
Re: No one can do "a perfect forgery" of my posts. Steve Carroll <frelwizzen@gmail.com> - 2018-10-14 14:56 -0700
Re: No one can do "a perfect forgery" of my posts. Steve Carroll <frelwizzen@gmail.com> - 2018-10-14 14:41 -0700
Re: "Path:" is the only line that's never fake. Steve Carroll <frelwizzen@gmail.com> - 2018-10-14 08:54 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-14 11:26 -0400
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-14 09:23 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-14 18:53 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-14 13:27 -0700
Re: slrn is trembling Melzzzzz <Melzzzzz@zzzzz.com> - 2018-10-14 20:55 +0000
Pipelining "Article" commands. Jeff-Relf.Me @. - 2018-10-14 14:23 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-15 13:49 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-15 07:34 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-15 21:54 -0400
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-15 19:15 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-15 21:51 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-16 03:16 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-15 20:33 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-16 10:26 -0400
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-16 07:44 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-16 15:17 +0000
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-16 12:26 -0400
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-16 09:46 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-16 10:21 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-16 14:00 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-16 16:49 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 12:35 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-04 20:44 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 14:09 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-04 14:50 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-04 22:32 +0000
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-04 23:03 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 16:28 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-04 16:54 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 00:02 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-04 17:20 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 17:31 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 00:32 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-04 17:41 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 00:54 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 18:02 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 01:07 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-04 18:11 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 18:48 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 02:06 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 08:01 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 15:35 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 08:37 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 08:53 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 08:57 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 09:17 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 09:19 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 09:41 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 16:19 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 09:23 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 16:40 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 09:41 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 17:39 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 11:07 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 18:14 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 11:41 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 18:52 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-06 08:46 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-06 11:29 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-06 11:48 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-06 11:51 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-06 12:19 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-06 15:34 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-08 21:27 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-08 17:49 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-08 18:13 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-09 07:31 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-09 13:45 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-09 07:55 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-09 15:55 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-09 09:20 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-09 09:39 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-09 09:41 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-09 10:23 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-09 23:38 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-09 17:47 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-09 11:09 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-10 09:04 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-10 13:56 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-11 05:02 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-10 10:33 -0400
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-10 19:21 +0000
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-12 20:46 -0400
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-12 23:50 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-08 18:44 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-06 14:08 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 11:32 -0700
Re: slrn is trembling "F. Russell" <fr@random.info> - 2018-10-05 00:32 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 17:46 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 00:55 +0000
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 01:17 +0000
Re: slrn is trembling chrisv <chrisv@nospam.invalid> - 2018-10-05 06:59 -0500
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 05:14 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 12:48 +0000
Re: slrn is trembling chrisv <chrisv@nospam.invalid> - 2018-10-05 11:17 -0500
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-05 13:35 -0400
Re: slrn is trembling Silicon Vee <siliconvee1945@yahoo.com> - 2018-10-11 01:36 +0200
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-04 17:07 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 00:12 +0000
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-04 17:21 -0700
Re: slrn is trembling SilverSlimer <silver@slim.er> - 2018-10-05 12:01 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 05:30 -0700
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 08:13 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-05 12:50 -0400
Re: slrn is trembling Steve Carroll <fretwizzer@gmail.com> - 2018-10-05 10:35 -0700
Re: slrn is trembling chrisv <chrisv@nospam.invalid> - 2018-10-10 08:51 -0500
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-10 07:09 -0700
Re: slrn is trembling Sam O'Nella <poison@donteatit.net> - 2018-10-05 16:43 -0400
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-10 10:34 -0400
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-10 07:56 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-10 12:38 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-11 02:12 -0700
Re: slrn is trembling Snit <usenet@gallopinginsanity.com> - 2018-10-12 12:27 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-12 12:42 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-12 21:47 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-14 03:28 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-12 20:45 -0700
Re: slrn is trembling Snit <usenet@gallopinginsanity.com> - 2018-10-05 15:15 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 15:41 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 19:21 -0700
Re: slrn is trembling Snit <usenet@gallopinginsanity.com> - 2018-10-05 13:44 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-05 17:48 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 17:15 -0700
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 16:13 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-04 20:47 -0400
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 01:09 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 18:18 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-04 21:38 -0400
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 19:04 -0700
Re: slrn is trembling owl <owl@rooftop.invalid> - 2018-10-05 02:05 +0000
Re: slrn is trembling Steve Carroll <frelwizzen@gmail.com> - 2018-10-04 19:35 -0700
Re: slrn is trembling DFS <nospam@nospam.com> - 2018-10-10 10:36 -0400
Page 3 of 8 — ← Prev page 1 2 [3] 4 5 6 7 8 Next page →
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-16 07:44 -0700 |
| Message-ID | <77edc67c-b1e9-4781-924c-2ac53da40331@googlegroups.com> |
| In reply to | #472316 |
On Tuesday, October 16, 2018 at 7:26:12 AM UTC-7, DFS wrote:
> On 10/15/2018 11:16 PM, owl wrote:
> > DFS <nospam@nospam.com> wrote:
> >> On 10/15/2018 9:49 AM, owl wrote:
> >>
> >>
> >>> See what kind of speed you get with this (redirect it to a file):
> >>> ------------------------------
> >>> #!/usr/bin/python
> >>> import socket
> >>>
> >>> # fill all these vars in:
> >>> SERVER=''
> >>> PORT=
> >>> USER=''
> >>> PASS=''
> >>> GROUP=''
> >>> FIRST=
> >>> LAST=
> >>>
> >>> s=socket.socket(socket.AF_INET,socket.SOCK_STREAM)
> >>> s.connect((SERVER,PORT))
> >>> s.settimeout(1)
> >>> s.send("authinfo user " + USER + "\r\n")
> >>> s.send("authinfo pass " + PASS + "\r\n")
> >>> s.send("group " + GROUP + "\n")
> >>> for x in range(FIRST,LAST,1):
> >>> s.send("article %d\r\n" % x)
> >>> while 1:
> >>> data=s.recv(512)
> >>> if not data: break
> >>> print data
> >>> s.close()
> >>> ------------------------------
> >>
> >>
> >> Writes 15-25 or so full articles to a file, then writes
> >> 430 No Such Article
> >> for the rest.
> >>
> >
> > Are you sure the article numbers in the range you provided
> > are actually available?
>
> duh on my part.
>
>
>
>
>
> >> Of those it writes, there's a blank line between each line of the post.
> >>
> >
> > For me, it properly writes the '.' article separator.
>
> I get all the data, including the article separator, but when writing it
> to a file there's a blank line written between each line of data.
>
> When printing to screen it's fine.
>
>
>
> #write all data to one file
> for x in range(FIRST,LAST):
> s.send("article %d\r\n" % x)
> with open("D:\\article_socket.txt", "w") as f:
> while 1:
> data=s.recv(512)
> if not data: break
> f.write(data)
>
>
> ~20 seconds for 1000 articles
>
>
>
>
> >> Throws error at the end:
> >> socket.timeout: timed out
> >>
> >
> > That's not an error. You have to have a timeout to break out
> > of the socket or it will sit and wait for input that never
> > comes.
> >
> >> Takes ~4 seconds for 100 requests.
> >>
> >> I assume you get better results.
> >
> > anon@lowtide:~/usenet$ time ./dah.py >pyout
> > Traceback (most recent call last):
> > File "./dah.py", line 19, in <module>
> > data=s.recv(512)
> > socket.timeout: timed out
> >
> > real 0m17.383s
> > user 0m0.348s
> > sys 0m0.472s
> > anon@lowtide:~/usenet$ grep ^220 pyout |wc -l
> > 4966
> > anon@lowtide:~/usenet$
>
>
>
> 5K in 17 seconds is about 5x faster than what I'm getting. I use
> blocknews server, and python on Windows.
Sadly this is what happens when seriously poor self esteem takes over Klaus Schadenfreude's life. It was Klaus Schadenfreude who was openly asking how better to post his scams. Already moved on from that. Keep up! His wish is to see Desk Rabbit annoyed by idiotic lying. And hey, that could work.
--
E-commerce Simplified!
https://youtu.be/HMx0RyzbPgQ
http://www.5z8.info/lemon-party-redux_v1o7pm_nakedgrandmas.jpg
http://prescottcomputerguy.com/screenflow
Jonas Eklundh Communication
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-16 15:17 +0000 |
| Message-ID | <uz8b083ga.ay@rooftop.invalid> |
| In reply to | #472316 |
DFS <nospam@nospam.com> wrote:
> On 10/15/2018 11:16 PM, owl wrote:
>> DFS <nospam@nospam.com> wrote:
>>> On 10/15/2018 9:49 AM, owl wrote:
>>>
>>>
...
>
>
>>> Of those it writes, there's a blank line between each line of the post.
>>>
>>
>> For me, it properly writes the '.' article separator.
>
> I get all the data, including the article separator, but when writing it
> to a file there's a blank line written between each line of data.
>
> When printing to screen it's fine.
>
>
>
> #write all data to one file
> for x in range(FIRST,LAST):
> s.send("article %d\r\n" % x)
> with open("D:\\article_socket.txt", "w") as f:
> while 1:
> data=s.recv(512)
> if not data: break
> f.write(data)
>
>
> ~20 seconds for 1000 articles
>
If you're actually still getting the '.' marker in the file, but
extra blank lines are being added, this may or may not be related:
https://sopython.com/canon/97/writing-csv-adds-blank-lines-between-rows/
So try adding 'wb' to the open() call.
But that open() should not even be necessary anyway. I just use '>'
redirection operator to write to a file. That will work in windows too.
./dah.py >outfile
or (without bash shebang):
python dah.py >outfile
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@nospam.com> |
|---|---|
| Date | 2018-10-16 12:26 -0400 |
| Message-ID | <ijoxD.495682$YL3.47569@fx48.iad> |
| In reply to | #472323 |
On 10/16/2018 11:17 AM, owl wrote: > If you're actually still getting the '.' marker in the file, but > extra blank lines are being added, this may or may not be related: > > https://sopython.com/canon/97/writing-csv-adds-blank-lines-between-rows/ > > So try adding 'wb' to the open() call. Even though I'm not using the cvswriter library, that fixed it, so thanks. > But that open() should not even be necessary anyway. I just use '>' > redirection operator to write to a file. That will work in windows too. > > ./dah.py >outfile > > or (without bash shebang): > > python dah.py >outfile That redirection works, but the output also has the alternating blank lines. https://imgur.com/a/r4KDU3R Only when opening the output file in 'wb' mode within the python code do I get valid results. The slow retrieval via blocknews is strange. It's always 20-30 seconds for 1000 articles. Tried it a few times with eternal-september. Consistently retrieves 1000 articles in 3.6 seconds! But ES only has cola - and most groups I think - going back to 2010. Blocknews goes back to Jul 2003 last I checked.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-16 09:46 -0700 |
| Message-ID | <2924eae7-1a06-48c8-a4d6-6d2a8b903635@googlegroups.com> |
| In reply to | #472339 |
On Tuesday, October 16, 2018 at 10:26:57 AM UTC-6, DFS wrote: > On 10/16/2018 11:17 AM, owl wrote: > > > If you're actually still getting the '.' marker in the file, but > > extra blank lines are being added, this may or may not be related: > > > > https://sopython.com/canon/97/writing-csv-adds-blank-lines-between-rows/ > > > > So try adding 'wb' to the open() call. > > Even though I'm not using the cvswriter library, that fixed it, so thanks. Seems like that's just the example there... 'wb' should work with any call to open where you're having this issue because that's what open does w/o it. > > But that open() should not even be necessary anyway. I just use '>' > > redirection operator to write to a file. That will work in windows too. > > > > ./dah.py >outfile > > > > or (without bash shebang): > > > > python dah.py >outfile > > > That redirection works, but the output also has the alternating blank lines. > > https://imgur.com/a/r4KDU3R Weird. > Only when opening the output file in 'wb' mode within the python code do > I get valid results. > > The slow retrieval via blocknews is strange. It's always 20-30 seconds > for 1000 articles. > > Tried it a few times with eternal-september. Consistently retrieves > 1000 articles in 3.6 seconds! > > But ES only has cola - and most groups I think - going back to 2010. > Blocknews goes back to Jul 2003 last I checked.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-16 10:21 -0700 |
| Message-ID | <2a5f05fa-24c0-4283-b48f-c57c4b854696@googlegroups.com> |
| In reply to | #472344 |
On Tuesday, October 16, 2018 at 9:46:28 AM UTC-7, Steve Carroll wrote: > On Tuesday, October 16, 2018 at 10:26:57 AM UTC-6, DFS wrote: > > On 10/16/2018 11:17 AM, owl wrote: > > > > > If you're actually still getting the '.' marker in the file, but > > > extra blank lines are being added, this may or may not be related: > > > > > > https://sopython.com/canon/97/writing-csv-adds-blank-lines-between-rows/ > > > > > > So try adding 'wb' to the open() call. > > > > Even though I'm not using the cvswriter library, that fixed it, so thanks. > > Seems like that's just the example there... 'wb' should work with any call to > open where you're having this issue because that's what open does w/o it. > > > > But that open() should not even be necessary anyway. I just use '>' > > > redirection operator to write to a file. That will work in windows too. > > > > > > ./dah.py >outfile > > > > > > or (without bash shebang): > > > > > > python dah.py >outfile > > > > > > That redirection works, but the output also has the alternating blank lines. > > > > https://imgur.com/a/r4KDU3R > > Weird. > > > Only when opening the output file in 'wb' mode within the python code do > > I get valid results. > > > > The slow retrieval via blocknews is strange. It's always 20-30 seconds > > for 1000 articles. > > > > Tried it a few times with eternal-september. Consistently retrieves > > 1000 articles in 3.6 seconds! > > > > But ES only has cola - and most groups I think - going back to 2010. > > Blocknews goes back to Jul 2003 last I checked. These degenerates get their jollies out of eliciting reactions to their attacks, which is the very definition of a troll. Nobody is being controlled by RMS. Mint's update system failed over and over again. Out-and-out drivel by an uninformed, tall-tale telling, scheming, conspiring lummox who would not tell the truth if his life depended on it. Klaus Schadenfreude is far too idiotic to write a Mint script. The only scripting he's capable of doing is copying code from online forums and claiming it as his own. Protected code is not enough to protect you. Can you cease seeking for my attention? -- Eight things to never feed your cat http://www.5z8.info/facebook-of-sex_w4l4wg_bomb http://www.5z8.info/boobs_j0v3qo_dont-just-drizzle Jonas Eklundh
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-16 14:00 -0700 |
| Message-ID | <ef091783-5882-451f-866d-617537e245bd@googlegroups.com> |
| In reply to | #472344 |
On Tuesday, October 16, 2018 at 9:46:28 AM UTC-7, Steve Carroll wrote:
> On Tuesday, October 16, 2018 at 10:26:57 AM UTC-6, DFS wrote:
> > On 10/16/2018 11:17 AM, owl wrote:
> >
> > > If you're actually still getting the '.' marker in the file, but
> > > extra blank lines are being added, this may or may not be related:
> > >
> > > https://sopython.com/canon/97/writing-csv-adds-blank-lines-between-rows/
> > >
> > > So try adding 'wb' to the open() call.
> >
> > Even though I'm not using the cvswriter library, that fixed it, so thanks.
>
> Seems like that's just the example there... 'wb' should work with any call to
> open where you're having this issue because that's what open does w/o it.
>
> > > But that open() should not even be necessary anyway. I just use '>'
> > > redirection operator to write to a file. That will work in windows too.
> > >
> > > ./dah.py >outfile
> > >
> > > or (without bash shebang):
> > >
> > > python dah.py >outfile
> >
> >
> > That redirection works, but the output also has the alternating blank lines.
> >
> > https://imgur.com/a/r4KDU3R
>
> Weird.
>
> > Only when opening the output file in 'wb' mode within the python code do
> > I get valid results.
> >
> > The slow retrieval via blocknews is strange. It's always 20-30 seconds
> > for 1000 articles.
> >
> > Tried it a few times with eternal-september. Consistently retrieves
> > 1000 articles in 3.6 seconds!
> >
> > But ES only has cola - and most groups I think - going back to 2010.
> > Blocknews goes back to Jul 2003 last I checked.
What were you expecting?
Just some names Klaus Schadenfreude has used
"Evil" John *
"Evil" Snit *
Big Crotch on a Small Fish
Cornelius Munshower
CSMA Moderator
Edward Stanfield
Fretwiz *
Hitman Hero
Measles
Petruzzellis Kids
Sigmond
Slaveen
Smit
Steve C *
Steve Camoll *
Steve Carroll <noone@xxxxxxxxxxx> *
Steve Carroll <stevecarroll@xxxxxxxxxxx> *
Steve Carroll <trollkiller@xxxxxx> *
Steve Carroll's Dog *
Steve Carrolll *
Steve Carrroll *
Yevette Owens
Yobo_Obyo
You're like a full moon on a cloudless night. We all see you there and let you know. And you're so foolish you keep repeating it.
It's simple to twist facts by focusing on hardly any isolated examples unrepresentative from what is something more common like GNU/Linux. What a better tactic from an honest advocates vantage point are the common events. Any heinously moronic insomniac could easily do the same.
Just rubbish from him. But he has left tech behind and is holding me accountable for the deeds of himself.
Klaus Schadenfreude claims to be the screencasting guru, let us see him put up a form without the sorting procedures.
The herd members value the lowest common denominator instead of choice.
--
One Smart Penny
http://www.5z8.info/--INITIATE-CREDIT-CARD-XFER--_k7s1jt_inject_worm
Jonas Eklundh Communication AB
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-16 16:49 +0000 |
| Message-ID | <a8bz00q.ayvo@rooftop.invalid> |
| In reply to | #472339 |
DFS <nospam@nospam.com> wrote: > On 10/16/2018 11:17 AM, owl wrote: > >> If you're actually still getting the '.' marker in the file, but >> extra blank lines are being added, this may or may not be related: >> >> https://sopython.com/canon/97/writing-csv-adds-blank-lines-between-rows/ >> >> So try adding 'wb' to the open() call. > > Even though I'm not using the cvswriter library, that fixed it, so thanks. > > > >> But that open() should not even be necessary anyway. I just use '>' >> redirection operator to write to a file. That will work in windows too. >> >> ./dah.py >outfile >> >> or (without bash shebang): >> >> python dah.py >outfile > > > That redirection works, but the output also has the alternating blank lines. > > https://imgur.com/a/r4KDU3R > Weird. And that's with redirecting a stdout print, not a write? I would think a print redirection would work without adding stuff, just like if you did: type afile.txt >bfile.txt > Only when opening the output file in 'wb' mode within the python code do > I get valid results. > > The slow retrieval via blocknews is strange. It's always 20-30 seconds > for 1000 articles. > > Tried it a few times with eternal-september. Consistently retrieves > 1000 articles in 3.6 seconds! > Cool. > But ES only has cola - and most groups I think - going back to 2010. > Blocknews goes back to Jul 2003 last I checked. >
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-04 12:35 -0700 |
| Message-ID | <b4f49b22-42cc-4acb-8f3e-0969b351d3fb@googlegroups.com> |
| In reply to | #470635 |
On Thursday, October 4, 2018 at 10:50:55 AM UTC-7, DFS wrote:
> On 10/4/2018 11:51 AM, Steve Carroll wrote:
> > On Thursday, October 4, 2018 at 8:07:40 AM UTC-6, DFS wrote:
> >
> > (snip)
> >
> >>> I've read this entire post (even replied to it already, just not posted 'cuz
> >>> I see my responses will probably change now that I've tried this). After
> >>> adjusting for the line length of the 'Subject' field with nntplib._MAXLINE,
> >>
> >> Why did you have to mess with MAXLINE?
> >
> > I was getting an error: "raise NNTPDataError('line too long')
>
> Yes, that's what I got. As I recall it was thrown on the
> 'Injection-Info' header for a few posts.
>
>
>
> >> I once increased MAXLINE because
> >> some weirdo posts from alt.usenet.kook had a monstrously long header,
> >> but that was maybe 3 posts in the 2.6M I've downloaded.
> >
> > Yeah, I noticed it wasn't in any of the scripts you gave me so there
> > must be a default that was working for most posts. How much room
> > does 2.6M take up on your drive?
>
> 14.1 GB
>
>
> >>> I can print 1000 posts of data to a file in ~4.5 seconds.
> >>
> >> Cool. Are you using this kind of call:
> >>
> >> response, subjects = news.xhdr("Subject","range of articles")
> >
> > I'm currently using:
> >
> > --
> > # print ('=====================')
> > print(news.xhdr("From","703470-704470"))
> > print(news.xhdr("Subject","703470-704470"))
> > print(news.xhdr("Date","703470-704470"))
> > print(news.xhdr("Message-ID","703470-704470"))
> > print(news.xhdr("References","703470-704470"))
> >
> >
> > for articleID in range(704470, 704490):
> >
> > print '====================='
> > print 'article',articleID
> > print '====================='
> >
> > try: response, artID, msgID, headers = news.head(str(articleID))
> > except (nntplib.NNTPTemporaryError,nntplib.NNTPProtocolError,nntplib.NNTPDataError,nntplib.NNTPReplyError) as headerError:
> > print("(article ID",articleID, "Header NNTP Error", headerError,")")
> > continue
> >
> > try: response, artID, msgID, body = news.body(str(articleID))
> > except (nntplib.NNTPTemporaryError,nntplib.NNTPProtocolError,nntplib.NNTPDataError,nntplib.NNTPReplyError) as bodyError:
> > print("(article ID",articleID, "Body NNTP Error", bodyError,")")
> > continue
> >
> > linenbr = 1
> > for bod in body:
> > print(bod)
> > linenbr += 1
> > --
>
>
> You keep showing just the print() routines. So you're writing the data
> to file(s) as well, I assume. From then you're going to parse it out
> into a relational db?
>
> I just discovered something. The python 2.7 docs for nntplib say the
> article() command returns the same data as the head() command (which
> just pulls down the headers).
>
> <quote>
> NNTP.article(id)
> Send an ARTICLE command, where id has the same meaning as for stat().
> Return as for head().
> </quote>
>
> So I never even tried it, until just now. And it turns out it retrieves
> the entire post, headers and body!
>
> So you could use the nntplib.article() command. I just did a test with
> it and stored 100 posts in 100 files in four to six seconds.
>
>
> import nntplib, time
> news = nntplib.NNTP('server',119,'user','password')
> r,a,b,e,g = news.group("comp.os.linux.advocacy") #have to login to a
> group when using article #s
> start = time.clock()
> for i, article in enumerate(range(1420100,1420200)):
> myfile = "D:\\cola_" + str(article)
> response, articleID, msgID, post = news.article(str(article))
> print i+1, articleID, msgID
> with open(myfile,'w') as f:
> for line in post:
> f.write(line + '\n')
> print "%.2fs to retrieve posts" % (time.clock() - start)
> news.quit()
>
>
> This is just as good as using suck or suckmt I think.
>
>
>
> > Running the above script with just the header info takes ~4.3 secs.
> >
> > I don't know how to get the article bodies that fast so it still takes
> > ~5 minutes for 1000 posts. In any event, up until I fixed my Python
> > issues I wasn't able to find out if it would even work but now I have
> > and it does, albeit slowly due to the nested loops. So, at roughly 12
> > thousand posts per hour it's no speed demon but it works.
>
> Yep. It's a bear to populate your db with a 1M post archive.
Here are some of the scripted posts from Jonas Eklundh... the script adds a nonsense or irrelevant insult or accusation after most sentences and adds numbers to the text so he can better track his trolling:
<https://groups.google.com/d/msg/comp.os.linux.advocacy/RZtEyvJr8HI/VcEqOk2qCgAJ> or <https://goo.gl/67NLfr>.
You can see a run of three scripted flood posts from his primary account.
From: Sandman <mr@sandman.net>
Message-ID: <sandman-b7df8761d3b6831e96d5976e9e67f379@individual.net>
X-Trace: individual.net +MPBYFbnugFd2iPraU5I9ABV/5ZlNHtqj79Ij19mAYCfL5sHI=
User-Agent: Sandmania 2.0
He also has them elsewhere, here are some examples:
<https://groups.google.com/d/msg/comp.os.linux.advocacy/Xetqyi1T0F0/cvoqp3eqCgAJ> OR <https://goo.gl/jy0rsr>.
<https://groups.google.com/d/msg/comp.os.linux.advocacy/10d0Emx_ABk/eN0r1_epCgAJ> OR <https://goo.gl/Rkz0PO>.
On that one he has a run of two.
And a longer and clearly scripted, content-free flood post:
<https://groups.google.com/d/msg/comp.os.linux.advocacy/2WS3xlecnw8/lizfGLOnCgAJ> OR <https://goo.gl/t7cTHd>.
And even more!
<https://groups.google.com/d/msg/comp.os.linux.advocacy/cYutxNP1hWc/KZikieXECgAJ> OR <https://goo.gl/Z6G7Ic>
<https://groups.google.com/d/msg/comp.os.linux.advocacy/RZtEyvJr8HI/6sJfxaDECgAJ> OR <https://goo.gl/mTXlFt>
Lots more but that is enough to prove the point multiple times over. Sandman has been flooding not just with his Google accounts but with his standard account. ALL of those come from the same source I listed above and it is Sandman's standard account.
Jonas Eklundh: busted.
-
This Trick Gets Women Hot For You
http://prescottcomputerguy.com
http://www.5z8.info/--INITIATE-CREDIT-CARD-XFER--_k7s1jt_inject_worm
Jonas Eklundh Communication
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-04 20:44 +0000 |
| Message-ID | <az0b808ga.vu3@rooftop.invalid> |
| In reply to | #470635 |
DFS <nospam@nospam.com> wrote: > > I just discovered something. The python 2.7 docs for nntplib say the > article() command returns the same data as the head() command (which > just pulls down the headers). > > <quote> > NNTP.article(id) > Send an ARTICLE command, where id has the same meaning as for stat(). > Return as for head(). > </quote> > > So I never even tried it, until just now. And it turns out it retrieves > the entire post, headers and body! > > So you could use the nntplib.article() command. I just did a test with > it and stored 100 posts in 100 files in four to six seconds. > Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). You can telnet/netcat to your server and issue them. No real need for python nntplib. I'm kind of surprised that you weren't just grabbing everything with article commands and then parsing.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-04 14:09 -0700 |
| Message-ID | <46b550bb-0089-49a7-b5c4-fe43593ca6bc@googlegroups.com> |
| In reply to | #470667 |
On Thursday, October 4, 2018 at 1:44:21 PM UTC-7, owl wrote: > DFS <nospam@nospam.com> wrote: > > > > I just discovered something. The python 2.7 docs for nntplib say the > > article() command returns the same data as the head() command (which > > just pulls down the headers). > > > > <quote> > > NNTP.article(id) > > Send an ARTICLE command, where id has the same meaning as for stat(). > > Return as for head(). > > </quote> > > > > So I never even tried it, until just now. And it turns out it retrieves > > the entire post, headers and body! > > > > So you could use the nntplib.article() command. I just did a test with > > it and stored 100 posts in 100 files in four to six seconds. > > > > Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). > You can telnet/netcat to your server and issue them. No real need for > python nntplib. I'm kind of surprised that you weren't just grabbing > everything with article commands and then parsing. Why do you keep rephrasing yourself? And you do, of course realize that it isn't impossible for Steven 'Super Troll' Carroll to be doing this, or encouraging those who are. Idiot. If Snit Glasser has 'myFile.doc' open in a word processor such as emacs and Steven 'Super Troll' Carroll wants to change its name to 'd.txt' via a bash script while editing a script, Snit Glasser's suggestion might be useful, if only to see it attach to an xmove display. -- What Every Entrepreneur Must Know https://youtu.be/u4xD43Khhkw https://www.facebook.com/JonasEklundh Jonas Eklundh Communication AB
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-04 14:50 -0700 |
| Message-ID | <fad10dc6-8f0c-4467-a3af-ac2ee2d51c8c@googlegroups.com> |
| In reply to | #470667 |
On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: > DFS <nospam@nospam.com> wrote: > > > > I just discovered something. The python 2.7 docs for nntplib say the > > article() command returns the same data as the head() command (which > > just pulls down the headers). > > > > <quote> > > NNTP.article(id) > > Send an ARTICLE command, where id has the same meaning as for stat(). > > Return as for head(). > > </quote> > > > > So I never even tried it, until just now. And it turns out it retrieves > > the entire post, headers and body! > > > > So you could use the nntplib.article() command. I just did a test with > > it and stored 100 posts in 100 files in four to six seconds. > > > > Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). > You can telnet/netcat to your server and issue them. No real need for > python nntplib. I'm kind of surprised that you weren't just grabbing > everything with article commands and then parsing. If you have an acct. with them, have you ever tried telnet on eternal september? I just tried with no luck (same with SSH) so, for now, I'm stuck with Python, which is fine 'cuz I've been meaning to learn a bit of it anyway.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-04 22:32 +0000 |
| Message-ID | <0z8b903ga.ay3@rooftop.invalid> |
| In reply to | #470674 |
Steve Carroll <fretwizzer@gmail.com> wrote: > On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: >> DFS <nospam@nospam.com> wrote: >> > >> > I just discovered something. The python 2.7 docs for nntplib say the >> > article() command returns the same data as the head() command (which >> > just pulls down the headers). >> > >> > <quote> >> > NNTP.article(id) >> > Send an ARTICLE command, where id has the same meaning as for stat(). >> > Return as for head(). >> > </quote> >> > >> > So I never even tried it, until just now. And it turns out it retrieves >> > the entire post, headers and body! >> > >> > So you could use the nntplib.article() command. I just did a test with >> > it and stored 100 posts in 100 files in four to six seconds. >> > >> >> Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). >> You can telnet/netcat to your server and issue them. No real need for >> python nntplib. I'm kind of surprised that you weren't just grabbing >> everything with article commands and then parsing. > > If you have an acct. with them, have you ever tried telnet on eternal > september? I don't have an account with them. > I just tried with no luck (same with SSH) so, for now, I'm > stuck with Python, which is fine 'cuz I've been meaning to learn a bit > of it anyway. You have to connect to the nntp port, which will be 119 if it's not a nntps connection. My newsserver allows either, but my newsreader doesn't do ssl, so I run stunnel from local port 119 to remote 563. Then I can connect either my newsreader or a netcat/telnet to localhost 119, and it's tunneled. You can also use opennssl to connect directly to port 563 on the server, and it's basically the same as a telnet/netcat: openssl s_client -connect your.news.server:563
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-04 23:03 +0000 |
| Message-ID | <a0b80083ga.vi@rooftop.invalid> |
| In reply to | #470678 |
owl <owl@rooftop.invalid> wrote: > Steve Carroll <fretwizzer@gmail.com> wrote: >> On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: >>> DFS <nospam@nospam.com> wrote: >>> > >>> > I just discovered something. The python 2.7 docs for nntplib say the >>> > article() command returns the same data as the head() command (which >>> > just pulls down the headers). >>> > >>> > <quote> >>> > NNTP.article(id) >>> > Send an ARTICLE command, where id has the same meaning as for stat(). >>> > Return as for head(). >>> > </quote> >>> > >>> > So I never even tried it, until just now. And it turns out it retrieves >>> > the entire post, headers and body! >>> > >>> > So you could use the nntplib.article() command. I just did a test with >>> > it and stored 100 posts in 100 files in four to six seconds. >>> > >>> >>> Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). >>> You can telnet/netcat to your server and issue them. No real need for >>> python nntplib. I'm kind of surprised that you weren't just grabbing >>> everything with article commands and then parsing. >> >> If you have an acct. with them, have you ever tried telnet on eternal >> september? > > I don't have an account with them. > >> I just tried with no luck (same with SSH) so, for now, I'm >> stuck with Python, which is fine 'cuz I've been meaning to learn a bit >> of it anyway. > > You have to connect to the nntp port, which will be 119 if it's not > a nntps connection. My newsserver allows either, but my newsreader > doesn't do ssl, so I run stunnel from local port 119 to remote 563. > Then I can connect either my newsreader or a netcat/telnet to localhost > 119, and it's tunneled. You can also use opennssl to connect directly > to port 563 on the server, and it's basically the same as a telnet/netcat: > > openssl s_client -connect your.news.server:563 > I just set up an account with them. Works fine with either netcat to port 119 or openssl to port 563. Issue these commands when you connect: authinfo user yourusername authinfo pass yourpassword group comp.os.linux.advocacy I get this: 281 Authentication succeeded group comp.os.linux.advocacy 211 446777 22199 705998 comp.os.linux.advocacy
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-04 16:28 -0700 |
| Message-ID | <d166ba44-bd7b-484d-a980-350e0c1d2faf@googlegroups.com> |
| In reply to | #470683 |
On Thursday, October 4, 2018 at 4:03:15 PM UTC-7, owl wrote: > owl <owl@rooftop.invalid> wrote: > > Steve Carroll <fretwizzer@gmail.com> wrote: > >> On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: > >>> DFS <nospam@nospam.com> wrote: > >>> > > >>> > I just discovered something. The python 2.7 docs for nntplib say the > >>> > article() command returns the same data as the head() command (which > >>> > just pulls down the headers). > >>> > > >>> > <quote> > >>> > NNTP.article(id) > >>> > Send an ARTICLE command, where id has the same meaning as for stat(). > >>> > Return as for head(). > >>> > </quote> > >>> > > >>> > So I never even tried it, until just now. And it turns out it retrieves > >>> > the entire post, headers and body! > >>> > > >>> > So you could use the nntplib.article() command. I just did a test with > >>> > it and stored 100 posts in 100 files in four to six seconds. > >>> > > >>> > >>> Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). > >>> You can telnet/netcat to your server and issue them. No real need for > >>> python nntplib. I'm kind of surprised that you weren't just grabbing > >>> everything with article commands and then parsing. > >> > >> If you have an acct. with them, have you ever tried telnet on eternal > >> september? > > > > I don't have an account with them. > > > >> I just tried with no luck (same with SSH) so, for now, I'm > >> stuck with Python, which is fine 'cuz I've been meaning to learn a bit > >> of it anyway. > > > > You have to connect to the nntp port, which will be 119 if it's not > > a nntps connection. My newsserver allows either, but my newsreader > > doesn't do ssl, so I run stunnel from local port 119 to remote 563. > > Then I can connect either my newsreader or a netcat/telnet to localhost > > 119, and it's tunneled. You can also use opennssl to connect directly > > to port 563 on the server, and it's basically the same as a telnet/netcat: > > > > openssl s_client -connect your.news.server:563 > > > > I just set up an account with them. Works fine with either netcat > to port 119 or openssl to port 563. Issue these commands when you > connect: > > authinfo user yourusername > authinfo pass yourpassword > group comp.os.linux.advocacy > > I get this: > 281 Authentication succeeded > group comp.os.linux.advocacy > 211 446777 22199 705998 comp.os.linux.advocacy You guys can only speculate from the viewpoint of a sociopath. And you do, of course realize that it isn't impossible for Steve Petruzzellis to be doing this, or encouraging those who are. I've worked for the OEM PC business for nearly 45 years. I have served top corporations selling to the aeronautics industry and the health industry. Never, with even a hint, were we on any occasion under a contractual obligation not to install any OS we wanted. We sold Xenix, Apple II, Symbian, among others with MS OSs. Steve Petruzzellis is the result of the truth that Marxists have been employed to take over responsibility for schooling kids. It is not mere happenstance that he is an idiotic Marxist. -- What Every Entrepreneur Must Know!! https://youtu.be/E3m_i-x92D0 Jonas Eklundh
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-04 16:54 -0700 |
| Message-ID | <7032cb07-9d53-4d69-97f5-6c6cef25d973@googlegroups.com> |
| In reply to | #470683 |
On Thursday, October 4, 2018 at 5:03:15 PM UTC-6, owl wrote: > owl <owl@rooftop.invalid> wrote: > > Steve Carroll <fretwizzer@gmail.com> wrote: > >> On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: > >>> DFS <nospam@nospam.com> wrote: > >>> > > >>> > I just discovered something. The python 2.7 docs for nntplib say the > >>> > article() command returns the same data as the head() command (which > >>> > just pulls down the headers). > >>> > > >>> > <quote> > >>> > NNTP.article(id) > >>> > Send an ARTICLE command, where id has the same meaning as for stat(). > >>> > Return as for head(). > >>> > </quote> > >>> > > >>> > So I never even tried it, until just now. And it turns out it retrieves > >>> > the entire post, headers and body! > >>> > > >>> > So you could use the nntplib.article() command. I just did a test with > >>> > it and stored 100 posts in 100 files in four to six seconds. > >>> > > >>> > >>> Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). > >>> You can telnet/netcat to your server and issue them. No real need for > >>> python nntplib. I'm kind of surprised that you weren't just grabbing > >>> everything with article commands and then parsing. > >> > >> If you have an acct. with them, have you ever tried telnet on eternal > >> september? > > > > I don't have an account with them. > > > >> I just tried with no luck (same with SSH) so, for now, I'm > >> stuck with Python, which is fine 'cuz I've been meaning to learn a bit > >> of it anyway. > > > > You have to connect to the nntp port, which will be 119 if it's not > > a nntps connection. My newsserver allows either, but my newsreader > > doesn't do ssl, so I run stunnel from local port 119 to remote 563. > > Then I can connect either my newsreader or a netcat/telnet to localhost > > 119, and it's tunneled. You can also use opennssl to connect directly > > to port 563 on the server, and it's basically the same as a telnet/netcat: > > > > openssl s_client -connect your.news.server:563 > > > > I just set up an account with them. Works fine with either netcat > to port 119 or openssl to port 563. Issue these commands when you > connect: > > authinfo user yourusername > authinfo pass yourpassword > group comp.os.linux.advocacy > > I get this: > 281 Authentication succeeded > group comp.os.linux.advocacy > 211 446777 22199 705998 comp.os.linux.advocacy I only have regular telnet (not all this fancy crap you have that I don't understand), I was unable to connect using it.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-05 00:02 +0000 |
| Message-ID | <sz0b003ga0gv.gho3@rooftop.invalid> |
| In reply to | #470692 |
Steve Carroll <fretwizzer@gmail.com> wrote: > On Thursday, October 4, 2018 at 5:03:15 PM UTC-6, owl wrote: >> owl <owl@rooftop.invalid> wrote: >> > Steve Carroll <fretwizzer@gmail.com> wrote: >> >> On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: >> >>> DFS <nospam@nospam.com> wrote: >> >>> > >> >>> > I just discovered something. The python 2.7 docs for nntplib say the >> >>> > article() command returns the same data as the head() command (which >> >>> > just pulls down the headers). >> >>> > >> >>> > <quote> >> >>> > NNTP.article(id) >> >>> > Send an ARTICLE command, where id has the same meaning as for stat(). >> >>> > Return as for head(). >> >>> > </quote> >> >>> > >> >>> > So I never even tried it, until just now. And it turns out it retrieves >> >>> > the entire post, headers and body! >> >>> > >> >>> > So you could use the nntplib.article() command. I just did a test with >> >>> > it and stored 100 posts in 100 files in four to six seconds. >> >>> > >> >>> >> >>> Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). >> >>> You can telnet/netcat to your server and issue them. No real need for >> >>> python nntplib. I'm kind of surprised that you weren't just grabbing >> >>> everything with article commands and then parsing. >> >> >> >> If you have an acct. with them, have you ever tried telnet on eternal >> >> september? >> > >> > I don't have an account with them. >> > >> >> I just tried with no luck (same with SSH) so, for now, I'm >> >> stuck with Python, which is fine 'cuz I've been meaning to learn a bit >> >> of it anyway. >> > >> > You have to connect to the nntp port, which will be 119 if it's not >> > a nntps connection. My newsserver allows either, but my newsreader >> > doesn't do ssl, so I run stunnel from local port 119 to remote 563. >> > Then I can connect either my newsreader or a netcat/telnet to localhost >> > 119, and it's tunneled. You can also use opennssl to connect directly >> > to port 563 on the server, and it's basically the same as a telnet/netcat: >> > >> > openssl s_client -connect your.news.server:563 >> > >> >> I just set up an account with them. Works fine with either netcat >> to port 119 or openssl to port 563. Issue these commands when you >> connect: >> >> authinfo user yourusername >> authinfo pass yourpassword >> group comp.os.linux.advocacy >> >> I get this: >> 281 Authentication succeeded >> group comp.os.linux.advocacy >> 211 446777 22199 705998 comp.os.linux.advocacy > > I only have regular telnet (not all this fancy crap you have that I > don't understand), I was unable to connect using it. It doesn't matter how you connect. Telnet works too. This is all that newsreader software does when connecting. It just sends nntp commands, and the server responds. The server doesn't care how you connect. It's just listening on the port and responding to commands. It's the same with HTTP and any other internet service. Each service has its own set of commands that it understands. If you succeed in connecting to nntp, type 'help' and the server will return a list of commands that you can play with. anon@lowtide:~$ telnet news.eternal-september.org 119 Trying 85.214.115.223... Connected to reader02.eternal-september.org. Escape character is '^]'. 200 reader02.eternal-september.org InterNetNews NNRP server INN 2.7.0 (20180513 snapshot) ready (posting ok) authinfo user XXXXXXXXX 381 Enter password authinfo pass XXXXXXXXX 281 Authentication succeeded group comp.os.linux.advocacy 211 446788 22199 706009 comp.os.linux.advocacy xhdr from 706009 221 Header or metadata information for from follows (from overview) 706009 Steve Carroll <fretwizzer@gmail.com> . quit 205 Bye! Connection closed by foreign host. anon@lowtide:~$
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-04 17:20 -0700 |
| Message-ID | <d6fa218e-5e68-4980-8dd7-9b2c59079a5b@googlegroups.com> |
| In reply to | #470694 |
On Thursday, October 4, 2018 at 6:02:52 PM UTC-6, owl wrote: > Steve Carroll <fretwizzer@gmail.com> wrote: > > On Thursday, October 4, 2018 at 5:03:15 PM UTC-6, owl wrote: > >> owl <owl@rooftop.invalid> wrote: > >> > Steve Carroll <fretwizzer@gmail.com> wrote: > >> >> On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: > >> >>> DFS <nospam@nospam.com> wrote: > >> >>> > > >> >>> > I just discovered something. The python 2.7 docs for nntplib say the > >> >>> > article() command returns the same data as the head() command (which > >> >>> > just pulls down the headers). > >> >>> > > >> >>> > <quote> > >> >>> > NNTP.article(id) > >> >>> > Send an ARTICLE command, where id has the same meaning as for stat(). > >> >>> > Return as for head(). > >> >>> > </quote> > >> >>> > > >> >>> > So I never even tried it, until just now. And it turns out it retrieves > >> >>> > the entire post, headers and body! > >> >>> > > >> >>> > So you could use the nntplib.article() command. I just did a test with > >> >>> > it and stored 100 posts in 100 files in four to six seconds. > >> >>> > > >> >>> > >> >>> Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). > >> >>> You can telnet/netcat to your server and issue them. No real need for > >> >>> python nntplib. I'm kind of surprised that you weren't just grabbing > >> >>> everything with article commands and then parsing. > >> >> > >> >> If you have an acct. with them, have you ever tried telnet on eternal > >> >> september? > >> > > >> > I don't have an account with them. > >> > > >> >> I just tried with no luck (same with SSH) so, for now, I'm > >> >> stuck with Python, which is fine 'cuz I've been meaning to learn a bit > >> >> of it anyway. > >> > > >> > You have to connect to the nntp port, which will be 119 if it's not > >> > a nntps connection. My newsserver allows either, but my newsreader > >> > doesn't do ssl, so I run stunnel from local port 119 to remote 563. > >> > Then I can connect either my newsreader or a netcat/telnet to localhost > >> > 119, and it's tunneled. You can also use opennssl to connect directly > >> > to port 563 on the server, and it's basically the same as a telnet/netcat: > >> > > >> > openssl s_client -connect your.news.server:563 > >> > > >> > >> I just set up an account with them. Works fine with either netcat > >> to port 119 or openssl to port 563. Issue these commands when you > >> connect: > >> > >> authinfo user yourusername > >> authinfo pass yourpassword > >> group comp.os.linux.advocacy > >> > >> I get this: > >> 281 Authentication succeeded > >> group comp.os.linux.advocacy > >> 211 446777 22199 705998 comp.os.linux.advocacy > > > > I only have regular telnet (not all this fancy crap you have that I > > don't understand), I was unable to connect using it. > > It doesn't matter how you connect. Telnet works too. This is all > that newsreader software does when connecting. It just sends nntp > commands, and the server responds. The server doesn't care how > you connect. It's just listening on the port and responding to > commands. It's the same with HTTP and any other internet service. > Each service has its own set of commands that it understands. > If you succeed in connecting to nntp, type 'help' and the server > will return a list of commands that you can play with. DOH! I haven't been on telnet or any BBS for ages ;) > anon@lowtide:~$ telnet news.eternal-september.org 119 > Trying 85.214.115.223... > Connected to reader02.eternal-september.org. > Escape character is '^]'. > 200 reader02.eternal-september.org InterNetNews NNRP server INN 2.7.0 (20180513 snapshot) ready (posting ok) > authinfo user XXXXXXXXX > 381 Enter password > authinfo pass XXXXXXXXX Just saw this post... but I've tried it by using every variation. One of them spit back: "481 Invalid credentials" But it isn't invalid, I copied them out of my script where they work fine. I tried with no quotes, single quotes, double quotes, using PASS in front with all of the above, etc. F*cker won't let me login. LOL! > 281 Authentication succeeded > group comp.os.linux.advocacy > 211 446788 22199 706009 comp.os.linux.advocacy > xhdr from 706009 > 221 Header or metadata information for from follows (from overview) > 706009 Steve Carroll <fretwizzer@gmail.com> *your* connection uses *my* name? > . > quit > 205 Bye! > Connection closed by foreign host. > anon@lowtide:~$
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-04 17:31 -0700 |
| Message-ID | <5f70e34e-3613-42eb-9c9e-b18399e8fb02@googlegroups.com> |
| In reply to | #470698 |
On Thursday, October 4, 2018 at 5:20:37 PM UTC-7, Steve Carroll wrote: > On Thursday, October 4, 2018 at 6:02:52 PM UTC-6, owl wrote: > > Steve Carroll <fretwizzer@gmail.com> wrote: > > > On Thursday, October 4, 2018 at 5:03:15 PM UTC-6, owl wrote: > > >> owl <owl@rooftop.invalid> wrote: > > >> > Steve Carroll <fretwizzer@gmail.com> wrote: > > >> >> On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: > > >> >>> DFS <nospam@nospam.com> wrote: > > >> >>> > > > >> >>> > I just discovered something. The python 2.7 docs for nntplib say the > > >> >>> > article() command returns the same data as the head() command (which > > >> >>> > just pulls down the headers). > > >> >>> > > > >> >>> > <quote> > > >> >>> > NNTP.article(id) > > >> >>> > Send an ARTICLE command, where id has the same meaning as for stat(). > > >> >>> > Return as for head(). > > >> >>> > </quote> > > >> >>> > > > >> >>> > So I never even tried it, until just now. And it turns out it retrieves > > >> >>> > the entire post, headers and body! > > >> >>> > > > >> >>> > So you could use the nntplib.article() command. I just did a test with > > >> >>> > it and stored 100 posts in 100 files in four to six seconds. > > >> >>> > > > >> >>> > > >> >>> Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). > > >> >>> You can telnet/netcat to your server and issue them. No real need for > > >> >>> python nntplib. I'm kind of surprised that you weren't just grabbing > > >> >>> everything with article commands and then parsing. > > >> >> > > >> >> If you have an acct. with them, have you ever tried telnet on eternal > > >> >> september? > > >> > > > >> > I don't have an account with them. > > >> > > > >> >> I just tried with no luck (same with SSH) so, for now, I'm > > >> >> stuck with Python, which is fine 'cuz I've been meaning to learn a bit > > >> >> of it anyway. > > >> > > > >> > You have to connect to the nntp port, which will be 119 if it's not > > >> > a nntps connection. My newsserver allows either, but my newsreader > > >> > doesn't do ssl, so I run stunnel from local port 119 to remote 563. > > >> > Then I can connect either my newsreader or a netcat/telnet to localhost > > >> > 119, and it's tunneled. You can also use opennssl to connect directly > > >> > to port 563 on the server, and it's basically the same as a telnet/netcat: > > >> > > > >> > openssl s_client -connect your.news.server:563 > > >> > > > >> > > >> I just set up an account with them. Works fine with either netcat > > >> to port 119 or openssl to port 563. Issue these commands when you > > >> connect: > > >> > > >> authinfo user yourusername > > >> authinfo pass yourpassword > > >> group comp.os.linux.advocacy > > >> > > >> I get this: > > >> 281 Authentication succeeded > > >> group comp.os.linux.advocacy > > >> 211 446777 22199 705998 comp.os.linux.advocacy > > > > > > I only have regular telnet (not all this fancy crap you have that I > > > don't understand), I was unable to connect using it. > > > > It doesn't matter how you connect. Telnet works too. This is all > > that newsreader software does when connecting. It just sends nntp > > commands, and the server responds. The server doesn't care how > > you connect. It's just listening on the port and responding to > > commands. It's the same with HTTP and any other internet service. > > Each service has its own set of commands that it understands. > > If you succeed in connecting to nntp, type 'help' and the server > > will return a list of commands that you can play with. > > DOH! I haven't been on telnet or any BBS for ages ;) > > > anon@lowtide:~$ telnet news.eternal-september.org 119 > > Trying 85.214.115.223... > > Connected to reader02.eternal-september.org. > > Escape character is '^]'. > > 200 reader02.eternal-september.org InterNetNews NNRP server INN 2.7.0 (20180513 snapshot) ready (posting ok) > > authinfo user XXXXXXXXX > > 381 Enter password > > authinfo pass XXXXXXXXX > > Just saw this post... but I've tried it by using every variation. > One of them spit back: "481 Invalid credentials" > > But it isn't invalid, I copied them out of my script where they work fine. > I tried with no quotes, single quotes, double quotes, using PASS in front > with all of the above, etc. F*cker won't let me login. LOL! > > > 281 Authentication succeeded > > group comp.os.linux.advocacy > > 211 446788 22199 706009 comp.os.linux.advocacy > > xhdr from 706009 > > 221 Header or metadata information for from follows (from overview) > > 706009 Steve Carroll <fretwizzer@gmail.com> > > *your* connection uses *my* name? > > > . > > quit > > 205 Bye! > > Connection closed by foreign host. > > anon@lowtide:~$ You've proven only what a moron you are. Turns out Snit's non-stop flooding comments of Klaus Schadenfreude met the agreed on criteria of trolling, so he pretended he never said that. You _do_ realize that the massive floods ending up in multiple groups started out as a joke about hacking Google. Any horribly wounded welfare receiver could easily do the same. -- I Left My Husband & Daughter At Home And THIS happened https://www.youtube.com/playlist?list=PLU_evUKollmjeuJy5V5UMotPUs65Q7YM6 http://www.5z8.info/yourdick_v1o3ww_manhunter http://www.5z8.info/horse-slaughter_w8c4en_launchexe Jonas Eklundh Communication AB
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-05 00:32 +0000 |
| Message-ID | <a0b803ta00ga.gah3@rooftop.invalid> |
| In reply to | #470698 |
Steve Carroll <fretwizzer@gmail.com> wrote: > On Thursday, October 4, 2018 at 6:02:52 PM UTC-6, owl wrote: >> Steve Carroll <fretwizzer@gmail.com> wrote: >> > On Thursday, October 4, 2018 at 5:03:15 PM UTC-6, owl wrote: >> >> owl <owl@rooftop.invalid> wrote: >> >> > Steve Carroll <fretwizzer@gmail.com> wrote: >> >> >> On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: >> >> >>> DFS <nospam@nospam.com> wrote: >> >> >>> > >> >> >>> > I just discovered something. The python 2.7 docs for nntplib say the >> >> >>> > article() command returns the same data as the head() command (which >> >> >>> > just pulls down the headers). >> >> >>> > >> >> >>> > <quote> >> >> >>> > NNTP.article(id) >> >> >>> > Send an ARTICLE command, where id has the same meaning as for stat(). >> >> >>> > Return as for head(). >> >> >>> > </quote> >> >> >>> > >> >> >>> > So I never even tried it, until just now. And it turns out it retrieves >> >> >>> > the entire post, headers and body! >> >> >>> > >> >> >>> > So you could use the nntplib.article() command. I just did a test with >> >> >>> > it and stored 100 posts in 100 files in four to six seconds. >> >> >>> > >> >> >>> >> >> >>> Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). >> >> >>> You can telnet/netcat to your server and issue them. No real need for >> >> >>> python nntplib. I'm kind of surprised that you weren't just grabbing >> >> >>> everything with article commands and then parsing. >> >> >> >> >> >> If you have an acct. with them, have you ever tried telnet on eternal >> >> >> september? >> >> > >> >> > I don't have an account with them. >> >> > >> >> >> I just tried with no luck (same with SSH) so, for now, I'm >> >> >> stuck with Python, which is fine 'cuz I've been meaning to learn a bit >> >> >> of it anyway. >> >> > >> >> > You have to connect to the nntp port, which will be 119 if it's not >> >> > a nntps connection. My newsserver allows either, but my newsreader >> >> > doesn't do ssl, so I run stunnel from local port 119 to remote 563. >> >> > Then I can connect either my newsreader or a netcat/telnet to localhost >> >> > 119, and it's tunneled. You can also use opennssl to connect directly >> >> > to port 563 on the server, and it's basically the same as a telnet/netcat: >> >> > >> >> > openssl s_client -connect your.news.server:563 >> >> > >> >> >> >> I just set up an account with them. Works fine with either netcat >> >> to port 119 or openssl to port 563. Issue these commands when you >> >> connect: >> >> >> >> authinfo user yourusername >> >> authinfo pass yourpassword >> >> group comp.os.linux.advocacy >> >> >> >> I get this: >> >> 281 Authentication succeeded >> >> group comp.os.linux.advocacy >> >> 211 446777 22199 705998 comp.os.linux.advocacy >> > >> > I only have regular telnet (not all this fancy crap you have that I >> > don't understand), I was unable to connect using it. >> >> It doesn't matter how you connect. Telnet works too. This is all >> that newsreader software does when connecting. It just sends nntp >> commands, and the server responds. The server doesn't care how >> you connect. It's just listening on the port and responding to >> commands. It's the same with HTTP and any other internet service. >> Each service has its own set of commands that it understands. >> If you succeed in connecting to nntp, type 'help' and the server >> will return a list of commands that you can play with. > > DOH! I haven't been on telnet or any BBS for ages ;) > >> anon@lowtide:~$ telnet news.eternal-september.org 119 >> Trying 85.214.115.223... >> Connected to reader02.eternal-september.org. >> Escape character is '^]'. >> 200 reader02.eternal-september.org InterNetNews NNRP server INN 2.7.0 (20180513 snapshot) ready (posting ok) >> authinfo user XXXXXXXXX >> 381 Enter password >> authinfo pass XXXXXXXXX > > Just saw this post... but I've tried it by using every variation. > One of them spit back: "481 Invalid credentials" > > But it isn't invalid, I copied them out of my script where they work fine. > I tried with no quotes, single quotes, double quotes, using PASS in front > with all of the above, etc. F*cker won't let me login. LOL! > >> 281 Authentication succeeded >> group comp.os.linux.advocacy >> 211 446788 22199 706009 comp.os.linux.advocacy >> xhdr from 706009 ^^^^^^^^^^^^^^^^ >> 221 Header or metadata information for from follows (from overview) >> 706009 Steve Carroll <fretwizzer@gmail.com> > > *your* connection uses *my* name? > That's running 'xhdr' command requesting the 'from' header for article 706009, which was a post of yours.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-04 17:41 -0700 |
| Message-ID | <35b0e823-0ead-4b92-9ea4-73f0ab64972a@googlegroups.com> |
| In reply to | #470701 |
On Thursday, October 4, 2018 at 6:32:56 PM UTC-6, owl wrote: > Steve Carroll <fretwizzer@gmail.com> wrote: > > On Thursday, October 4, 2018 at 6:02:52 PM UTC-6, owl wrote: > >> Steve Carroll <fretwizzer@gmail.com> wrote: > >> > On Thursday, October 4, 2018 at 5:03:15 PM UTC-6, owl wrote: > >> >> owl <owl@rooftop.invalid> wrote: > >> >> > Steve Carroll <fretwizzer@gmail.com> wrote: > >> >> >> On Thursday, October 4, 2018 at 2:44:21 PM UTC-6, owl wrote: > >> >> >>> DFS <nospam@nospam.com> wrote: > >> >> >>> > > >> >> >>> > I just discovered something. The python 2.7 docs for nntplib say the > >> >> >>> > article() command returns the same data as the head() command (which > >> >> >>> > just pulls down the headers). > >> >> >>> > > >> >> >>> > <quote> > >> >> >>> > NNTP.article(id) > >> >> >>> > Send an ARTICLE command, where id has the same meaning as for stat(). > >> >> >>> > Return as for head(). > >> >> >>> > </quote> > >> >> >>> > > >> >> >>> > So I never even tried it, until just now. And it turns out it retrieves > >> >> >>> > the entire post, headers and body! > >> >> >>> > > >> >> >>> > So you could use the nntplib.article() command. I just did a test with > >> >> >>> > it and stored 100 posts in 100 files in four to six seconds. > >> >> >>> > > >> >> >>> > >> >> >>> Those are standard nntp commands (article, head, body, xhdr, xpat, etc.). > >> >> >>> You can telnet/netcat to your server and issue them. No real need for > >> >> >>> python nntplib. I'm kind of surprised that you weren't just grabbing > >> >> >>> everything with article commands and then parsing. > >> >> >> > >> >> >> If you have an acct. with them, have you ever tried telnet on eternal > >> >> >> september? > >> >> > > >> >> > I don't have an account with them. > >> >> > > >> >> >> I just tried with no luck (same with SSH) so, for now, I'm > >> >> >> stuck with Python, which is fine 'cuz I've been meaning to learn a bit > >> >> >> of it anyway. > >> >> > > >> >> > You have to connect to the nntp port, which will be 119 if it's not > >> >> > a nntps connection. My newsserver allows either, but my newsreader > >> >> > doesn't do ssl, so I run stunnel from local port 119 to remote 563. > >> >> > Then I can connect either my newsreader or a netcat/telnet to localhost > >> >> > 119, and it's tunneled. You can also use opennssl to connect directly > >> >> > to port 563 on the server, and it's basically the same as a telnet/netcat: > >> >> > > >> >> > openssl s_client -connect your.news.server:563 > >> >> > > >> >> > >> >> I just set up an account with them. Works fine with either netcat > >> >> to port 119 or openssl to port 563. Issue these commands when you > >> >> connect: > >> >> > >> >> authinfo user yourusername > >> >> authinfo pass yourpassword > >> >> group comp.os.linux.advocacy > >> >> > >> >> I get this: > >> >> 281 Authentication succeeded > >> >> group comp.os.linux.advocacy > >> >> 211 446777 22199 705998 comp.os.linux.advocacy > >> > > >> > I only have regular telnet (not all this fancy crap you have that I > >> > don't understand), I was unable to connect using it. > >> > >> It doesn't matter how you connect. Telnet works too. This is all > >> that newsreader software does when connecting. It just sends nntp > >> commands, and the server responds. The server doesn't care how > >> you connect. It's just listening on the port and responding to > >> commands. It's the same with HTTP and any other internet service. > >> Each service has its own set of commands that it understands. > >> If you succeed in connecting to nntp, type 'help' and the server > >> will return a list of commands that you can play with. > > > > DOH! I haven't been on telnet or any BBS for ages ;) > > > >> anon@lowtide:~$ telnet news.eternal-september.org 119 > >> Trying 85.214.115.223... > >> Connected to reader02.eternal-september.org. > >> Escape character is '^]'. > >> 200 reader02.eternal-september.org InterNetNews NNRP server INN 2.7.0 (20180513 snapshot) ready (posting ok) > >> authinfo user XXXXXXXXX > >> 381 Enter password > >> authinfo pass XXXXXXXXX > > > > Just saw this post... but I've tried it by using every variation. > > One of them spit back: "481 Invalid credentials" > > > > But it isn't invalid, I copied them out of my script where they work fine. > > I tried with no quotes, single quotes, double quotes, using PASS in front > > with all of the above, etc. F*cker won't let me login. LOL! > > > >> 281 Authentication succeeded > >> group comp.os.linux.advocacy > >> 211 446788 22199 706009 comp.os.linux.advocacy > >> xhdr from 706009 > ^^^^^^^^^^^^^^^^ > > >> 221 Header or metadata information for from follows (from overview) > >> 706009 Steve Carroll <fretwizzer@gmail.com> > > > > *your* connection uses *my* name? > > > > That's running 'xhdr' command requesting the 'from' header for > article 706009, which was a post of yours. Ah, I missed that. Is it possible to get a range of posts and save them to a local file? I'm looking through 'help' and playing around but I don't see anything for a range (I tried OVER but that's not it).
[toc] | [prev] | [next] | [standalone]
Page 3 of 8 — ← Prev page 1 2 [3] 4 5 6 7 8 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web