Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I throw this here as draft idea but I believe there is room of improvement.
This is a functioning version of Simplex Bot that does not require any change of the backend and simply query the postgres database against a self created simple sql database storing users registered robot. Robot is matched against same token used by telegram.
Maybe a bot that would use redis channels instead of proactively checking for new notifications in the database would be more efficient. Also to make it user friendly I would imagine that alongside "enable telegram bot", a new "enable simplex bot" button that would show simplex bot address and token would be needed.
It is usable right now, but the user would manually need to copy the telegram token, and interact with the bot through message
, as shown below:
To use the bot:
docker run -it -v ./simplex/database:/simplex_database lndtest-simplex simplex-chat -p 5225 -d /simplex_database/test_db
. This will allow you to give a name to your bot