Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2024-07-02 | telegram-chat: drop extra conversion | 1 | -2/+2 | ||
The JSON parser war actually fixed in RouterOS 7.15beta4. Let's bump the required version to next stable release instead. | |||||
2024-06-21 | certs: Go Daddy Secure Certificate Authority - G2 -> Go Daddy Root ↵ | 1 | -1/+1 | ||
Certificate Authority - G2 | |||||
2024-05-25 | telegram-chat: drop extra parenthesis | 1 | -3/+3 | ||
2024-05-24 | telegram-chat: convert the message (command) to string | 1 | -10/+11 | ||
RouterOS 7.15beta4 fixed a bug in JSON parser: *) console - do not convert string to array in ":deserialize" command; Before that change commands with a comma caused very crazy issues. Let's convert the message to a string. This does not give exactly the expected result, but mitigates telegram-chat to explode. A command like... /ip/address/print proplist=address,network; ... is converted to... /ip/address/print proplist=address;network; ... and results in: Columns: ADDRESS # ADDRESS 0 10.0.0.1/24 1 127.0.0.1/8 bad command name network (line 1 column 36) | |||||
2024-04-29 | telegram-chat: shorten the message | 1 | -1/+1 | ||
2024-04-01 | telegram-chat: use :deserialize ... | 1 | -7/+6 | ||
... instead of $ParseJson. This requires RouterOS 7.13. | |||||
2024-04-01 | telegram-chat: read file content...routeros-7.13-2change-126 | 1 | -5/+4 | ||
... instead of getting it. This lifts the size limit, though we are still limited by Telegram message size. This requires RouterOS 7.13. | |||||
2024-03-21 | telegram-chat: note active state when answering broadcast | 1 | -1/+1 | ||
2024-03-21 | telegram-chat: improve readability with symbols | 1 | -6/+9 | ||
2024-03-12 | telegram-chat: switch to $LogPrint | 1 | -13/+16 | ||
2024-03-12 | telegram-chat: drop main function, use :do with on-error | 1 | -6/+4 | ||
2024-03-12 | telegram-chat: error when making directory fails | 1 | -1/+3 | ||
2024-03-12 | global-functions: $ScriptLock: do not exit from global function | 1 | -1/+3 | ||
2024-03-04 | telegram-chat: move code into function | 1 | -128/+133 | ||
2024-01-30 | telegram-chat: use :jobname to get script name | 1 | -1/+3 | ||
2024-01-30 | telegram-chat: add (and increase) random delay on error | 1 | -0/+11 | ||
Chances are that two devices schedule the script (nearly) simultaneously. Causing a lot of failures from fetch. Instead of forcing a retry on *every* invocating we add (and increase) a random delay, that is slowly decreasd on success. This should minimize failures... | |||||
2024-01-30 | telegram-chat: fix concatenation (and retry with delay) | 1 | -1/+1 | ||
Ups... 😳 | |||||
2024-01-01 | update copyright for 2024 | 1 | -1/+1 | ||
2023-11-22 | telegram-chat: get rid of '.txt' file extension | 1 | -3/+3 | ||
2023-10-19 | telegram-chat: rework the retry logic | 1 | -3/+5 | ||
... with increasing delay. | |||||
2023-10-19 | telegram-chat: log when sending notice | 1 | -0/+1 | ||
2023-10-19 | telegram-chat: drop extra conversion | 1 | -1/+1 | ||
2023-10-17 | telegram-chat: retry on fetch failure... | 1 | -7/+16 | ||
... and exit with a warning. | |||||
2023-10-17 | telegram-chat: make messages silent... | 1 | -2/+2 | ||
... at least those not indicating an error. | |||||
2023-10-16 | telegram-chat: use $ParseJson for all JSON | 1 | -2/+1 | ||
2023-10-16 | telegram-chat: do not act on foreign reply... | 1 | -1/+2 | ||
... even if active! | |||||
2023-10-16 | telegram-chat: rename variable | 1 | -3/+3 | ||
2023-10-16 | telegram-chat: answer question mark with short noticechange-106-2 | 1 | -1/+7 | ||
2023-10-16 | telegram-chat: restore indention | 1 | -25/+25 | ||
2023-10-16 | telegram-chat: do not nest conditions | 1 | -3/+4 | ||
2023-10-16 | telegram-chat: act on reply without delay | 1 | -4/+4 | ||
2023-10-16 | telegram-chat: act on reply from selfchange-106-1 | 1 | -1/+3 | ||
2023-10-16 | global-functions: make $ParseJson global | 1 | -26/+1 | ||
2023-10-16 | telegram-chat: parse (one level of) JSON into array | 1 | -33/+41 | ||
2023-10-16 | telegram-chat: do not cover existing variable | 1 | -3/+3 | ||
2023-09-15 | telegram-chat: create status files with /file/addrouteros-7.9beta4-9 | 1 | -4/+4 | ||
We have no content, thus no issues with file size. | |||||
2023-09-15 | telegram-chat: use the full command name :execute | 1 | -1/+1 | ||
2023-03-07 | rename scripts and add file extension ".rsc"change-95 | 1 | -0/+150 | ||
No functional change for the user... The migration is done automatically. |