Board:   [WWIVnet] WWIV Development
Subject: Re: autosend prototype testing
From:    Xenos #1 @60
To:      Rushfan #1 @513
Date:    Fri Jan 27, 2023 15:24

On Saturday, January 28, 2023 at 00:18, Rushfan wrote:

R>RE: Re: autosend prototype testing
R>BY: Xenos #1 @60
R>
R>
R>X> p.s. the autosend prototype works as an epreproc.net program.
R>
R>So cool to see this.  One thing I was thinking about before as a different a
R>newer approach would be to have some email aliases defined and then the
R>handler for them (like a eprogs.net but likely defined in json file vs. flat
R>file and also key'ed by email address and not minor_type).
R>
R>Conceptually it could be
R>
R>"areafix": "@internal"
R>"autosend": "xenos-autosend"
R>
R>Where we use @internal for internally handled versions of things.
R>
R>heck, could reuse the @script too and extend wwivbasic to have access to the
R>messageapi to do something simple.
R>

i'm prototyping it in epreprogs because the hook is there to take advantage of,
python3 code gets written which could be reused elsewhere, and at this point
it's basically proof-of-concept.

ideally, it should be in network2, and built-in.

my early implementation of ibbslastcaller modded network2 to intercept posts
with a specific title and copy them to another file, which was what my original
ibbs-extract code processed. but this was superfluous because ibbslastcaller
posts were already being sent to a specific file, which was the message base of
the ibbs data sub.

i like the idea of email aliases as triggers for externals. it's certainly more
flexible. aliases, procmail and .forward files are great examples of extending
email capabilities on *nix.

i'd like to see the messageapi accessible in wwivbasic!
ditto, python. maybe we can have a c/c++ python extension.

  A  .-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-.
 /*\ | /\liens' /\lcove! WWIV on Linux, Taguig, Metro Manila, Philippines  |
/ v \`-=-=-=-=-=-=-=-=-=-=-=-[ WWIV Development ]-=-=--=-=-=-=-=-=-=-=-=-=-'
.