Twitter's API policy hangs over the fate of two types of products One type is infofi One type is scraper robots, for example, when CZ sends a message, the robot automatically sends a meme, promotes it, and completes manual automatic scraper robots Scraper robots have been replaced with data scraping tools or crawlers during previous campaigns The pattern has been established. No longer relying on official APIs Can Infofi products be overused with the same technological means? Technically feasible, but I believe it will be difficult to implement in practice At present, the product community is crazily discussing this direction (such as using open-source scraper on GitHub, Claude agents to quickly build crawlers, or turning to third-party paid APIs), but the reality is At present, X's anti crawling measures have been upgraded to the abnormal level There is currently no publicly available tutorial that allows you to climb X bot and survive for one month. Therefore, the dominance of Bloom bot is absolute. But I still don't think Bloom's solution can withstand Kaito level API calls Although there are dedicated X scraper actors such as crapfly, Bright Data, Scrapingdog, Apify, SociaVault, etc However, according to the current infofi model, the long-term cost is enormous. Short term life extension is sufficient. Taking Kaito as an example, the advertising prices for a single project are all above 100000 units. Using this portion of revenue to rent paid third-party APIs and deliver current advertising tasks is feasible in terms of business logic and ethics. But it will greatly weaken Kaito's own profit margin in the long run I personally think that the mode of manually submitting the article link after the creator finishes writing the article is more feasible. In fact, I often didn't know I was on the list before and missed out on many airdrops. The airdrop that I did not receive was neither returned to the project team nor reissued to me. But it was a magnificent entry into Kaito's own pocket. I think it's meaningless.