Scott, I agree with you that it could do a better job of providing context as it gives almost none at all. Occasionally I'll cut and paste something more descriptive, but that's just a stopgap. I've noted similar things in the past: https:/
A possibly better version might be a mashup of Known's "Share" funcitonality, but with the proper markup for likes and reposts, but this would take a bit of reconfiguration which I haven't had the itch to fix just yet. My general value on likes and reposts like these is fairly low and if I want to keep more context I use other methods, particularly if I want to keep more context for my personal site search in the future.
In particular, for things like these, I'm a big fan of having the actual blockquote of tweets using their javascript for display, that way if Twitter were to fail one day, I'll still have the physical content even if I loose the display portion.
Chris, thanks for the reply. I agree with you on the blockquote idea. The twitter embed isn't searchable and, like you said, if Twitter were to go away it would be pretty useless. I actually do it that way on my Wordpress side. Right now on my Known instance Likes are borderline. I mean at least they show something. But if someone were to look at the site they would have know idea what I "liked". Retweets are even worse. For whatever reason, they don't show any text at all. Super annoying and I can't figure it out. They don't look that way on your site or Kevin Marks. See http:/ / stream.techlifeweb.com/ 2017/ repost-of-jase-tomios-tweet-0c016042bb. It shows nothing. If I hit edit the info is there but is isn't present in the read UI.
Scott Kingery, Feb 09 2017 on stream.techlifeweb.com