Benjamin Cowen | Personal

With #BTC dominance at 60%, my maxi hat has been removed. But with QT continuing and ALT/BTC pairs still off their historic lows, it makes sense to be open to dominance going higher into EOY. I honestly don't really care if it does or not at this point, but I also don't just want to leave people hanging on this view either. Last cycle dominance topped when QT ended, and so there always remains a chance that the same thing happens again. Normally BTC dominance goes down in post-halving years. The implication of this would be that QT ends in December (at the last FOMC of the year). Would probably need a catalyst for the Fed to end QT with markets continuing to put in new all time highs.

Still a decent chance that #ALT / #BTC pairs go to the range lows. They really are not that far away. In fact, In Nov. 2020, they went from the current levels to the range lows in only about a month. With #BTC dominance at 60% it can already make sense to diversify as not all #ALTs have to bottom against BTC at the same time. If you are new to the cryptoverse, please understand that ALT/BTC pairs are not the same as ALT/USD pairs.

Dear @engineering @elonmusk @Support @X I would like to make a suggestion for implementing the following missing API functionality. The use case: There are many crypto/finance related X accounts that have 30 to 400+(in rare cases) impersonators. They are highly aware of that issue, receiving messages from people that got scammed by the impersonator accounts. But the volume is simply too much for them to manually stay on top of the reporting, to do something about it. Resulting in them realistically not making any reports. What is missing: There currently is no API endpoint for making violation reports, other than Spam. Any other violation is not possible to report by API, and can only be done by web/app users, manually. Which takes people about 15seconds per report. What do we need: A new endpoint to be able to report one or a bulk of accounts, for impersonating 1 specific account. The single endpoint should accept a twitter_id for the account being impersonated, and the twitter_id of the impersonator. The bulk endpoint should accept a twitter_id for the account being impersonated, and a list(dictionary) with impersonator twitter_id's. Note: You could simply port the x.com/i/api/1.1/repo… endpoint with selective_choices "DeceptiveIdentitiesOption" being used on the website, to a V2 endpoint 🙏

#BTC is at $76k and still no one cares. Youtube views to these crypto youtube channels still running at 1/4th of what they were averaging in 2021