Christina WarrenI miss quote tweeting the most. I rarely abused it and I think the argument it was primarily used for abuse both devalues the real value of why USERS invented the quote tweet to begin with and gives too much power to the so-called abuse that could be better solved with better abuse/block tools.
Paul Haddad 
@film_girl I really miss it too, I've tried to adapt to it, I really have but still miss it.
@paul users invented the RT/QT for a reason, you know?
Scott Perry@film_girl @paul I feel like sufficiently advanced link previews in the client could bridge a lot of this gap, even allowing "quoting" from off-network
@numist @film_girl honestly at that point its just playing silly games, hydrate the Post and add a option to Quote from the Boost button and call it a day.
At this point the only reason I haven't done it is because I have concerns of how to do it without causing a height changing timeline, which I try to avoid as much as possible.
@paul @film_girl Totally, but I'd argue silly games are good; they're how these things become real—like how Twinkle caused location tagging to become part of Twitter.
wrt height-changing do you mean because the cells would load previews asynchronously? Definitely seems like care would be needed to avoid weird scroll offset woe.
@numist @film_girl yes Twitter had an API that allowed you to load up to 100 Tweets at a time, that'd be really good for something like this as we could hydrate the Posts at load time and base layout, etc.. on that.
Here you can only load one post at a time by ID, which makes that kind of technique very problematic. What if there's 20 quotes in your timeline.
@paul @film_girl Oof, yeah. I guess you could add posts to the visible timeline as they become data-complete (batched into some time quanta) but even that is going to require thoughtful code—suddenly the silly game has gotten serious
@numist add to that, hey guess what there's no way to really 100% tell if a link is an actual link to a post or a link that just has a similar format.
@paul Well, previews don't have to be restricted to toots, as long as you can determine whether there are social card tags in the head then you're good (quote-tooting a tweet being the most obviously useful possibility).
Unless the site is too slow but in the incremental model you'd need heuristics on when to give up on a preview regardless.
@numist doing something like that, a direct request to the site, is problematic from the privacy standpoint. Right now everything goes from the client to the server and nowhere else (I mean obviously unless you tap on a link and open it SFVC).
@paul Yeah, appropriately enough it's also a thundering herd problem. CDNs solve this problem for static assets, feels like there's an opportunity for a preview caching service. Hmmmm…