During the installation of DA on one of my VM a broadcast with wall popped up.. That was all it took.. I scrambled to figure out what did that and replied with my greeting using wall. Since that moment I am unable to get the memories of all the telephone system abuse, bbs, fidonet, 2600 and so forth out of my head.
So far I've been fiddling around with the basics, echo redirection, wall, talk, write & mesg.
yTalk and nTalk are next on the list. Many providers blanket policy with NO IRC daemon and I suppose it's valid in many contexts. However I am just thinking of use between users on the servers, and between the servers.. For admin and reseller users to start.
Possibly later a means to be in shell and chat with a hosting client through their DA panel.
Self contained, low impact and no/low requirements are what I'm looking for. I get aggravated having to mess around with my browser, firewalls, plug-ins and such for third-party subscription types chat services.
Anyhow, I wanted to ask if anyone has been down this road yet and if there may be any input?
So far it looks quite workable and I'm kind of excited to begin working on this in the next month or two.
So far I've been fiddling around with the basics, echo redirection, wall, talk, write & mesg.
yTalk and nTalk are next on the list. Many providers blanket policy with NO IRC daemon and I suppose it's valid in many contexts. However I am just thinking of use between users on the servers, and between the servers.. For admin and reseller users to start.
Possibly later a means to be in shell and chat with a hosting client through their DA panel.
Self contained, low impact and no/low requirements are what I'm looking for. I get aggravated having to mess around with my browser, firewalls, plug-ins and such for third-party subscription types chat services.
Anyhow, I wanted to ask if anyone has been down this road yet and if there may be any input?
So far it looks quite workable and I'm kind of excited to begin working on this in the next month or two.