Telegram notification service

Parad0x e0dc5c4dae - Corrected some language mistakes hace 6 años
src e0dc5c4dae - Corrected some language mistakes hace 6 años
systemd-unit 33beb64627 - Updated totify`s unit file to support enable hace 6 años
.gitattributes 8fdc1faa82 - Moved to typescript hace 6 años
.gitignore 215808bbec - Add packaging script hace 6 años
LICENSE.md 492c8b3f2c - Fixed license author and year hace 6 años
README.md e0dc5c4dae - Corrected some language mistakes hace 6 años
TODO e086d8483e - Added TODO hace 6 años
client.js 8fdc1faa82 - Moved to typescript hace 6 años
package-lock.json 44eadf8b22 - Removed nodemon and empty settings hace 6 años
package.json 44eadf8b22 - Removed nodemon and empty settings hace 6 años
pkg.sh b1b9b81f69 - Fixed pkh.sh script final cwd hace 6 años
tsconfig.json 8fdc1faa82 - Moved to typescript hace 6 años

README.md

Totify

Simple communication bridge between clients and telegram. Using sockets is simple way for other clients to send notification. Current version support only one way communication (from client to telegram) but it should be possible to implement registering command. Protocol is based on queue where elements are separated with semicolons.

Protocol Operations

register (name)

Reply with "<id>&<auth>"

register;Test App;

login (authcode)

Reply with "OK" on success or "ERR" with message;

login;PIZS-4681-bKUp-2154;

notify (msg)

Need authentication Reply with "OK" on success or "ERR" with message;

notify; test notification;

ping

Reply with pong

ping;

close

Reply with closing message and close connection

close;

Communication Sample

Server in: register;Test App;close;
Server out: 5&GSFBT-665-oJDDKqerYCWwfmtFWOOD;
Server in: login;EDSPG-466-VlyoDV9i6mBOAwle0hZU;ping;notify;Test;close;
Server out: OK;pong;OK;Closing connection;
Server in: login;invalid-code;
Server out: ERR;auth unmatched or not activated;
Server in: notify;notify without login;
Server out: ERR;need to be logged;