Telegram | Telegram for Android source | Bot library

Try to install the corresponding type declarations by running the command npm i @types/faker

I couldn't find a way to view metrics in Heroku's free tier but found an alternative which is Render.com. At the time of writing this render.com allows users' to view metrics in their free tier.

You could use global variable to control when it can translate and when it can't do it - ie, paused. And use message /start to set it False, and /end to set it True.

Not tested code - I'm not sure if module runs all in one thread
(multiprocessing would need to keep it in file or database).

Code needs also to check user ID so only admin could do this.

This has to do with struct padding.

Generally speaking, members of a struct start at an offset which is a multiple of that member's size for alignment purposes. Because of this, there are 4 padding bytes between the stat and latitude members so that the latter can reside at an offset that is a multiple of 8. That means the struct is 4 bytes larger than you think it is.

If you're able to, you should rearrange the members so that they align at a natural offset so that there is no padding between the members (although there may still be padding at the end).

If that's not an option, you can pack the struct using a compiler-specific attribute. If you're using gcc, you would do the following:

As your Bot already is an Admin of the channel you want it to post in, you just need to change the chat_id for Bot.send_message() to the one of the channel the bot is meant to send posts in.

You can obtain this ID for example by using Bgram Telegram client or IDBot.

Hope it helps ;)

TdLib is what you looking for!

TDLib (Telegram Database Library) is a cross-platform, fully functional Telegram client. We designed it to help third-party developers create their own custom apps using the Telegram platform.

TdLib supports multiple languages and has a JSON interface for other languages. So don't worry about your programming language.

It even abstracts whether the internet is connected or not, downloads multiple files based on priority, and so on. I strongly suggest you use TdLib.

https://core.telegram.org/tdlib

https://github.com/tdlib/td

I would propose to take a look in the RateLimiter direction. Maybe it does not work as expected, depending on the number of requests your application does over time. From the Javadoc for Ratelimiter: "It is important to note that the number of permits requested never affects the throttling of the request itself ... but it affects the throttling of the next request. I.e., if an expensive task arrives at an idle RateLimiter, it will be granted immediately, but it is the next request that will experience extra throttling, thus paying for the cost of the expensive task." Also helpful might be this discussion: github or github

I could imaginge there is some throttling adding up or other effect in the RateLimiter, i would try to play around with it and make sure this thing really works the way you want. Alternatively, consider using Spring @Scheduled to read from your queue. You might want to spice it up using embedded JMS for further goodies (message persistence etc).

You need to realize that when you trigger that delay in a Lambda function, that instance of the function becomes suspended and will not handle another request. A Lambda function instance will not be sent another request until it returns a response. The Lambda function instance is effectively blocked, just watching its system clock waiting for the 2 minute delay to finish.

When you trigger another request while the first request is waiting for the delay, all you are doing is starting another instance, which is then also going to sit and wait for its own 2 minute delay to complete.

The way you've coded this Lambda function, each request is going to trigger a 2 minute delay and wait for that delay before it returns a response. And you are getting charged for each of those 2 minute delays, because you are still occupying AWS compute resources, although all they are doing is monitoring a system clock for 2 minutes.

I suggest having your Lambda function quickly push the message into an SQS delay queue and exit as soon as it has done that. Then have another Lambda function configured with the SQS queue as an event source, that takes the SQS message and does your delete.