Paulie @20fB gave me some nudges, but we both figured it would be much better to ask here on fsxNet.
To help any responders, he was looking for any door kits; like RefDoor, but more in depth. I know there are several available, and forgot the
main one to suggest...
To help any responders, he was looking for any door kits; like
RefDoor, but more in depth. I know there are several available, and
forgot the main one to suggest...
Magidoor sounds cool to me, but I had tough time finding it, is it
available online or can be found here on some BBS?
Paulie @20fB gave me some nudges, but we both figured it wouldbetter to ask here on fsxNet.
be much
To help any responders, he was looking for any door kits; like RefDoor, but more in depth. I know there are several available, and forgot the main one to suggest...
I just wrote about am old-skool door kit: https://retroshed.us/bbs-door-dev-1/
With the above you end up with a 'door' that's generic enough to
pretty much work on any system, but uses modern terminal kits and
techniques making life easier there as well.
You could do that, but you'll have to implement dropfile handling, connection timeouts and time-left handling yourself.
Thank you both NuSkooler & apam, this is insightful!
aLPHA wrote to paulie420 <=-
I just wrote about am old-skool door kit: https://retroshed.us/bbs-door-dev-1/
apam wrote to NuSkooler <=-
For magidoor, it's pretty much some convienence functions, dropfile handling and writing to either a socket or stdio depending on OS, plus
the timeout handling - I wonder if you could then use ncurses on top of that for window drawing etc.
My advice: don't. Look for *terminal kits* instead, and us stdio. This works in all the modern boards (and can be wrapped for any older softs easily). There are nice term kits for pretty much any language out
there.
You've all been very helpful and I appreciate it the most, especially
for such a niche/small(er) scene in today's world (who knows why that's good actually).
I just wrote about am old-skool door kit: https://retroshed.us/bbs-door-dev-1/
Dope article, thanks!
You could do that, but you'll have to implement dropfile handling, connection timeouts and time-left handling yourself.
It's really the learning curve you want to go with, if it's something
like ncurses, you can use the knowledge elsewhere.
For magidoor, it's pretty much some convienence functions, dropfile handling and writing to either a socket or stdio depending on OS, plus
the timeout handling - I wonder if you could then use ncurses on top of that for window drawing etc.
On Sat Dec 3 14:42:00 2022, Bugz wrote to aLPHA <=-
aLPHA wrote to paulie420 <=-
I just wrote about am old-skool door kit: https://retroshed.us/bbs-door-dev-1/
Ah ha! another gopher! If I could get comfortable with go versioning
I'd get my library released. You can check out my demo door on
Smuggler's Cove. Apam was nice/brave enough to put it on his BBS.
On Sat Dec 3 10:40:00 2022, NuSkooler wrote to thunderoxx <=-
thunderoxx around Saturday, December 3rd...
Thank you both NuSkooler & apam, this is insightful!
To be clear, we all have our opinions, but I don't think anyone is really "right". The real goal: Have fun :)
On Sat Dec 3 17:24:00 2022, esc wrote to apam <=-
You could do that, but you'll have to implement dropfile handling, connection timeouts and time-left handling yourself.
I take for granted doorkits handle all of this, which is nice. That said, stdio games seem to work as expected when the user drops carrier and they close. I suppose that's the bbs handling it somehow, I have no idea really.
It's really the learning curve you want to go with, if it's something like ncurses, you can use the knowledge elsewhere.
I will say that working with ncurses directly is like a step backwards in time, and not in a good way :P doorkits have /much/ better implementation strategies for the things we intend to do with writing characters and colors on a screen. ncurses is industry standard for good reason, but we've got some better optimized code for our purposes in doorkits.
For magidoor, it's pretty much some convienence functions, dropfile handling and writing to either a socket or stdio depending on OS, plus the timeout handling - I wonder if you could then use ncurses on top of that for window drawing etc.
I wrote a roguelike (very basic) in c over the past several days using ncurses. I've been thinking about porting it over to a very simple, lightweight, stay-out-of-your-way doorkit. I may experiment with magidoor as well as others and write up my experience.
Nevertheless I think the doors /you/ have made, which use magidoor, all work quite well and feel snappy and seemingly run without any major issues. So kudos to you for that!
Nice advice, Nu... I am a GREEN HORN but learning more and more about Python... I'd LOVE to be able to write to the terminal/user w/ it; you don't gotta go into detail, but you think I could use your method in Python for outputting to the term?
apam wrote to Bugz <=-
But... probably best to point people to your bbs (Red Green BBS) as
mine is private (just that it has a new user password - if people want
to visit i'm happy to share it, but not publicly, I got tired of
trolls)
On Saturday, December 3rd paulie420 muttered...
Nice advice, Nu... I am a GREEN HORN but learning more and more about Python... I'd LOVE to be able to write to the terminal/user w/ it; yo don't gotta go into detail, but you think I could use your method in Python for outputting to the term?
On Thursday December 1st paulie420 said...
Paulie @20fB gave me some nudges but we both figured it wouldbetter to ask here on fsxNet.
be much
To help any responders he was looking for any door kits; like RefDoor but more in depth. I know there are several available and forgot the main one to suggest...
My advice: dont. Look for *terminal kits* instead and us stdio. This works in all the modern boards (and can be wrapped for any older softs easily). There are nice term kits for pretty much any language out there.
With the above you end up with a door thats generic enough to pretty much work on any system but uses modern terminal kits and techniques making life easier there as well.
...ofc if you want to do it oldschool for the true feel Ive had success with FPC and some of the Pascal kits floating around but I cant remember their names :D
--
|08 ■ |12NuSkooler |06// |12Xibalba |08- |07|06The place of fear|07
|08 ■ |03xibalba|08.|03l33t|08.|03codes |08(|0344510|08/|03telnet|08 |0344511|08/|03ssh|08)
|08 ■ |03ENiGMA 1/2 WHQ |08| |03Phenom |08| |0367 |08| |03iMPURE |08| |03ACiDic
--- ENiGMA 1/2 v0.0.13-beta (linux; x64; 16.16.0)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
Ah! Sorry, I forgot you're private. So is Red Green BBS!
The embarrassment of having spams sent from my BBS was enough for me
to lock new users with a password. If you don't have the time to
actively monitor it, lock it down.
I'll get Red Green reconfigured so new users can't post to the networks.
I can handle local message base spam. That doesn't go very far.
I also completely forgot about having door++ out there. That's what I based my go one on.
https://github.com/stevet11/door
Take care,
Steve
claw wrote to Bugz <=-
Wow so you actually had someone get signed up and then spam on your
BBS? Seems like a lot of work to go to for a small audience.
What did the do? local boards? nets? elaborate please.
They setup 3 accounts. Used one to spam dove-net. I delete the account, but didn't think to check for others. About a week later, another spam into dove-net. I got the other two accounts deleted that time.
The spam was links to a cracks site.
Do anything you can to get links to your website, I guess.
Take care,
bugz
DrClawMy favorite badguy ^^. Thanks for bringing back memories.
Standard Ports for SSH/Telnet Web/HTTP://Noverdu.com:808If you can, you might want to add the following CSS to your ftelnet index.html:
It will create a black background on the body, looks much nicer. And the second line streches the screen a bit more. You could make it 80vh if
you dont like it too big ;).
check www.thawk.nl/ftelnet/ for example..
Standard Ports for SSH/Telnet Web/HTTP://Noverdu.com:808If you can, you might want to add the following CSS to your ftelnet index.html:
<style>
body {background:black;}red Doors!/50Nodes/No Time Use! Stay On!
.fTelnetCrtCanvas {height:100vh !important;}
</style>
It will create a black background on the body, looks much nicer. And the second line streches the screen a bit more. You could make it 80vh if
you dont like it too big ;).
check www.thawk.nl/ftelnet/ for example..
oP!
... Why is the man who invests all your money called a broker?
<style>
body {background:black;}
.fTelnetCrtCanvas {height:100vh !important;}
</style>
Yeah I'm not much of a developer. I will have to see if I can figure out to put this in. For the most part its some very basic HTML code that was generated by the fTelnet folks to make it work. If you would ever be up t help with that I would appreciate it. MRC or discord or Teamspeak or what you prefer
Are you hosting the fTelnet code generated by the embed-v2.ftelnet.ca website? Im pretty sure you can copy paste the code above in the same generated block (top).
Hit me up on Discord if it doesnt work (DonderMuis) on Arak/Phenom etc.
oP!
On Sunday, December 4th apam said...
You could do that, but you'll have to implement dropfile handling, connection timeouts and time-left handling yourself.
Dropfiles are so basic, and many of the values don't make sense any longer (or are dummy values & ignored anyway), so I guess I don't see this as a blocker. Connection timeouts are generally handled by the BBS: If the connection drops, the board drops the door PID.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,064 |
| Nodes: | 17 (1 / 16) |
| Uptime: | 18:30:41 |
| Calls: | 501,325 |
| Calls today: | 4 |
| Files: | 109,413 |
| D/L today: |
2,164 files (306M bytes) |
| Messages: | 302,017 |