Account Suspension When Using Twikit Library on X (Twitter)

[karasungur]

Whenever I use the Twikit library, no matter which account I use it with, my X (Twitter) account gets suspended. Why is this happening? I’m only using it to fetch a user’s tweets and the users who retweeted them.

[pepo-ec]

Yes. The same thing happened to me, and the worst part is that it wasn't immediate; a day went by, and suddenly I have an email in each account. I mean, I used a development account, and since everything seemed fine, I moved it to production. Although the development account was notified after a day, the main account was suspended shortly after.

This was my code:

import asyncio
from twikit import Client

USERNAME = '---'
EMAIL = '---'
PASSWORD = '---'

client = Client('en-US')

async def main():
    await client.login(
        auth_info_1=USERNAME ,
        auth_info_2=EMAIL,
        password=PASSWORD
    )

    # Create tweet with media
    TWEET_TEXT = "My random text!"
    MEDIA_IDS = [
        await client.upload_media('/tmp/oculto.jpg'),
    ]

    result = await client.create_tweet(
        text=TWEET_TEXT, 
        media_ids=MEDIA_IDS
    )
    print(f"Resultado: {result.text}\n\n{result}")

asyncio.run(main())

[karasungur]

Yes. The same thing happened to me, and the worst part is that it wasn't immediate; a day went by, and suddenly I have an email in each account. I mean, I used a development account, and since everything seemed fine, I moved it to production. Although the development account was notified after a day, the main account was suspended shortly after.

This was my code:

import asyncio
from twikit import Client

USERNAME = '---'
EMAIL = '---'
PASSWORD = '---'

client = Client('en-US')

async def main():
    await client.login(
        auth_info_1=USERNAME ,
        auth_info_2=EMAIL,
        password=PASSWORD
    )

    # Create tweet with media
    TWEET_TEXT = "My random text!"
    MEDIA_IDS = [
        await client.upload_media('/tmp/oculto.jpg'),
    ]

    result = await client.create_tweet(
        text=TWEET_TEXT, 
        media_ids=MEDIA_IDS
    )
    print(f"Resultado: {result.text}\n\n{result}")

asyncio.run(main())

How long after you started using it did the suspension happen? Also, did you pay attention to Twitter API rate limits?

[alphaleadership]

for reading is not an issue

[giftedstan]

for anyone still getting account bans, here's what i noticed, whenever i login using twikit, thats when i get banned, but for any account that i manually extract the cookies from the browser, i dont get banned

[alphaleadership]

and you can get data but not tweet with banned account

[dannychirkov]

for anyone still getting account bans, here's what i noticed, whenever i login using twikit, thats when i get banned, but for any account that i manually extract the cookies from the browser, i dont get banned

Yeah bro, that's exactly how it is. If I remember correctly, twikit logs in for every action, so the system should work like this: a one-time login to save the cookies, then just logs and all actions through them.

[alphaleadership]

so you need to extract cookie with the same method than yt-dlp to get reed off that

[alphaleadership]

https://github.com/yt-dlp/yt-dlp/blob/master/yt_dlp/cookies.py

[giftedstan]

and you can get data but not tweet with banned account

no, i mean, i no longer get banned

[dannychirkov]

so you need to extract cookie with the same method than yt-dlp to get reed off that
https://github.com/yt-dlp/yt-dlp/blob/master/yt_dlp/cookies.py

You got the same functionality in twikit, no?

save_cookies

[giftedstan]

for anyone still getting account bans, here's what i noticed, whenever i login using twikit, thats when i get banned, but for any account that i manually extract the cookies from the browser, i dont get banned

Yeah bro, that's exactly how it is. If I remember correctly, twikit logs in for every action, so the system should work like this: a one-time login to save the cookies, then just logs and all actions through them.

not really my issue, like, my previous process was

log in with twikit,
save cookies
then for future sessions i use the cookies

but that always results in bans, so now i simply log in on my browser, manually copy the cookies, then use it in twikit

[alphaleadership]

so you need to extract cookie with the same method than yt-dlp to get reed off that
https://github.com/yt-dlp/yt-dlp/blob/master/yt_dlp/cookies.py

You got the same functionality in twikit, no?

save_cookies

no is not extracted from browser

[dannychirkov]

so you need to extract cookie with the same method than yt-dlp to get reed off that
https://github.com/yt-dlp/yt-dlp/blob/master/yt_dlp/cookies.py

You got the same functionality in twikit, no?
save_cookies

no is not extracted from browser

Exactly, I haven’t used it in a while. I just remembered that I used to extract cookies from the browser using the Cookie-Editor extension, and then converted them into the required format using a script by this guy.

https://github.com/ScarlettPPC/TweetAway/blob/main/cookieconvert.py

[cmj]

I don't have an issue with suspended accounts. Maybe 3 in the past year, but they're a drop in the bucket in the scheme of things. I tried the yt-dlp option just for curiosity's sake:
yt-dlp -u <user> -p <pass> --write-pages -v <url>

And that also failed, I think that hasn't been updated in a while.

I just updated an old proof-of-concept script that seems to work, but I won't know immediately if onboarding/login is the issue for suspensions.

https://github.com/cmj/twitter-tools/blob/main/auth/twitter-cookie.sh

I should add I just use them to scrape and for Nitter instances; don't do any writes to the site.

As previously mentioned, make sure you grab the cookie and then run scripts that call the cookie, otherwise you're doing a login every run and it will obviously be flagged.