510 karma · joined August 29, 2011
https://twitter.com/ptr/status/696025411898085376
read the timelines ... very interesting.
the first is from a Twitter iOS dev, the second a former TL PM.
> Given how much the best users of twitter hate the idea of a 10k char limit for tweets, it will definitely happen. :(
So as long as it's going to do it, can I request that it support Markdown? Medium doesn't really support it other than through an API.
UX is something many businesses seem to really struggle with. If unnecessary friction is added, it really should cause stakeholders and designers to pause. The "read more" CTA will lead to more truncated tweets within the first 140 chars, something that is visually unappealing and breaks the reading experience by forcing a manual action. The workarounds you describe are not used by everyone and I'd wager that most users simply keep their posts within the 140 char limit rather than pict-tweet or storm a longer convo. Yes it forces brevity, but that is the Twitter identity which supports the product's skimmability usefulness. Give users a read more option, and many will post a few extra chars just because they don't have to put much thought into their wording now. Short term: usage goes up. Long term: quality decreases as Twitter becomes just another Facebook or Medium. It will be worse than Medium though because the audience Twitter is going after is more generic.
I've always argued that Twitter's userbase is more influential and valuable because of its forced brevity and fact that it was unique.
I already avoid truncated tweets and want to read long-form content elsewhere. So, I won't be using Twitter more. Maybe others will, but again, I'd wager that Twitter is simply sliding down a path that will be ultimately more harmful for its long term sustainability.
Would much rather hear a firm statement that they are keeping reverse chronological tweets and 140 char limits because that is their identity.