Re: Note - ISP Screwed Up - Can WRITE But Not SEE

Subject	Re: Note - ISP Screwed Up - Can WRITE But Not SEE
Newsgroups	comp.os.linux.misc
References	(1 earlier) <20250122210010.2353d60f@ryz.dorfdsl.de> <c96dnWLIkv08Fwz6nZ2dnZfqnPWdnZ2d@earthlink.com> <74ac8126-3732-0c2d-ef7e-87766df419ac@example.net> <vmtrde$1ll9u$23@dont-email.me> <aae6a8dd-fe2b-68ec-8627-c45b5da6959e@example.net>
From	"186282@ud0s4.net" <186283@ud0s4.net>
Organization	wokiesux
Date	2025-01-24 01:29 -0500
Message-ID	<8Yicnf7eGZv5rg76nZ2dnZfqn_WdnZ2d@earthlink.com> (permalink)

Show all headers | View raw

On 1/23/25 4:05 PM, D wrote:
> 
> 
> On Thu, 23 Jan 2025, The Natural Philosopher wrote:
> 
>> On 23/01/2025 15:44, D wrote:
>>>
>>>
>>> On Wed, 22 Jan 2025, 186282@ud0s4.net wrote:
>>>
>>>> On 1/22/25 3:00 PM, Marco Moock wrote:
>>>>> On 22.01.2025 00:19 Uhr 186282@ud0s4.net wrote:
>>>>>
>>>>>> Well, I can see - by posting with my normal ISP and
>>>>>> then reading from NeoDome (but can't POST from Neo).
>>>>>
>>>>> Maybe they restrict posting to avoid abuse.
>>>>> Ask the admin of it.
>>>>
>>>>  Yep, they don't allow posting anymore - too
>>>>  many spammers. None of the other freebies
>>>>  seem to work at all any more or want you
>>>>  to "register". Some ISPs block port 119.
>>>>  This is not good.
>>>>
>>>>  My provider finally did fix it. Alas they
>>>>  may only have one old guy who knows how
>>>>  the NNTP server works. Don't think they
>>>>  even offer it to newbies anymore.
>>>>
>>>>  By modern standards, usenet is kinda small
>>>>  data-wise - and mostly just text. Would not
>>>>  take a super-box. Maybe some people are
>>>>  worried about liability - lots of weird
>>>>  stuff here ? Perhaps someone in a kinda
>>>>  off-the-map country can start a new free
>>>>  service. (hmmm ... Belize maybe?)
>>>
>>> I think it should be entirely feasible, and fairly cheap, to start 
>>> your own usenet provider on a few hetzner VM:s. The only thing you'd 
>>> need is a few peers, inn (or equivalent) and off you go.
>>>
>>> I've toyed with the idea myself from time to time, but so far haven't 
>>> had the time to do something about it since other projects have 
>>> priority.
>>
>> Yep.
>> I have set up a few INN servers. The problem back in the day was the 
>> binary newsgroups - people uploading pirate images of massive size..
> 
> Isn't it very easy to just not offer the binary crap? There are way 
> better methods today to get your hands on binaries than trawling through 
> newsgroups downloading and integrating small compressed files.
> 
>> It does take a bit of looking after. If you let everyone access it 
>> before you know it there is a huge amount of illegal shit being 
>> transferred on legitimate newsgroups, ratware is smashing against 
>> every door it can find and people are trying to DOS it just because 
>> someone called them out for being a doofus.
> 
> It is very interesting! How long before someone would try and destroy 
> your publicly available free news server? ;)
> 
> On the other hand, one could always hope that the nr of people who even 
> know what it is is so small that it could live happily unmoderated!
> 
> On the other hand, if spam increases too much or the complaints keep 
> piling up, maybe the peers will drop you?
> 
>> But technically its not hard to do for a small community of users
> 
> A hobby project for you? =)


   There must be something in-between usenet and 'X' - http
   rather than p119. Simple interface but hooks for better
   alternative reader apps.

   Remember BBS's ? The trick was that there was usually only
   ONE server holding all the messages. Depending, this is not
   necessarily terrible. The spreads-it-around nature of usenet
   is interesting, good redundancy, but the number of feed servers
   seems to be decreasing, fewer and fewer sources for the articles.

   As for binaries ... you just set a reasonable limit for msg size,
   and forbid .part's. A detector for ascii-encoded bin will work too.

   As such, a modern BBS - prob with one or two fail-over servers -
   would be the middle path. Structure everything like usenet,
   just NOT usenet. Could even pipe in actual usenet articles,
   for as long as they last.

   Again though the "liability" issue for un-PC content. It's
   sort of a prob in the USA but a much bigger prob in the EU
   and beyond. As said, such a system needs to be located in
   a who-knows/cares-country where it's hard to get at legally.

Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Note - ISP Screwed Up - Can WRITE But Not SEE "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-22 00:19 -0500
  Re: Note - ISP Screwed Up - Can WRITE But Not SEE Marco Moock <mm+usenet-es@dorfdsl.de> - 2025-01-22 21:00 +0100
    Re: Note - ISP Screwed Up - Can WRITE But Not SEE "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-22 19:16 -0500
      Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-23 16:44 +0100
        Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 16:40 +0000
          Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-23 22:05 +0100
            Re: Note - ISP Screwed Up - Can WRITE But Not SEE "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-24 01:29 -0500
              Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-24 10:33 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE Rich <rich@example.invalid> - 2025-01-24 20:17 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-24 23:23 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE Rich <rich@example.invalid> - 2025-01-25 04:24 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 02:18 -0500
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-25 11:32 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 12:03 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-25 18:38 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 18:05 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-25 23:36 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 00:34 -0500
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-25 10:57 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 11:44 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE Rich <rich@example.invalid> - 2025-01-25 17:39 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 18:06 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-25 23:31 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE rbowman <bowman@montana.com> - 2025-01-25 23:42 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-26 11:35 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 21:16 -0500
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-26 12:58 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE Rich <rich@example.invalid> - 2025-01-26 05:18 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-26 03:22 -0500
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-26 09:50 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-26 15:31 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-26 18:32 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE Rich <rich@example.invalid> - 2025-01-26 20:13 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-27 10:02 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE Rich <rich@example.invalid> - 2025-01-27 21:42 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-28 10:21 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-28 09:59 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-28 16:23 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-28 15:36 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-28 21:38 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-27 09:51 +0100
              Re: Note - ISP Screwed Up - Can WRITE But Not SEE Richard Kettlewell <invalid@invalid.invalid> - 2025-01-24 09:54 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-24 11:48 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 00:49 -0500
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-25 11:01 +0100
            Re: Note - ISP Screwed Up - Can WRITE But Not SEE The Natural Philosopher <tnp@invalid.invalid> - 2025-01-24 11:29 +0000
              Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-24 19:20 +0100
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-25 00:12 +0000
                Re: Note - ISP Screwed Up - Can WRITE But Not SEE D <nospam@example.net> - 2025-01-25 10:42 +0100
            Re: Note - ISP Screwed Up - Can WRITE But Not SEE Rich <rich@example.invalid> - 2025-01-24 20:11 +0000

csiph-web