Currently system recognizes which user is which based off of GroupMe name, which is user-assigned and user-changable. Though the system also tries to keep track of name changes, these don't persist across session.
Better would be to 'understand' the unique user ID the GroupMe API sends on each message:
Currently system recognizes which user is which based off of GroupMe name, which is user-assigned and user-changable. Though the system also tries to keep track of name changes, these don't persist across session.
Better would be to 'understand' the unique user ID the GroupMe API sends on each message:
https://dev.groupme.com/tutorials/bots
Then work around the following mappings:
GroupMe ID to real name [permanent] GroupMe ID to GroupMe name [not permanent] GroupMe ID to SteamID [permanent] GroupMe ID to Dota2ID [permanent]