Cynics and the interested invited to nail down what, why and how Branch is good.
I'd like to thank everyone for participating and please note there are some side branches which are still going. Good night and good luck.
Cynics and the interested invited to nail down what, why and how Branch is good.
Stewart Curry
✖
David
✖
Oisín Hurley
✖
Bou
✖
Nate VanderEnde
✖
Toby DiPasquale
✖
Jake von Slatt
✖
Jason Connery
✖
Charlie Joslin
✖
Raheel Ahmad
✖
Kevin Dangoor
✖
Mfk
✖
Jonathan Poma
✖
Yes, the moderation of users is the key. A bit elitist but if done well can lead to quality discussions (one hopes.)
We tried Branch a month ago for a @storyful discussion but critically we kept the list of people internal and this led to an uninspired wank session.
I think you need opposing viewpoints for a good discussion. Much like a formal debate.
I reckoned I was immune to new "social networks" however now I am using both app.net and branch. I like app.net because it is a nice experiment, and a potentially worthy one. *This* is more interesting because of the branching nature - I like having a traceable origin of a thing and I like being able to go off on a tangent (cough) from a thing too. It strikes me as a thing one can replace comments on one's blog -- "start a branch on this article", "join the branch on this article".
BTW - thanks Paul :)
Yeah, I've been thinking about it from the perspective of my website. The problem would be though the invite only nature of Branch. But, I guess you could create a link to the Branch and people can then ask to join. Now, if there was a way for a Branch to automatically get created for each new post on your site, that could be very cool...
Oh that is interesting. Not to view Branch as a bunch of isolated discussions but as a web of conversations without the usual noise. I've felt tentative starting new discussions, because of the invite overhead, but if you treat it more casually, while keeping the invite quality high, it could (forgive me) go viral.
I'm envisioning a twisty at the end of a post title that would open a panel listing the branches that are discussing the post, accompanied by a + to start a branch yourself.
Once you are in branchland, then the prime brancher can add new buddies.
Consider the usefulness of having a number of branches hooked to a post or article - one branch could be a critique of the authors naive semiotic ontology, and yet another may consist of "that's what she said" quips. You get both bread AND circuses. +1
Well I wasn't going to do any management at all - to hell with comments, frankly, but if people want to discuss a post, then a branch I think is a good place to do it. I think when I say "you" in the previous item, I'm referring to the commenter, or someone who has something to say, rather than the author.
As branch setter upper the commenter gets to choose people who might be interesting to have in the branch. Many of the "your ma" types will enlist other "your ma" types. And decent branches can lead to further articles.
But I generally wouldn't respond to comments unless they are regarding missing attributions, code updates, etc, i.e. substantive diffs rather than opinion.
What happens if you try the bookmarklet?
javascript:(function()%7Bwindow.__branchHost__%3D%27http:
I find with twitter conversations you are at the mercy of a good clients conversation support. This might be a good place to jump out to. Plus, probably easier to retrieve.
Also, nice that it's not like a full on forum registration or something you need to go through just to take part in a single thread.
If there was a way to start a private conversation that is not visible on the internet, to discuss a topic, it could then be taken public later and people who participate could still follow the line of arguments etc.
The reason for privacy first might be to brainstorm first a fully unstructured problem or question that is relevant to only a few people to something that is more of a half-structured but more focused problem relevant to many.
There's been similar questions asked about the (recently fully funded) app dot net. I love the fact that new services offer new choices and while there are similarities to other platforms I'm hoping that the differences begin to shine. I've been reading other conversations on Branch all morning and it seems to be a much simpler proposition than G+. Plus a timely opportunity to get out of my usual echo chambers. Thanks for the invite.
Every time something new comes along in the social media world I immediately start thinking of ways to use it in education. I assume this is because the last 17 years of my life have been consumed by school.
So what could Branch be good for? At the high school level, teachers can use it as homework. They post a question, article, video, etc and tell the students they have to have a discussion (details can adapt to topic/size of class/etc).
Students can start discussions with each other (either required for class or just to help each other study).
At the college level, professors can require that students create a branch on a relevant topic and invite industry experts to comment and add to the discussion.
One way to use Branch would be to present results from a survey you have done and invite people to jointly interpret the results using a true dialog approach rather than just a commenting approach.
So Branch would be good to for the synthesizing process of various inputs. You could have a discussion phase where you offer very different points of views, including opposing views and then you could agree to have a synthesizing phase where you design an output where you build on the various points of views.
I like the education ideas by Charlie. It is a great way to ask people for ideas to improve. Asking people what we are doing wrong is less useful in my view than asking people what they would like to see instead and why. We are overtrained in pointing out defects, and need to be actively focused on design and ideas for solutions. Branch would be great for that.
I really like the visual separation of the various tangents of the conversation. A single timeline or even a tree-like structure a la Wave is too cluttered to really follow the various topics proffered. Seems like it might be slightly tilted towards a question/answer format but it doesn't seem so bad as to be useful *only* for that. I'd really like to see the ability to play around with the structure of the trunk and the branches: highlight some, subdue others, perhaps some sort of history rewriting a la git?
The notion of inviting people to a conversation reminds me of panel discussions. As long as the panel is the *right* collection of people, the discussion can be very interesting indeed (even as a spectator).
If you're into web development, I'd bet the following panels would be interesting to you:
panelpicker.sxsw.com
panelpicker.sxsw.com
but not everyone can be at SXSW (though they may try).
I think kevin is pretty much on point here. i really believe that the concept of invitations may be the most vital, most unique piece of branch.com
invitations given by participants to "outsiders" creates an interesting social contract for both parties.
for the contributor sending the invitation to a branch, the entire community can see who added a new contributor. this keeps contributors accountable to other contributors for the quality of the individual they bring into the fold.
for the individual invited to the conversation, the social contract inherently encourages them 1) to contribute and 2) to contribute meaningfully.
-----
each branch then, takes on its own culture of contribution and is perpetuated by participation.
brilliant
Building on Jonathan's point, if you receive a request from someone to join the conversation and you refuse it, what will be the consequences? Will this person start a branch and complain about an elitist approach by another branch? For example, a discussion about the Republican vs Democrat presidential programs or campaigns, may lead to opposing branches when requests to join are rejected.
How will people view rejection when they are excluded from joining a conversation? Will hire hackers to bring Branch down?
I wonder who decided on the limit of 750 characters and why? What are the criteria for 750? Why not a 1,000. I, for one, would be happy to have unlimited or let's say 5,000 characters and I would be willing to pay for it e.g. $ 3 a month. I would also be willing to pay for the ability to have private conversations.
Not sure panelists would want 5000 character posts, either writing or reading them. You want back and forth discussion with a bit more space than 140c on Twitter.
Private branches sound like a good idea though what real practical use would you have of them over other private chat rooms? Would it be you start private with the intention of it going public?
So...re: @paul's comment about this thread getting long and about points being worth branching off into new points. i just tried to take @bou's latest comment into a new branch and was informed that, because i was added by a user to this branch but did not receive a "formal invitation" i could not branch the conversations.
i get the quality control measure, but it leads to exactly what this has become -- a somewhat disjointed conversation that's beginning to feel more like a comment thread.
it'd be nice if any contributor to this branch could take another's point and create a new branch out of it.
@paul - i'm with ya. manageable growth is important for them here...in day 2 of the public beta :)
that said, extending branches i can see really meeting two diferent use cases:
1) a post in the existing branch sparks an entirely new conversation, and that is branched out and grows
2) somewhat like [cough] facebook's newsfeed where a "branch" might just be a one-off comment on a post within the existing branch that a user decides to post in a branch to avoid interrupting the thread with a one-off comment
(this post is kind of a one-off comment that's interrupting the branch...)
.@pomajp Yeah. I'm not going to have any idea if I will like Branch until I can create my own and then it will depend on whether or not it's compelling to the folks that I want to have the conversation with. The most important part of social media to me is whether or not the people I want to talk to can be easily enticed onto it.
I think there are two interesting conversations to be had:
1. What about rejecting a request to join (see above)
2. The conversation starter can end the conversation any time. That gives him/her power - albeit somewhat limited, because somebody else can decide to branch off and restart. But it sends an interesting signal if the originator of the conversation says: I close this down.
I'd like to thank everyone for participating and please note there are some side branches which are still going. Good night and good luck.
Thanks for your feedback! Team Branch
Please refresh the page and try again.