Which, to me, is the disappointing thing about the new character limit: it does nothing to address this emerging usage pattern, one might even say emerging form of communication, of the tweetstorm.
It seems pretty clear that tweetstorms enable a certain mode of marshaling thoughts and communicating them in an off-the-cuff way that blogging services never identified or understood. And yet Twitter's product org doesn’t seem to understand it either.
On the contrary, it's harder to navigate because it is intermingled with all sorts of boxes, whitespace, tags, icons and hidden menus. Everything is hair-triggered by a touch making the whole page unstable. Tweetstorms fork into secondary threads that are hard to follow, unlike HN or reddit, and use 3 screens for content that fits on half a screen.
https://www.reddit.com/r/programming/comments/7bekig/an_inte...
Thus we only get a single linear reading, and it wastes space by being presented as a floating "windows" above the main page.
Never mind that it is damn hard to see the full image, as no amount of clicking will actually make it fill the whole screen. Only bringing up the tweet "window" and then right clicking the image gets anywhere close.
Please see my responses inline
> can we make the page do this
yes np
> Does the flux capacitor have enough jiggawatts to make this work?
It does if we don't add anything new
> etc
[1]: https://www.theverge.com/2017/9/10/16284526/twitter-experime...
After all, the start of Twitter was as a sms relay.