Thomas Soubrier

Adding my voice to this issue. Running a small instance on a 2 cores, 4GB of ram (T3a.medium on AWS), whenever I upload videos the CPU jumps to 100% use,...

Saw that earlier, it sucks... Just to confirm, if you get a paid access to the Twitter API, you theoretically still can use it as is right @robertoszek ? Providing...

I am seconding this feature request, not only from the network interruption POV but basically any crash that would happen after the `Posting tweets` stage has started. If there was...

Thanks @robertoszek for looking into this! I ran the bot using verbose - A LOT of things got printed. The DEBUG lines I got before the error are as follows:...

@robertoszek 1.2.1rc5 gives me the same error: Error log ```shell 1.2.1rc5 mastodon@ip-XXX:~/pleroma-bot$ ../.local/bin/pleroma-bot --forceDate problematic_user `^y6gB@@BBQA{, :fB@@@@@@BBBBBQgU" `f@@@@@@@@BBBBQgg80H~ H@@B@BB@BBBB#Qgg&0RNT z@@&B@BBBBBBQgg80RD6HK ;@@@QB@BBBB#Qgg&0RN6WqS q@@@@@BBBBQgg80RN6HAqSo _ _ z@@@@BBBB#Qg8&0RN6WqSUhr | | | | -H@@@@BBBBQQg80RD6HAqSKh(...

@robertoszek On another note, the very first time I tried to run the bot with that new user I got an additional WARNING before the error message, like so: WARNING...

Hi @robertoszek, ran with 1.2.1rc7 verbose, I can see your new debug statements as Error log ```shell DEBUG:urllib3.connectionpool:https://api.twitter.com:443 "GET /2/tweets/1542840797925900288?poll.fields=duration_minutes%2Cend_datetime%2Cid%2Coptions%2Cvoting_status&media.fields=duration_ms%2Cheight%2Cmedia_key%2Cpreview_image_url%2Ctype%2Curl%2Cwidth%2Cpublic_metrics%2Calt_text&expansions=attachments.poll_ids%2Cattachments.media_keys%2Cauthor_id%2Centities.mentions.username%2Cgeo.place_id%2Cin_reply_to_user_id%2Creferenced_tweets.id%2Creferenced_tweets.id.author_id&tweet.fields=attachments%2Cauthor_id%2Ccontext_annotations%2Cconversation_id%2Ccreated_at%2Centities%2Cgeo%2Cid%2Cin_reply_to_user_id%2Clang%2Cpublic_metrics%2Cpossibly_sensitive%2Creferenced_tweets%2Csource%2Ctext%2Cwithheld HTTP/1.1" 429 94 DEBUG:pleroma_bot:x-rate-limit-remaining: 0 x-rate-limit-reset: 1674358688 x-rate-limit-limit: 300 reset_time:...

@robertoszek I looked up into the rate limit issue that I was running into. ```shell DEBUG:urllib3.connectionpool:https://api.twitter.com:443 "GET /2/tweets/1542840797925900288?poll.fields=duration_minutes%2Cend_datetime%2Cid%2Coptions%2Cvoting_status&media.fields=duration_ms%2Cheight%2Cmedia_key%2Cpreview_image_url%2Ctype%2Curl%2Cwidth%2Cpublic_metrics%2Calt_text&expansions=attachments.poll_ids%2Cattachments.media_keys%2Cauthor_id%2Centities.mentions.username%2Cgeo.place_id%2Cin_reply_to_user_id%2Creferenced_tweets.id%2Creferenced_tweets.id.author_id&tweet.fields=attachments%2Cauthor_id%2Ccontext_annotations%2Cconversation_id%2Ccreated_at%2Centities%2Cgeo%2Cid%2Cin_reply_to_user_id%2Clang%2Cpublic_metrics%2Cpossibly_sensitive%2Creferenced_tweets%2Csource%2Ctext%2Cwithheld HTTP/1.1" 429 94 DEBUG:pleroma_bot:x-rate-limit-remaining: 0 x-rate-limit-reset: 1674358688 x-rate-limit-limit: 300 ``` Bringing the...

That would actually be fantastic if it could do that yeah. I'm assuming this was an already known issue, apologies for bothering you with that. I will post the results...

Ran the 1.2.1rc8 bot with the same settings, using my twitter_token in the config.yml. The bot behaved according to your comment above: Debug log ```shell DEBUG:urllib3.connectionpool:https://api.twitter.com:443 "GET /2/tweets/... HTTP/1.1" 429...