3 ms·
> and can have premium subscription features prominently featured. The former could have been rolled into the API, but the latter would have been basically impo
by masklinn 4y ago
> 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.
- smith7018 4y ago> Twitter could have made the validity of these certs / keys conditional on subscription integration. With what staff?
- kemayo 4y agoOh, 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.
- masklinn 4y ago> 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. So did I. No feature no key, no key no third party client.
- kemayo 4y agoSorry, I misinterpreted you -- I thought you were talking about gating features to specific clients. :D