Twitter shadow ban

Shadowban is a measure that Twitter's algorithms use to combat fraud. This year, the algorithms have been updated and the anti-fraud is in full force. In fact, when your messages go into requests, it means that the initial trust users have in you is low, and only 5% of them are likely to respond.

The message can be delivered directly to the mammoth (user's) private messages, or it can end up in queries. Twitter's algorithms decide where your message goes. If it ends up in queries, the reason for this could be a nerfed IP address, so using a foreign dedicated server with ded.im is recommended; using key phrases such as "Please open this file" or "Password for the archive", which are considered signs of fraud; or using low-quality bots to gain followers.

The solution to the problem of subscriber baiting can be easy and clever. You can use "reciprocal subscriptions" search and subscribe to different users using different queries. This will get you more than 100 live and active subscribers per day.

Hence, your posts will not get hit by queries when you use this strategy.
If a user has once sent a complaint about your post, chances are that a similar post with a similar structure will be automatically placed in the request folder by Twitter.

However, there is a solution to determine if your message is read, even if it has gotten into requests.

When a message gets into the requests folder, the user can open it, but if it is not accepted, the double checkmarks indicating it has been read will not appear.

To get around this limitation, you can attach an image to a message, and the user will have to accept the message to see the image. Otherwise, the image will not appear in the requests folder.