Re: News on AIOE's outage

On 3/9/23 12:50, OldbieOne wrote:
> <[email protected]> wrote in message
> news:[email protected]...
>> On Wed, 8 Mar 2023 16:24:51 -0500
>> "OldbieOne" <[email protected]> wrote:
>>> <[email protected]> wrote in message
>>> news:[email protected]...
>>>> On Fri, 3 Mar 2023 14:19:46 -0500
>>>> Tony <[email protected]> wrote:
>>>>> Sn!pe wrote:
>>>>>> Don Spam's Reckless Son <[email protected]>
> wrote:
>>> <snip>
>>>>>
>>>>> AIOE is supposed to take top priority due to all the school children
> who
>>>>> now can't learn anything on usenet. Eternal September the guy who runs
>>>>
>>>> How many kids ever used usenet even in the 90s, never mind now?
>>>
>>> I was about 8 when I first accessed USENET....
>>>
>>> Something tells me that the average age on USENET now has to be 55+
> except
>>> for maybe one or two younger ped0s who should be arrested and hung by
> their
>>> b@lls until dead.
>>
>> I'm < 55. First used usenet when I was at uni in the 90s.
> 
> If you were 18 in the 90's you're not too far behind ;)
> 
> My first experience with USENET was a limited feed via the BBS my father was
> a user of
> in the late 80's, but I was pretty much using USENET regularly by way of my
> ISP's provided
> NNTP service and through college access from the early 90's until it's
> "death" in the post-9/11
> culling.
> 
> I don't think it'll ever be the same as it was, but I'm glad that it's still
> here in some form or other.

What if you made it better than it ever was?

What is stopping you anons from getting together and making the code to 
improve it?

There are many things that could be improved to make NNTP a frictionless 
experience for users and admins. Friction is death bane for software.

Improve or re-invent the protocol. Remove the unnecessary functions of 
the protocol to streamline it. Simplify the left-over functions for 
asynchronous exchange instead of requiring a keep-alive session. Use 
signed tokens to order the commands in each session so that the session 
can be continued where it left off even several minutes in between 
connections and commands.

Improve the client. Fork a GUI client and make it better.

Improve the server and client so that configuration of accounts is 
always automatic and not prone to user error or arcane options causing 
failures.

Improve the server. Make it a point-click install experience. Make it so 
mere mortals can be up and running in no time.

Imagine a NNTP server with a GUI configuration and a setup wizard to get 
all the options right.

Imagine a NNTP server that automatically generates TLS keys and ensures 
all connections are encryption.

Imagine a NNTP server that automatically registers letsencrypt keys.

Imagine a built-in web front end with automated user registration and 
verification.

Imagine easy checkboxes to make some groups open and make some groups 
require registration.

Imagine extra features like hidden newsgroups, secret newsgroups, and 
author message cancellation.

Imagine extra encryption options built-in.

Imagine easy configuration for partial or small feed syncing to preserve 
bandwidth.

Imagine optional mix routing built-in to the client and the servers.

Imagine high-level spam handling in the GUI interface.

Imagine keyword and sender filtering at the server level.

It looks like RetroGuy at RocksolidBBS.com is already on this track. You 
could fork his code and hack away and push back improvements.

Imagine.

Write the code.

Run more servers.

Profit!

-- 

Imagine More Meat!