Telegram notification service

Parad0x 666f641aa4 - Corrected some language mistakes 6 gadi atpakaļ
src 666f641aa4 - Corrected some language mistakes 5 gadi atpakaļ
systemd-unit 9c018d3a86 - Updated totify`s unit file to support enable 5 gadi atpakaļ
.gitattributes 8fdc1faa82 - Moved to typescript 5 gadi atpakaļ
.gitignore 215808bbec - Add packaging script 5 gadi atpakaļ
LICENSE.md 492c8b3f2c - Fixed license author and year 5 gadi atpakaļ
README.md 666f641aa4 - Corrected some language mistakes 5 gadi atpakaļ
TODO 6a07c9e4d2 - Added TODO 5 gadi atpakaļ
client.js 8fdc1faa82 - Moved to typescript 5 gadi atpakaļ
package-lock.json d9aa6d3b47 - Removed nodemon and empty settings 5 gadi atpakaļ
package.json d9aa6d3b47 - Removed nodemon and empty settings 5 gadi atpakaļ
pkg.sh 457ebf151e - Fixed pkg.sh script final cwd 5 gadi atpakaļ
tsconfig.json 8fdc1faa82 - Moved to typescript 5 gadi atpakaļ

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;