That's sort of how I've got the bulletin system working. There's nothing to be done about the scripts on the communicator itself, but using the native network itself to relay content instead of trying to distribute a completely separate application seems like a more resilient method, so far.
I suppose you could use the same kind of scripting to create a timekeeper "bot" on a communicator. Have it reply automatically to requests for the date, or send a text to the bulletin bot prompting calendar updates each time the day turns over.
You would need another spare communicator, though. I've tried making dummy accounts on the network, and they don't verify. There's some identifying piece of hardware in the comms that's required.
no subject
I suppose you could use the same kind of scripting to create a timekeeper "bot" on a communicator. Have it reply automatically to requests for the date, or send a text to the bulletin bot prompting calendar updates each time the day turns over.
You would need another spare communicator, though. I've tried making dummy accounts on the network, and they don't verify. There's some identifying piece of hardware in the comms that's required.