I am still checking to see what he might have posted from CCO yesterday. I am a little miffed he was even able to log on and create an account as the name he used -- Pengo -- is in the twitlist.cfg file.
Hopefully, that at least kept his posts from going out but I shall soon see.
New users can read, but not post, on my BBS, unless it's local.
Hopefully that doesn't put off too many users, but does put off the spammers / scammers / awful people doing awful things.
Though I did tend to think that this corner of the online world was
mostly away from that, because it's unusual technology with almost no return on time invested.
Always annoying when that doesn't turn out to be the case.
Hello Adept,
On Tue, Apr 23 2024 21:03:48 +0000, you wrote:
New users can read, but not post, on my BBS, unless it's local.
Seems to me like a good plan. I would imagine if a user wants to post, they would probably write you and either ask for access to do so, or ask why they currently can't. ;)
This turd seems to be calling a bunch of BBSs to see which ones he can
get away with what he's doing.. and with that said, it doesn't really
seem like someone brand new to BBSing, if he can make his way through multiple BBSs to spam the same post over and over.
the name he used -- Pengo -- is in the twitlist.cfg file. >
Well, huh, that name sounds familiar as a relatively-recent addition
on my board, too.
But I think I have it set so that new users can't immediately post,
and since his new-user message was underwhelming or non-existent, I
didn't bother to upgrade the account, either.
That is how I have it set on my Synchronet system. Here, he did post a new-user message and ironically (or not!) it included his paranoid rant!
<grin>
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 69 |
Nodes: | 4 (0 / 4) |
Uptime: | 00:12:09 |
Calls: | 1,333 |
Calls today: | 2 |
Files: | 8,466 |
Messages: | 305,351 |