How important is it to have https access fro Synchronet and ftelnetaccess
on your BBS? Do your users logon from the web and ftelnet? Do most use telnet and/or ssh?
HusTler wrote to All <=-
How important is it to have https access fro Synchronet and
ftelnet access on your BBS?
Do your users logon from the web and ftelnet?
Do most use telnet and/or ssh?
On 10-30-19 10:52, Nightfox wrote to HusTler <=-
I'm not sure it's highly important to have https access. Many people
Do your users logon from the web and ftelnet?
No. Not enabled on my system.
Do most use telnet and/or ssh?
Only telnet enabled here.
How important is it to have https access fro Synchronet and
ftelnet access on your BBS?
Not important to me at all. I do not have web access to my BBS
enabled. To me, a BBS should be accessed from an ANSI-type
application to make it as similar to the dial-up days as possible.
Thanks for that. Maybe I'm better off without the web stuff. I don'tthink
the younger generation is even interested in BBSing. I can't even get my 30 year old son to create an account on my BBS. He can't get past the login screens. lol
Nightfox wrote to Gamgee <=-
How important is it to have https access fro Synchronet and
ftelnet access on your BBS?
Not important to me at all. I do not have web access to my BBS
enabled. To me, a BBS should be accessed from an ANSI-type
application to make it as similar to the dial-up days as possible.
Having fTelnet (or similar) hosted on a web page can be handy for
users to log in and access the ANSI interface if they don't have
a telnet program installed.
Also, what about RIP?
Having fTelnet (or similar) hosted on a web page can be handy for
users to log in and access the ANSI interface if they don't have
a telnet program installed.
I suppose so.... but to me if they want to call a BBS they
should/would have a telnet client installed. :-)
Also, what about RIP?
Another non-factor for me. Don't have menus for it and don't even
know how they're created. Also, if a caller doesn't have a telnet
client available, they certainly don't know about a RIP-capable
client.
On 10-31-19 09:59, Nightfox wrote to HusTler <=-
I never thought using a BBS was that difficult though.. But maybe
that's because I had been using computers since I was a kid, even
before I got my own. My dad was always into computers (and still is) -
He was often messing around on computers such as the TRS-80 (before I
was born), so there was always a computer (or 2 or 3) around when I was growing up. Also, the schools I went to often had an area with
computers, usually Apple 2 in the 80s (we'd play games such as Logo, Oregon Trail, etc. on them), and later, Macintosh computers. My dad eventually started using IBM PC compatibles at home. So I grew up learning about that stuff, and I was fine using DOS.
I've seen some videos on YouTube with young kids using old technology
and trying to figure it out.. Sometimes funny results.
On 10-31-19 13:46, Gamgee wrote to Nightfox <=-
Having fTelnet (or similar) hosted on a web page can be handy for
users to log in and access the ANSI interface if they don't have
a telnet program installed.
I suppose so.... but to me if they want to call a BBS they
should/would have a telnet client installed. :-)
Also, what about RIP?
Another non-factor for me. Don't have menus for it and don't even
know how they're created. Also, if a caller doesn't have a telnet
client available, they certainly don't know about a RIP-capable
client.
Having fTelnet (or similar) hosted on a web page can be handy for
should/would have a telnet client installed. :-)
Also, what about RIP?
Another non-factor for me. Don't have menus for it and don't even
know how they're created. Also, if a caller doesn't have a telnet
client available, they certainly don't know about a RIP-capable
client.
I'm not a big fan of the "web does everything" model. Web versions oftext
based systems have always had some odd annoyances (most commonly with copy/paste). Give me a dedicated client anyday.
HusTler wrote to Gamgee <=-
Also, what about RIP?
Another non-factor for me. Don't have menus for it and don't even
know how they're created. Also, if a caller doesn't have a telnet
client available, they certainly don't know about a RIP-capable
client.
Did you know Synchronet comes with Rip menus ? I'm sure you've
saw them in sbbs/text/menus
Nightfox wrote to Gamgee <=-
Having fTelnet (or similar) hosted on a web page can be handy for
users to log in and access the ANSI interface if they don't have
a telnet program installed.
I suppose so.... but to me if they want to call a BBS they
should/would have a telnet client installed. :-)
I always thought the same, but there are casual users who might
not have a BBS telnet client installed because they just don't
use one very often. Those types of users might only be inclined
to call your BBS if there is something like fTelnet available.
Also, what about RIP?
Another non-factor for me. Don't have menus for it and don't even
know how they're created. Also, if a caller doesn't have a telnet
client available, they certainly don't know about a RIP-capable
client.
If they don't know about RIP, they might not be familiar with
ANSI either.
I don't have any RIP menus, but sometimes I've wondered if it
would be useful to have something more GUI-like such as RIP. If
there was something like fTelnte that supported RIP, it might
look a little more 'modern' than ANSI, which I wonder if some
users might be interested in.
Tony Langdon wrote to Gamgee <=-
Having fTelnet (or similar) hosted on a web page can be handy for
users to log in and access the ANSI interface if they don't have
a telnet program installed.
I suppose so.... but to me if they want to call a BBS they
should/would have a telnet client installed. :-)
I'm not a big fan of the "web does everything" model. Web
versions of text based systems have always had some odd
annoyances (most commonly with copy/paste). Give me a dedicated
client anyday.
That aside, I don't mind providing such interfaces for those masochists^H^H^H^H^H^H^H^H^Hpeople who like them. :)
Also, what about RIP?
Another non-factor for me. Don't have menus for it and don't even
know how they're created. Also, if a caller doesn't have a telnet
client available, they certainly don't know about a RIP-capable
client.
Something I'd liked to have seen more of back in the day. The
concept of RIP did intrigue me.
On 10-31-19 17:34, Nightfox wrote to Tony Langdon <=-text
I'm not a big fan of the "web does everything" model. Web versions of
based systems have always had some odd annoyances (most commonly with copy/paste). Give me a dedicated client anyday.
That's true, it has its drawbacks, but I don't think it really hurts anything to have a web telnet client available. A lot of people these
On 10-31-19 22:04, Gamgee wrote to Tony Langdon <=-
Same here, to the point that I choose to not offer the web access,
at least for now.
That aside, I don't mind providing such interfaces for those masochists^H^H^H^H^H^H^H^H^Hpeople who like them. :)
Hehe! One of my other reasons for not enabling that interface is
the increased security risks that it brings with it.
Something I'd liked to have seen more of back in the day. The
concept of RIP did intrigue me.
Agreed, it was fairly rare even back then, in my part of the scene
anyway. I don't recall there being a client easily obtained/used
to call such systems, either.
On 10-31-19 21:59, Gamgee wrote to Nightfox <=-
You know, Hustler reminded me in a message in this thread, that
Synchronet actually does come with RIP menus... I had completely forgotten that myself. Sometime soon I'm gonna point a RIPterm
client at my board and see what I see. :-)
You know, Hustler reminded me in a message in this thread, that Synchronet actually does come with RIP menus... I had completely forgotten that myself. Sometime soon I'm gonna point a RIPterm
client at my board and see what I see. :-)
Tony Langdon wrote to Gamgee <=-
You know, Hustler reminded me in a message in this thread, that
Synchronet actually does come with RIP menus... I had completely forgotten that myself. Sometime soon I'm gonna point a RIPterm
client at my board and see what I see. :-)
I get an ANSI telnet session. Obviously have to do something
more to get RIP happening.
I just tried my system, calling it from a Win7 box and running
"RIPTel" as the client. The "logon" screens showed as normal ANSI
(as expected), but the Main Menu was definitely RIP! Also saw a
few other menus that were RIP as well, and they looked great.
Listing *.rip in your /sbbs/text/menu directory will show you
which menus are there for RIP. It's pretty basic and "stock", but
it works... :-)
On 11-01-19 11:01, Gamgee wrote to Tony Langdon <=-
I just tried my system, calling it from a Win7 box and running
"RIPTel" as the client. The "logon" screens showed as normal ANSI
(as expected), but the Main Menu was definitely RIP! Also saw a
few other menus that were RIP as well, and they looked great.
Listing *.rip in your /sbbs/text/menu directory will show you
which menus are there for RIP. It's pretty basic and "stock", but
it works... :-)
Tony Langdon wrote to Gamgee <=-
I just tried my system, calling it from a Win7 box and running
"RIPTel" as the client. The "logon" screens showed as normal ANSI
(as expected), but the Main Menu was definitely RIP! Also saw a
few other menus that were RIP as well, and they looked great.
Listing *.rip in your /sbbs/text/menu directory will show you
which menus are there for RIP. It's pretty basic and "stock", but
it works... :-)
Yes, I investigated further and got the RIP menus. Quite
functional, though the swapping between RIP and ANSI modes was a
bit disconcerting. :)
On 11-01-19 20:42, Gamgee wrote to Tony Langdon <=-
Yes, I investigated further and got the RIP menus. Quite
functional, though the swapping between RIP and ANSI modes was a
bit disconcerting. :)
Yes, it is.
I guess now you'll have to customize them and add the ones to
replace the ANSI screens. Let us know when you're done, and what tool/editor you used to accomplish it... :-)
Tony Langdon wrote to Gamgee <=-
Yes, I investigated further and got the RIP menus. Quite
functional, though the swapping between RIP and ANSI modes was a
bit disconcerting. :)
Yes, it is.
I guess now you'll have to customize them and add the ones to
replace the ANSI screens. Let us know when you're done, and what tool/editor you used to accomplish it... :-)
I don't do UI stuff really. I find it too tedious. :( And I
have nothing to generate RIP menus with anyway.
I also found another issue. I was already logged in using
SyncTerm. When I logged in using RIPTel, Synchronet also
switched my preexisting session to RIP, and that persisted even
after the RIP session was logged out. I had to log out of and
back into the SyncTerm session to get standard ANSI back. :)
Yeah, I hear that. I have some custom ANSI stuff, but not about
to create RIP stuff. Nobody uses it anyway.
On 11-02-19 12:45, Richard Williamson wrote to Tony Langdon <=-
thats because when you logged into with ripterm it changed a flag in
your user,it isn't session based it just goes by the last time you
logged in
On 11-02-19 12:51, Gamgee wrote to Tony Langdon <=-
Yeah, I hear that. I have some custom ANSI stuff, but not about
to create RIP stuff. Nobody uses it anyway.
Well that's interesting. Probably from the "auto detect" function
of the terminal/Syncterm.
On 11-02-19 12:35, Nightfox wrote to Gamgee <=-
Re: Re: Web Question?
By: Gamgee to Tony Langdon on Sat Nov 02 2019 12:51 pm
Yeah, I hear that. I have some custom ANSI stuff, but not about
to create RIP stuff. Nobody uses it anyway.
Of course nobody uses it if nobody is creating RIP stuff.. ;)
toOn 11-01-19 20:42, Gamgee wrote to Tony Langdon <=-
Yes, I investigated further and got the RIP menus. Quite
functional, though the swapping between RIP and ANSI modes was a
bit disconcerting. :)
Yes, it is.
I guess now you'll have to customize them and add the ones to
replace the ANSI screens. Let us know when you're done, and what tool/editor you used to accomplish it... :-)
I don't do UI stuff really. I find it too tedious. :( And I have nothing to generate RIP menus with anyway.
I also found another issue. I was already logged in using SyncTerm. When logged in using RIPTel, Synchronet also switched my preexisting session to RIP, and that persisted even after the RIP session was logged out. I had
log out of and back into the SyncTerm session to get standard ANSI back. :)
thats because when you logged into with ripterm it changed a flag in your user, it isn't session based it just goes by the last time you logged in
On 11-02-19 21:18, Digital Man wrote to Tony Langdon <=-
That problem was fixed early this year. Please upgrade.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 295 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 07:55:06 |
| Calls: | 6,642 |
| Calls today: | 2 |
| Files: | 12,190 |
| Messages: | 5,326,192 |