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 2 of 8 — ← Prev page 1 [2] 3 4 5 6 7 8 Next page →
| From | snipeco.2@gmail.com (Sn!pe) |
|---|---|
| Date | 2018-10-14 22:47 +0100 |
| Subject | Re: No one can do "a perfect forgery" of my posts. |
| Message-ID | <1nwon9a.1bk6xu4puq26kN%snipeco.2@gmail.com> |
| In reply to | #472056 |
Sir Gregory Hall, Esq. <greghall@yacht_maester.fake> wrote: > 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. Yeah, yeah, with alt.net appearing at both ends of the preload. -- ^Ï^ My pet rock Gordon just is.
[toc] | [prev] | [next] | [standalone]
| From | "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> |
|---|---|
| Date | 2018-10-14 17:53 -0400 |
| Subject | Re: No one can do "a perfect forgery" of my posts. |
| Message-ID | <cje7sd9qfar724kqhlsv462merfa83pspm@4ax.com> |
| In reply to | #472059 |
On Sun, 14 Oct 2018 22:47:14 +0100, snipeco.2@gmail.com (Sn!pe) wrote: >Sir Gregory Hall, Esq. <greghall@yacht_maester.fake> wrote: > >> 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. > >Yeah, yeah, with alt.net appearing at both ends of the preload. No, I only have to put the alt.net in to adhere to the rules. I can easily leave the alt.net out but that would be rule-breaking and I always follow the rules. -- 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 22:58 +0100 |
| Subject | Re: No one can do "a perfect forgery" of my posts. |
| Message-ID | <1nwonpc.11tcg921075hi9N%snipeco.2@gmail.com> |
| In reply to | #472062 |
Sir Gregory Hall, Esq. <greghall@yacht_maester.fake> wrote: > On Sun, 14 Oct 2018 22:47:14 +0100, snipeco.2@gmail.com (Sn!pe) wrote: > > >Sir Gregory Hall, Esq. <greghall@yacht_maester.fake> wrote: > > > >> 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. > > > >Yeah, yeah, with alt.net appearing at both ends of the preload. > > No, I only have to put the alt.net in to adhere to the rules. > I can easily leave the alt.net out but that would be rule-breaking > and I always follow the rules. You're just scared that CC would TOS you, because you have no other NSP to go to. -- ^Ï^ My pet rock Gordon just is.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-14 14:56 -0700 |
| Subject | Re: No one can do "a perfect forgery" of my posts. |
| Message-ID | <0183dae4-278d-47b2-b226-b80c108ee330@googlegroups.com> |
| In reply to | #472059 |
On Sunday, October 14, 2018 at 2:47:17 PM UTC-7, Sn!pe wrote: > Sir Gregory Hall, Esq. <greghall@yacht_maester.fake> wrote: > > > 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. > > Yeah, yeah, with alt.net appearing at both ends of the preload. > > -- > ^Ï^ My pet rock Gordon just is. Do you have a CCNA certification? Both Newton and Steven 'The Fool' Petruzzellis had their oversights and their humiliations. But one played it as the effect of ghosts and didn't do anything too appalling that could not be blamed on someone else. I have been in multiple groups to even partially understand the depths of Steven 'The Fool' Petruzzellis's indecency. - I Left My Husband & Daughter At Home And THIS happened http://www.5z8.info/mercenary_w5v9dl_open.exe https://youtu.be/GPPqvw8iEBs Jonas Eklundh Communication
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-14 14:41 -0700 |
| Subject | Re: No one can do "a perfect forgery" of my posts. |
| Message-ID | <d62272ea-8de0-4157-a138-fcd338a1c8a1@googlegroups.com> |
| In reply to | #472055 |
On Sunday, October 14, 2018 at 2:29:30 PM UTC-7, Jeff-Relf.Me wrote: > > > 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. Don't look now, but I think Klaus Schadenfreude has a serious woody for John Gohde. Being self-governed as it is, bulletin boards will never go away but it'll never be what your grandfather would use. When I was new here, I wanted to be trusting and nonjudgemental. I gave Klaus Schadenfreude more than a reasonable person could be expected to. Who are you even talking to? What do you get out of lying? He upsets multiple groups of people who have nothing to do with anything, but that's a conceited fool for you. What you and I care about isn't a factor. Klaus Schadenfreude doesn't have any concept of what he is blubbering about. Klaus Schadenfreude is an idiot -- folks have blocked his socks. What he really needs is a bot that keeps switching names, then flood posts have a possibility at being one quarter as repetitive as he is. -- Top Ten Ways Klaus Schadenfreude Trolls https://www.youtube.com/watch?v=u4xD43Khhkw https://youtu.be/qwb1Ez0GWMA Jonas Eklundh Communication
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-14 08:54 -0700 |
| Subject | Re: "Path:" is the only line that's never fake. |
| Message-ID | <96f7cba7-271a-45f5-a1d1-6fea6a7a7025@googlegroups.com> |
| In reply to | #471991 |
On Sunday, October 14, 2018 at 8:40:28 AM UTC-7, 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'. > > -- > ^Ï^ My pet rock Gordon just sneered. Having to put up with the use of Fedora is not what most want to do. With no support at all, as is the norm for Onion Knight. Dropping support for 16 bit apps is obvious. Why does Onion Knight focus on Klaus Schadenfreude's ego so much? He is as incompetent as Onion Knight. Of course my first statement stands sincere and correct. Frankly I do not really think you understand. -- "You'll notice how quickly he loses interest when everything is about him. He clearly wants the attention" Steve Carroll, making the dumbest comment ever uttered.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@nospam.com> |
|---|---|
| Date | 2018-10-14 11:26 -0400 |
| Message-ID | <ufJwD.316258$Vl2.213729@fx46.iad> |
| In reply to | #471946 |
On 10/14/2018 4:41 AM, Jeff-Relf.Me@. wrote: >> 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. At that rate you can get all of cola since July 2003 in 94 minutes. > I "pipeline" 100 "Article" commands at a time ( all at once ), > and I use a 4 MegaByte input buffer -- it's very sophisticated. Show us the source! > 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. You do these checks and still get 1000 posts in 4 seconds? > 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. Are you storing all the downloaded data in one big file?
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-14 09:23 -0700 |
| Message-ID | <0bb4578b-009a-4fe5-aa04-5830cdcaa32e@googlegroups.com> |
| In reply to | #471988 |
On Sunday, October 14, 2018 at 9:27:25 AM UTC-6, DFS wrote: > On 10/14/2018 4:41 AM, Jeff-Relf.Me@. wrote: > >> 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. > > At that rate you can get all of cola since July 2003 in 94 minutes. That's what I'm getting now using the telnet script owl gave me (and it goes to one big file). > > I "pipeline" 100 "Article" commands at a time ( all at once ), > > and I use a 4 MegaByte input buffer -- it's very sophisticated. > > Show us the source! Or explain what it means, even ;) > > 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. > > You do these checks and still get 1000 posts in 4 seconds? That would be pretty amazing so I doubt it. > > 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. > > Are you storing all the downloaded data in one big file?
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-14 18:53 +0000 |
| Message-ID | <a8s00b0a.39s@rooftop.invalid> |
| In reply to | #471999 |
Steve Carroll <fretwizzer@gmail.com> wrote: > On Sunday, October 14, 2018 at 9:27:25 AM UTC-6, DFS wrote: >> On 10/14/2018 4:41 AM, Jeff-Relf.Me@. wrote: > >> > 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. >> >> You do these checks and still get 1000 posts in 4 seconds? > > That would be pretty amazing so I doubt it. > That kind of check is almost instantaneous. Here, about six million lines of mixed \n, \r\n tested in less than a second: anon@lowtide:~/usenet/database$ file rns rns: ASCII text, with CRLF, LF line terminators anon@lowtide:~/usenet/database$ wc -l rns 6160000 rns anon@lowtide:~/usenet/database$ time ./testrns '\r' count: 2080000 '\n' count: 6160000 '\r\n' count: 2080000 real 0m0.666s user 0m0.628s sys 0m0.028s anon@lowtide:~/usenet/database$
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2018-10-14 13:27 -0700 |
| Message-ID | <31d8b949-9b46-4312-9787-ac6067ca8c6a@googlegroups.com> |
| In reply to | #472029 |
On Sunday, October 14, 2018 at 12:53:45 PM UTC-6, owl wrote: > Steve Carroll <fretwizzer@gmail.com> wrote: > > On Sunday, October 14, 2018 at 9:27:25 AM UTC-6, DFS wrote: > >> On 10/14/2018 4:41 AM, Jeff-Relf.Me@. wrote: > > > > >> > 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. > >> > >> You do these checks and still get 1000 posts in 4 seconds? > > > > That would be pretty amazing so I doubt it. > > > > That kind of check is almost instantaneous. Here, about six million > lines of mixed \n, \r\n tested in less than a second: Holy Batsh*t! > > anon@lowtide:~/usenet/database$ file rns > rns: ASCII text, with CRLF, LF line terminators > anon@lowtide:~/usenet/database$ wc -l rns > 6160000 rns > anon@lowtide:~/usenet/database$ time ./testrns > '\r' count: 2080000 > '\n' count: 6160000 > '\r\n' count: 2080000 > > real 0m0.666s > user 0m0.628s > sys 0m0.028s > anon@lowtide:~/usenet/database$
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <Melzzzzz@zzzzz.com> |
|---|---|
| Date | 2018-10-14 20:55 +0000 |
| Message-ID | <t3OwD.19532$ik6.12211@fx09.am4> |
| In reply to | #472045 |
On 2018-10-14, Steve Carroll <fretwizzer@gmail.com> wrote: > On Sunday, October 14, 2018 at 12:53:45 PM UTC-6, owl wrote: >> Steve Carroll <fretwizzer@gmail.com> wrote: >> > On Sunday, October 14, 2018 at 9:27:25 AM UTC-6, DFS wrote: >> >> On 10/14/2018 4:41 AM, Jeff-Relf.Me@. wrote: >> >> > >> >> > 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. >> >> >> >> You do these checks and still get 1000 posts in 4 seconds? >> > >> > That would be pretty amazing so I doubt it. >> > >> >> That kind of check is almost instantaneous. Here, about six million >> lines of mixed \n, \r\n tested in less than a second: > > Holy Batsh*t! nntp servers are much slower then processing power of computer. Needles to say I have compressed disks and I don't notice any slowdowns... Decompressing file before reading takes less time then reading, actually CPU is not busy at all. -- press any key to continue or any other to quit...
[toc] | [prev] | [next] | [standalone]
| From | Jeff-Relf.Me @. |
|---|---|
| Date | 2018-10-14 14:23 -0700 |
| Subject | Pipelining "Article" commands. |
| Message-ID | <Jeff-Relf.Me@Oct.14--2.23pm.Seattle.2018> |
| In reply to | #471988 |
> > I "pipeline" 100 "Article" commands at a time ( all at once ), > > and I use a 4 MegaByte input buffer -- it's very sophisticated. > > Show us the source! You've seen it; it's "X.CPP" in "Jeff-Relf.Me/X.ZIP". LoopJ( er( 100, ReqArts ) ) d += _Str( d, "Article %I64d\r\n", artNum-- ); Oddly, "Article %d" doesn't work, even though I'm running x64 code. Updating Visual Studio may change the "Windows SDK" and the "14.15.26726" in "C:\__\EXEs\VisualStudio2017\VC\Tools\MSVC\14.15.26726\lib\x64". My "text" servers: News5.Open-News-Network.ORG News2.Open-News-Network.ORG > > 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. > > You do these checks and still get 1000 posts in 4 seconds? Yes, posts are converted as they're downloaded. > > 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. > > Are you storing all the downloaded data in one big file? Yes, it updates "Cola.TXT" and/or "Phy.TXT"; I keep what I want to read, discarding the rest; see: Jeff-Relf.Me/Cola_Regs.HTM My posts to Usenet ( since Feb 2012 ): Jeff-Relf.Me/Posts.TXT
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-15 13:49 +0000 |
| Message-ID | <s98a0b80ab.a3@rooftop.invalid> |
| In reply to | #471988 |
DFS <nospam@nospam.com> wrote:
> On 10/14/2018 4:41 AM, Jeff-Relf.Me@. wrote:
>>> 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.
>
> At that rate you can get all of cola since July 2003 in 94 minutes.
>
>
>> I "pipeline" 100 "Article" commands at a time ( all at once ),
>> and I use a 4 MegaByte input buffer -- it's very sophisticated.
>
> Show us the source!
>
>
>> 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.
>
> You do these checks and still get 1000 posts in 4 seconds?
>
>
>> 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.
>
> Are you storing all the downloaded data in one big file?
>
>
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()
------------------------------
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-15 07:34 -0700 |
| Message-ID | <c35d7329-06a7-4384-8f55-5ad8b552aaad@googlegroups.com> |
| In reply to | #472151 |
On Monday, October 15, 2018 at 6:49:39 AM UTC-7, owl wrote:
> DFS <nospam@nospam.com> wrote:
> > On 10/14/2018 4:41 AM, Jeff-Relf.Me@. wrote:
> >>> 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.
> >
> > At that rate you can get all of cola since July 2003 in 94 minutes.
> >
> >
> >> I "pipeline" 100 "Article" commands at a time ( all at once ),
> >> and I use a 4 MegaByte input buffer -- it's very sophisticated.
> >
> > Show us the source!
> >
> >
> >> 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.
> >
> > You do these checks and still get 1000 posts in 4 seconds?
> >
> >
> >> 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.
> >
> > Are you storing all the downloaded data in one big file?
> >
> >
>
> 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()
> ------------------------------
One guy reported him years ago. As expected, it did squat to thwart the dunce.
I think Ronb does not even know what is wrong with Trump.
Don't look now, but I think Ronb has a serious mancrush on Snit.
--
I Left My Husband & Daughter At Home And THIS happened!!
https://youtu.be/lF8yk7ul4Mw
https://www.reddit.com/r/linux/comments/6sfhq6/what_desktop_tasks_does_linux_handle_better_than/
Jonas Eklundh Communication AB
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@nospam.com> |
|---|---|
| Date | 2018-10-15 21:54 -0400 |
| Message-ID | <LwbxD.307388$3L2.37190@fx44.iad> |
| In reply to | #472151 |
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.
Of those it writes, there's a blank line between each line of the post.
Throws error at the end:
socket.timeout: timed out
Takes ~4 seconds for 100 requests.
I assume you get better results.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-15 19:15 -0700 |
| Message-ID | <e606609c-cff5-4243-b2c1-d19581e7f9e3@googlegroups.com> |
| In reply to | #472249 |
On Monday, October 15, 2018 at 6:53:50 PM UTC-7, DFS 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.
>
> Of those it writes, there's a blank line between each line of the post.
>
> Throws error at the end:
> socket.timeout: timed out
>
> Takes ~4 seconds for 100 requests.
>
> I assume you get better results.
Hint: You won't go into a party, guzzle all the grog, deck all the goats, nab the valuables and technicolor yawn in the bedroom without being disinvited. I will not ask Slimer how any part of Desk Rabbit's rear tastes no matter how habitually Slimer licks it. Enough already. You're again trying to act like you know as much as Desk Rabbit. You're the dull knife in the drawer and your many hare-brained scripts show this. LOL!
That is the problem today and newer teachers don't have a clue; people from pre-tech generations should know better than to fall for the indoctrination BS. Where did you learn to program?
They insist Googling for advice for an RMS-approved application is trolling.
I do not understand that. Illiteracy is illiteracy and there are all kinds of people who are okay with it. A few are even teachers.
--
E-commerce Simplified
http://www.5z8.info/myspace-of-sex_q7q7zl_instant-purchase
Jonas Eklundh Communication AB
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-15 21:51 -0700 |
| Message-ID | <5c8dd3e0-02c3-406b-a82b-f4b8737e744a@googlegroups.com> |
| In reply to | #472251 |
On Monday, October 15, 2018 at 7:15:53 PM UTC-7, Steve Carroll wrote:
> On Monday, October 15, 2018 at 6:53:50 PM UTC-7, DFS 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.
> >
> > Of those it writes, there's a blank line between each line of the post.
> >
> > Throws error at the end:
> > socket.timeout: timed out
> >
> > Takes ~4 seconds for 100 requests.
> >
> > I assume you get better results.
>
>
>
> Hint: You won't go into a party, guzzle all the grog, deck all the goats, nab the valuables and technicolor yawn in the bedroom without being disinvited. I will not ask Slimer how any part of Desk Rabbit's rear tastes no matter how habitually Slimer licks it. Enough already. You're again trying to act like you know as much as Desk Rabbit. You're the dull knife in the drawer and your many hare-brained scripts show this. LOL!
>
> That is the problem today and newer teachers don't have a clue; people from pre-tech generations should know better than to fall for the indoctrination BS. Where did you learn to program?
>
> They insist Googling for advice for an RMS-approved application is trolling.
>
> I do not understand that. Illiteracy is illiteracy and there are all kinds of people who are okay with it. A few are even teachers.
>
> --
> E-commerce Simplified
> http://www.5z8.info/myspace-of-sex_q7q7zl_instant-purchase
> Jonas Eklundh Communication AB
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In article <328ae2c8-12e1-4830-b455-53187a4bc309@googlegroups.com>, Steve
Carroll wrote:
> > Sandman:
> > <http://usenet.sandman.net/misc/snit_flood> It doesn't show what
> > interval the script is run at, but how he has used it, at least in
> > the beginning. I stopped logging it this way back in may :)
>
> From what I've personally looked at, it looks like it's all over the
> map.
Yes, with obvious scripted sessions. Not saying some of it isn't manual.
> > Sandman:
> > Maybe I'll update it :)
>
> What would it take to do that?
For "later" to occur!
<http://usenet.sandman.net/misc/postingtimes/Snit/Flooding>
That's a running tally of Snit's non-sock posts and his flooding during the
last month. It'll update automatically and always show the last two months.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBAgAGBQJZyKjaAAoJECFEwfBaA+jR4QEIAIWE3GfOGnnxynLfUhRnWv+l
OkvAvQ8GofGI1JjIOn7NnlyfGRV/JPiIzJmzoCrdV6uY9E9qaYOXScF4M5Vas4bv
2WqBlNIh7se9g6Zkj330L12RkuZckS5l0nJ++OTbmztOzLtAlrWKHADTiJ9u8JnR
BCjcAhMrjQ0Jwut34hJr57pzj7p88oYCPP46IcrEMbWnd03n43BGUVLGr9i9pYU+
7F6867hOzaFJ4DdRE52zv15yIYVUIHx7HFNNtV7ZfPRBRQQuyA403S8PM1RC/nQ/
RKau+ma21bzltpxlqTO+XAXMMLLZiGXy8hbv4Ib/tPlc5cKI3P6UDZ4exbbCmnE=
=1Dqa
-----END PGP SIGNATURE-----
--
Do not click this link!
http://tinyurl.com/kmqe66h
https://youtu.be/48_DdtLGR9s
Jonas Eklundh
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2018-10-16 03:16 +0000 |
| Message-ID | <s11p40z00b.aa@rooftop.invalid> |
| In reply to | #472249 |
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? If I have it ask for articles beyond
the latest, my server returns "423 Bad article number" for each
of those.
https://tools.ietf.org/html/rfc3977#section-6.2.1
<quote>
First form (message-id specified)
220 0|n message-id Article follows (multi-line)
430 No article with that message-id
Second form (article number specified)
220 n message-id Article follows (multi-line)
412 No newsgroup selected
423 No article with that number
Third form (current article number used)
220 n message-id Article follows (multi-line)
412 No newsgroup selected
420 Current article number is invalid
</quote>
> Of those it writes, there's a blank line between each line of the post.
>
For me, it properly writes the '.' article separator.
> 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$
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2018-10-15 20:33 -0700 |
| Message-ID | <acd0e154-3d1b-418e-9018-8e16cc9c7dfd@googlegroups.com> |
| In reply to | #472255 |
On Monday, October 15, 2018 at 8:16:59 PM UTC-7, 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? If I have it ask for articles beyond
> the latest, my server returns "423 Bad article number" for each
> of those.
>
> https://tools.ietf.org/html/rfc3977#section-6.2.1
> <quote>
> First form (message-id specified)
> 220 0|n message-id Article follows (multi-line)
> 430 No article with that message-id
>
> Second form (article number specified)
> 220 n message-id Article follows (multi-line)
> 412 No newsgroup selected
> 423 No article with that number
>
> Third form (current article number used)
> 220 n message-id Article follows (multi-line)
> 412 No newsgroup selected
> 420 Current article number is invalid
> </quote>
>
>
> > Of those it writes, there's a blank line between each line of the post.
> >
>
> For me, it properly writes the '.' article separator.
>
> > 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$
Perhaps you use it erroneously. Do you not understand the use of https? But God feels the need to insult the cult-like herd of convenient friends. I'm well aware the stuff I link to from YouTube is total tenderfoot level; that said, it is good enough. That's what God does when he gets cornered. He creates a flood, starts a trolling thread so he can claim it was Steve Petruzzellis. Don't blame me it was my left hand... and then God replies to it with his right hand. I'm getting a lot of killed files. I'm guessing the sock frenzy circus is in its brain damage mode again. Drives the trolls crazy when they do not get attention. I'd reply to God honestly but he's a moron who screws around to realize his craving to call everyone a jerk. Despite God's claim that he has "no enthusiasm in making automated posts" (a lie as demonstrated by the fact that he annoyed everyone in COLA) he was seen asking others how they would install a virus remotely. I bet he thinks his wife's life was rough.
--
"You'll notice how quickly he loses interest when everything is about him. He clearly wants the attention"
Steve Carroll, making the dumbest comment ever uttered.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@nospam.com> |
|---|---|
| Date | 2018-10-16 10:26 -0400 |
| Message-ID | <5ymxD.210161$nH2.93852@fx26.iad> |
| In reply to | #472255 |
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.
[toc] | [prev] | [next] | [standalone]
Page 2 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