Marisag wrote to All on 06-21-18 11:59 <=-
I am almost done creating a new cross-platform sysop pager and would
like to get some extra testing done. Basicly there are two sides - one that runs on the SBBS server that creates a file when someone pages the sysop, and one that runs on the machine you want to notify on. They
don't have to be the same at all.
Right now I have it playing a sound on the local side if a chat is requested on the server side. You then connect to your BBS and chat the user. If the user logs out before that it will remove the notifyer for that node.
If you have a linux SBBS that would be best first, then when I know
thats working I will like to test the windows server & client.
Let me know if you want to try it! Would like to get feedback on the documentation too.
On 06-21-18 11:59, Marisag wrote to All <=-
I am almost done creating a new cross-platform sysop pager and would
like to get some extra testing done. Basicly there are two sides - one that runs on the SBBS server that creates a file when someone pages the sysop, and one that runs on the machine you want to notify on. They
don't have to be the same at all.
Right now I have it playing a sound on the local side if a chat is requested on the server side. You then connect to your BBS and chat the user. If the user logs out before that it will remove the notifyer for that node.
If you have a linux SBBS that would be best first, then when I know
thats working I will like to test the windows server & client.
Let me know if you want to try it! Would like to get feedback on the documentation too.
On 06-21-18 14:01, Bill McGarrity wrote to Marisag <=-
I whipped up some javascript that will tweet the sysop if they're
indeed available to chat. The sysop has to set his twitter BBS account
the push ability for tweets so they get alarmed on their phones.
I whipped up some javascript that will tweet the sysop if they're
indeed available to chat. The sysop has to set his twitter BBS
account the push ability for tweets so they get alarmed on their
phones.
2 issues with that for me:
1. I don't do Twitter, and 2. If I did, it's generally too "noisy" (which is the main reason I dropped it), unless I have a dedicated account.
On 06-21-18 16:55, Nightfox wrote to Tony Langdon <=-
Yeah, I created a Twitter account years ago but I never really ended up using it. For me, the issue is that it isn't too noisy, but much the opposite - I don't know anyone who uses Twitter much, so I didn't have anyone to follow on Twitter. And I don't think it's very interesting
to post something on a social media site if nobody is following me
(nobody or very few people will see it or reply to it).
On 06-21-18 17:52, Marisa Giancarla wrote to alt.bbs.synchronet <=-
@VIA: VERT
From Newsgroup: alt.bbs.synchronet
My script currently has a window that displays the node, name, and date
of a user wanting to chat. I'm planning on having it minimize to the
task bar/ menu bar and then open up if someone pages the sysop.
Tony Langdon wrote to Bill McGarrity on 06-22-18 06:53 <=-
On 06-21-18 14:01, Bill McGarrity wrote to Marisag <=-
I whipped up some javascript that will tweet the sysop if they're
indeed available to chat. The sysop has to set his twitter BBS account
the push ability for tweets so they get alarmed on their phones.
2 issues with that for me:
1. I don't do Twitter, and 2. If I did, it's generally too "noisy" (which is the main reason I dropped it), unless I have a dedicated account.
On 06-23-18 18:16, Bill McGarrity wrote to Tony Langdon <=-
Well, as I said, this is a dedicated account for the BBS so I don't get any noise from the 1 billion other posters... just mine. :)
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 189:11:49 |
| Calls: | 2,004 |
| Calls today: | 1 |
| Files: | 11,114 |
| Messages: | 942,265 |