Hi
Trying to setup a bot to greet any new contact that sends advertisement to the Mesh (or a text message)
New users use radio presets and dont know there are other resources like maps, discord etc etc
There seems to be a limitation to trigger only on text messages in the automation - python bot scripts
Can you see if it can be added as part of a simple bot script rather then trying to do a separate API based one?
Hi
Trying to setup a bot to greet any new contact that sends advertisement to the Mesh (or a text message)
New users use radio presets and dont know there are other resources like maps, discord etc etc
There seems to be a limitation to trigger only on text messages in the automation - python bot scripts
Can you see if it can be added as part of a simple bot script rather then trying to do a separate API based one?
<!-- github-sync-id:4466851833 -->
this sounds as network abuse.
but still this won't work, new contact doesn't heard your advertisement and doesn't have your contact — he cannot decode your message.
this sounds as network abuse.
but still this won't work, new contact doesn't heard your advertisement and doesn't have your contact — he cannot decode your message.
<!-- github-comment-id:4480991547 -->
It's your personal opinion @hackruu
Anyway, I have done it outside of RT automation, just thought it would be a nice feature to have
It's your personal opinion @hackruu
Anyway, I have done it outside of RT automation, just thought it would be a nice feature to have
<!-- github-comment-id:4483012816 -->
This is probably not something we're going to add support for. Meaningful automation beyond simple bots should be done via HA or other scriptable means, and yeah I generally agree with hackruu that blind messaging contacts that may not have your keys, or worse, flood adverting in response to a new advert, is a quick way to make the mesh noisy. If you are interested in extending the code, the fanout modules do receive all mesh events (which is how the HA integration works), but that probably wouldn't be a PR I'd merge. RemoteTerm is really intended to be a chat client first and foremost, with some ultralight automation but with more meaningful processing done elsewhere if desired.
This is probably not something we're going to add support for. Meaningful automation beyond simple bots should be done via HA or other scriptable means, and yeah I generally agree with hackruu that blind messaging contacts that may not have your keys, or worse, flood adverting in response to a new advert, is a quick way to make the mesh noisy. If you are interested in extending the code, the fanout modules do receive all mesh events (which is how the HA integration works), but that probably wouldn't be a PR I'd merge. RemoteTerm is really intended to be a chat client first and foremost, with some ultralight automation but with more meaningful processing done elsewhere if desired.
<!-- github-comment-id:4493084057 -->
Could have added a bot feature to greet someone on the public channel it was not seen before. Anyway, we have done our code outside of RT
Could have added a bot feature to greet someone on the public channel it was not seen before. Anyway, we have done our code outside of RT
<!-- github-comment-id:4493135081 -->
Yeah, but I can see that causing issues with generating spam in the public channel. Glad you found a solution that works for you. Generally, for RemoteTerm, I'm going to keep built-in automation limited to the simple bots, although you have inspired me to maybe add a data-feed MQTT that's basically HA but a bit less aggressively structured.
Yeah, but I can see that causing issues with generating spam in the public channel. Glad you found a solution that works for you. Generally, for RemoteTerm, I'm going to keep built-in automation limited to the simple bots, although you have inspired me to maybe add a data-feed MQTT that's basically HA but a bit less aggressively structured.
<!-- github-comment-id:4493181413 -->
Don't know what MC is like where you are, but for pretty much anything you say that it generate spam, noise, network abuse
New members will generate way more, just trying to find more information
Don't know what MC is like where you are, but for pretty much anything you say that it generate spam, noise, network abuse
New members will generate way more, just trying to find more information
<!-- github-comment-id:4493207413 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi
Trying to setup a bot to greet any new contact that sends advertisement to the Mesh (or a text message)
New users use radio presets and dont know there are other resources like maps, discord etc etc
There seems to be a limitation to trigger only on text messages in the automation - python bot scripts
Can you see if it can be added as part of a simple bot script rather then trying to do a separate API based one?
this sounds as network abuse.
but still this won't work, new contact doesn't heard your advertisement and doesn't have your contact — he cannot decode your message.
It's your personal opinion @hackruu
Anyway, I have done it outside of RT automation, just thought it would be a nice feature to have
This is probably not something we're going to add support for. Meaningful automation beyond simple bots should be done via HA or other scriptable means, and yeah I generally agree with hackruu that blind messaging contacts that may not have your keys, or worse, flood adverting in response to a new advert, is a quick way to make the mesh noisy. If you are interested in extending the code, the fanout modules do receive all mesh events (which is how the HA integration works), but that probably wouldn't be a PR I'd merge. RemoteTerm is really intended to be a chat client first and foremost, with some ultralight automation but with more meaningful processing done elsewhere if desired.
Could have added a bot feature to greet someone on the public channel it was not seen before. Anyway, we have done our code outside of RT
Yeah, but I can see that causing issues with generating spam in the public channel. Glad you found a solution that works for you. Generally, for RemoteTerm, I'm going to keep built-in automation limited to the simple bots, although you have inspired me to maybe add a data-feed MQTT that's basically HA but a bit less aggressively structured.
Don't know what MC is like where you are, but for pretty much anything you say that it generate spam, noise, network abuse
New members will generate way more, just trying to find more information