Twikit reply isn't displayed as reply, while reply made in X is

[vicmortelmans]

Hi,

This reply is made with Twikit: https://x.com/sedcontraest/status/1838974207629140146 (*)
This reply is made in X: https://x.com/sedcontraest/status/1838975330226233710

If I look at the original post, it shows that 2 replies are made, but only the reply made in X is displayed:

https://x.com/vicmortelmans/status/1838942074005062104

How can it be that two replies are handled differently?

This is the line where I make the reply:

        response = await sedcontraest_twikit_client.create_tweet(text=reply, reply_to=tweet.id)

(*) the twikit reply contains the OP twitter handle, I thought it might improve visibility, but I tested also without the handle and it's just the same...

[CoderMike1]

same problem here

[AritzUMA]

I have the same problem to since the last update

[vicmortelmans]

It's getting worse. The last reply I made using Twikit got mysteriously deleted. Twikit returned the tweet id and no errors, but the reply isn't visible even on my own account and when I put the id in an url, it says the post has been deleted:

https://x.com/sedcontraest/status/1841176266319212809

X is on to me?

[AritzUMA]

I have the same problem weeks ago, is not you.

[trillox9]

It's getting worse. The last reply I made using Twikit got mysteriously deleted. Twikit returned the tweet id and no errors, but the reply isn't visible even on my own account and when I put the id in an url, it says the post has been deleted:

https://x.com/sedcontraest/status/1841176266319212809

X is on to me?

I have the same problem weeks ago, is not you.

Have you found a solution? I’m experiencing the same problem: tweets made with the bot are only visible to the account set up in the bot. They’re not visible to other accounts. The account hasn’t been shadowbanned, because if I tweet manually, I can see the tweet with other accounts as well.

[vicmortelmans]

No, I've put my project on hold waiting for a solution... Best regards, Vic Oct 21, 2024 10:17:53 trillox9 ***@***.***>:

…

It's getting worse. The last reply I made using Twikit got mysteriously deleted. Twikit returned the tweet id and no errors, but the reply isn't visible even on my own account and when I put the id in an url, it says the post has been deleted: https://x.com/sedcontraest/status/1841176266319212809 X is on to me? I have the same problem weeks ago, is not you. Have you found a solution? I’m experiencing the same problem: tweets made with the bot are only visible to the account set up in the bot. They’re not visible to other accounts. The account hasn’t been shadowbanned, because if I tweet manually, I can see the tweet with other accounts as well. — Reply to this email directly, view it on GitHub[#223 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AABHZDEVXEW2TXWQH5OOQXDZ4S2CXAVCNFSM6AAAAABO27T5POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRVHE2DONRUGY]. You are receiving this because you authored the thread.

[trillox9]

No, I've put my project on hold waiting for a solution... Best regards, Vic Oct 21, 2024 10:17:53 trillox9 @.***>:
…
It's getting worse. The last reply I made using Twikit got mysteriously deleted. Twikit returned the tweet id and no errors, but the reply isn't visible even on my own account and when I put the id in an url, it says the post has been deleted: https://x.com/sedcontraest/status/1841176266319212809 X is on to me? I have the same problem weeks ago, is not you. Have you found a solution? I’m experiencing the same problem: tweets made with the bot are only visible to the account set up in the bot. They’re not visible to other accounts. The account hasn’t been shadowbanned, because if I tweet manually, I can see the tweet with other accounts as well. — Reply to this email directly, view it on GitHub[#223 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AABHZDEVXEW2TXWQH5OOQXDZ4S2CXAVCNFSM6AAAAABO27T5POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRVHE2DONRUGY]. You are receiving this because you authored the thread.

The developer should still be active; they released an update two weeks ago. They should consider this issue, as without the ability to tweet, the application loses 50% of its functionality.