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 1 of 8 [1] 2 3 4 5 6 7 8 Next page →
| From | DFS <nospam@nospam.com> |
|---|---|
| Date | 2018-10-04 10:08 -0400 |
| Subject | Re: slrn is trembling |
| Message-ID | <K8ptD.100112$ZJ2.25135@fx33.iad> |
On 9/29/2018 3:26 PM, Steve Carroll wrote:
> On Friday, September 28, 2018 at 10:34:54 PM UTC-6, DFS wrote:
>> On 9/28/2018 11:33 AM, Steve Carroll wrote:
>>> On Friday, September 28, 2018 at 8:54:48 AM UTC-6, DFS wrote:
>>>> On 9/27/2018 1:39 PM, Steve Carroll wrote:
>>>>> On Wednesday, September 26, 2018 at 5:48:30 PM UTC-6, DFS wrote:
>>>>>> On 9/26/2018 6:54 PM, Steve Carroll wrote:
>>>>>>>>
>>>>>>>> But adding ISO-8859-1 did the trick.
>>>>>>>
>>>>>>> Here's an example of a post that *was* choking but now isn't... I added
>>>>>>> the BODY delims:
>>>>>>
>>>>>>
>>>>>> Cool, but do you plan on capturing the data in the relational db? Looks
>>>>>> like you're just printing it to screen for now.
>>>>>
>>>>> Currently it's going to the screen and to a file, the latter of which I intend
>>>>> to parse into suitable pieces to be input into a DB.
>>>>
>>>>
>>>> So then I recommend you structure your file(s) very similarly, if not
>>>> identically, to the file(s) downloaded via suck or suckmt. Then you
>>>> won't have to write 2 dissimilar parser programs.
>>>
>>> True. I haven't messed with suck in awhile, I should probably go back
>>> and do so.
>>>
>>>> The advantage of using the python nntp library is you can pull down a
>>>> single header for huge numbers of posts at a time (1K, 10K, even 50K,
>>>> whatever) and put the info into a database right away, rather than
>>>> saving the whole post to a file, then later parsing each file.
>>>
>>> Well, you don't have to do it right away, obviously, but I get your point.
>>> What about networks issues, dropouts and such (I'm currently getting
>>> them for some reason)?
>>
>> Network drops can affect your code execution, but most python nntplib
>> requests are filled very quickly.
>>
>> news.xhdr("Subject","5000-15000") takes no time
>>
>> 10000 separate news.body() calls, on the other hand, takes a LONG time.
>> But so does opening 10000 files and extracting the body from them. So
>> it's a tradeoff.
>
> 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 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.
> 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")
> It took over 300
> seconds to do what I showed you earlier, tagging HEADERS and such,
> so this is definitely the fast way to get the data... just have to deal with
> it. One thing I noticed, I get a lot of this (not that I need 'Path'):
>
> ---
> ('703522', 'eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.166.216.MISMATCH!x81-v6no80816ita.0!news-out.google.com!c63-v6ni118ith.0!nntp.google.com!x188-v6no80444ite.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail')
> ---
>
> What's producing all these "MISMATCH!" entries (there are 385 of them)?
Don't know, but I seriously doubt it has anything to do with python.
> I can't install suckmt (couldn't even find suck on my system and I've used it
> in the past!) for some reason, I ran 'make' as per the instructions and got
> errors. I'm having some system issues I have to deal with. No matter, using
> the nntplib is hella fast so I'm not sure I'd need suck or suckmt anyway,
You don't need suck or suckmt. I created the entire system without
using suckmt, but later went back and used it to download all the posts,
so I could experiment recreating the db entirely from files (versus the
nntplib method of one header at a time).
One problem with using suckmt is the huge number of files. It becomes
slow once you get several hundred thousand files in a folder, so you
have to deal with that. On Windows it just plain crawls.
> I just have to figure out how to deal with the data using Python 3. A similar
> line like what you just posted...
>
> headers = content[:content.index('')]
>
> ... puked up in Python 3 in an earlier script (the one I'm using). I'm not sure
> how this accessor works. That I can find, the colon denotes a list and in that
> location it reverses direction. I don't have experience with many languages
> and this is a syntax I've not seen but it seems it's from the beginning to
> whatever content.index('') is in the file (I'd assume this syntax still works in
> Python 3 so maybe it was another issue).
content[:content.index('')]
is the same is
content[0:content.index('')]
and yes it means get data from/including the beginning (0-based) item up
to but not including the data in the position in the object where '' is
first found.
You can play around with slicing arrays and strings - it's very useful
stuff.
[toc] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-04 08:51 -0700 |
| Message-ID | <e0777414-4790-4fa0-9ce1-d889f604f26e@googlegroups.com> |
| In reply to | #470591 |
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')
> 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?
> > 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
--
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.
(snip)
> One problem with using suckmt is the huge number of files. It becomes
> slow once you get several hundred thousand files in a folder, so you
> have to deal with that. On Windows it just plain crawls.
Suck did it to a single file. No matter, the nntplib works well enough
for my needs.
> > I just have to figure out how to deal with the data using Python 3. A similar
> > line like what you just posted...
> >
> > headers = content[:content.index('')]
> >
> > ... puked up in Python 3 in an earlier script (the one I'm using). I'm not sure
> > how this accessor works. That I can find, the colon denotes a list and in that
> > location it reverses direction. I don't have experience with many languages
> > and this is a syntax I've not seen but it seems it's from the beginning to
> > whatever content.index('') is in the file (I'd assume this syntax still works in
> > Python 3 so maybe it was another issue).
>
>
> content[:content.index('')]
> is the same is
> content[0:content.index('')]
>
> and yes it means get data from/including the beginning (0-based) item up
> to but not including the data in the position in the object where '' is
> first found.
>
> You can play around with slicing arrays and strings - it's very useful
> stuff.
I'd like to get to the same level with it as I have with JS (not great),
and it looks like I can focus attention on the job now (x-ing fingers).
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@nospam.com> |
|---|---|
| Date | 2018-10-04 13:50 -0400 |
| Message-ID | <0qstD.79312$uJ2.3100@fx27.iad> |
| In reply to | #470609 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-04 11:59 -0700 |
| Message-ID | <055d7376-8773-4ca9-8cd3-4fd8c1a2764f@googlegroups.com> |
| In reply to | #470635 |
On Thursday, October 4, 2018 at 11:50:55 AM UTC-6, DFS wrote:
(snip)
> > 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
Is that just for COLA or all your groups? Seems like it'd be all,
IIRC Jonas talked about ~3GB for COLA awhile back
(snip)
> 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?
Yes to both.
> 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).
I've been using: <https://docs.python.org/3/library/nntplib.html>
> <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 it does!
> 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.
I got rid of the timer and tweaked to write 'em into one file, similar
to the non-mt version of suck:
<https://imgur.com/a/VLKbgBG>
Takes half my previous time at 2.5 minutes. How are you getting
them fast? Is my issue related to ES's server speed?
When trying under Python 3 I get that unpacking error, has 4...
sees 2 or some such. In any event, this is a huge speed increase
for me, thanks!
> > 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.
No doubt!
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@nospam.com> |
|---|---|
| Date | 2018-10-04 21:23 -0400 |
| Message-ID | <W1ztD.39291$xo2.777@fx31.iad> |
| In reply to | #470652 |
On 10/4/2018 2:59 PM, Steve Carroll wrote:
> On Thursday, October 4, 2018 at 11:50:55 AM UTC-6, DFS wrote:
>
> (snip)
>
>>> 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
>
> Is that just for COLA or all your groups? Seems like it'd be all,
> IIRC Jonas talked about ~3GB for COLA awhile back
4 groups, 2.62M total posts, going back 15 years per group.
> (snip)
>
>> 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?
>
> Yes to both.
So at this point you still haven't discovered the joy of loading the
data into parent/child tables (where you put a new Subject in the
Subject table, get the new SubjectID, then put it in the Post table with
all the other header IDs). This - assigning IDs and building and
maintaining relations - is part of what makes using a relational db a
hassle.
On the other hand: if you do it right you have no redundant
data/repeating rows; you have one place to make changes to an entity;
you have a smaller, faster database; and you can easily make or capture
relations between entities, ie assign multiple nyms to one ID so you can
get accurate stats.
>> 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).
>
> I've been using: <https://docs.python.org/3/library/nntplib.html>
>
>> <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 it does!
If I had known that I never would've used suckmt. In fact, I'm gonna
use a variation of that routine below to pull down the whole article as
an adjunct to my load process.
>> 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.
>
> I got rid of the timer and tweaked to write 'em into one file, similar
> to the non-mt version of suck:
>
> <https://imgur.com/a/VLKbgBG>
Is that from eternal-september? I see in your screenshot the post has
the xref header, which captures the articleID for the group. blocknews
doesn't send an xref header, so if you use blocknews make sure you write
the articleID out to the file (or in the filename) with code. With the
articleID you can easily ensure you get all posts from that server.
They're assigned sequentially, of course, so articleIDs almost exactly
track the post date/timestamp.
You don't _have to_ capture the articleID, but it makes life easier so I
highly recommend it. And remember: it's unique for that post in that
newsgroup on that server. ServerID, GroupID, ArticleID can be a unique
index in your system - could even be a PK if you want, but that I don't
recommend.
> Takes half my previous time at 2.5 minutes. How are you getting
> them fast? Is my issue related to ES's server speed?
Most likely.
That code above downloads from blocknews and writes to files 10 to 20
posts per second (depending on your network speed).
When I first used blocknews, it was a shock how much faster it was than
ES. I no longer use ES at all.
blocknews costs money, though. It'll cost you about $4.00 to get all 15
years of cola. http://www.blocknews.net
> When trying under Python 3 I get that unpacking error, has 4...
> sees 2 or some such. In any event, this is a huge speed increase
> for me, thanks!
Cool.
>>> 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.
>
> No doubt!
I asked the blocknews people to send me their entire cola archive, but
they refused. So I had to pull the whole thing down with code - many
hours of computer processing time. Like you're doing!
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-05 08:12 -0700 |
| Message-ID | <4d8974b2-34c9-471d-9edf-cc0fda2152e0@googlegroups.com> |
| In reply to | #470718 |
On Thursday, October 4, 2018 at 7:23:05 PM UTC-6, DFS wrote:
> On 10/4/2018 2:59 PM, Steve Carroll wrote:
> > On Thursday, October 4, 2018 at 11:50:55 AM UTC-6, DFS wrote:
> >
> > (snip)
> >
> >>> 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
> >
> > Is that just for COLA or all your groups? Seems like it'd be all,
> > IIRC Jonas talked about ~3GB for COLA awhile back
>
> 4 groups, 2.62M total posts, going back 15 years per group.
>
>
> > (snip)
> >
> >> 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?
> >
> > Yes to both.
>
> So at this point you still haven't discovered the joy of loading the
> data into parent/child tables (where you put a new Subject in the
> Subject table, get the new SubjectID, then put it in the Post table with
> all the other header IDs). This - assigning IDs and building and
> maintaining relations - is part of what makes using a relational db a
> hassle.
Right now I feel like I'm miles away from that point ;)
> On the other hand: if you do it right you have no redundant
> data/repeating rows; you have one place to make changes to an entity;
> you have a smaller, faster database; and you can easily make or capture
> relations between entities, ie assign multiple nyms to one ID so you can
> get accurate stats.
I plan on doing it the way you've talked about.
> >> 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).
> >
> > I've been using: <https://docs.python.org/3/library/nntplib.html>
> >
> >> <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 it does!
>
> If I had known that I never would've used suckmt. In fact, I'm gonna
> use a variation of that routine below to pull down the whole article as
> an adjunct to my load process.
Unless I get owl's shell script going and it's turns out to be faster, this
way is my best bet right now... I'm happy with it.
> >> 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.
> >
> > I got rid of the timer and tweaked to write 'em into one file, similar
> > to the non-mt version of suck:
> >
> > <https://imgur.com/a/VLKbgBG>
>
> Is that from eternal-september?
Yes.
> I see in your screenshot the post has
> the xref header, which captures the articleID for the group. blocknews
> doesn't send an xref header, so if you use blocknews make sure you write
> the articleID out to the file (or in the filename) with code. With the
> articleID you can easily ensure you get all posts from that server.
> They're assigned sequentially, of course, so articleIDs almost exactly
> track the post date/timestamp.
>
> You don't _have to_ capture the articleID, but it makes life easier so I
> highly recommend it. And remember: it's unique for that post in that
> newsgroup on that server. ServerID, GroupID, ArticleID can be a unique
> index in your system - could even be a PK if you want, but that I don't
> recommend.
I'll definitely continue to capture the articleID, it's currently the only
thing I see that will tie things together relatively easily.
> > Takes half my previous time at 2.5 minutes. How are you getting
> > them fast? Is my issue related to ES's server speed?
>
> Most likely.
>
> That code above downloads from blocknews and writes to files 10 to 20
> posts per second (depending on your network speed).
>
> When I first used blocknews, it was a shock how much faster it was than
> ES. I no longer use ES at all.
>
> blocknews costs money, though. It'll cost you about $4.00 to get all 15
> years of cola. http://www.blocknews.net
I don't need anymore that what I get from ES, in fact, I rarely use it.
> > When trying under Python 3 I get that unpacking error, has 4...
> > sees 2 or some such. In any event, this is a huge speed increase
> > for me, thanks!
>
> Cool.
>
>
>
> >>> 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.
> >
> > No doubt!
>
> I asked the blocknews people to send me their entire cola archive, but
> they refused. So I had to pull the whole thing down with code - many
> hours of computer processing time. Like you're doing!
I doubt I'll ever grab the amount you have, I'm just doing this for the
learning experience.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-05 08:21 -0700 |
| Message-ID | <60ced57c-0aa5-4263-b2a0-9e5784102ee0@googlegroups.com> |
| In reply to | #470800 |
On Friday, October 5, 2018 at 8:12:45 AM UTC-7, Steve Carroll wrote:
> On Thursday, October 4, 2018 at 7:23:05 PM UTC-6, DFS wrote:
> > On 10/4/2018 2:59 PM, Steve Carroll wrote:
> > > On Thursday, October 4, 2018 at 11:50:55 AM UTC-6, DFS wrote:
> > >
> > > (snip)
> > >
> > >>> 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
> > >
> > > Is that just for COLA or all your groups? Seems like it'd be all,
> > > IIRC Jonas talked about ~3GB for COLA awhile back
> >
> > 4 groups, 2.62M total posts, going back 15 years per group.
> >
> >
> > > (snip)
> > >
> > >> 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?
> > >
> > > Yes to both.
> >
> > So at this point you still haven't discovered the joy of loading the
> > data into parent/child tables (where you put a new Subject in the
> > Subject table, get the new SubjectID, then put it in the Post table with
> > all the other header IDs). This - assigning IDs and building and
> > maintaining relations - is part of what makes using a relational db a
> > hassle.
>
> Right now I feel like I'm miles away from that point ;)
>
> > On the other hand: if you do it right you have no redundant
> > data/repeating rows; you have one place to make changes to an entity;
> > you have a smaller, faster database; and you can easily make or capture
> > relations between entities, ie assign multiple nyms to one ID so you can
> > get accurate stats.
>
> I plan on doing it the way you've talked about.
>
> > >> 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).
> > >
> > > I've been using: <https://docs.python.org/3/library/nntplib.html>
> > >
> > >> <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 it does!
> >
> > If I had known that I never would've used suckmt. In fact, I'm gonna
> > use a variation of that routine below to pull down the whole article as
> > an adjunct to my load process.
>
> Unless I get owl's shell script going and it's turns out to be faster, this
> way is my best bet right now... I'm happy with it.
>
> > >> 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.
> > >
> > > I got rid of the timer and tweaked to write 'em into one file, similar
> > > to the non-mt version of suck:
> > >
> > > <https://imgur.com/a/VLKbgBG>
> >
> > Is that from eternal-september?
>
> Yes.
>
> > I see in your screenshot the post has
> > the xref header, which captures the articleID for the group. blocknews
> > doesn't send an xref header, so if you use blocknews make sure you write
> > the articleID out to the file (or in the filename) with code. With the
> > articleID you can easily ensure you get all posts from that server.
> > They're assigned sequentially, of course, so articleIDs almost exactly
> > track the post date/timestamp.
> >
> > You don't _have to_ capture the articleID, but it makes life easier so I
> > highly recommend it. And remember: it's unique for that post in that
> > newsgroup on that server. ServerID, GroupID, ArticleID can be a unique
> > index in your system - could even be a PK if you want, but that I don't
> > recommend.
>
> I'll definitely continue to capture the articleID, it's currently the only
> thing I see that will tie things together relatively easily.
>
> > > Takes half my previous time at 2.5 minutes. How are you getting
> > > them fast? Is my issue related to ES's server speed?
> >
> > Most likely.
> >
> > That code above downloads from blocknews and writes to files 10 to 20
> > posts per second (depending on your network speed).
> >
> > When I first used blocknews, it was a shock how much faster it was than
> > ES. I no longer use ES at all.
> >
> > blocknews costs money, though. It'll cost you about $4.00 to get all 15
> > years of cola. http://www.blocknews.net
>
> I don't need anymore that what I get from ES, in fact, I rarely use it.
>
> > > When trying under Python 3 I get that unpacking error, has 4...
> > > sees 2 or some such. In any event, this is a huge speed increase
> > > for me, thanks!
> >
> > Cool.
> >
> >
> >
> > >>> 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.
> > >
> > > No doubt!
> >
> > I asked the blocknews people to send me their entire cola archive, but
> > they refused. So I had to pull the whole thing down with code - many
> > hours of computer processing time. Like you're doing!
>
> I doubt I'll ever grab the amount you have, I'm just doing this for the
> learning experience.
I thought showing Klaus Schadenfreude a little generosity might help the situation. It did not.
Gee, imagine Klaus Schadenfreude trying to pin his rubbish on Jonas Eklundh and me, no one has ever seen that before <sarcasm>. Of course my unedited statement stands proper and correct. But Klaus Schadenfreude feels the need to attack the herd. So be it.
From what I've seen (which is none of it lately), it looks like the flood script needs more and more resources. Why does Klaus Schadenfreude focus on Jonas Eklundh's pride so much? Lying sack of shit does it every time. Then the deluge begins. Because the wimp just has to run to other groups to get the attention he's not getting here.
Really, what lie?
--
Get Rich Slow!!
https://www.facebook.com/profile.php?id=100012978552519
Jonas Eklundh Communication
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-05 09:55 -0700 |
| Message-ID | <11d5b01b-6249-4ea9-ac61-769f3bb3854e@googlegroups.com> |
| In reply to | #470718 |
On Thursday, October 4, 2018 at 7:23:05 PM UTC-6, DFS wrote: (snip) > > Takes half my previous time at 2.5 minutes. How are you getting > > them fast? Is my issue related to ES's server speed? > > Most likely. It's not the ES server, I just used owl's script and grabbed from artID 700000 to 705000 in under 19 seconds (17.4 MB).
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@nospam.com> |
|---|---|
| Date | 2018-10-05 13:51 -0400 |
| Message-ID | <1wNtD.54979$Ol2.35643@fx17.iad> |
| In reply to | #470821 |
On 10/5/2018 12:55 PM, Steve Carroll wrote: > On Thursday, October 4, 2018 at 7:23:05 PM UTC-6, DFS wrote: > > (snip) > >>> Takes half my previous time at 2.5 minutes. How are you getting >>> them fast? Is my issue related to ES's server speed? >> >> Most likely. > > It's not the ES server, I just used owl's script and grabbed from artID > 700000 to 705000 in under 19 seconds (17.4 MB). Nice. Reading ES via Thunderbird, and downloading via python, is very slow.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-05 11:16 -0700 |
| Message-ID | <c6947802-b8d0-46a7-8cae-b8ac41aa955b@googlegroups.com> |
| In reply to | #470828 |
On Friday, October 5, 2018 at 10:50:56 AM UTC-7, DFS wrote: > On 10/5/2018 12:55 PM, Steve Carroll wrote: > > On Thursday, October 4, 2018 at 7:23:05 PM UTC-6, DFS wrote: > > > > (snip) > > > >>> Takes half my previous time at 2.5 minutes. How are you getting > >>> them fast? Is my issue related to ES's server speed? > >> > >> Most likely. > > > > It's not the ES server, I just used owl's script and grabbed from artID > > 700000 to 705000 in under 19 seconds (17.4 MB). > > Nice. > > Reading ES via Thunderbird, and downloading via python, is very slow. You hacked it and read multiple reviews and your "professional opinions" lead you to that assumption, did they? Bravo, Klaus Schadenfreude, you are now living rent-free inside Jeremy's beady little brain. Lul. Seriously, those of you who troll are not able to check Klaus Schadenfreude anymore. Already moved on from that. You are too slow! - This Trick Gets Women Hot For You https://youtu.be/r7wys2JvBD0 http://www.macadvocacy.pw/2005/Nov/09/236626.html http://www.5z8.info/boobs_j0v3qo_dont-just-drizzle Jonas Eklundh Communication
[toc] | [prev] | [next] | [standalone]
| From | Jeff-Relf.Me @. |
|---|---|
| Date | 2018-10-14 01:41 -0700 |
| Subject | "Path:" is the only line that's never fake. |
| Message-ID | <Jeff-Relf.Me@Oct.14--1.41am.Seattle.2018> |
| In reply to | #470718 |
> That code above downloads from blocknews and writes to files > 10 to 20 posts per second (depending on your network speed). > > > > > I don't know how to get the article bodies that fast so it still takes > > > > ~5 minutes for 1000 posts. > > > > 12 thousand posts per hour it's no speed demon but it works. I prefer "Text" (INN) servers because they have accurate "Path:" lines; "Path:" is the only line that's never fake; for anonymity, "Binary" servers remove it. A year and a half ago, I told you: Glorb [ an INN server, Like "EternalSeptember" ] is taking just 4 seconds to download a thousand posts, full header and body. I "pipeline" 100 "Article" commands at a time ( all at once ), and I use a 4 MegaByte input buffer -- it's very sophisticated. Upon receiving a chunk ( e.g. a 30 KiloByte Article ), I check for proper line endings -- "\r\n" in the header, "\r" and/or "\n" in the body, if the "Content-Type:" is text. I don't parse the Body UnlessAndUntil I have the full header ( so I know what the "Content-Type:" is ). The body itself may have varios (MIME) "Content-Type:" lines.
[toc] | [prev] | [next] | [standalone]
| From | "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> |
|---|---|
| Date | 2018-10-14 11:16 -0400 |
| Subject | Re: "Path:" is the only line that's never fake. |
| Message-ID | <m8n6sdhvufno9mcgeg3gj59i4ebbk231q5@4ax.com> |
| In reply to | #471946 |
On Sun, 14 Oct 2018 01:41:42 -0700 (Seattle), Jeff-Relf.Me @. wrote: <...> >I prefer "Text" (INN) servers because they have accurate "Path:" lines; >"Path:" is the only line that's never fake; . . . <...> I regularly fake the Path: Altopia allows path preloading. A nice feature when forging and frogging. I rarely forge because that's a TOSSable offence but I do sneak a forgery in from time to time just to stir the pot and for future angst should the nym being forged find out and become pissed off. I've snuck in more than a few Sn!pe forgeries in obscure froups just because he hates it and also because he promised to get me TOSSed should I ever forge, instead of frog him. LOL. -- Yours Truly, Gregory Hall "Sometimes it's hard to tell them apart. When he drowns in his shit bucket, I plan to nominate him for a Darwin." --Rhonda Lea Kirk Fries
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-14 08:38 -0700 |
| Subject | Re: "Path:" is the only line that's never fake. |
| Message-ID | <bc313a38-6afc-4c95-ba0e-cb78bf910118@googlegroups.com> |
| In reply to | #471986 |
On Sunday, October 14, 2018 at 8:16:48 AM UTC-7, Sir Gregory Hall, Esq. wrote:
> On Sun, 14 Oct 2018 01:41:42 -0700 (Seattle), Jeff-Relf.Me @. wrote:
>
> <...>
>
> >I prefer "Text" (INN) servers because they have accurate "Path:" lines;
> >"Path:" is the only line that's never fake; . . .
>
> <...>
>
> I regularly fake the Path: Altopia allows path preloading. A nice feature
> when forging and frogging. I rarely forge because that's a TOSSable offence
> but I do sneak a forgery in from time to time just to stir the pot and for
> future angst should the nym being forged find out and become pissed off.
>
> I've snuck in more than a few Sn!pe forgeries in obscure froups just
> because he hates it and also because he promised to get me TOSSed
> should I ever forge, instead of frog him. LOL.
>
> --
>
> Yours Truly,
> Gregory Hall
>
> "Sometimes it's hard to tell them apart.
> When he drowns in his shit bucket, I plan
> to nominate him for a Darwin."
> --Rhonda Lea Kirk Fries
Carroll, 4/10/2015 4:04 PM:
-----
Cute trick... To the guy who hacked my Google account.
-----
No details. Seems to treat it as a joke.
Carroll, 4/10/2015 5:02 PM, <https://goo.gl/51rsmZ>:
-----
Email Hacking Is A Serious Crime
-----
No longer "cute"... now it is a serious crime. OK.
Carroll, 4/10/2015 5:07 PM:
By now he is posting more links to how serious this crime against him is.
Carroll, 4/10/2015 7:25 PM:
-----
I didn't write that.
-----
Now he is denying the posts from his own account. OK, he was "hacked". Someone else posted this. Hard to hack a gmail account given how they use two-step authentication and someone would need access to his phone or the like... but at least POSSIBLE.
Even then, though, if someone tries to guess your password Google alerts you and lets you know what IP address and other info. I know because someone in a Denver internet cafe has tried mine on several occasions.
Google even forces you to change your password when this happens. Very hard to hack these days.
So already Carroll's story is unlikely.
But let us accept it... someone somehow hacked his account bypassing the two step verification. This person did not, however, change his password and Carroll posted within an hour of the "hacker". Before that, unless he is an idiot, he changed his password and the "hacker" was locked out. The "hacker" got one post in.
But Carroll could not leave his story there.
Carroll, 4/10/2015 8:36 PM, <https://goo.gl/NJ2bMH>:
-----
Someone hacked my fretwizzer gmail acct so, for the time being,
don't trust anything from it.
-----
Wait. What? Even after Carroll figured out this "hacker" who was too stupid to change his password had broken into his account and Carroll *surely* must have changed his own password, he is saying the "hacker" might still have access. Might be able to break Google's two-step verification process *again*.
This is *very* unlikely... to the point of being unbelievable.
Even worse for him: he notes which of his accounts he is claiming was hacked - but in the past he has denied even using the other accounts! LOL! He screwed up and made it very clear he has multiple accounts and felt the need to note which one. He made the same mistake in the next quote where he speaks of WHICH of his gmail accounts he is claiming was hacked. Oops! If he only posts with one there would be no need to specify which one!
He has completely screwed up in his game to pretend he posts with only one gmail account. Completely idiotic of him, too!
Carroll, 4/10/2015 8:38 PM, <https://goo.gl/YA7gMO>:
-----
Some mentally deficient child hacked my 'fretwizzer' gmail account
so I may have to kill it. For the time being, don't assume
anything that's coming from it was written by me.
-----
He is still saying that he may have to kill the account instead of just changing the password which anyone with half a brain would have already done (and Google *forces* you to do when someone even tries to hack your account... I know because someone in the Denver area has tried to hack mine multiple times... likely Carroll but I have no proof of this). And he specifies WHICH of his accounts! He is directly admitting he uses more than one account! His claim of being "forged" with his second account is a lie. Proved.
Carroll, 4/10/2015 8:40 PM, <https://goo.gl/j6yCuV>:
-----
Looks like it's still being hacked despite me taking precautions,
I may have to kill the account.
-----
What makes it look like its still being hacked? And what precautions other than changing the two-step verification options does he need? And how would someone bypass this... is he really on the NSA watch list? Seems you would need someone at that level to be doing this. He watches too much TV where they computer hackers spend thirty seconds and bypass all security.
Just nonsense.
Carroll, 4/11/2015 12:05 PM:
-----
Apparently Google is having issues with their accounts to the
point where they're ready to undertake some additional measures.
-----
But, of course, no evidence of this... and what measures? They already alert users if someone else tries to guess your password and use two-step authentication and even force you to make a new password if it seems someone is trying to hack you.
-----
They're now involving several federal agencies in things they
didn't bother with previously in an effort to deal with people who
hack into accounts. They've asked me to leave the account open.
-----
So now Google is letting Carroll know how they are handling these things - and asking him to leave a *hacked* account open... one someone can be using to steal his identity. No. This does not pass the sniff test in any way. Even if they were doing this for some bizarre sting operation, which is in itself far fetched, they would have told Carroll to not make it public information so the hacker would not know.
Just insanity. His own story is so idiotic and full of idiotic claims it simply cannot be true. Carroll uses his secondary Google account - the one he accesses via Tor and is referred to as his Tor account - to have plausible deniability for things he says there. Now he is working to do the same thing with his main account. Maybe Carroll read a report like this: <http://cnnmon.ie/111QeT8> [money.com]. If so he missed the part where they note if you are *really* hacked, which is rare, the hackers change your password and lock you out. Why would they not?
-----
There's some new legislation that will help them deal with this
issue... which probably means more BS for us ;)
-----
Yes, new legislation to make sure Carroll does not have to deal with "hackers" and "forgers" which do not even exist.
The funny part is, this happened shortly after someone in the Denver area, likely Carroll, tried to guess *my* passwords and they did it from an Internet café (Google tells you the IP and that can be used to trace back).
My guess: Carroll is the one who was working to guess my password and figured this new lie of his was a good way to deny his own words even more than he does with his Tor account *and* a way to make it so if I had talked about him trying to hack my account he could say I was just copying his comments. "Proving" I read his posts... which for now I am to see how absurd his lies are. :)
Carroll, 4/11/2015 12:25 PM:
-----
The person who hacked into my Gmail acct. changed the wording on
this post. I've removed the others but Google asked me to leave
one standing for some odd reason.
-----
Here Carroll claims the hacker changed the wording on a post of his from *before* he had even claimed he was hacked. So this hacker not only can *post* for him but edit his old Usenet posts.
I call utter bullshit on this. Out and out lie from Carroll. And then Carroll says Google asked him to not delete these "hacked" posts... this is nonsense. Why would Google want him to leave forged posts in the public and why would Google not just keep their own copy? Even Carroll notes it is for "some odd reason" - yeah, because Carroll is telling stories that make *no* sense at all.
Carroll is lying. Maybe there is some kernel of truth to his stories? Even if so - and frankly it is unlikely he will ever show any evidence to back his claims - the details he is posting are absurd.
Carroll, 4/11/2015 2:10 PM:
-----
And he's so high he thinks people still have to manually enter all
their passwords in whenever they want to use anything that's been
password protected ;)
-----
Nobody had suggested, hinted, implied, or said anything like what Carroll says they did.
Maybe his story will be someone stole his laptop (or mobile device) and he had his passwords saved? If so why not have the device deactivated remotely? Why has he not said anything about this?
My guess: he realizes he screwed up when trying to guess my passwords and is now building a story so he can say his computer was stolen and it was not him. Or, LOL, maybe someone broke into his house and did it.
This unknown hacker knew he was obsessed with me and carried on acting like him. Makes complete sense, eh?
Carroll, 4/12/2015 8:45 AM, <https://goo.gl/KMf4pa>:
-----
The first one, that has since been deleted. My bad for having such
a feeble password on this account.
-----
Now he suggests it was merely from someone guessing his password - which contradicts his above insinuations that it could have been from a saved password on a device he had.
His story changes with the telling.
But as noted, when someone tries to guess your password Google has ways to deal with it. I know - Carroll or someone in his neck of the woods recently tried it with me.
Carroll, 4/12/2015 9:29 AM:
-----
The account in question here is a gmail account. Contrary to
Snit's delusions, I have no idea what a TOR account looks like but
it's a good bet it doesn't bear much of a resemblance to a gmail
account.
-----
Here Carroll plays stupid and pretends that if when he or anyone uses the Tor browser *Carroll* pointed to this somehow changes the way the gmail interface looks. Um, no. Worse it might do is make Google think you are in another country and you would have to set it back to English. But the basic look stays the same.
He is playing stupid and pretending to not know how the Tor browser he pointed to works. Just idiotic of him.
-----
That idiocy aside, I love how Snit has repeatedly, for years,
feigned ignorance about gmail accounts, yet, he keeps disclosing
info that proves he knows about them. Some fools do stuff like
this when they believe people are as stupid as the fool needs them
to be ;)
-----
I do not think Google would allow you to edit your Usenet / groups posts but I do not use it much and do not know for sure. Seems absurd that they would... and others have now said they do not. But given how I do not use Google Groups for posting why would I know the details of their system for certain?
Carroll, 6/16/2015 8:47 PM:
-----
Your obsession with me is insane. Working with Google I now have
proof you and ebot worked together to hack me. Clever. If I press
charges against you I have to also include her so you remain safe
for now.
Do not think this is over.
-----
No evidence of working with Google on this (and all out and out lies). Carroll is making public threats based on lies.
Carroll, 6/16/2015 8:50 PM:
-----
I promised COLA your trolling days were over so you contacted ebot
and worked with her to hack my account. I might not be able to get
your ass handed to you in court over this but wait until your boss
at Yavapai College contacts you.
Maybe you should make that call first. Ask about your comments on
incest.
See if those can not be quoted.
-----
Direct lies and threats by Carroll.
Carroll, 6/16/2015 8:51 PM:
-----
You went too far this time Snit. We have trolled each other for
years but to contact ebot and get her to help you hack my account
was over a line.
-----
A complete and utter lie from Carroll.
Carroll, 6/16/2015 8:52 PM:
-----
The above post is Snit hacking my account.
-----
A complete and utter lie... more false accusations from him.
Carroll, 6/16/2015 8:53 PM:
-----
You edited those posts when you hacked my account. Do not trust
anything from my fretwizzer account now that Snit and ebot have
access to it.
-----
More unsupported claims and attacks by Carroll.
Carroll, 4/16/2015 8:56 PM:
-----
Working with Google I now have proof Snit and ebot hacked the
account. Many of the older posts were edited. You can see evidence
of this by Snit pointing to "old" posts which have been modified to
say I claimed I was his "personal newsgroup rapist", a phrase I
have never used.
-----
No evidence of Carroll working with Google. No evidence of any older posts being edited.
--
This broke the Internet!
https://youtu.be/UkAyrfOZaXc
https://www.reddit.com/r/linux/comments/6sfkup/what_desktop_tasks_does_linux_handle_better_than/=
https://goo.gl/Fho5Nq
Jonas Eklundh Communication
[toc] | [prev] | [next] | [standalone]
| From | snipeco.2@gmail.com (Sn!pe) |
|---|---|
| Date | 2018-10-14 16:40 +0100 |
| Subject | Re: "Path:" is the only line that's never fake. |
| Message-ID | <1nwo66f.5tyjet14f56ptN%snipeco.2@gmail.com> |
| In reply to | #471986 |
Sir Gerkory Hall, Esq. <nelly@fake.yacht_maester> grotesquely grunted: > On Sun, 14 Oct 2018 01:41:42 -0700 (Seattle), Jeff-Relf.Me @. wrote: > > <...> > > >I prefer "Text" (INN) servers because they have accurate "Path:" lines; > >"Path:" is the only line that's never fake; . . . > > <...> > > I regularly fake the Path: Altopia allows path preloading. A nice feature > when forging and frogging. I rarely forge because that's a TOSSable offence > but I do sneak a forgery in from time to time just to stir the pot and for > future angst should the nym being forged find out and become pissed off. > > I've snuck in more than a few Sn!pe forgeries in obscure froups just > because he hates it and also because he promised to get me TOSSed > should I ever forge, instead of frog him. LOL. > See you, Gerk. You -still- can't do a perfect forgery of me, ineffectual prattler that you are. Just sayin'. -- ^Ï^ My pet rock Gordon just sneered.
[toc] | [prev] | [next] | [standalone]
| From | "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> |
|---|---|
| Date | 2018-10-14 11:43 -0400 |
| Subject | Re: "Path:" is the only line that's never fake. |
| Message-ID | <gvo6sd5hl49kfj6ntc5v733t1451s1kqad@4ax.com> |
| In reply to | #471991 |
On Sun, 14 Oct 2018 16:40:24 +0100, snipeco.2@gmail.com (Sn!pe) wrote: >Sir Gerkory Hall, Esq. <nelly@fake.yacht_maester> grotesquely grunted: >> On Sun, 14 Oct 2018 01:41:42 -0700 (Seattle), Jeff-Relf.Me @. wrote: >> >> <...> >> >> >I prefer "Text" (INN) servers because they have accurate "Path:" lines; >> >"Path:" is the only line that's never fake; . . . >> >> <...> >> >> I regularly fake the Path: Altopia allows path preloading. A nice feature >> when forging and frogging. I rarely forge because that's a TOSSable offence >> but I do sneak a forgery in from time to time just to stir the pot and for >> future angst should the nym being forged find out and become pissed off. >> >> I've snuck in more than a few Sn!pe forgeries in obscure froups just >> because he hates it and also because he promised to get me TOSSed >> should I ever forge, instead of frog him. LOL. >> > >See you, Gerk. You -still- can't do a perfect forgery of me, >ineffectual prattler that you are. Just sayin'. I am able to do a perfect forgery and would except for the fact that you'd use it to get me TOSSed. You said as much. -- Yours Truly, Gregory Hall "Sometimes it's hard to tell them apart. When he drowns in his shit bucket, I plan to nominate him for a Darwin." --Rhonda Lea Kirk Fries
[toc] | [prev] | [next] | [standalone]
| From | snipeco.2@gmail.com (Sn!pe) |
|---|---|
| Date | 2018-10-14 17:12 +0100 |
| Subject | Re: "Path:" is the only line that's never fake. |
| Message-ID | <1nwo7ko.m3kl41178vm3N%snipeco.2@gmail.com> |
| In reply to | #471992 |
Sir Gregory Hall, Esq. <greghall@yacht_maester.fake> wrote: > On Sun, 14 Oct 2018 16:40:24 +0100, snipeco.2@gmail.com (Sn!pe) wrote: > >Sir Gerkory Hall, Esq. <nelly@fake.yacht_maester> grotesquely grunted: > >> On Sun, 14 Oct 2018 01:41:42 -0700 (Seattle), Jeff-Relf.Me @. wrote: > >> > >> <...> > >> > >> >I prefer "Text" (INN) servers because they have accurate "Path:" lines; > >> >"Path:" is the only line that's never fake; . . . > >> > >> <...> > >> > >> I regularly fake the Path: Altopia allows path preloading. A nice feature > >> when forging and frogging. I rarely forge because that's a TOSSable offence > >> but I do sneak a forgery in from time to time just to stir the pot and for > >> future angst should the nym being forged find out and become pissed off. > >> > >> I've snuck in more than a few Sn!pe forgeries in obscure froups just > >> because he hates it and also because he promised to get me TOSSed > >> should I ever forge, instead of frog him. LOL. > >> > > > >See you, Gerk. You -still- can't do a perfect forgery of me, > >ineffectual prattler that you are. Just sayin'. > > I am able to do a perfect forgery and would except for > the fact that you'd use it to get me TOSSed. You said > as much. [sigh] We've been through this before, in this very froup. Post your perfect forgery of me here, using Eternal September and including the header:- Injection-Info: snipe.eternal-september.org; [...] - and maybe we'll believe you. Once again, I hereby give you full permission, for one post only, to prove that you can make a perfect, undetectable forgery of me. -- ^Ï^ My pet rock Gordon just is.
[toc] | [prev] | [next] | [standalone]
| From | "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> |
|---|---|
| Date | 2018-10-14 12:23 -0400 |
| Subject | Re: "Path:" is the only line that's never fake. |
| Message-ID | <g0r6sd1g9l8f6ov0n3911lquh2it0rr9q6@4ax.com> |
| In reply to | #471996 |
On Sun, 14 Oct 2018, snipeco.2@gmail.com (Sn!pe) wrote: >Sir Gregory Hall, Esq. <greghall@yacht_maester.fake> wrote: >> On Sun, 14 Oct 2018, snipeco.2@gmail.com (Sn!pe) wrote: >> >> >See you, Gerk. You -still- can't do a perfect forgery of me, >> >ineffectual prattler that you are. Just sayin'. >> >> I am able to do a perfect forgery and would except for >> the fact that you'd use it to get me TOSSed. You said >> as much. > >[sigh] > >We've been through this before, in this very froup. > >Post your perfect forgery of me here, using >Eternal September and including the header:- > >Injection-Info: snipe.eternal-september.org; [...] > >- and maybe we'll believe you. > >Once again, I hereby give you full permission, >for one post only, to prove that you can make >a perfect, undetectable forgery of me. "Am able to" and "Am willing to" are birds of a different feather. I don't trust ES any more than I can throw an ostrich over a prison fence. In the past they were guilty of sharing so-called confidential IP information so what's to keep them from doing so yet again? You are probably in league with those vultures. -- Yours Truly, Gregory Hall "Sometimes it's hard to tell them apart. When he drowns in his shit bucket, I plan to nominate him for a Darwin." --Rhonda Lea Kirk Fries
[toc] | [prev] | [next] | [standalone]
| From | snipeco.2@gmail.com (Wader of Doom) |
|---|---|
| Date | 2018-10-14 18:01 +0100 |
| Subject | Re: "Path:" is the only line that's never fake. |
| Message-ID | <1nwo9yu.8wig1aq8199zN%snipeco.2@gmail.com> |
| In reply to | #472000 |
Sir Gregory Hall, Esq. <greghall@yacht_maester.fake> wrote: > On Sun, 14 Oct 2018, snipeco.2@gmail.com (Sn!pe) wrote: > >Sir Gregory Hall, Esq. <greghall@yacht_maester.fake> wrote: > >> On Sun, 14 Oct 2018, snipeco.2@gmail.com (Sn!pe) wrote: > >> > >> >See you, Gerk. You -still- can't do a perfect forgery of me, > >> >ineffectual prattler that you are. Just sayin'. > >> > >> I am able to do a perfect forgery and would except for > >> the fact that you'd use it to get me TOSSed. You said > >> as much. > > > > [sigh] > > > > We've been through this before, in this very froup. > > > > Post your perfect forgery of me here, using > > Eternal September and including the header:- > > > > Injection-Info: snipe.eternal-september.org; [...] > > > > - and maybe we'll believe you. > > > > Once again, I hereby give you full permission, > > for one post only, to prove that you can make > > a perfect, undetectable forgery of me. > > > > "Am able to" and "Am willing to" are birds of a > different feather. > > I don't trust ES any more than I can throw an > ostrich over a prison fence. In the past they > were guilty of sharing so-called confidential IP > information so what's to keep them from doing > so yet again? > > You are probably in league with those vultures. > Bok-bok, bok-bok, bok-bok, bok-ERK! -- Darth Wader, WoD #1 No Club I can't help it 'bout the shape I'm in, I can't sing, I ain't pretty and my legs are thin. Don't ask me what I think of you, I might not give the answer that you want me to.
[toc] | [prev] | [next] | [standalone]
| From | Jeff-Relf.Me @. |
|---|---|
| Date | 2018-10-14 14:29 -0700 |
| Subject | No one can do "a perfect forgery" of my posts. |
| Message-ID | <Jeff-Relf.Me@Oct.14--2.29pm.Seattle.2018> |
| In reply to | #471992 |
> > You -still- can't do a perfect forgery of me, > > I am able to do a perfect forgery, and would, except for > the fact that you'd use it to get me TOSSed. You said as much. No one can do "a perfect forgery" of my posts because the "Path:" line would be off.
[toc] | [prev] | [next] | [standalone]
| From | "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> |
|---|---|
| Date | 2018-10-14 17:33 -0400 |
| Subject | Re: No one can do "a perfect forgery" of my posts. |
| Message-ID | <8gd7sd9p3tdaoso7l38r906sd6ae0bo2c6@4ax.com> |
| In reply to | #472055 |
On Sun, 14 Oct 2018 14:29:27 -0700 (Seattle), Jeff-Relf.Me @. wrote: >Path: peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.fr7!futter-mich.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!post01.iad!fx07.iad.POSTED!not-for-mail I can easily path preload that path. -- Yours Truly, Gregory Hall "Sometimes it's hard to tell them apart. When he drowns in his shit bucket, I plan to nominate him for a Darwin." --Rhonda Lea Kirk Fries
[toc] | [prev] | [next] | [standalone]
Page 1 of 8 [1] 2 3 4 5 6 7 8 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web