Cryptocurrency donations for bots, groups and channels
Show a button for sending quick donations to maintainers of bots, groups or channels using cryptocurrency. This could use either an established cryptocurrency like Bitcoin, Etherium, EOS, etc. – or some…
> That's why you send "random" data and locally within your bot you map that "random" data to the actual commands (via a key-value store)
Work arround: Desing your bot to manage callback_data differently so that you never reach 64chars.
How do I make the hash persist from the point the callback button is clicked to after it is clicked? Do I store the hash inside my own database?
I would suggest you to enter the @BotTalk group and ask there for more info.
The callback_data just contains info on where to search in my database for the string after the callback_data is sent.
I encountered a new problem with this: When the user presses 2 different callback button on the same page in quick succession, this crashes the bot as the 2nd string overwrites the 1st string before the first callback_data gives command to search the database.
Will the hash map method u recommend meet the same problem given it also saves the data into own database before the callback? Any workaround to this issue?