Telegram notification service

Parad0x c76d252c6b - Updated README.md 6 éve
src 58921567a4 - Added JSDocs for most functions 5 éve
systemd-unit 9c018d3a86 - Updated totify`s unit file to support enable 5 éve
.gitattributes 8fdc1faa82 - Moved to typescript 5 éve
.gitignore 215808bbec - Add packaging script 5 éve
LICENSE.md 492c8b3f2c - Fixed license author and year 5 éve
README.md c76d252c6b - Updated README.md 5 éve
TODO 6a07c9e4d2 - Added TODO 5 éve
client.js 8fdc1faa82 - Moved to typescript 5 éve
package-lock.json d9aa6d3b47 - Removed nodemon and empty settings 5 éve
package.json d9aa6d3b47 - Removed nodemon and empty settings 5 éve
pkg.sh 457ebf151e - Fixed pkg.sh script final cwd 5 éve
tsconfig.json 8fdc1faa82 - Moved to typescript 5 éve

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's Operators

register

Reply with "<id>&<auth>"

register;

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 server connection

close;

Sample Comunication

Server in: register;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;