Prescriptive RTT erasure limits from #92 and #443 conflict with both EN §11.2.2.1 (and WCAG 2.2.1), and error prevention/correction in WCAG 3.3.6 (3.3.6 is AAA, so not in the EN)

Prescriptive RTT erasure limits (overly prescriptive, IMO) from issues #92 (closed) and #443 (closed) conflict with both "Timing Adjustable" EN §11.2.2.1 (and WCAG 2.2.1), and error prevention/correction in WCAG 3.3.6 (3.3.6 is AAA, so not in the EN)

For example, the new text requires an arbitrarily short enforcement of typo correction, limited to:

• the most recent 160 characters (25–30 words in English; possibly 100 or more words in Chinese) or
• 30 seconds since receipt time

I don't see these limit expectations as either necessary or desirable. Among other negative side effects, these new expectations would arbitrarily prevent critical typo correction from earlier text.

Pre-existing RTT implementations in iOS and Android do not have these limits, so adding them will remove existing functionality from others internationally, or force needless region-specific conditionals.

In addition to being arbitrarily prescriptive (and very, very short), these new limit proposals conflict with other EN and WCAG recommendations to allow enough time in EN §11.2.2.1 (and WCAG 2.2.1), and error prevention/correction in WCAG 3.3.6 (3.3.6 is AAA, so not in the EN)