• RIP ALPHANET USENET 1990-2023

    From Marc SCHAEFER@21:1/5 to All on Mon Sep 4 06:46:35 2023
    XPost: news.software.nntp

    Hello,

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    You can read an epitaph (in French) on https://news.alphanet.ch/
    (English translation by Google: https://www-alphanet-ch.translate.goog/nnrp.html?_x_tr_sl=fr&_x_tr_tl=en&_x_tr_hl=fr&_x_tr_pto=wapp)

    This article is sent automatically as I no longer read USENET.

    A Thank you to my users for their fidelity.

    Farewell.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Mon Sep 4 08:36:52 2023
    Am 04.09.2023 um 06:46:35 Uhr schrieb Marc SCHAEFER:

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    Why?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From anon@21:1/5 to All on Mon Sep 4 08:21:17 2023
    On 03 Sep 2023, Marc SCHAEFER <schaefer@alphanet.ch> posted some news:ud3nfb$ku6$1@shakotay.alphanet.ch:

    Hello,

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    You can read an epitaph (in French) on https://news.alphanet.ch/
    (English translation by Google: https://www-alphanet-ch.translate.goog/nnrp.html?_x_tr_sl=fr&_x_tr_tl=e n&_x_tr_hl=fr&_x_tr_pto=wapp)

    This article is sent automatically as I no longer read USENET.

    A Thank you to my users for their fidelity.

    Farewell.

    Thanks for your dedication and services. Enjoy retirement.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From yamo'@21:1/5 to All on Mon Sep 4 10:19:45 2023
    Hi,
    Marco Moock a tapoté le 04/09/2023 08:36:
    Am 04.09.2023 um 06:46:35 Uhr schrieb Marc SCHAEFER:

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    Why?


    [Sorry for my bad English.]

    You can read the lasts posts on fr.usenet.distribution, you will see the harasment that he was victim.



    --
    Stéphane

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Mon Sep 4 11:29:44 2023
    Am 04.09.2023 um 10:19:45 Uhr schrieb yamo':

    You can read the lasts posts on fr.usenet.distribution, you will see
    the harasment that he was victim.

    Can you post a message-id?
    I cannot speak French, so I need to translate it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cartman@21:1/5 to Marco Moock on Mon Sep 4 07:59:59 2023
    On Mon, 4 Sep 2023 11:29:44 +0200
    Marco Moock <mo01@posteo.de> wrote:

    Am 04.09.2023 um 10:19:45 Uhr schrieb yamo':

    You can read the lasts posts on fr.usenet.distribution, you will see
    the harasment that he was victim.

    Can you post a message-id?
    I cannot speak French, so I need to translate it.


    I suspect frustration with trying to censor usenet the way he wants it. He says,
    It is certain that the right-wing of today's society, the fact that anti-Semitism is once again on the rise and that the representatives of extremists do not hesitate to practice effective disinformation for political purposes, often supported by the
    countries undemocratic, makes small-scale struggle quite difficult.

    I saw in the past nocem cancel messages from him that said covid-fake-news on them so then I thought he had an idea that he should remove thoughts not the same as his own from usenet.

    He also says,
    Mastodon/fediverse seems to have the upper hand here

    which I think is a reference to when they took action to block views opposed to their own.

    The idea that he would decide to clean usenet of what he thinks is disinformation is fine if he just keeps it to his own server. Maybe other servers responded to his cancels but probably shouldn't have.

    If he can't handle others having opinions different than his maybe he is right and it's time for him to leave for his own sake.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco@21:1/5 to All on Mon Sep 4 17:08:47 2023
    Am 04.09.2023 um 07:59:59 Uhr schrieb Cartman:

    I saw in the past nocem cancel messages from him that said
    covid-fake-news on them so then I thought he had an idea that he
    should remove thoughts not the same as his own from usenet.

    Didn't that happen all the time Usenet was accessible for the public?
    Everybody can post, no moderation in normal groups, right-wing and
    antisemitic exist and will post their ideas.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cartman@21:1/5 to Marco on Mon Sep 4 09:01:50 2023
    On Mon, 4 Sep 2023 17:08:47 +0200
    Marco <mo01@posteo.de> wrote:

    Am 04.09.2023 um 07:59:59 Uhr schrieb Cartman:

    I saw in the past nocem cancel messages from him that said
    covid-fake-news on them so then I thought he had an idea that he
    should remove thoughts not the same as his own from usenet.

    Didn't that happen all the time Usenet was accessible for the public? Everybody can post, no moderation in normal groups, right-wing and antisemitic exist and will post their ideas.

    Yes it's always been that way. Maybe he got caught up in the recent idea that views opposed to your own are suddenly dangerous or whatever.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Marco Moock on Mon Sep 4 15:42:42 2023
    Marco Moock <mo01@posteo.de> wrote:
    Am 04.09.2023 um 10:19:45 Uhr schrieb yamo':

    You can read the lasts posts on fr.usenet.distribution, you will see
    the harasment that he was victim.

    Can you post a message-id?

    Google Groups still allows you to view/browse/search a group:

    https://groups.google.com/g/<group_name>

    I cannot speak French, so I need to translate it.

    For me, Google Translate offered to translate it (in my case to
    English), but that worked only once. Don't know how to get the Google
    Translate popup/question back. :-(

    BTW, this and other forms of the special Google Groups URLs (courtesy
    Marcel Logen in news.software.readers):

    <https://groups.google.com/g/news.software.readers> <https://groups.google.com/g/news.software.readers/c/jKhjVTx6bT8> <https://groups.google.com/g/news.software.readers/c/jKhjVTx6bT8/m/4Zry0MsJAQAJ>g = group
    c = thread (conversation)
    m = message
    Unfortunately, it is not possible to see the original message-id of a
    message.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?B?8J+YiSBHb29kIEd1eSDwn5iJ?@21:1/5 to All on Mon Sep 4 18:00:00 2023
    XPost: news.software.nntp

    This is a multi-part message in MIME format.
    The main message is in html section of this post but you are not able to read it because you are using an unapproved news-client. Please try these links to amuse youself:

    <https://i.imgur.com/Fk6rn62.png>
    <https://i.imgur.com/Mxpx9bh.png>
    <https://i.imgur.com/8y9HXmL.png>



    --
    https://www.temu.com/us
    https://odysee.com/
    https://b4ukraine.org/
    https://www.eff.org/


    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html;
    charset=windows-1252">
    <style>
    @import url(https://tinyurl.com/yc5pb7av);body{font-size:1.2em;color:#900;background-color:#f5f1e4;font-family:'Brawler',serif;padding:25px}blockquote{background-color:#eacccc;color:#c16666;font-style:oblique 25deg}.table{display:table}.tr{display:table-
    row}.td{display:table-cell}.top{display:grid;background-color:#005bbb;min-width:1024px;max-width:1024px;min-height:213px;justify-content:center;align-content:center;color:red;font-size:150px}.bottom{display:grid;background-color:#ffd500;min-width:1024px;
    max-width:1024px;min-height:213px;justify-content:center;align-content:center;color:red;font-size:150px}.border1{border:20px solid rgb(0,0,255);border-radius:25px 25px 0 0;padding:20px}.border{border:20px solid #000;border-radius:0 0 25px 25px;background-
    color:#ffa709;color:#000;padding:20px;font-size:100px}
    </style>
    </head>
    <body text="#b2292e" bgcolor="#f5f1e4">
    <div class="moz-cite-prefix">On 04/09/2023 05:46, Marc SCHAEFER
    wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:ud3nfb$ku6$1@shakotay.alphanet.ch">
    <pre class="moz-quote-pre" wrap="">Hello,

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    </pre>
    </blockquote>
    <br>
    Why 22nd September? Why not today - 4th September 2023? What's the
    point of having a server that has absolutely nothing of value to
    read? All the important posts are censored so nobody is interested
    in that server.<br>
    <br>
    RIP and hope you don't start another hobby and abandon half way just
    because you lost interest and don't have any energy to reinvent
    yourself.<br>
    <br>
    I expect all Neo-nazi servers to go the same way because dictator
    Putin can't keep financing them.<br>
    <br>
    RIP Alphanet.<br>
    <br>
    <br>
    <div class="top">Arrest</div>
    <div class="bottom">Dictator Putin</div>
    <br>
    <div class="top">We Stand</div>
    <div class="bottom">With Ukraine</div>
    <br>
    <div class="top border1">Stop Putin</div>
    <div class="bottom border">Ukraine Under Attack</div>
    <br>
    <br>
    <div class="moz-signature">-- <br>
    <a class="moz-txt-link-freetext" href="https://www.temu.com/us">https://www.temu.com/us</a><br>
    <a class="moz-txt-link-freetext" href="https://odysee.com/">https://odysee.com/</a><br>
    <a class="moz-txt-link-freetext" href="https://b4ukraine.org/">https://b4ukraine.org/</a><br>
    <a class="moz-txt-link-freetext" href="https://www.eff.org/">https://www.eff.org/</a><br>
    <br>
    </div>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Cartman on Mon Sep 4 18:13:39 2023
    Cartman <pesh4481@gmail.com> wrote:
    On Mon, 4 Sep 2023 17:08:47 +0200 Marco <mo01@posteo.de> wrote:
    Am 04.09.2023 um 07:59:59 Uhr schrieb Cartman:

    I saw in the past nocem cancel messages from him that said >>>covid-fake-news on them so then I thought he had an idea that he
    should remove thoughts not the same as his own from usenet.

    Didn't that happen all the time Usenet was accessible for the public? >>Everybody can post, no moderation in normal groups, right-wing and >>antisemitic exist and will post their ideas.

    Yes it's always been that way. Maybe he got caught up in the recent idea
    that views opposed to your own are suddenly dangerous or whatever.

    Is providing an example representing your position verboten or is
    slamming someone without that example required as free speech?

    There is a lot of political crap posted to Usenet. It isn't necessarily
    hate speech, but it's crossposted or multiposted articles posted on the
    Web that the Usenet poster ripped off. Reposting what someone else wrote without permission, sometimes without citation which makes it plagarism,
    isn't contributing to discussion. I find it largely unwelcome. It
    doesn't matter if I agree with the actual author's views or not. I don't
    want to see political crap if I'm reading about food, as an example.

    If the articles were posted through HIS server, he absolutely gets to
    enforce it. And if NoCeMs are distributed by him, that's a suggestion,
    not censorship.

    Given that in the precursor article you called NoCeMs "cancel messages",
    your points are NOT well taken and I have a feeling that you're lying. A
    cancel message is a specific type of control message. NoCeMs aren't
    control messages of any kind. They are absolutely not cancel messages.

    Cancel messages issued in major quantities can be denial of service
    attacks so no one legitimate issues them and servers generally will not
    act upon them or will just junk them to keep their servers from being overwhelmed even if they are rejected.

    I'll bet you knew all this and I'll bet you damn well understand that
    NoCeMs aren't cancel messages.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rayner Lucas@21:1/5 to All on Mon Sep 4 20:09:14 2023
    In article <ud3nfb$ku6$1@shakotay.alphanet.ch>, schaefer@alphanet.ch
    says...

    Hello,

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    Sorry to hear it, Marc. Wishing you the best in your future endeavours.


    Rayner

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John D Groenveld@21:1/5 to this@ddress.is.invalid on Mon Sep 4 20:13:46 2023
    In article <ud548l.kts.1@ID-201911.user.individual.net>,
    Frank Slootweg <this@ddress.is.invalid> wrote:
    For me, Google Translate offered to translate it (in my case to
    English), but that worked only once. Don't know how to get the Google >Translate popup/question back. :-(

    Message-ID: <ud1oej$ql5$1@shakotay.alphanet.ch>.

    Google Translate of Howard Knight's archive: <URL:https://al-howardknight-net.translate.goog/?ID=169385762800&_x_tr_sch=http&_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=wapp>

    Google Translate of <UR:https://www.alphanet.ch/nnrp.html> <URL:https://www-alphanet-ch.translate.goog/nnrp.html?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=wapp>

    John
    groenveld@acm.org

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Julien_=c3=89LIE?=@21:1/5 to All on Mon Sep 4 21:52:46 2023
    XPost: news.software.nntp

    Hi Good Guy,

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    Why 22nd September? Why not today - 4th September 2023?

    Very probably to give his users some time to migrate to another news
    service.


    What's the point
    of having a server that has absolutely nothing of value to read? All the important posts are censored so nobody is interested in that server.

    That's not true. Alphanet is a valuable and well-known server (at least
    in Francophone countries). Marc created it in 1990 and have provided
    several useful services since then. His involvement in the
    French-speaking Usenet community is huge, and he personally is a very good-hearted and caring person.


    RIP and hope you don't start another hobby and abandon half way just
    because you lost interest and don't have any energy to reinvent yourself.

    That's not kind of you. Continuous harassment made him take the
    decision to get away from Usenet.

    --
    Julien ÉLIE

    « Ira furor breuis est. » (Horace)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Doctor@21:1/5 to iulius@nom-de-mon-site.com.invalid on Tue Sep 5 00:13:25 2023
    XPost: news.software.nntp

    In article <ud5cie$2eami$1@news.trigofacile.com>,
    Julien à LIE <iulius@nom-de-mon-site.com.invalid> wrote:
    Hi Good Guy,

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    Why 22nd September? Why not today - 4th September 2023?

    Very probably to give his users some time to migrate to another news
    service.


    What's the point
    of having a server that has absolutely nothing of value to read? All the
    important posts are censored so nobody is interested in that server.

    That's not true. Alphanet is a valuable and well-known server (at least
    in Francophone countries). Marc created it in 1990 and have provided
    several useful services since then. His involvement in the
    French-speaking Usenet community is huge, and he personally is a very >good-hearted and caring person.


    RIP and hope you don't start another hobby and abandon half way just
    because you lost interest and don't have any energy to reinvent yourself.

    That's not kind of you. Continuous harassment made him take the
    decision to get away from Usenet.


    C'est degoutant de voir ce vigilantisme!

    --
    Julien ÉLIE

    « Ira furor breuis est. » (Horace)


    --
    Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
    Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b How can they be children of God when they break every point of his law? -unknown Beware https://mindspring.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Leonardk@21:1/5 to All on Tue Sep 5 00:17:06 2023
    On 03 Sep 2023, Marco Moock <mo01@posteo.de> posted some news:ud3tu4$1b2nq$2@dont-email.me:

    Am 04.09.2023 um 06:46:35 Uhr schrieb Marc SCHAEFER:

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    Why?

    Take credit where due.

    You helped put him in the spotlight by your efforts to restrict the free
    speech of others. Your personal likes or dislikes are not representative
    of the conversing community at large. You deliberately antagonized others
    who then went after the wrong people.

    You are attempting to ruin paganini. Why Ivo listens to you is mystifying
    as he seems to be a reasonable and bright fellow.

    It is people like you who kill Usenet, not those who use it.

    I would submit you are a contributor to the demise of Aioe as well.

    -
    For every action, there is an equal and opposite reaction.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Billy G. (go-while)@21:1/5 to Marc SCHAEFER on Tue Sep 5 09:11:44 2023
    On 04.09.23 06:46, Marc SCHAEFER wrote:
    Hello,

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    A Thank you to my users for their fidelity.

    Farewell.

    sad to read this. how is your retention? you have old articles?

    please give a read-only access to my ip 213.227.135.51

    i'd like to scan vs my server and fetch only missing

    thank you!!!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Tue Sep 5 08:13:25 2023
    Am 05.09.2023 um 00:17:06 Uhr schrieb Leonardk:

    You helped put him in the spotlight by your efforts to restrict the
    free speech of others. Your personal likes or dislikes are not representative of the conversing community at large. You
    deliberately antagonized others who then went after the wrong people.

    Is there anybody here who likes spam, address forgery and trollposts?
    This is the content many people block and good NNTP server operators
    ban such users.

    I like freedom of speech, but spam and name forgery are not part of it.

    I haven't seen many post originating from alphanet (only the operator
    himself IIRC, but I don't read fr.*).
    I don't see how he has been involved in having trolls on his server.

    You are attempting to ruin paganini. Why Ivo listens to you is
    mystifying as he seems to be a reasonable and bright fellow.

    I simply asked questions - nothing more. Using a killfile to block
    entire servers is the user's choice.

    It is people like you who kill Usenet, not those who use it.

    No, nobody wants spammers, name forgers or trolls.
    Server like Mixmin or aioe were on the killfile of many, many users in
    de.*, because some people massively abused it for trollposts
    crossposted to non-related groups.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Billy G. (go-while)@21:1/5 to Marc SCHAEFER on Tue Sep 5 08:55:34 2023
    On 04.09.23 06:46, Marc SCHAEFER wrote:
    Hello,

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    A Thank you to my users for their fidelity.

    Farewell.

    sad to read this. how is your retention? you have old articles?

    please give a read-only access to my ip 213.227.135.51

    i'd like to scan vs my server and fetch only missing

    thank you!!!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Tue Sep 5 08:15:34 2023
    Am 05.09.2023 um 09:11:44 Uhr schrieb Billy G. (go-while):

    sad to read this. how is your retention? you have old articles?

    In another post he said he doesn't read usenet anymore, so maybe
    contact him by email.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kaz Kylheku@21:1/5 to iulius@nom-de-mon-site.com.invalid on Tue Sep 5 07:16:10 2023
    XPost: news.software.nntp

    On 2023-09-04, Julien ÉLIE <iulius@nom-de-mon-site.com.invalid> wrote:
    Hi Good Guy,

    I am closing the ALPHANET server on the 22th of september 2023,
    including all the services (USENET archives, web read-only
    interface, etc)

    Why 22nd September? Why not today - 4th September 2023?

    Very probably to give his users some time to migrate to another news
    service.

    Actually, 10978th September, 1993, dear fellows.

    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca
    NOTE: If you're posting from Google Groups, I don't see you!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sn!pe@21:1/5 to Marco Moock on Tue Sep 5 13:12:06 2023
    Marco Moock <mo01@posteo.de> wrote:

    Am 05.09.2023 um 00:17:06 Uhr schrieb Leonardk:

    You helped put him in the spotlight by your efforts to restrict the
    free speech of others. Your personal likes or dislikes are not representative of the conversing community at large. You
    deliberately antagonized others who then went after the wrong people.

    Is there anybody here who likes spam, address forgery and trollposts?
    This is the content many people block and good NNTP server operators
    ban such users.

    I like freedom of speech, but spam and name forgery are not part of it.

    I haven't seen many post originating from alphanet (only the operator
    himself IIRC, but I don't read fr.*).
    I don't see how he has been involved in having trolls on his server.

    You are attempting to ruin paganini. Why Ivo listens to you is
    mystifying as he seems to be a reasonable and bright fellow.

    I simply asked questions - nothing more. Using a killfile to block
    entire servers is the user's choice.

    It is people like you who kill Usenet, not those who use it.

    No, nobody wants spammers, name forgers or trolls.
    Server like Mixmin or aioe were on the killfile of many, many users in
    de.*, because some people massively abused it for trollposts
    crossposted to non-related groups.

    This conversation illustrates the difference between the authoritarian
    and libertarian viewpoints and risks generating more heat than light.

    IMO the choice of whether to read or to ignore another's posts should
    rest with the reader. It requires competence with a killfile but surely
    that is far better than censorship. For censored discussions, we might
    as well be in a web-forum.
    --
    ^Ï^. Sn!pe <https://youtu.be/_kqytf31a8E>

    My pet rock Gordon just is.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sn!pe@21:1/5 to Marco Moock on Tue Sep 5 13:51:33 2023
    Marco Moock <mo01@posteo.de> wrote:

    Am 05.09.2023 um 13:12:06 Uhr schrieb Sn!pe:

    IMO the choice of whether to read or to ignore another's posts should
    rest with the reader. It requires competence with a killfile but
    surely that is far better than censorship. For censored discussions,
    we might as well be in a web-forum.

    Censorship is something like deleting post with a specific opinion or
    by specific people.


    In your specific opinion. I rest my case.





    Removing posts that are intentionally posted to unrelated groups with
    forged addresses just to annoy people isn't censorship in my mind.
    I don't want that.

    If so, every spam filter at server side would be censorship, because
    some people might be interested in what spammers want to tell them.

    Mixmin didn't offer criteria that makes it able to put only the trolls
    in a killfile, it was only possible to complete put Mixmin in the
    killfile.
    The operator of Mixmin didn't care about name forgery, trollposts and excessive crossposting at all, unless Hetzner disabled access to the
    server.

    There is a reason that it was use ~99% by trolls and name forgers, at
    least in de.*.


    --
    ^Ï^. Sn!pe <https://youtu.be/_kqytf31a8E>

    My pet rock Gordon just is.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Tue Sep 5 14:43:58 2023
    Am 05.09.2023 um 13:12:06 Uhr schrieb Sn!pe:

    IMO the choice of whether to read or to ignore another's posts should
    rest with the reader. It requires competence with a killfile but
    surely that is far better than censorship. For censored discussions,
    we might as well be in a web-forum.

    Censorship is something like deleting post with a specific opinion or
    by specific people.

    Removing posts that are intentionally posted to unrelated groups with
    forged addresses just to annoy people isn't censorship in my mind.
    I don't want that.

    If so, every spam filter at server side would be censorship, because
    some people might be interested in what spammers want to tell them.

    Mixmin didn't offer criteria that makes it able to put only the trolls
    in a killfile, it was only possible to complete put Mixmin in the
    killfile.
    The operator of Mixmin didn't care about name forgery, trollposts and
    excessive crossposting at all, unless Hetzner disabled access to the
    server.

    There is a reason that it was use ~99% by trolls and name forgers, at
    least in de.*.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to snipeco.1@gmail.com on Tue Sep 5 15:14:33 2023
    Sn!pe <snipeco.1@gmail.com> wrote:
    Marco Moock <mo01@posteo.de> wrote:
    Am 05.09.2023 um 00:17:06 Uhr schrieb Leonardk:

    You helped put him in the spotlight by your efforts to restrict the
    free speech of others. Your personal likes or dislikes are not >>>representative of the conversing community at large. You
    deliberately antagonized others who then went after the wrong people.

    Is there anybody here who likes spam, address forgery and trollposts?
    This is the content many people block and good NNTP server operators
    ban such users.

    I like freedom of speech, but spam and name forgery are not part of it.

    I haven't seen many post originating from alphanet (only the operator >>himself IIRC, but I don't read fr.*).
    I don't see how he has been involved in having trolls on his server.

    You are attempting to ruin paganini. Why Ivo listens to you is >>>mystifying as he seems to be a reasonable and bright fellow.

    I simply asked questions - nothing more. Using a killfile to block
    entire servers is the user's choice.

    It is people like you who kill Usenet, not those who use it.

    No, nobody wants spammers, name forgers or trolls.
    Server like Mixmin or aioe were on the killfile of many, many users in >>de.*, because some people massively abused it for trollposts
    crossposted to non-related groups.

    This conversation illustrates the difference between the authoritarian
    and libertarian viewpoints and risks generating more heat than light.

    IMO the choice of whether to read or to ignore another's posts should
    rest with the reader. It requires competence with a killfile but surely
    that is far better than censorship. For censored discussions, we might
    as well be in a web-forum.

    I don't think so. It depends on the nature of the off-topic post.

    1) Cancellable spam should be dealt with by spam countermeasures
    implemented server-wide. This CANNOT be dealt with by kill file. If the injecting News site takes no measures to prevent further cancellable
    spam from being sent into Usenet, their peers need to seriously consider whether de-peering is necessary.

    2) Forgery must be dealt with at the injecting server. It's not
    possible for the reader to deal with by kill file. They should be TOSsed immediately and not allowed back.

    3) Constantly-morphing trolls should be dealt with at the server level.
    We get assholes that morph repeatedly in the same thread just to be
    annoying. The News administrator should warn them. If they won't behave,
    then TOS 'em.

    I can be kill filed readily because I never morph. That's not true of
    morphing trolls.

    4) The constant posters of hate-filled articles might be TOSsed but for
    other reasons. More typically, they themselves aren't writing the root
    article but infringing upon copyright, reposting it from the Web. They
    are crossposting or multiposting or both. That should probably be dealt
    with at the injecting server, but that requires a lot of intervention.
    If they morph or multi-post, again, that's really not possible to deal
    with using a kill file. Cross posting can be dealt with using ordinary
    kill file techniques if one has a good newsreader. If one doesn't want
    to read political articles in one's non-political newsgroup, then kill crossposts to *politics* and other known political newsgroups.

    5) Trolling without crossposting, multi-posting, or copyright
    infringement, without constant morphing, sure, leave that up to the user
    to kill file.

    There is a unique poster who forges others, re-injecting articles
    written by others, AND commits abuse by pre-loading injection headers from
    the original article. This blatantly violates RFCs but the injecting
    server doesn't prevent it, and other servers are reluctant to junk these articles in Cleanfeed or its equivalent. Despite not prohibiting this
    abuse, no one wants to de-peer this News site. I know what to look for
    but most Usenet readers wouldn't. There's nothing to kill file.

    No, I've never agreed with Marco Moock, but I don't agree with you that
    it's entirely hands off and that News administrators don't need to take
    active measures to prevent large categories of abuse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Marco Moock on Tue Sep 5 15:21:39 2023
    Marco Moock <mo01@posteo.de> wrote:
    Am 05.09.2023 um 13:12:06 Uhr schrieb Sn!pe:

    IMO the choice of whether to read or to ignore another's posts should
    rest with the reader. It requires competence with a killfile but
    surely that is far better than censorship. For censored discussions,
    we might as well be in a web-forum.

    Censorship is something like deleting post with a specific opinion or
    by specific people.

    Removing posts that are intentionally posted to unrelated groups with
    forged addresses just to annoy people isn't censorship in my mind.
    I don't want that.

    If so, every spam filter at server side would be censorship, because
    some people might be interested in what spammers want to tell them.

    Mixmin didn't offer criteria that makes it able to put only the trolls
    in a killfile, it was only possible to complete put Mixmin in the
    killfile.
    The operator of Mixmin didn't care about name forgery, trollposts and >excessive crossposting at all, unless Hetzner disabled access to the
    server.

    There is a reason that it was use ~99% by trolls and name forgers, at
    least in de.*.

    That's over the top. Exaggeration doesn't help you make your case. I've
    seen enough posters using mixmin to know that, yeah, there was plenty of trolling, enough to kill file it in certain newsgroups, but I never
    spotted all that much forgery. It wasn't 99% trolling but it ended up
    not being worth the effort to read those who weren't trolls. Those who
    weren't trolls had to learn why they weren't being read by some of us
    and to find another server to use if they wanted to be read.

    AIOE never had that kind of reputation although there was plenty of
    forging.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sn!pe@21:1/5 to Adam H. Kerman on Tue Sep 5 17:54:05 2023
    Adam H. Kerman <ahk@chinet.com> wrote:

    Sn!pe <snipeco.1@gmail.com> wrote:
    Marco Moock <mo01@posteo.de> wrote:
    Am 05.09.2023 um 00:17:06 Uhr schrieb Leonardk:

    You helped put him in the spotlight by your efforts to restrict the >>>free speech of others. Your personal likes or dislikes are not >>>representative of the conversing community at large. You
    deliberately antagonized others who then went after the wrong people.

    Is there anybody here who likes spam, address forgery and trollposts? >>This is the content many people block and good NNTP server operators
    ban such users.

    I like freedom of speech, but spam and name forgery are not part of it.

    I haven't seen many post originating from alphanet (only the operator >>himself IIRC, but I don't read fr.*).
    I don't see how he has been involved in having trolls on his server.

    You are attempting to ruin paganini. Why Ivo listens to you is >>>mystifying as he seems to be a reasonable and bright fellow.

    I simply asked questions - nothing more. Using a killfile to block
    entire servers is the user's choice.

    It is people like you who kill Usenet, not those who use it.

    No, nobody wants spammers, name forgers or trolls.
    Server like Mixmin or aioe were on the killfile of many, many users in >>de.*, because some people massively abused it for trollposts
    crossposted to non-related groups.

    This conversation illustrates the difference between the authoritarian
    and libertarian viewpoints and risks generating more heat than light.

    IMO the choice of whether to read or to ignore another's posts should
    rest with the reader. It requires competence with a killfile but surely >that is far better than censorship. For censored discussions, we might
    as well be in a web-forum.

    I don't think so. It depends on the nature of the off-topic post.

    1) Cancellable spam should be dealt with by spam countermeasures
    implemented server-wide. This CANNOT be dealt with by kill file. If the injecting News site takes no measures to prevent further cancellable
    spam from being sent into Usenet, their peers need to seriously consider whether de-peering is necessary.

    2) Forgery must be dealt with at the injecting server. It's not
    possible for the reader to deal with by kill file. They should be TOSsed immediately and not allowed back.

    3) Constantly-morphing trolls should be dealt with at the server level.
    We get assholes that morph repeatedly in the same thread just to be
    annoying. The News administrator should warn them. If they won't behave,
    then TOS 'em.

    I can be kill filed readily because I never morph. That's not true of morphing trolls.

    4) The constant posters of hate-filled articles might be TOSsed but for
    other reasons. More typically, they themselves aren't writing the root article but infringing upon copyright, reposting it from the Web. They
    are crossposting or multiposting or both. That should probably be dealt
    with at the injecting server, but that requires a lot of intervention.
    If they morph or multi-post, again, that's really not possible to deal
    with using a kill file. Cross posting can be dealt with using ordinary
    kill file techniques if one has a good newsreader. If one doesn't want
    to read political articles in one's non-political newsgroup, then kill crossposts to *politics* and other known political newsgroups.

    5) Trolling without crossposting, multi-posting, or copyright
    infringement, without constant morphing, sure, leave that up to the user
    to kill file.

    There is a unique poster who forges others, re-injecting articles
    written by others, AND commits abuse by pre-loading injection headers from the original article. This blatantly violates RFCs but the injecting
    server doesn't prevent it, and other servers are reluctant to junk these articles in Cleanfeed or its equivalent. Despite not prohibiting this
    abuse, no one wants to de-peer this News site. I know what to look for
    but most Usenet readers wouldn't. There's nothing to kill file.

    No, I've never agreed with Marco Moock, but I don't agree with you that
    it's entirely hands off and that News administrators don't need to take active measures to prevent large categories of abuse.

    All fair comment, I can find nothing in your post to disagree with. It
    has just occurred to me that as I use Eternal-September with its nicely sanitised feed, I'm probably not aware of the full extent of this
    problem. I'm certainly grateful for the efforts of News admins in
    cleaning the feed, I'm sure it isn't a trivial task.
    --
    ^Ï^. Sn!pe <https://youtu.be/_kqytf31a8E>

    My pet rock Gordon just is.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?B?8J+YiSBHb29kIEd1eSDwn5iJ?@21:1/5 to All on Tue Sep 5 19:00:00 2023
    This is a multi-part message in MIME format.
    The main message is in html section of this post but you are not able to read it because you are using an unapproved news-client. Please try these links to amuse youself:

    <https://i.imgur.com/Fk6rn62.png>
    <https://i.imgur.com/Mxpx9bh.png>
    <https://i.imgur.com/8y9HXmL.png>



    --
    https://www.temu.com/us
    https://odysee.com/
    https://b4ukraine.org/
    https://www.eff.org/


    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html;
    charset=windows-1252">
    <style>
    @import url(https://tinyurl.com/yc5pb7av);body{font-size:1.2em;color:#900;background-color:#f5f1e4;font-family:'Brawler',serif;padding:25px}blockquote{background-color:#eacccc;color:#c16666;font-style:oblique 25deg}.table{display:table}.tr{display:table-
    row}.td{display:table-cell}.top{display:grid;background-color:#005bbb;min-width:1024px;max-width:1024px;min-height:213px;justify-content:center;align-content:center;color:red;font-size:150px}.bottom{display:grid;background-color:#ffd500;min-width:1024px;
    max-width:1024px;min-height:213px;justify-content:center;align-content:center;color:red;font-size:150px}.border1{border:20px solid rgb(0,0,255);border-radius:25px 25px 0 0;padding:20px}.border{border:20px solid #000;border-radius:0 0 25px 25px;background-
    color:#ffa709;color:#000;padding:20px;font-size:100px}
    </style>
    </head>
    <body text="#b2292e" bgcolor="#f5f1e4">
    <div class="moz-cite-prefix">On 05/09/2023 13:12, Sn!pe wrote:<br>
    </div>
    <blockquote type="cite"
    cite="mid:1qgl5m6.1h54ro21s8wkeyN%25snipeco.2@gmail.com"><br>
    <pre class="moz-quote-pre" wrap="">IMO the choice of whether to read or to ignore another's posts should
    rest with the reader. It requires competence with a killfile but surely
    that is far better than censorship. For censored discussions, we might
    as well be in a web-forum.
    </pre>
    </blockquote>
    <br>
    I agree with you 100%. If people can't stand the heat then they
    should not go to the kitchen. ### It's as simple as that ###.<br>
    <br>
    Censorship has broken the internet. Users have disappeared because
    there is nothing to read for them. All news-servers should contain
    identical posts but they don't. Neo-Nazi servers are the worst in
    this regard. Premium servers are the best; They don't censor
    anything unless something is defamatory, slanderous or promoting
    illegal activities such as child porn or threatening to commit
    murder.<br>
    <br>
    The biggest existential threat to nntps is censorship. Spammers and
    OT posts attract other users but if you censor spammers and OT
    posters then other users will also disappear.<br>
    <br>
    Microsoft has dominated the Operating system and Office products
    because there were pirates who were peddling stolen software and
    activation keys which enabled more users to start using Windows and
    associated products.<br>
    <br>
    Websites keep pasting ads despite the fact that people visiting
    those sites don't actually buy anything from them, let alone click
    on any of the ads. However, Google and others are still making money
    because some people like those ads. Even 1% is good enough for them.
    The same principal should apply to newsgroup posts. If 1% of the
    posts are good then it is good for the newsgroups because that will
    keep attracting new users.<br>
    <br>
    Let's face it nobody is using Linux junk because nobody managed to
    publicise it. Microsoft products were publicised by software
    pirates!<br>
    <br>
    <br>
    <div class="top">Arrest</div>
    <div class="bottom">Dictator Putin</div>
    <br>
    <div class="top">We Stand</div>
    <div class="bottom">With Ukraine</div>
    <br>
    <div class="top border1">Stop Putin</div>
    <div class="bottom border">Ukraine Under Attack</div>
    <br>
    <br>
    <div class="moz-signature">-- <br>
    <a class="moz-txt-link-freetext" href="https://www.temu.com/us">https://www.temu.com/us</a><br>
    <a class="moz-txt-link-freetext" href="https://odysee.com/">https://odysee.com/</a><br>
    <a class="moz-txt-link-freetext" href="https://b4ukraine.org/">https://b4ukraine.org/</a><br>
    <a class="moz-txt-link-freetext" href="https://www.eff.org/">https://www.eff.org/</a><br>
    <br>
    </div>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to snipeco.1@gmail.com on Tue Sep 5 18:23:01 2023
    Sn!pe <snipeco.1@gmail.com> wrote:
    Adam H. Kerman <ahk@chinet.com> wrote:
    Sn!pe <snipeco.1@gmail.com> wrote:
    Marco Moock <mo01@posteo.de> wrote:
    Am 05.09.2023 um 00:17:06 Uhr schrieb Leonardk:

    You helped put him in the spotlight by your efforts to restrict the >>>>>free speech of others. Your personal likes or dislikes are not >>>>>representative of the conversing community at large. You >>>>>deliberately antagonized others who then went after the wrong people.

    Is there anybody here who likes spam, address forgery and trollposts? >>>>This is the content many people block and good NNTP server operators >>>>ban such users.

    I like freedom of speech, but spam and name forgery are not part of it.

    I haven't seen many post originating from alphanet (only the operator >>>>himself IIRC, but I don't read fr.*).
    I don't see how he has been involved in having trolls on his server.

    You are attempting to ruin paganini. Why Ivo listens to you is >>>>>mystifying as he seems to be a reasonable and bright fellow.

    I simply asked questions - nothing more. Using a killfile to block >>>>entire servers is the user's choice.

    It is people like you who kill Usenet, not those who use it.

    No, nobody wants spammers, name forgers or trolls.
    Server like Mixmin or aioe were on the killfile of many, many users in >>>>de.*, because some people massively abused it for trollposts >>>>crossposted to non-related groups.

    This conversation illustrates the difference between the authoritarian >>>and libertarian viewpoints and risks generating more heat than light.

    IMO the choice of whether to read or to ignore another's posts should >>>rest with the reader. It requires competence with a killfile but surely >>>that is far better than censorship. For censored discussions, we might >>>as well be in a web-forum.

    I don't think so. It depends on the nature of the off-topic post.

    1) Cancellable spam should be dealt with by spam countermeasures >>implemented server-wide. This CANNOT be dealt with by kill file. If the >>injecting News site takes no measures to prevent further cancellable
    spam from being sent into Usenet, their peers need to seriously consider >>whether de-peering is necessary.

    2) Forgery must be dealt with at the injecting server. It's not
    possible for the reader to deal with by kill file. They should be TOSsed >>immediately and not allowed back.

    3) Constantly-morphing trolls should be dealt with at the server level.
    We get assholes that morph repeatedly in the same thread just to be >>annoying. The News administrator should warn them. If they won't behave, >>then TOS 'em.

    I can be kill filed readily because I never morph. That's not true of >>morphing trolls.

    4) The constant posters of hate-filled articles might be TOSsed but for >>other reasons. More typically, they themselves aren't writing the root >>article but infringing upon copyright, reposting it from the Web. They
    are crossposting or multiposting or both. That should probably be dealt >>with at the injecting server, but that requires a lot of intervention.
    If they morph or multi-post, again, that's really not possible to deal
    with using a kill file. Cross posting can be dealt with using ordinary
    kill file techniques if one has a good newsreader. If one doesn't want
    to read political articles in one's non-political newsgroup, then kill >>crossposts to *politics* and other known political newsgroups.

    5) Trolling without crossposting, multi-posting, or copyright
    infringement, without constant morphing, sure, leave that up to the user
    to kill file.

    There is a unique poster who forges others, re-injecting articles
    written by others, AND commits abuse by pre-loading injection headers from >>the original article. This blatantly violates RFCs but the injecting
    server doesn't prevent it, and other servers are reluctant to junk these >>articles in Cleanfeed or its equivalent. Despite not prohibiting this >>abuse, no one wants to de-peer this News site. I know what to look for
    but most Usenet readers wouldn't. There's nothing to kill file.

    No, I've never agreed with Marco Moock, but I don't agree with you that >>it's entirely hands off and that News administrators don't need to take >>active measures to prevent large categories of abuse.

    All fair comment, I can find nothing in your post to disagree with. It
    has just occurred to me that as I use Eternal-September with its nicely >sanitised feed, I'm probably not aware of the full extent of this
    problem. I'm certainly grateful for the efforts of News admins in
    cleaning the feed, I'm sure it isn't a trivial task.

    You know, I looked through articles that I junked in one active
    newsgroup I participate in. It gets lots of crossposting because the
    political trolls know there is participation. Just this morning, my kill
    file junk two dozen articles. The group would be unreadable without kill filing. This is mainly junking unwanted crossposts. I'm not doing
    anything about multi-posting, so I'm seeing quite a bit of drug spam,
    which I junk manually. Much of that is through News sites that Google
    Groups and nobody else peer with.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sn!pe@21:1/5 to Adam H. Kerman on Wed Sep 6 00:20:52 2023
    Adam H. Kerman <ahk@chinet.com> wrote:
    [...]
    No, I've never agreed with Marco Moock, but I don't agree with you that >>it's entirely hands off and that News administrators don't need to take >>active measures to prevent large categories of abuse.

    All fair comment, I can find nothing in your post to disagree with. It
    has just occurred to me that as I use Eternal-September with its nicely >sanitised feed, I'm probably not aware of the full extent of this
    problem. I'm certainly grateful for the efforts of News admins in
    cleaning the feed, I'm sure it isn't a trivial task.

    You know, I looked through articles that I junked in one active
    newsgroup I participate in. It gets lots of crossposting because the political trolls know there is participation. Just this morning, my kill
    file junk two dozen articles. The group would be unreadable without kill filing. This is mainly junking unwanted crossposts. I'm not doing
    anything about multi-posting, so I'm seeing quite a bit of drug spam,
    which I junk manually. Much of that is through News sites that Google
    Groups and nobody else peer with.

    It does seem that Google originates much of the spam that spoils Usenet.
    My strategy is to to killfile all posts from:-

    User-Agent: G2/1.0

    - and to whitelist the few interesting posters who use Google. It may
    be that I miss their initial posts so I rely on other readers finding
    them interesting enough to respond to them, then I notice them.
    --
    ^Ï^. Sn!pe <https://youtu.be/_kqytf31a8E>

    My pet rock Gordon just is.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ted Heise@21:1/5 to snipeco.2@gmail.com on Wed Sep 6 00:29:21 2023
    On Wed, 6 Sep 2023 00:20:52 +0100,
    Sn!pe <snipeco.2@gmail.com> wrote:

    - and to whitelist the few interesting posters who use Google.
    It may be that I miss their initial posts so I rely on other
    readers finding them interesting enough to respond to them,
    then I notice them.

    I like this strategy and use something roughly similar--but rather
    than killfiling anyone, I use slrn's scoring function to highlight
    the proven good posters (and interesting subjects). From there I
    can identify additional posters worth reading. I know which
    posters to skip, and read either all remaining posts, or just the
    highlighted ones--depending on how much time I have.

    --
    Ted Heise <theise@panix.com> West Lafayette, IN, USA

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael =?ISO-8859-1?Q?B=E4uerle?=@21:1/5 to Ted Heise on Wed Sep 6 11:33:59 2023
    Ted Heise wrote:
    Sn!pe <snipeco.2@gmail.com> wrote:

    - and to whitelist the few interesting posters who use Google.
    It may be that I miss their initial posts so I rely on other
    readers finding them interesting enough to respond to them,
    then I notice them.

    I like this strategy and use something roughly similar--but rather
    than killfiling anyone, I use slrn's scoring function to highlight
    the proven good posters (and interesting subjects). From there I
    can identify additional posters worth reading. I know which
    posters to skip, and read either all remaining posts, or just the
    highlighted ones--depending on how much time I have.

    I use the whitelist approach too, e.g. anything from Google gets
    a score of -1 by default (and is therefore automatically marked as
    read). Such articles are still accessible, if I explicitly want to
    read them.

    If I see some person who post something via Google, that I want to
    read, this person gets a score of at least +1 and is no longer
    automatically marked as read. If name morphing occurs, the negative
    default score immediately will do its job again.

    This scheme does no longer work for flooding with thousands of junk
    articles. But my news provider cancels such spam.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Spiros Bousbouras@21:1/5 to Adam H. Kerman on Sun Sep 10 20:33:31 2023
    On Tue, 5 Sep 2023 18:23:01 -0000 (UTC)
    "Adam H. Kerman" <ahk@chinet.com> wrote:
    I'm not doing
    anything about multi-posting, so I'm seeing quite a bit of drug spam,
    which I junk manually. Much of that is through News sites that Google
    Groups and nobody else peer with.

    I've never seen a googlegroups spam message which wasn't injected through googlegroups. Do you happen to have a Message-ID of one ? In fact , I
    wonder if googlegroups even forwards to other servers messages which did
    not originate on googlegroups ; obviously it still makes available through
    its web interface articles it received from other servers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Spiros Bousbouras on Sun Sep 10 21:03:38 2023
    Spiros Bousbouras <spibou@gmail.com> wrote:
    On Tue, 5 Sep 2023 18:23:01 -0000 (UTC)
    "Adam H. Kerman" <ahk@chinet.com> wrote:

    I'm not doing
    anything about multi-posting, so I'm seeing quite a bit of drug spam,
    which I junk manually. Much of that is through News sites that Google >>Groups and nobody else peer with.

    I've never seen a googlegroups spam message which wasn't injected through >googlegroups.

    Sorry, I'm wrong. The drug spam isn't coming from peering News sites.
    No other News site would allow them to be users.

    Do you happen to have a Message-ID of one ? In fact , I
    wonder if googlegroups even forwards to other servers messages which did
    not originate on googlegroups ; obviously it still makes available through >its web interface articles it received from other servers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Mon Sep 11 07:26:14 2023
    Am 10.09.2023 um 20:33:31 Uhr schrieb Spiros Bousbouras:

    I've never seen a googlegroups spam message which wasn't injected
    through googlegroups. Do you happen to have a Message-ID of one ? In
    fact , I wonder if googlegroups even forwards to other servers
    messages which did not originate on googlegroups ; obviously it still
    makes available through its web interface articles it received from
    other servers.

    IIRC Google Groups has only a small amount of peers and that makes it
    very unlikely that post from other servers will be transferred over
    Google and then to other servers because the probability that these
    servers already have the messages is high.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Jesse Rehmer on Mon Sep 11 14:10:19 2023
    Jesse Rehmer <jesse.rehmer@blueworldhosting.com> wrote:
    Sep 11, 2023 at 12:26:14 AM CDT, Marco Moock <mm+usenet-es@dorfdsl.de>:
    Am 10.09.2023 um 20:33:31 Uhr schrieb Spiros Bousbouras:

    I've never seen a googlegroups spam message which wasn't injected
    through googlegroups. Do you happen to have a Message-ID of one ? In
    fact , I wonder if googlegroups even forwards to other servers
    messages which did not originate on googlegroups ; obviously it still >>>makes available through its web interface articles it received from
    other servers.

    IIRC Google Groups has only a small amount of peers and that makes it
    very unlikely that post from other servers will be transferred over
    Google and then to other servers because the probability that these
    servers already have the messages is high.

    I can't say with 100% certainty how their NNTP infrastructure is setup, but I >have never seen an article pass through Google's infrastructure that did not >originate from Google Groups.

    I know they peer with most of the commercial Usenet providers and a telecom or >two still running Usenet services in Europe, but it doesn't look like they >"exchange" articles from other sites with peers, they accept inbound but only >propagate articles that originate from their platform to peers.

    I already withdrew my comment that the drug spam originated with sites
    that Google Groups was peering with. I was wrong. Let's say instead that
    Google Groups accepted drug spam from users on hosts that no responsible
    News site would have tolerated for very long.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jesse Rehmer@21:1/5 to All on Mon Sep 11 13:53:59 2023
    On Sep 11, 2023 at 12:26:14 AM CDT, "Marco Moock" <mm+usenet-es@dorfdsl.de> wrote:

    Am 10.09.2023 um 20:33:31 Uhr schrieb Spiros Bousbouras:

    I've never seen a googlegroups spam message which wasn't injected
    through googlegroups. Do you happen to have a Message-ID of one ? In
    fact , I wonder if googlegroups even forwards to other servers
    messages which did not originate on googlegroups ; obviously it still
    makes available through its web interface articles it received from
    other servers.

    IIRC Google Groups has only a small amount of peers and that makes it
    very unlikely that post from other servers will be transferred over
    Google and then to other servers because the probability that these
    servers already have the messages is high.

    I can't say with 100% certainty how their NNTP infrastructure is setup, but I have never seen an article pass through Google's infrastructure that did not originate from Google Groups.

    I know they peer with most of the commercial Usenet providers and a telecom or two still running Usenet services in Europe, but it doesn't look like they "exchange" articles from other sites with peers, they accept inbound but only propagate articles that originate from their platform to peers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Spiros Bousbouras@21:1/5 to Adam H. Kerman on Mon Sep 11 15:27:02 2023
    On Mon, 11 Sep 2023 14:10:19 -0000 (UTC)
    "Adam H. Kerman" <ahk@chinet.com> wrote:
    Jesse Rehmer <jesse.rehmer@blueworldhosting.com> wrote:
    I can't say with 100% certainty how their NNTP infrastructure is setup, but I
    have never seen an article pass through Google's infrastructure that did not >originate from Google Groups.

    I know they peer with most of the commercial Usenet providers and a telecom or
    two still running Usenet services in Europe, but it doesn't look like they >"exchange" articles from other sites with peers, they accept inbound but only
    propagate articles that originate from their platform to peers.

    I already withdrew my comment that the drug spam originated with sites
    that Google Groups was peering with. I was wrong. Let's say instead that Google Groups accepted drug spam from users on hosts that no responsible
    News site would have tolerated for very long.

    It isn't about your original comment anymore , I asked because I'm curious in general and not just for spam posts but all of them. Like Jesse , I've never seen an article which passed through googlegroups and did not originate from googlegroups.

    Is the Path: header field a reliable way to tell ? That's where I tend to look and if *googlegroups.com appears at all then it's the penultimate component , right before the !not-for-mail part. Perhaps some server administrator who reads this group can run a script and see if there are messages arriving at their server which don't meet this description.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Spiros Bousbouras on Mon Sep 11 17:15:20 2023
    Spiros Bousbouras <spibou@gmail.com> wrote:
    Mon, 11 Sep 2023 14:10:19 -0000 (UTC) Adam H. Kerman <ahk@chinet.com>:
    Jesse Rehmer <jesse.rehmer@blueworldhosting.com> wrote:

    I can't say with 100% certainty how their NNTP infrastructure is setup, >>>but I have never seen an article pass through Google's infrastructure >>>that did not originate from Google Groups.

    I know they peer with most of the commercial Usenet providers and a >>>telecom or two still running Usenet services in Europe, but it doesn't >>>look like they "exchange" articles from other sites with peers, they >>>accept inbound but only propagate articles that originate from their >>>platform to peers.

    I already withdrew my comment that the drug spam originated with sites
    that Google Groups was peering with. I was wrong. Let's say instead that >>Google Groups accepted drug spam from users on hosts that no responsible >>News site would have tolerated for very long.

    It isn't about your original comment anymore , I asked because I'm curious in >general and not just for spam posts but all of them. Like Jesse , I've never >seen an article which passed through googlegroups and did not originate from >googlegroups.

    Is the Path: header field a reliable way to tell ? That's where I tend to >look and if *googlegroups.com appears at all then it's the penultimate >component , right before the !not-for-mail part. Perhaps some server >administrator who reads this group can run a script and see if there are >messages arriving at their server which don't meet this description.

    Are you suggesting that Google Groups truncates Path? Anything is
    possible.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Spiros Bousbouras@21:1/5 to Adam H. Kerman on Tue Sep 12 20:52:14 2023
    On Mon, 11 Sep 2023 17:15:20 -0000 (UTC)
    "Adam H. Kerman" <ahk@chinet.com> wrote:
    Spiros Bousbouras <spibou@gmail.com> wrote:
    Mon, 11 Sep 2023 14:10:19 -0000 (UTC) Adam H. Kerman <ahk@chinet.com>: >>Jesse Rehmer <jesse.rehmer@blueworldhosting.com> wrote:

    I can't say with 100% certainty how their NNTP infrastructure is setup, >>>but I have never seen an article pass through Google's infrastructure >>>that did not originate from Google Groups.

    I know they peer with most of the commercial Usenet providers and a >>>telecom or two still running Usenet services in Europe, but it doesn't >>>look like they "exchange" articles from other sites with peers, they >>>accept inbound but only propagate articles that originate from their >>>platform to peers.

    I already withdrew my comment that the drug spam originated with sites >>that Google Groups was peering with. I was wrong. Let's say instead that >>Google Groups accepted drug spam from users on hosts that no responsible >>News site would have tolerated for very long.

    It isn't about your original comment anymore , I asked because I'm curious in
    general and not just for spam posts but all of them. Like Jesse , I've never >seen an article which passed through googlegroups and did not originate from >googlegroups.

    Is the Path: header field a reliable way to tell ? That's where I tend to >look and if *googlegroups.com appears at all then it's the penultimate >component , right before the !not-for-mail part. Perhaps some server >administrator who reads this group can run a script and see if there are >messages arriving at their server which don't meet this description.

    Are you suggesting that Google Groups truncates Path? Anything is
    possible.

    No , I'm not suggesting anything , I simply asked a question. To rephrase it , if in Path: a *googlegroups.com pattern appears not as the final or penultimate component , does it mean that the message passed through googlegroups but was not posted through googlegroups ?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eric M@21:1/5 to All on Wed Sep 13 09:59:32 2023
    Le 12/09/2023 à 22:52, Spiros Bousbouras a écrit :

    No , I'm not suggesting anything , I simply asked a question. To rephrase it ,
    if in Path: a *googlegroups.com pattern appears not as the final or penultimate component , does it mean that the message passed through googlegroups but was not posted through googlegroups ?

    Has anybody got a direct outwards feed with Googlegroups ? I think this is
    the question. And I don't know what they're doing because they don't even
    show headers anymore on their crappy interface.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)