Hey @bonnell, thanks for your answer.
Here’s a simple example:
I have a strong need for a custom Tweet View.
Entities like hashtags, user mentions, urls, or even media (which are in fact part of content for some TWTRTweet), should be sort of highlighted or able to receive some action inside of this custom tweet view.
I’m trying to avoid manual parsing and recognition of these entities because of 2 reasons:
- It’s not in the interest of very good performance and it’s easy to have some edge case parsing errors
- This data is already there, correctly parsed by Twitter, returned by REST API in JSON, saved in TwitterKit (but unfortunately it’s private).
If this data was just public, it would open a lot of possibilities, possibly new ideas, or at least simplify and increase quality of some processes for developers that are using TwitterKit.
Thank you for sharing this internally.