Change Details

The TCL Twitter client code wrote during the last update to compute the amount of characters use the Twitter API to determine the maximal, but cache the value. We need to document the process to update the value somewhere in the documentation (and do it).

The TCL Twitter client code wrote during the last update to compute the amount of characters use the Twitter API to determine the maximal, but cache the value. We need to document the process to update the value somewhere in the documentation (and do it). **Twitter documentation refresh** When this bug was initially filed, Twitter documentation wasn't clear. https://developer.twitter.com/en/docs/counting-characters offers a len of 280. Let's call the unit of this count twitter-point. | **Type** | **Value** | | ASCII | 1 twitter-point | | Emoji | 2 twitter-points | We can test code against https://github.com/twitter/twitter-text/blob/master/conformance/validate.yml

The TCL Twitter client code wrote during the last update to compute the amount of characters use the Twitter API to determine the maximal, but cache the value. We need to document the process to update the value somewhere in the documentation (and do it). **Twitter documentation refresh** When this bug was initially filed, Twitter documentation wasn't clear. https://developer.twitter.com/en/docs/counting-characters offers a len of 280. Let's call the unit of this count twitter-point. | **Type** | **Value** | | ASCII | 1 twitter-point | | Emoji | 2 twitter-points | We can test code against https://github.com/twitter/twitter-text/blob/master/conformance/validate.yml