Loading Profile...
Add Threaded Replies and Conversation Display
Replies to tweets are not threaded with the original tweet.
I’m disappointed
66
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
The best point from the company
-
This is now largely implemented in the update to 2.0b. We will continue to refine it but the core functionality is now there.
The company thinks
this is one of the best points
-
Inappropriate?We will be adding this back soon, but other aspects of our Twitter implementation are higher priority still. But we will get this aspect of Nambu back in place.
-
Inappropriate?Want to have the reply under each tweet back~
I really like this feature from last Nambu
This reply was created from a merged topic originally titled
Want to have the reply under each tweet back~.
I’m happy with Nambu
-
Inappropriate?beta version do not show reply twit on timeline. I think reply twit make me understand context of twit
This reply was created from a merged topic originally titled
show reply twit on each twit. -
Inappropriate?Pleeeease! Please please please! It is SUCH a pain to have to use "view on Twitter.com" to figure out what someone's replying to!
I’m frustrated
-
Inappropriate?I second the "please please please" -- it's impossible to follow any conversation or even @replies directed to me personally without this function. I can't think of any top Twitter client that *doesn't* implement either threaded conversations or some way of tracking the "in reply to" of others' @ tweets.
I’m frustrated
7 Comments Add a comment
This is one of the best points
-
Twitter needs to adding for this, to do it properly. You can currently only follow conversations between people you happen follow, and you consume a lot of your API allotment to do it. Frankly, the Twitter API sucks for this, and so we are no in rush to work on it yet. -
And yet, off the top of my head, Socialite, Tweetie, Tweetdeck, and Seesmic all manage to track conversations/replies without forcing you to view the tweet in a browser. So, how are they doing it, if it's impossible?
-
Well you are not really tracking conversations as they exist within Twitter, you are only tracking conversations as they exist between people you follow. You can get the original tweet you do not have in your timeline, but that is about it.
-
Okay, but first, most users ARE actually talking about trying to track conversations between people we follow. Second, Nambu doesn't offer ANY indication of what original post an @reply is in response to. In Tweetie or Socialite, for instance, you can click on the @reply and see the entire progression of several @ replies back and forth. You can, in fact, see the entire conversation, chronologically.
-
Nambu is still in private beta for a reason. Not sure why you keep comparing us to clients that been in development for years, which I would never be able to use anyway because they are really quite horrible for other reasons. We will get there, but it does not happen overnight.
-
I brought them up because you seemed to be saying that it wasn't possible to do. That's all. I like Nambu a lot, and even in beta it's closer to being my ideal twitter client than almost everything out there. I'm pushing for conversation tracking to be a strong consideration as development continues because that's one of my dealbreakers. And yes, I understand it takes time.
-
Unfortunately, Twitter does not provide API methods to do this properly, and with 150 API requests you exhaust them pretty quickly with this feature. We will be adding it, but still hoping Twitter adds a simple API method to grab the entire conversation in one request.
-
Inappropriate?Eric: you may want to implement this partially for the threads in the Nambu database only: first fetch all new tweets, then for each check if the related one is in the local db and create the thread graph from this. While not perfect, this is what most people are interested in.
I’m sad
1 person thinks
this is one of the best points
1 Comment Add a comment
This is one of the best points
-
I understand. Nowhere did I say that we will not do it.
-
Inappropriate?eric/ pbtweet shows conversation of each twit, it's vey helpful to understand context of twits. if API has limits, how about option to use or not
-
Inappropriate?Echofon too
-
Inappropriate?I'm still missing a conversation view, preferably similar to the one used in Tweetie. This would make it a lot easier to follow an ongoing conversation, especially when following a lot of people.
This reply was created from a merged topic originally titled
Add a Conversation View.
I’m confident
-
Inappropriate?Nambu is great and allows me to keep my Twitter "stuff" all nice and organized, I don't think I am in the market to switch anytime soon. One feature that I would like to see added is the ability to view a person's timeline or our tweet histories/conversations within Nambu, rather than having to go to the Twitter website. The beta of Echofon does this quite well, by opening up a drawer after you click on a username on a tweet. The strength of Nambu is that it does Twitter well and doesn't add a lot of extra features or fluff (rss, facebook, etc) but this would add another way to manage and view tweets from within a single application.
This reply was created from a merged topic originally titled
Managing conversations (feature request).
I’m happy to be part of the beta process and hopeful to see what happens in the future!
-
Inappropriate?Threaded replies - "No rush to work on it"? But this was so cool in the old version - bring it back!
I’m frustrated
1 Comment Add a comment
This is one of the best points
-
Only because the Twitter API does not really support this properly, and it eats up your API limit pretty quickly if we starting pulling in lots of individual tweets. But we will be doing it soon since it seems everyone wants it regardless of the fact the conversations you are get currently are not complete and the feature slows down regular timeline refreshes.
-
Inappropriate?as conversations will be between people you already know surely you can just cache the tweets and their id's. If that won't work can you at least add in a button on each tweet to show the tweet that was being replied to?
I’m hopeful
1 Comment Add a comment
This is one of the best points
-
Caching is not really the issue. Most conversations you review will be new ones. We will be adding an icon to a tweet when a conversation is applicable, yes, and adding this feature soon, after auto-complete, which we are working on now.
-
Inappropriate?It's the lack of this one feature that's keeping me using Nambu 1 most of the time (in 10.5). In all other respects, the beta is now a nice improvement over the original ... but without knowing the context of a reply, it's really difficult to use on a regular basis.
-
Inappropriate?I used Nambu 1 till it stopped working a few months ago.
Nambu 1 was the app that made me like Twitter. I was so totally confused by what seemed like random tweets till I saw the threaded conversations and understood the discussions underway.
Then I upgraded from Leopard to SL 10.6.2. I was thrilled to see that as of today, Nambu 2 had gone public. I am disappointed though to see that the threaded tweets feature is missing. I will go back to using Lounge but as soon as Nambu has the threaded feature back, I'm jumping ship and will use exclusively Nambu once again!
Thank you for the great work, guys!1 Comment Add a comment
This is one of the best points
-
Threaded replies and conversations are there, but done a little differently. If a tweet is reply you can click the in reply... link to see the tweet replied to or follow a conversation if there is one.
-
Inappropriate?This is now largely implemented in the update to 2.0b. We will continue to refine it but the core functionality is now there.
The company thinks
this is one of the best points
3 Comments Add a comment
This is one of the best points
-
Hmmm Well I just can't see it in this version and the new way this feature is implemented. When I click on the @"username" in the reply, it opens up a Safari tab that takes me to the @"username" Twitter page and not even to the replied tweet. So this is confusing still. :-)
It could be I don't know how to set it up properly in the prefs. Maybe you should post a tutorial to see how to do this correctly? Or at the very least what the threaded discussions now look like. I might be dumb but I just don't see it. -
MacHeadCase
you have 2 choices... you can select the dessired twitt and press the "r" key it open a new box with the original message..
By the second choice you can click on the text "in reply to" and it makes the same option
Once you have open a box with the 2 messages (the original and the reply) you can see an arrow apponting to the right of your monitor... It appears when the message it's a reply to a conversation with more than 2 twitts... If you click on it arrow, you can see the complete conversation..
Maybe too later I can post any images to have a best idea.... -
Ok "r" works partially for me, thanks for this! It works only for my tweets being replied to, I wish it would be for all tweets across the board.
I don't see the "in reply to" though and can only see arrows on the right hand-side for ReTweets, unless I misunderstand your post. Screenshots would indeed help!
But it would be nice to set it in prefs for all conversations instead of only one selected at a time. In Lounge.app, you can view horizontally the conversations so seeing threaded conversations doesn't take up much window real estate. -
Inappropriate?Ok I finally understand how this works now! Got a reply from Peter Rhodes in this thread
http://feedback.nambu.com/nambu/topic...
and can see how this works now! Thank you to all of you for the help. -
Inappropriate?Well I still don't know how it works. Clicking 'r' does nothing at all. Command-R gives me a reply box. And there are no words saying "in reply to.." next to the username.
I'm just trying Nambu again for the first time in months, and I still find it seriously lacking. Tweetie has faults too, but at least I can find threaded replies in there.1 Comment Add a comment
This is one of the best points
-
If 'r' does not work, then the replier did not use the "reply" function that creates a 'In-Reply-To:' header. You may check that thread on twitter.com and see if it has a "In reply to ..." text attached.
Otherwise Alt-R shows the whole thread -
Inappropriate?To pilhuhn: Thanks for answering that. To Mr. Miller: It works as intended. If you do not like it, then for sure you should use something else. I personally do not see the point of presenting links to conversations that do not exist. In the official Twitter application for OS X you end up clicking to see "conversations" only to see one tweet, over and over again. If you like that, there is not much we can do for you.
-
Inappropriate?Ah, I have finally understood. I was using the non-beta version of Nambu on my laptop. Now that I'm on my desktop, I see that the beta version has all the "reply to" things and other good things.
When will this version be available widely? I'd like the new version of Nambu on my laptop as well.
1 Comment Add a comment
This is one of the best points
-
You can download the latest versions on the website anytime. http://nambu.com. There are no longer any private versions. Sorry, I assumed you were running the latest public versions.
-
Inappropriate?I think it *is* possible to also show conversations with others, and I think tweetie does this.
You should be able to use the in_reply_to_user_id or in_reply_to_screen_name fields, then get the last X tweets from that person, and merge them in the graph. IE there's no need to do a separate API request for each "in reply to" message. It should even be possible to show conversation between more than 2 people this way.
Ofcourse when the in_reply_to tweet is already cached locally, there's no need to do any calls -
Inappropriate?So, I just found out there's more than the initial reply when you hit the > button. Wasn't totally obvious at first. Thanks!
EMPLOYEE
