"User Bot" Deployment suggestions? about gramjs HOT 5 OPEN

Hey, I'll try to answer your questions to the best of my ability.

For deploying it doesn't really matter since any VPS that runs 24/7 and has an internet connection should be able to run it granted it has node >12. I've never dealt with GCP or AWS so I couldn't really help you with those.

You are correct you can't query members using the normal bot API.

This library doesn't only run users. it can also run normal bots that you create from @Botfather and those don't need a phone just a token.

Generated sessions can last forever granted you don't log them out from another device. ideally, you should never login more than once.

normal bots when used with this library can query member list using GetParticipants (you should use https://painor.gitbook.io/gramjs/getting-started/available-methods/getting-participants-of-a-group-channel)
for the rest, you can use Raw events and detect when a user was kicked or left. you can use the other library if you're more comfortable with it since Raw events in telegram are a bit hard to deal with.

from gramjs.

Thank you for responding so quickly! You saved me a ton of time & headaches!

I was assuming I had to use a "User Bot" in order to get the participants of a group. Now that I know I can use regular bot credentials it greatly simplifies things.

I am going to try to use this library in conjunction with npm "node-telegram-bot-api". I really only need the ability to getParticipants() from this library. The other npm package has much nicer event handlers and support for webhooks which means I can deploy this on a simple express app in GCP App Engine which doesn't need to poll 24/7.

My only concern is that I will technically have 2 telegram clients connected at the same time using the same bot credentials. Could this be a potential problem or am I overthinking things?

Also is there a way to disable the long list of blue "Debugging" logs in the terminal? Not super important, but I don't know what any of it means so it's just clutter.

from gramjs.

the limit for the same telegram clients connecting at the same time is around 9 or 10. after that you won't be getting updates from some of them so you should be fine.

for logging check https://gram.js.org/faq#how-do-i-stop-logging

from gramjs.

Just curious, anyone trying running this within an AWS Lambda function ?

from gramjs.

Just curious, anyone trying running this within an AWS Lambda function?

not sure how that would work. to receive updates you'd need to have a connection open so that won't work in lambda as far as I know.

from gramjs.