VE3XEC wrote to All <=-
I'm posting this message as an AX.25 client on my BBS, just to see
how Synchronet's line editor works here.
Not so great - I may need to come up with something different.
I have managed to forward some mailing lists into JNOS using Synchronet's listserve. I would like to move the packet floods (bulletins, general messages, etc.) to/from Syncronet, but have given up for the time being as
to how to accomplish this.
echicken wrote to W6RAY <=-
I've written a script that serves as a gateway between AX.25 clients
(via a KISS TNC) and Synchronet's terminal server (via RLogin.) With
this script running on your BBS, an unproto AX.25 client can connect
to your station, and then interact with your BBS as would any telnet,
ssh, rlogin, dial-up user. I am mostly done writing a custom command shell that takes into account some of the requirements of AX.25
clients.
I'll post an update here once all of the pieces of the puzzle are in
place and this becomes a usable system. I'll also update the documentation on the Synchronet wiki, which is now outdated in some
areas.
If I understand the JNOS manual, it can act as an AX.25 client, or at least you can attach to it. I will have to look into if further to make sure I understand correctly...
The only thing that worries me is often times there is profanity on DOVE-,
Fido-, and othernets, a no-no on the air, even digital modes.
The only thing that worries me is often times there is profanity on DOVE-, Fido-, and othernets, a no-no on the air, even digital modes.
Now I've built a TNC-Pi for this kit and am hoping to get it on the air soon enough. It seems that using this in conjuction with JNOS and telnet access is a good way to go. Not sure how I'm going to approach this, but so far this bbs has been a great source of information.
Yes, that is a concern, and one that I've already thought of (and had handle in my previous version of this software.) I'll be adding a text filter to t ax25tunnel.js script right at the point where it sends text over the air to client, and it will mask out any words that match against a sysop-maintained list of bad words.
The greatest issue that I'm having with this is trying to define a realistic set of *actual* banned words. Every list of "bad" words that I encounter ha some very silly entries on it.
Forgive my butting in and lack of foreknowledge about the subject, but are all AX.25 communications assumed or required to be cleartext?
Again, I haven't researched this yet, so forgive my intrusion if I'm missing bits here. Assuming that the FCC is the entity that would be regulating these transmissions, would not permutations of the 'Seven Dirty Words' being censored be sufficient?
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 103 |
Nodes: | 16 (0 / 16) |
Uptime: | 02:17:58 |
Calls: | 5,865 |
Calls today: | 5 |
Files: | 8,496 |
D/L today: |
585 files (548M bytes) |
Messages: | 343,608 |
Posted today: | 1 |