First: > > > What do you think about a "telnet" access for JabberForge? I think it > > > > Yes to both! Except for SSH instead of telnet. > > > > Ted - BBSes? ex 1:105/36...
Yes, SSH would be fine! :) Luar, ex 4:850/11 -- and: In Thu, Nov 29, 2001 at 04:00:55PM -0600, Thomas Muldowney wrote: > Well I guess the gatewaying will stay, but I'm completely against a BBS > =) What does that add? another interface without a common protocol to > access elements inside it? No thanks. Yes it has cool neato factors, > and I even have a special one running on one of my servers, but i don't > think it fits the bill here. > > --temas No, my idea is not another interface without a common protocol, it's just another interface with a common protocol. I think JabberForge needs to be a "big server" (not hardware talking), that talks with "client-servers", like jabber itself! This can help so much the job, imagine this, you are programmer, you and other programmers make the jabberforge "kernel". Other people knows lots of html, php, perl, etc, they can make the Web interface, that communicates as a client for JabberForge. I love the BBS's, and I can make a client-server for SSH, you can easily separate the jobs for everyone. If tomorrow appears a new standard that it's not HTML, it's not TCP/IP, it's ... mmh, brainwaves! we can do a client-server for jabberforge communicating in brainwaves with the people, without redoing aaaall the stuff! I don't know, maybe it's a crazy idea... :) I know some programming stuff, in java and C/C++, (and another languages in my past like pascal, delphi, basic :), if you need a hand developing jabberforge "kernel", I can give my hand, just ask for it! :) Bye! Luar Roj� _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
