> So your argument of mouse vs keyboard use doesn't even convince ME, an > avid keyboard user.
I like it how I'm supposed to be the one that's an "uninformed idiot", except for the fact that I actually use the Twitter website daily, and I can tell you that simply typing @name is faster than having to click a reply swoosh, especially since the website's text field is automatically focused when the page is loaded. Like I said, I *use* the reply swooshes *myself* because I like to get the accurate metadata, too! What part of "I understand the benefits, I just want the benefits of the old way as well" is hard to understand? > Instead you just want to add extra unnecessary metadata and then have > programmers try to guess what the original intention was. Thanks for completely misunderstanding what I'm trying to point out. Programmers need not do guesswork at all. Programmers can leave it up to the user to decide whether a tweet is a genuine reply or not, because the user is the best-equipped to figure this out. Users can use whether a reply was specifically linked by the twitterer or if it was automatically linked by Twitter, and they can use the text of the linked tweet to figure it out, too. > And what AI are they going to use to determine whether this extra > metadata or lack thereof means that this is an actualreply? They're > going to go whichever they prefer. *facepalm* There is no AI involved. The point is to equip the user with as much information as possible to determine the context of the tweet. Even approximate context is better than none. > Meaning that they are going to get a different result for > 'conversations' depending on whether they use Summize (which is going > to have to choose one method) or some other client. Yes, that's right, depending on whether the client or the app in particular is dependent upon extremely accurate twitter conversation links (like, for example, conversation-trackers like the now-defunct Quotably), or if they just want the user to be able to figure out more information about the topic in question (such as most Twitter clients). The only "different result" that will occur is that those who wish to use the approximate data will have longer conversations that may or may not be accurate. But they will be a complete superset of the shorter, exact conversations that use the exact in_reply_to data. Users can easily figure out when the approximate context is wrong in the course of scanning such data, far faster than any AI that I'm supposedly advocating for. > I'm just not convinced by it. Please provide a way to easily figure out which tweet this is in response to, given the new policy of Twitter to not auto-link manual replies: http://twitter.com/KuraFire/status/1176556069 . Until you do, I am unconvinced that *you* understand the complete exercise in *utter* frustration the new feature has caused in trying to follow some conversations.
