> and can have premium subscription features prominently featured. The former could have been rolled into the API, but the latter would have been basically impossible.
Not so, clients have exclusive keys (whose supply has been highly restricted since they were introduced a few years ago, making gaining any sort of grounds with new clients a challenge).
Twitter could have made the validity of these certs / keys conditional on subscription integration.
Oh, I didn't mean letting the clients support them, I meant making the clients support them and feature them how Twitter wanted them to.
E.g. if they wanted to change the notifications defaults everywhere to showing the "verified" notifications first, as a way to promote sales of Twitter Blue... good luck getting the third party clients to go along with that without some serious coercive micromanagement.
Not so, clients have exclusive keys (whose supply has been highly restricted since they were introduced a few years ago, making gaining any sort of grounds with new clients a challenge).
Twitter could have made the validity of these certs / keys conditional on subscription integration.