I have some suggestions about hosting from a residential ISP. I'll post those when I get a chance. Right now I don't have the time.
There are some services available that can mitigate the issues you experienced, Smash.
as the 90s turned into the 2000s, content on boards of any type became feast or famine.
The only way that we will be able to sustain the takeback and regrowth is to advertise what we are doing.
"Cordcutters" earned a name, the cable tv industry will never be the same. Decentralized social media needs a common identifier, but not a common owner. Kinda like the GNU public license.
A mikrotik router mitigated all of it. I could even run tarpits for ssh scanners. Honestly, I didnt want the pipe my wife and kids used being the same exposed target. Moving to a cloud host was cheap insurance...AND i dont need a server, UPS... redundancy, pay for static ips, basically no fuss no muss.
2021-04-22 23:25 from smashbot64
I remember why I remember you... ddial. West Philly to Conshohocken.
Savage Frontier. Now I am positive we both know sybill.lync very
well. Hello old friend. It is hillarious how small earth is.
Oh wow! Yes, you got it! I'll pass on the message. Wow, small world indeed!
I ran a BBS on my own computer during the 90s, and originally I thought about doing that again, but opted for a VPS.
my bad... sybill.linq
Sybil/lynq, something like that. My ex girlfriend. We still talk. I just figured I'd clue everyone else in. We refer to a Ddial in Philly, this weird chat system ran on Apple II computers. They had a very strange vibe, but paved the way for what we take for granted today.
https://disboardia.net
ssh: bbs@disboardia.net password bbs
telnet: disboardia.net
Subject: Smashbot Citadel
It is starting. It is happening. The wave of Anti-Social Media is going to break on the shore soon.
Visit, contribute, support. Stop feeding the mouth that bites you. Support your local or distant Citadel BBS.
https://citadel.smashbot.com/display_enter
And another one. It needs traffic. Visit, post. Create rooms. Make your space on the Citadels. They're designed to do this.
https://disboardia.net/
Uncensored has the most established user base and the most content, so it needs the least help.
But cross pollination from one BBS to another usually travels both ways. You may end up dragging members from Uncensored to these other Citadels, and vice versa.
People start making "rounds*, going through each BBS to find the one with the hottest current topics... Citadels end up working like a little round-robing network. More so in the old days where your favorite one would be busy, so you would call a different one, and end up creating a traffic jam over at THAT one... it was a very holistic process... Every Citadel got its turn because the people who couldn't get in at the "hot" one would go somewhere else and in turn make THAT one the "hot" one.
The Internet screwed that dynamic up, too.
Sun May 09 2021 19:50:00 MST from TheDaveI have joined these two. I'm still not on Uncensored.
Now we just have to get him calling back, and break TheDave of his Facebook habit.
I feel so much better when I've been gone from Facebook for so long they start sending me e-mails trying to bait me into logging back in.
Wed May 12 2021 19:38:01 MST from ASCII ExpressYes, thanks for calling.
Can someone help me find where I have messed up? I now have citadel answering telnet port 23. I can read messages just fine with a telnet client however when it comes to
entering a username and password, it does not work.
It allows me to enter username but then at the password prompt I have no opportunity to input a password, it just immediately fires back "wrong password".
Here is a photo of what I am experiencing:
It's probably something simple but I can't figure out where I went wrong.
Subject: Re: Citadel Telnet text server
I've experienced this beofre - notice how there are weird characters before your name?
!"'smashbot
Maybe you're in the wrong terminal mode. Are you using Putty? I feel like maybe this was something with putty - and the issue is that it isn't parsing the keyboard input for your password right. I unfortunately forget how I fixed it when it happened to me - but I'm not sure it was server side.
Can someone help me find where I have messed up? I now have citadel answering telnet port 23. I can read messages just fine with a telnet client however when it comes to
entering a username and password, it does not work.
It allows me to enter username but then at the password prompt I have no opportunity to input a password, it just immediately fires back "wrong password".
Here is a photo of what I am experiencing:
It's probably something simple but I can't figure out where I went wrong.
This is what I'm seeing. I enter my name and it automatically returns a password and returns to the name prompt.
And I've ABSOLUTELY had both problems on my Telnet server...
It is something in your init.d or inetd or something like that... maybe the way you're calling the citadel.rc shell in the account you've set up to autolaunch the textclient.
I absolutely cannot remember what I had wrong - but it was absolutely a misconfiguration caused by Operator Error.
I dont think its file permission related at this point. its starting to look like some meatball options were missed or taken at compile time due to the easy install script I used to install citadel. I ran it with no arguments. Perhaps it didnt agree with my particular debian instance. Seems as if the script was written with redhat/fedora in mind.
I could be way off.
Sun May 16 2021 10:08:56 MST from ParanoidDelusions <paranoiddelusions@wallofhate.com>This is what I'm seeing. I enter my name and it automatically returns a password and returns to the name prompt.
And I've ABSOLUTELY had both problems on my Telnet server...
It is something in your init.d or inetd or something like that... maybe the way you're calling the citadel.rc shell in the account you've set up to autolaunch the textclient.
I absolutely cannot remember what I had wrong - but it was absolutely a misconfiguration caused by Operator Error.
it is 100% server side. Client doesnt get a chance to argue password input no matter what.
Fri May 14 2021 14:50:42 MST from ParanoidDelusions <paranoiddelusions@wallofhate.com> Subject: Re: Citadel Telnet text serverI've experienced this beofre - notice how there are weird characters before your name?
!"'smashbot
Maybe you're in the wrong terminal mode. Are you using Putty? I feel like maybe this was something with putty - and the issue is that it isn't parsing the keyboard input for your password right. I unfortunately forget how I fixed it when it happened to me - but I'm not sure it was server side.
Can someone help me find where I have messed up? I now have citadel answering telnet port 23. I can read messages just fine with a telnet client however when it comes to
entering a username and password, it does not work.
It allows me to enter username but then at the password prompt I have no opportunity to input a password, it just immediately fires back "wrong password".
Here is a photo of what I am experiencing:
It's probably something simple but I can't figure out where I went wrong.