adam/contact
1
0 Fork 0
mirror of https://github.com/pdxlocations/contact.git synced 2026-11-02 09:00:32 +01:00
Code Issues 16 Packages Projects Releases Wiki Activity

[Feature Request] Add prompt and handling for new meshtastic firmware 2 second text message rate limit #65

New Issue
Closed
opened 2026-10-05 03:18:46 +02:00 by adam · 3 comments
adam commented 2026-10-05 03:18:46 +02:00
Owner
Copy link
Copy source

Meshtastic firmwares newer than 2.7.0 implement a rate limit to outgoing text messages. See https://github.com/meshtastic/firmware/pull/7139 .

Newer Android client versions add an error message when trying to send a message too quickly, letting the user know they need to wait (similar to the traceroute rate limit.) Since typing multiple messages quickly is relatively easier with a computer keyboard, it seems like this limit will be easier to hit with this client than with others such as mobile device clients. Contact should at least tell the user if they're trying to send a message too quickly. We may also want to consider not showing the failed message in the outgoing messages window, or leaving the user's entered text in the message input window so they can more easily send their message after waiting sufficient time and not need to retype or copy/paste the message again. We could also consider automatically queue up the outgoing message and only try to send it after an appropriate delay, along with some UI indicator for showing the message waiting to be sent.

Meshtastic firmwares newer than 2.7.0 implement a rate limit to outgoing text messages. See https://github.com/meshtastic/firmware/pull/7139 . Newer Android client versions add an error message when trying to send a message too quickly, letting the user know they need to wait (similar to the traceroute rate limit.) Since typing multiple messages quickly is relatively easier with a computer keyboard, it seems like this limit will be easier to hit with this client than with others such as mobile device clients. Contact should at least tell the user if they're trying to send a message too quickly. We may also want to consider not showing the failed message in the outgoing messages window, or leaving the user's entered text in the message input window so they can more easily send their message after waiting sufficient time and not need to retype or copy/paste the message again. We could also consider automatically queue up the outgoing message and only try to send it after an appropriate delay, along with some UI indicator for showing the message waiting to be sent. <!-- github-sync-id:3229650536 -->
adam closed this issue 2026-10-05 03:18:46 +02:00
adam commented 2026-10-05 03:18:47 +02:00
Author
Owner
Copy link
Copy source

I think the firmware sends the errors to the clients for these things. Catching and handling those would be great too!

I think the firmware sends the errors to the clients for these things. Catching and handling those would be great too! <!-- github-comment-id:3071237458 -->
adam commented 2026-10-05 03:18:48 +02:00
Author
Owner
Copy link
Copy source

Looks like soon we may be able to process routing errors
https://discord.com/channels/867578229534359593/931765413350613052/1395062285202100224

Looks like soon we may be able to process routing errors https://discord.com/channels/867578229534359593/931765413350613052/1395062285202100224 <!-- github-comment-id:3079178421 -->
adam commented 2026-10-05 03:18:49 +02:00
Author
Owner
Copy link
Copy source

Fixed in #212 by just checking the time between sends.

Fixed in #212 by just checking the time between sends. <!-- github-comment-id:3130824768 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/contact#65