The Gillmor Gang — Robert Scoble, Jason Calacanis, Michael Vizard, and Kevin Marks — track Google Chrome OS, Silverlight, and salesforce Chatter. Recorded live Wednesday, November 25, 2009.

The Gillmor Gang — Michael Arrington, JP Rangaswami, Robert Scoble, Kevin Marks, and Saul Hansell — take sides in the iDroid Wars. Recorded live Thursday, November 12, 2009.

The Gillmor Gang — Robert Scoble, Kevin Marks, Phil Windley, Chris Messina, and Craig Burton — convene Identity Gang ’09. Recorded live Thursday, November 5, 2009.

Full transcript coming soon, courtesy of Simulscribe.

The Gillmor Gang — Steve Gillmor, Robert Scoble, Kevin Marks, and Facebook’s Bret Taylor — on the 6 month developer roadmap. Recorded live Thursday, October 29, 2009.

Full transcript below the video, courtesy of Simulscribe.

Mr. STEVE GILLMOR: Hi. This is Steve Gillmor and this is The Gillmor Gang, welcome. Today, we’re going to be – yesterday actually we have an interesting time down at the new Facebook headquarters and there was some interesting announcements as Facebook slowly trudges toward overhauling their environment. And one of the first things that was announced was our guests elevation to an actual title and responsibilities. Welcome, Bret Taylor.

Mr. BRET TAYLOR (Director of Products, Facebook): Thanks for having me.

Mr. GILLMOR: So, what your job and…

Mr. TAYLOR: I’m the director of products for the Facebook platform. So, I work in product management here and currently managed the platform product specifically so that’s Facebook connect and the platform on Facebook.com, the canvass pages and other negotiating points of Facebook.com.

Mr. GILLMOR: OK. Also, we’ll get back to that in a second. Also joining us is the infamous Robert Scoble.

Mr. ROBERT SCOBLE: Hey, what’s up?

Mr. TAYLOR: Hello there.

Mr. SCOBLE: Hey. How you doing, Bret? Congrats.

Mr. TAYLOR: Thank you.

Mr. GILLMOR: And someone who is also at the event yesterday, Kevin Marks.

Mr. KEVIN MARKS (British Telecom): Hey, there.

Mr. TAYLOR: Hey, Kevin.

Mr. MARKS: Good to see you again, Bret.

Mr. GILLMOR: All right. So, getting back to what – what was announced yesterday. Can you sort of summarize it?

Mr. TAYLOR: Yeah. So we basically published a six month road map for our plans for the Facebook platform. Obviously, one of the complaints we have gotten from developers in the past that lots of businesses are filling their business on top of their platform. And they want to, you know, plan, you know, for the next six and 12 months for their businesses but they’re – they weren’t aware what changes we were going to make to our platform and that’s very difficult for them to do that plan in. So, we sort of heard of (unintelligible) internally to try to write out specifically what our plans are for the next six months so quite the most significant thing. The main – the central parts of the things we are changing were changing some of the communication channels available to developers on Facebook.com and we’re doing some UI revisions to Facebook.com that will talk(ph) Facebook apps. And then we announced a couple of new products in addition to stuff that we’re doing for developers like the open graph API.

Mr. GILLMOR: Well, the open graph API, I think is the most interesting part of this I think for not only developers but users. But before we go there, how much of the decisions or the process of starting to collapse a number of different channels as was put into one or three events, email or the inbox, the stream and I forgot what the third one was. How much of that were you involved with since you coming over from FriendFeed?

Mr. TAYLOR: I was fairly involved obviously. There were – are a lot of it was sort of a note(ph) when I got here and some of it, you know, I was involved with. I think the prospective that I brought was largely of an external developer. I was a developer on the platform until very recently. And the main prospective I brought was that I thought one of the things that the platform could most use it for me then is simplicity. A lot of competing platforms like FriendFeed and like Twitters were didn’t provide all the functionality of Facebook platform but also where a little easier for new developers to understands. And so, simple plan of details is something I’m very supportive of because I really do think as a new developer, the channels that are available, you mention the stream, the Facebook inbox and now we’re providing access to our email addresses as well. They’re really easy for new developers to understand so I think it’s going to lead to a much easier developer experience and a much better user experience in the end.

Mr. SCOBLE: But Brett does that new functionality give access to my friend’s email addresses?

Mr. TAYLOR: No, it got…

Mr. SCOBLE: So, could I – OK, because it let….

Mr. TAYLOR: Because it’s a much, much concrete and unlimited scope feature.

Mr. GILLMOR: Now, Robert you have to…

Mr. TAYLOR: Facebook connect site and you click connect and that dialog that says, you know, do you want to connect with this site? They’re well, if the developer asked, there will be a check box there that says do you want to also provide this connect site with your email address. And they only provide your email address, so that’s very clear at the time that you’re doing it, that this action is being taken. So, it’s not something that you’ll – you’ll be aware of it when it happens and it’s only your email address provides you one specific application.

Mr. SCOBLE. OK. So, you still can’t go to nap that would, you know, bring my email addresses of my friends into Outlook or into Gmail or something like that.

Mr. TAYLOR: Right now, that’s currently not possible. I think it’s something we’re really interested in. I think it’s possibly the most complex and most interesting part of our platform and other platforms like it. It’s – it turns out that I was talking a little bit to Kevin about this yesterday.

Mr. SCOBLE: Yeah, I see.

Mr. TAYLOR: Because a lot of users and…

Mr. SCOBLE: That’s an understatement.

Mr. TAYLOR: Yeah, as a – well, assumption is when I was – when thinking about infrastructure problems at Facebook and Google, problems that are – are insignificant for smaller companies are significant here. So, when you’re comparing, it’s only going to takes ten nanoseconds versus five nanoseconds. For most start ups, it’s like well, you’re measuring the nanoseconds so who cares, just choose whichever is most convenient. Well, you know, Facebook and Google, you multiply that by ten trillion because of the number of request per second you get and all of a sudden that becomes a significant technical decision. Well, I think with interface problems, the number and widely varying technical awareness of Facebook users, makes user interface problems that are similarly complex. So, you know, as much as I think it’s a worthwhile that you know if it would be nice if you could, you know, import your Facebook friend’s phone numbers into your phone provided that functionality also means that.

Mr. SCOBLE: Yeah.

Mr. TAYLOR: One of your friends who might not be so technically aware, might accidentally give up your phone number to a malicious application. And so, you know, we’re struggling with this like sort of somewhat conflicted desires to provide that functionality to developer will also protect our users from applications that, you know, are as and of or like are as well meaning as say, Gmail. And so, it’s something that I think we’re committed to in spirit but I don’t want to like understate the complexity of actually doing it. And I don’t think we really have like solutions for all those problems in our head and so right now I do think we’re making the correct decision, a sort of early on the side of protecting our user’s privacy. But it doesn’t – you were not committed to providing that in the future, we can figure out a way that like protects our user’s privacy in addition to providing the functionality to developers.

Mr. MARKS: So, I mean. The – I think there’s a bunch of interesting stuff there about understand that there are different classes of application and we had a little chat about it. Just say, it would be great to talk about it here. And you sort of hinted towards like yesterday but separating out the games from the rest of the apps but they still have the same privileges. But already, there are different kinds of applications that can ask for different kind of things. So, you’re using a client like seismic to log in to Facebook that can read my entire feed and posting, do a lot more. At the moment, I get four or five different old books because I have to go through to say yes, yes, yes, yes, yes. You can do that.

Mr. TAYLOR: Yeah.

Mr. MARKS: Whereas, conversely there are things about the ACL you quiz out that shows that even a simple quiz out can read that the – I and still can read all my friend’s political affiliations and things like that. So, there’s a sort of Facebook is basically up to now had this one size fixed old privacy modeled broadly. And I think…

Mr. TAYLOR: Yeah.

Mr. MARKS: I think, you probably now have enough applications to sort of do some interesting stats across that and say what all the different kinds of apps, what are the different classes of these and can we actually segment into something – some interest. Is that something you’re looking at?

Mr. TAYLOR: Absolutely. One of the things we’re actively working on internally is providing more granule or access control at the time that you connect with an application on the web or install an application on Facebook .com. And what – I think – that so we are actively working on that so that you can not authorize access to your friends’ data if you just wanted, you know, essentially log into a website but you’re committed to that particular aspect of the application or furthermore provide more access for applications you trust deeply. I think we’re working through right now. The user interface that use to associate with that, you know, the wrong way to do it is a dialog box with 28 check boxes of all the things you wanted private access too and there is a right way and we’re figuring out what that balance is. There are sort of pockets(ph) these tapes of privacy settings into something that I think can users, can understand well. But we’re actively working on it and as side effect to that project, we hope that we can reduce the number of dialog boxes to, you know, one or two or something very reasonable. I have experience the sequence of dialog boxes that you’re referring to and it’s a really bad user experience. So, we’re definitely working on fixing that.

Mr. MARKS: Right. We have something – well, there’s two aspects of this, something that we’ve found when we were doing the open idea about hybrid stuff which Facebook now calls and I think plateau(ph) and…

Mr. TAYLOR: Yeah.

Mr. MARKS: And whichever provides (unintelligible) writing on that. And they found that every option you added increase a number here and canceled out the whole thing because if you try to make a choice, they give up.

Mr. TAYLOR: Yeah.

Mr. MARKS: But conversely at the – you know the other effect I’ve seen with this and other situations is if you make people click two boxes on their way to something, they just click them anyway because with problem without even reading them because there’s a task they want to achieve and therefore work through that. So, I think there’s – we’re going to have to come up with some interesting, you know, it needs to be a one click thing to start with. One of the nice things about Owl(ph), and you know this is the way I push it to influence Owl thing, you say maybe. But is that you – because you’re giving away a token that knows what the act is and what the context you’ve asked for it in. And you can actually change its permissions over time.

Mr. TAYLOR: Yes.

Mr. MARKS: So that you’re given this half of token, you can later say actually now I don’t want that to have my email address or OK, I trust it now, it can have my email address, it can have my friend’s phone number or whatever and leave the permission because it’s not bound to a username and password log in. You haven’t given away the whole thing. I think that’s going to give us some more possibilities in the future. So, it may let us – and there’s a thing that Twitter apps do, a lot of them where you go to the Owl thing and they say we want the ability to tweet on your behalf and then if they send a tweet saying I just signed up with Twitter, I bet, so when you think you busted, I didn’t ask you to do that.

Mr. TAYLOR: So.

Mr. MARKS: And it would be nice if you could spot, you know, catch those before they go out. And you know, Facebook has that prominent space. There’s all kinds of, you know, battles that you’ve been having with some of the app developer as you – if behave that way.

Mr. TAYLOR: Yeah. Well, so first of all Facebook authorization is also revocable after the fact. So, there’s – either you click on your applications link on Facebook.com, you know, you can’t revoke any application that you know on there. I think supporting up is a good idea and I can only speak to like when or if we’ll do that but I think that like for factual purposes, Facebook’s authorization scheme and a lot, not pretty well to each other. And so, it’s not, you know, it wouldn’t be as huge technical fit to do so and it’s something that we’ve talked about that is, you know, the complexity of just moving from one system to another is very large. So, you know, I’m not sure whether we’ll do it but it’s something we’ve talked about. I think that I agree that I think that offer some possibilities and I do think basically you want to make it really easy to start using the application but you also want to make it clear to users, the consequences of their actions. I think there’s liking to hear it.

Mr. MARKS: Yeah.

Mr. TAYLOR: Between those things and set up – I think we’re as actively just going to iterate on this and I think that the dialog box where we – a user can provide their email address and application which I referred to earlier, that’s one place where we’ve done a few experiments already. And I think we reached a place so we can pretty reach sort of that happy middle grounds that we – initiate views on awareness. But you know, I think we’re iterating all these things. It’s only – only related to it.

Mr. GILLMOR: Jumping up to stack a little bit, you know, this is certainly of interest to developers but there are also implications of these changes for users and for entrepreneurs who are trying to volt on to the platform, not necessarily at the technical level but at the implications for competing with Twitter and so on and so can – if we characterized Facebook’s environment as a series of phases maybe starting with Beacon(ph) and then moving to connect and its early iterations will forget the first abort to attempt to have it. And then, you know perhaps so was the third phase in between then and now. But what do you see these phases representing this sort of a new pro level?

Mr. TAYLOR: So, one thing is that we are focusing a great deal more on Facebook connect. We want – I mean at a high level the Facebook platform is a platform for identity. It’s – I think especially with some of the changes we’re making with yesterday’s announcement, by far the best authentication and authorization system for website to use. Just a simple identity system and then on top of that identity system we want to provide services for distribution and share it and also for personalization. And so I think, you know, the first iteration of the Facebook platform was largely applications that run within Facebook.com and really interactively a Facebook profile as sort of a user interface level. I think in the future, our hope is that you sort of bring your Facebook identity with you around the web so that when you’re using sites like Yelp or Digg, you know, you’re – you can have it personalized based on your social network and you can also share your activity on that those sites back into Facebook so that your friends, you know, can sort of share that and make those sites like more social than they are today. As I think, that’s really one sort of a directional stage (unintelligible) is that we really are excited how – some echo back there.

Mr. GILLMOR: Yes. I think it’s just a bandwidth channel, just a second.

Mr. TAYLOR: Anyway, so I think we are really excited of about that in particular and overtime, appropriate that user – when they think that basically because of platform. They really think of it all over the web rather than something that exist within a canvas page on Facebook.com primarily. And so, that probably one of the more significant sort of strategic shows we were making. I’m not saying we are really – still focus on outrunning within Facebook.com, obviously, I think our big games got dash board(ph) which you reference earlier is like one – one clear way that we are trying to really promote the most popular names on Facebook.com. But I think that over the next year, one of my main metric for success is how many sites adopt connected. How many sites does adopting connect really fundamentally change our business and make their business work better.

Mr. GILLMOR: All right. So, that leads into the open graph API fairly directly.

Mr. TAYLOR: Yeah.

Mr. GILLMOR: Wouldn’t you say that this is going to be the – much in the same way that when Google opened the rest of the web to Googlist technologies with that sense that it really fundamentally change the platform. Don’t you think this is going to have the same effect?

Mr. TAYLOR: I hope so. I think that, as I said it is because this was a part of our six-month road map. I do think that it is not entirely, you know, concretely defined yet. So, you know, I think that there is a lot of the devils(ph) in the details in a lot of these things but I’m really excited about it. At a high level for the listeners, you haven’t heard much about it. The open graph API basically means that any page on the web can be a note in Facebook’s graph. And what that mean as you can go to any page on the web that’s enabled it and you can send that page and it will show up on your profile, just like a Facebook page does. It can published updates to your stream and it can sharpen search results if you’re searching for, you know, something name like that page and enough of your friends are connected to it, just like Facebook pages today. I’m really excited about it because I think that, you know, as we talk about Facebook and Facebook can act as really a platform for identify, having the things that you’re connect to even around the web rather than limit just on Facebook.com is completely in that spirit. And I think, its like offers are really exciting opportunity for developers to integrate with Facebook in a very lightweight way and still control your brand and your user experience.

Mr. GILLMOR: Robert. You were going to jump out.

Mr. SCOBLE: No. I’m excited that’s the future though.

Mr. GILLMOR: You know, that’s why I’m asking you too.

Mr. SCOBLE: Huffingtonpost is using Facebook connect in getting a lot of traffic and building a unique experience for their users.

Mr. TAYLOR: Yeah, it’s really – I think that’s really been also one of our focuses. I think we want to make it easier to adopt connect and also easier and it’s like author a clear path for connect, you know, really improving your business. I think they’re like, right now, you just put in the connect button on your site, isn’t going to like change your business overnight. So, one of the things we’re going to focus on is like providing a better templates for having a (unintelligible). So you get all the benefits of the distribution of virility and increase the, you know, sign operates and you know, decrease drop off as Kevin was referring to earlier. So, we have a lot of work to do there but I’m really excited about it because those partners who have implemented it and put some thought into that really seen a huge benefit from doing so.

Mr. MARKS: So, is the open graph API effect really going to let you read feeds from the rest of the web in Facebook? That seems to be what you are implying by saying, I can post off from the web into my feed.

Mr. TAYLOR: So, I can’t really say what it will or will not do because, I mean, we have some sketches…

Mr. MARKS: Is this (unintelligible) is?

Mr. TAYLOR: I don’t really want to, you know, it’s a little early to say what, you know, the specifics of what it will do. I will say though it’s less focus on feeds necessarily than identity. You know, I think that really, you know, the Facebook stream is about sharing and it’s a little more transient, you know. It’s like what’s going on right now and your profile is really about who you are and who you’re connected to. And I think that the one goal of the graph API is to really extend the identity component. We do provide tools for sites to share into the stream already and the graph API is sort of a parallel to that in the profile. It’s a way for you to like add, you know, stuff your profile and add connections that exists all around the web. So, for example, you know, you might be connected to a cause on causes, not sort of a more permanent connection that goes at your profile versus say, sharing a blog post from Scobleizer which is, you know, something that goes into the stream and is more transient.

Mr. MARKS: Right now, what was going on is that your existing connect lets me on your site, share your story into my feed. It doesn’t let your site share a story into my feed directly which easy to imply, I could subscribe to, you know, Scobleizer.com or whatever, and have his post show up in my feed in the same way they’re doing FriendFeed, that can be something if we’re going to hear that.

Mr. TAYLOR: I think, you know, again, the implementation deals on details are still being, you know, work out, but I think that that’s like definitely one of the goals that – that relationship that you have on Scobleizer.com can be really transparently taken interchange between Facebook and Scobleizer.

Mr. GILLMOR: Right. But, you know…

Mr. SCOBLE: I think I’m proud…

Mr. GILLMOR: Hang on a second.

Mr. SCOBLE: OK

Mr. GILLMOR: I’m just going to nail this done. You know, much in the same way that when you did made the decision of FriendFeed to move to a more real time and then completely real time architecture. You may not have had any idea about what the details of the implementation were going to be three months, six months out. But you sure did know that it was going to be a big deal.

Mr. TAYLOR: Yeah.

Mr. GILLMOR: So, don’t you have the same sense here?

Mr. TAYLOR: I do. I really think that to me, I really like the idea that Facebook is sort of the social infrastructure on which a lot of these sites can get distribution and personalization, because it’s so difficult to build out that infrastructure. And so to me this is just a way of making it, so when I’m browsing around the web, you know, I’m sort of like taking my Facebook identity with me. So I do think this is going to be a really huge deal as we do it right and so really what I’m focusing on right now is just the product manager and me just trying to help work with the engineering team and try to speck out exactly what that looks like and make it really easier for developers to adopt.

Mr. GILLMOR: Is it going to have a real-time component?

Mr. TAYLOR: Yeah. I – you know, again – I, again, I don’t really think – I, we’ll still working on the details. So, it’s probably little early to talk about that.

Mr. GILLMOR: What about the IM functionality? That wasn’t really mentioned and they roll up into the inbox. It seems like much at the event yesterday, the wall characteristics seemed to be so being left alone sort of as a legacy and IM wasn’t even mentioned, but it seems like there’s going to be a collision between those forms and that’s why I ask you about the real time aspect of it. I mean, this is going to – so much of our identity these days is map to real time. It seems like it’s a fundamental thing and it seem odd to me that IM wasn’t even discussed.

Mr. TAYLOR: So, initially, the IM functionality won’t change and it will still exist. If there is relatively limited scope to which developers can interact with IM, there is a real-time invitation, APIs or games in particular, but right now, you know, as you mentioned as also, separate experience is on Facebook.com. I think it’s safe to say that we are iterating a lot of our user interface for the next few months. Some of the mocks for those new UIs were included in the presentation on the road map yesterday. But it’s probably – there’s a lot of people think, you know, about these problems and probably not. Not my place to say where it will end up but I, you know, obviously, I’m really excited about real time as you know. So, I think we’ll end up in a pretty good spot but I can’t really say what that will be.

Mr. GILLMOR: Robert.

Mr. SCOBLE: Bret, there seems to be a difference between meta data that you put into the system like I would put on my profile page, you know, I tell people I’m a Liberal Democrat, that’s 44 years old, that’s male, etc., versus what’s going on right now is the Twitter lesser turning on for everybody and everybody is building this. That’s metadata that’s being built by other people about you, sort of like Flicker tagging is happening. Do you see in the API an ability for us to build new kinds of metadata that are not just controlled about you? Controlled by you? You know, the user.

Mr. TAYLOR: Yeah. I know, I think that’s a really interesting thing and actually Facebook I think has probably the most prominence form of this on the web with photo tagging. The photo tags on Facebook are probably my favorite part of the site. I do know, they’re the favorite part of a lot of people. It’s clicking on photos of Robert on Facebook is one of the coolest thing. Just because like from every all of these people who have never actually met, but you know, I’m looking at, you know, just photos of that person. So, I think it is okay specifically with our graph that we’re really interested in, is helping you build out your identity and having people in your social network help build out your network. Your identity whether it’s tagging you in post or tagging you in photos. So I think that’s a really, really great thing and I hope that the work we’re doing on Facebook.com and also with open graph API will hopefully, will definitely enable that functionality.

Mr. SCOBLE: Where do you see – where do you see us in this world? Are we 10 percent down with the social graph? Are we 50 percent down? Are we getting close to having it built out? You know, what other kinds of metadata do you think people are going to need about us?

Mr. TAYLOR: Well, I think for me it just comes down to user experience. The reason I love the photo tagging functionality of Facebook is because I’m sort of – I get to sort of really get a lens into my friend’s life from a – sort of my extended social network, people I don’t necessarily know personally but who also are connected through my friend. And I think in that sense, we’re not really there yet because that only really works well for photos today but there is a whole bunch of other aspects of what I do online, whether it’s interacting with the source code projects I interact with on getup.com, or you know, if I meant to skateboard in, you know, there’s like a whole wealth of things and that we’re a little bit – is not captured by Facebook true or if I’m in the movies, you know. And there’s a bunch of Facebook applications today that fallen to all these verticals, you know, whether it’s a movie, or entertainment, or technical things. And I really hope that with things like the open graph API, a lot of those verticals and I’m personally passion about that comes to make sense for Facebook to do can really be build out so that when I go to Facebook.com, and when I look at someone’s profile, I can see what truly represents them, even if that content or those objects in the graph are hosted elsewhere.

Mr. GILLMOR: Is it possible that …

Mr. MARKS: Didn’t you have that profile boxes?

Mr. GILLMOR: Why don’t you try to …Sorry go ahead.

Mr. MARKS: Didn’t you have that with profile boxes and then took it away again? I mean, the original – the first iteration of apps on Facebook was about putting box on the profile from a third parties and that then was already banished often to a sort of hidden tab that nobody finds anymore.

Mr. TAYLOR: Yeah. I think those are probably generally regarded as like not the most elegant way to do what I’m talking about. Yeah, it tended to be more about bling than actual connections so that make any sense.

Mr. GILLMOR: You know, that was the kind of MySpace, you know, hangover.

Mr. TAYLOR: Yeah, that’s sort of. I think it’s more important to know like what, you know, what say, like causes on connected to, than it is to like provide, you know, a canvass on which, you know, lot of different developers can put relatively garish things on people profiles that made it a little difficult to navigate the site. And so, I think we wanted to provide that functionality, but in a way that provides value to our users and developers. The only thing is that like, I think there’s a lot of details we work out with the open graph API. But one problem with profile box is that they were silos, meaning, if there are, you know, whoever provide the profile box knew what was in it but no other developers in Facebook itself didn’t actually know what was represented in that box and hopefully with something like open graph API, that data can flow more freely between applications which I think is really important so, you know, applications can build on each other as oppose to just sort of existing in this double silos.

Mr. GILLMOR: That’s a good opening for, you know, one of the things that currently doesn’t work very well isn’t represented by the Facebook space is FriendFeed. So, can you see FriendFeed being integrated using the open graph API?

Mr. TAYLOR: Yeah, I mean, I actually do think that that’s like an interesting idea. I think that – one thing is -FriendFeed was particularly focused on sort of the communication channels in that particular style of communication on the site and my hope is that as we’re working on the platform, the reason I was really excited about working on it is expanding this to a point that applications like FriendFeed that really work well within it and into the platform that we’re working on right now. The areas are probably working on right now existed when FriendFeed started. FriendFeed would have been much more successful and much more widespread than it was and so really to me like that’s one of the things I always keep in my head is, you know, as a recent entrepreneur, what is the platform that would have really driven, you know, my business to a next level. And so, I do think that ‘we’re going in that right direction.

Mr. MARKS: So that’s, I mean, what I would bring the activity streams up there because Facebook is already generating those, which is great and have taken part in that, you know, standardization group. But we’re also, you know, the photograph one is a great example where exporting the feed of taggings in photographs is useful, but if you can actually draw the ones in from Flicker that don’t set(ph)last week and from iPhoto and from the other side in MySpace even …

Mr. GILLMOR: Yeah, the aggregation model.

Mr. MARKS: Actually tagging, drawing that back in there saying, all right, here’s, you know, here’s the photos that Kevin posted at Flicker that are tagged with Robert Scoble or whatever. That would sort of be interesting and it gets this – yeah, there’s some complications there because you would have mapped the identities from one space to another. But the fact that we’ve commandeered to move that around is very hopeful. I mean…

Mr. TAYLOR: Yeah.

Mr. MARKS: Having seen (unintelligible) for that.

Mr. TAYLOR: I think that’s a very promising thing and the direction we’re really interested in moving. They said, we really want to be the social infrastructure of UL and I think that – in particular, you know, I’m an avid user of Picasa Web Albums and we have a lot of avid Flickr users here and I think we’re really committed to making those products work really well and kind of bringing in what I think is a really, really positive social experience on Facebook.com and integrating it with the really positive photos experience on those sites and something we’re really committed to. And we’re that, as I said, worked some of the details that we’re really trying to work through right now.

Mr. GILLMOR: I don’t want to go too far down the rat hole of talking about, you know, Flickr and these kinds of, you know, media issues when we’ve got some very low hanging truth here that I’d like to get to, such as – right now, you can’t really have a conversation on Facebook. You know, these orphan comments that – you know, I was at the restaurant with Cliff Garrisher(ph) a little while ago and he got some sort of a comment on Facebook and he was trying to find it on his iPhone and he literally couldn’t get to it. I mean, you know – and then you got this product that you use to have something to deal with that right now, it’s the only real technology that works on the network. So, you know, where are we going to go with this and how long is it going to take?

Mr. TAYLOR: Well, obviously I love FriendFeed’s experience as well, but I also think that Facebook as a product, provides a lot of different value to a lot of different users, you know. The community that’s formed on FriendFeed and all the countries that it’s become popular, particularly the U.S., Turkey and to some degree, certain countries in Asia are really using it as sort of primarily, as a discussions tool and I think that, you know, one thing I’m very realistic about at Facebook is it’s a lot of different things to a lot of different people. You know, it is like the functionality of profile navigation and photo browsing and photo sharing and there’s lots of other features of Facebook that make up the Facebook experience for…

Mr. GILLMOR: Sure. But…

Mr. TAYLOR: Blogger Facebook user based, so I’m not sure it have like a great answer about where all these things ends up, but…

Mr. GILLMOR: I’m not looking for an answer. I’m looking for just your take on what is the value proposition of real-time conversation, because basically, you have the only tool that works and yet it’s not represented in Facebook.

Mr. TAYLOR: Yeah. Well, I think there’s a couple of things. I mean, I think it’s interesting that a lot of people are finally working on communication tools after I think a long period of relatively little innovation in the space. So there’s sites like FriendFeed and sites like Twitter, there’s Google Wave and they’re all experimenting with what I would say are quite distinct variations on this problem. But I’m hoping that – you know, I’m not sure where all these things will end up because I think there are very experiences, but I think that like, we will end up with a new set of user phase standards for real-time communication by the end of this and there’s a lot of complexity that goes along with that like all the new protocols that kind of introduced as a side effect of these interfaces. But I think that like we’re in this period of rapid iteration and innovation, and as a consequence, you’re seeing things like PubSubHubbub and RSS Cloud and sort of more technical, you know, infrastructure related to this and you’re seeing a lot of different start-ups, introduced lots of interesting user interfaces on top of these protocols and so, I think it’s a period where it’s worthwhile to just have a lot of people trying a lot of different things and my hope is by the end of it, that this type of experience will be incorporated to all of our favorite products. Just like I think that there was this period in the Web 2.0 days, we’re adding, you know, profiles and like social features to the site. It was like a noble idea. And now, you wouldn’t ever go to a site that didn’t incorporate some sort of profile and social features. My hope is that a lot of these real-time communication things just become ubiquitous and sort of the standard on which, you know, lots of products feel – and again, I don’t really know where it’ll end up, but I think we’re in that period of just iteration.

Mr. SCOBLE: Bret, Bret, the things that Steve’s asking for really aren’t real time. They’re like permalinks to the objects that we’re talking about, the threads or the items and also, we need search. We need to be able to – you know, what we take it for grand on FriendFeed is I can search for, you know, every item that has the word Obama in the title that has 15 likes and I can find things really fast doing that and I can’t do that on Facebook.

Mr. TAYLOR: Yeah, I would say like I – you know, I understand that there’s some, you know, flaws with the Facebook stream product, but I do think that you’ve identified a couple of things I think that are important. You know, permalinks, notifications, you know, and other aspects just keep you involved with the conversation are really important and so those are the types of things that I think we’re trying to figure out because, you know, permalinks are important and notifications are important, but one thing that people who installed the FriendFeed IM bot noticed is if you get the notifications wrong, you could, you know, die and like drown in the sea of instant messages, you know.

Mr. SCOBLE: Yeah.

Mr. TAYLOR: But I just don’t think that I agree with all of the criticisms of the Facebook stream and I agree with the criticisms of FriendFeed that I’ve heard and that’s sort of what I mean. I don’t think this is a solved, you know, problem yet and I do think that we will see some best practices coming out of it. And when we do, I think a lot of platforms including Facebook will probably adapt to all those best practices, but I think we’re in a healthy period of experimentation at the moment.

Mr. GILLMOR: Well, you mentioned – go ahead, Robert.

Mr. SCOBLE: One thing that people kept complaining about FriendFeed is that you didn’t have control of who appeared on your screen and that seems to be a fundamental difference between Facebook and Twitter. Twitter, I have complete control of who appears on my screen. If I don’t want to see Steve Gillmor, I block him and he does not show up on my news feed anymore. But – and I can do that on FriendFeed, but I can’t quite do it on Facebook. Facebook, if somebody – if I’m a friend with Steve Gillmor and then he – and then you comment on Steve Gillmor’s items, you show up on my news feed, right? And I didn’t invite you there. I didn’t ask to see you. You appeared for some reason and that causes people to distrust or dislike or causes them to see noise that they didn’t…

Mr. GILLMOR: No. I think that’s actually an asset of the technology. But what’s…

Mr. TAYLOR: It is in some places.

Mr. GILLMOR: What is Bret – what’s your answer, Bret?

Mr. TAYLOR: Oh, I was just going to say that I’m a little bit with Steve on this. I don’t think it’s implemented perfectly today. Obviously, ideally, your stream would only show you those things that you actually wanted to see. I’m predicting that is imperfect and something that I think the team is really iterating on here, but one thing that I – it is, I think, are people’s Facebook networks genuinely represent the real social networks. It’s something that I think is fairly unique to Facebook in the grand – the whole world of social networks. And as a consequence, seeing people that are, you know, you are connected to through one level of interaction is probably disproportionately value on – valuable on Facebook than compared to other networks because it’s probably someone you actually know or heard of given that your social network is represented more accurately here. And so I think if implemented correctly, it can be really valuable because that kind of serendipity is something that is very common in real life. You know, if you’re having a conversation with your friend and they start talking about, you know, some article that their other friend told them about, that’s like a completely normal behavior and capturing that natural social behavior within, you know, a network like Facebook I think has a lot of value. And that said, I agree with you like it has to be implemented well and it has to feel natural and – but I think that will come with a few design iterations.

Mr. SCOBLE: So this will continue to be a fundamental difference between Facebook and Twitter going forward?

Mr. TAYLOR: Hey, you know, I’m just one person here and I’m working on the platform and you’re talking about an area of the product that I use regularly, but I’m only peripherally involved in. So I can’t say what – you know, I (unintelligible) in the news team. Anything you can think of, the news feed team would be willing to try and I don’t which direction they’re going to take.

Mr. SCOBLE: Yeah.

Mr. GILLMOR: It’d be interesting if we could just cut out the disclaimer and just go right to the answer.

(Soundbite of laughter)

Mr. TAYLOR: I’m not working on it actively, so you’re asking me what…

Mr. GILLMOR: Yeah. I was going to ask to you about what you – I was going to ask you what you thought about Google Wave. Now, you don’t need to have a disclaimer there.

Mr. TAYLOR: Well, I’m even more by bias there because Lars and Yens are two of my best friends.

Mr. GILLMOR: Uh huh.

Mr. TAYLOR: We work on Google Maps together and so…

Mr. GILLMOR: Well, all right. So instead of talking about FriendFeed – God knows why not.

Mr. TAYLOR: Yeah.

Mr. GILLMOR: Let’s talk about Wave. They’ve got some problems in terms of UI.

Mr. SCOBLE: Some problems they put into a stupid email interface.

Mr. GILLMOR: Well.

Mr. TAYLOR: Well, I’ve got…

Mr. GILLMOR: We know what Robert thinks about this and…

Mr. SCOBLE: I mean, I was talking about – to somebody yesterday at the Twitter conference and we both said, why didn’t they just put it into an infinite loop or something? You know, some sort of super Wiki because there’s a lot of power there that I want to get to, but I don’t want to steal with the stupid UI of the email, you know?

Mr. TAYLOR: Well, I think one thing that Wave (unintelligible) is it’s truly new. They really tried to do something that had never been done before and they did it all at once. It wasn’t, you know, like an iterative change from some previous thing. And as a consequence, people go in there with certain expectations and some people go thinking this is the next generation of email and they’re comparing it to email. And some people here, it’s kind of like Twitter for whatever reason. They go in and compare it to Twitter. And I think, you know, if you talked to Lars and Yens, they’re thinking of it as just, you know, an entirely new sort of collaboration tool and I think that’s like a – I really respect the fact that they tried to do something completely differently and in particular, one…

Mr. SCOBLE: I guess my argument is I wish they had just freed their mind and gone completely differently and…

Mr. TAYLOR: Yeah.

Mr. SCOBLE: Not tried to pull it in the email interface because I want to use it for the Gillmor Gang. I want to have a Wave for the Gillmor Gang. It’s magical to get, you know, a thousand people all editing different parts of this continuous stream and putting in videos and putting in, you know, integration with live data sources and stuff. It’s really cool technology and if they had just simplified the UI so I could have one URL with one stream with permalinks for each item or each object on the graph there, it would be really cool.

Mr. MARKS: But that’s the thing, Robert. They’re not individual items. There are edits to a document. So structurally, underneath is much more like a Wiki than it is like a Twitter or an actively feed. So…

Mr. SCOBLE: Yeah. But see, this is the modern world. You know, each piece on this new super Wiki should have a URL so I can point to it. Because already, I have Waves that are like 16-feet long, right?

Mr. MARKS: What are your…

Mr. GILLMOR: I find it ironic, Robert, that you want a super Wiki when, you know, that – how are you going to control that page?

Mr. SCOBLE: There’s no controlling on it.

Mr. GILLMOR: Oh.

Mr. SCOBLE: Except on Twitter. You get to control Twitter.

Mr. GILLMOR: So we’re back to two weeks ago, Robert, than last week.

(Soundbite of laughter)

Mr. GILLMOR: We’ve been having this wrong dialog, friend.

Mr SCOBLE: You get to control Twitter, man. That’s where your control feeds are going to reside.

Mr. GILLMOR: About how to control your page and…

Mr. MARKS: I’m just running on Robert’s Facebook page with Sidewiki.

Mr. GILLMOR: Exactly.

Mr. SCOBLE: I know you know how to control Twitter. You can put side Wiki on my Twitter account and then it’s all there.

Mr. GILLMOR: So you know, basically, Bret, this gives you some time in which to be able to figure this stuff out because everybody else sucks even more, right?

Mr. TAYLOR: Well, I have to say one thing that is – you know, it’s one thing that I have used way before that I found to be a really nice experience is just collaborating on a product doc like a product spec. You know, I sent out Wave with like the initial version and then we spent some time editing it together and it was a smaller group of people not a thousand, and I think that that type of used cases perhaps, one of the things they had in mind when they designed the system and I thought…

Mr. GILLMOR: Right, and that…

Mr. TAYLOR: It’s a really unique and valuable experience.

Mr. GILLMOR: That kind of Ogres for, you know, a reasonable integration with Google Apps as opposed to necessarily the mail part.

Mr. TAYLOR: Yeah. Again, I hope they do something like that. I think a lot of enterprises could gain a lot of value from it.

Mr. GILLMOR: All right. So what about FriendFeed? When are we going to start hearing about FriendFeedish stuff in Facebook? Forget the road map now. Now we’re talking Turkey.

Mr. TAYLOR: Yeah, that’s fair. To me, one of the things I’m really excited with is open enough the Facebook Apps more widely and more openly. Reason I’m excited about connect and open graphic API’s, to me, it represents – there’s obviously the discussions part of FriendFeed but also, I think one of the things when we started FriendFeed we’re really excited about was kind of like this social layer on top of the web that makes any sense, you know, making all the sites you use a little more social. And to me, the combination of connect and some of the products that we’re working on is really realizing that vision out of a much larger scale because of Facebooks, you know. And so for me, that’s one of the most FriendFeedy thing that I’m working on and even though it’s obviously a little bit unrelated to some of the discussions components of it. So I’m really personally really passionate about that, which is why I chose to work on the (unintelligible).

Mr. GILLMOR: As I was suggesting before and I think you agree with me – at least, there was some interesting idea. If you look at the discussions part of FriendFeed as an interface that can be expressed through, you know, a window on, you know, a page, must we get rid of the fan page thing?

Mr. TAYLOR: Yeah.

Mr. GILLMOR: Which I understand that the word fan is going to go away…

Mr. TAYLOR: Yeah.

Mr. GILLMOR: Real soon now. So at that point, you’ve got sort of an iGoogle. Only it’s an iFacebook that you’re beginning to develop and so couldn’t that, you know, that aspect of the real-time chat be sort of integrated by itself and then migrated into the four API overtime?

Mr. TAYLOR: I absolutely hope that’s technically possible. I think that’s something we’ve thought about.

Mr. GILLMOR: OK. So what other pieces of FriendFeed are there? There’s the aggregation?

Mr. TAYLOR: Yeah. I mean, again, I think that a lot of what were doing is not going to be translated directly, but I think like…

Mr. GILLMOR: The capability of being able to – I mean, the API allows us to be able to significantly model the routing of individual elements off the network.

Mr. TAYLOR: Yeah.

Mr. GILLMOR: The things that Kevin is working on with the activity stream group in terms of finding, you know, agreed upon standards for that FriendFeed and very little else allows you to do that today.

Mr. TAYLOR: Yeah.

Mr. GILLMOR: So you know, how do we move that – you know, I mean, obviously, you’re committing to at least for an unknown period maintaining that ability inside of the FriendFeed shell.

Mr. TAYLOR: Yeah. So I mean, all these people are completely candid here. The aggregation – I think that the FriendFeed API was genuinely a positive thing. The aggregation components of FriendFeed have been a bit of a blast in the (unintelligible) and the press because the level of intentionality of things that we aggregated varied widely. So some people would import, you know, their Netflix, you know, rental stream and then someone else would import, you know, their Facebook status updates, and obviously, the Facebook status updates were much more intentional, much higher quality, much more likely to be commented on or liked. And,you know, if you went and decided to queue 10 movies in your Netflix queue all at once and it’s, you know, viewed into your FriendFeed stream, that would be like – you know, most of our users would just complain about that. And so one thing that I – you know, we’re thinking like – I don’t think I want to like translate certain things on FriendFeed directly because I think that they were done in a way that like get rid – you know, we have, you know, a chance to do them again. We probably would do differently. And I think that one thing that we’re thinking about is really focusing on the APIs and focusing on things like making sure that your Facebook experience represents really authentic user actions and really intentional things that they’ve shared. And so as a consequence like I think that a lot of stuff around connects on the stream APIs, the open graphic, yeah, that we’re working on, hopefully, the sum of those really captures a lot the value that you’re talking about even if the APIs themselves look a little different just because I do think that – you know, I’m really concerned that we don’t end up with sort of the same user interface problems that I thought we ended up with on Friendfeed.com.

Mr. GILLMOR: Right. On the other hand, you know, I hide a lot of things. Once you…

Mr. TAYLOR: Yeah. Well, unfortunately, with – you know, that was probably reasonable for FriendFeed. But you know, as I’ve said, Facebook has a lot of users with wide…

Mr. GILLMOR: I understand. I understand the dynamic of moving from basically in the early adapter sort of leading edge kind of environment to one that is global and where you’ve got a lot of moms and pops that just – and grandmas that just don’t care.

Mr. TAYLOR: Yeah.

Mr. GILLMOR: But being able to translate those tools at the API level so that they can, you know, so the people can – I mean, we’re building on top of FriendFeed.

Mr. TAYLOR: Yeah.

Mr. GILLMOR: And I’m certainly somewhat confident, less so from the last thing you just said that we’re going to be able to exploit those things because I think that we were at a very early stage in terms of, you know, the people inside FriendFeed and at the developer level of being able to harness tools, you know, the discovery process of finding out what the value of what you had created along with some of the workarounds that I can certainly understand you want to not perpetuate things that don’t work well.

Mr. TAYLOR: Yeah. So I certainly think that our goals are in line and maybe it just comes down to doing – getting the details right so that APIs will be at the same level of express activity that you, you know, you’re using today.

Mr. GILLMOR: OK. I think that we’ve been censored by the Facebook police and your image is now frozen.

(Soundbite of laughter)

Mr. TAYLOR: Well, maybe this is good – I actually have to go in a couple of minutes, anyway. Do you want to just wrap up them?

Mr. GILLMOR: Unfortunately, yes. No. I think we’ve gotten further than I actually thought we would in terms of getting you to talk about FriendFeed. So bottom line, do you think that there is going to be a continued use of FriendFeed that is going to be viable to keep the lights on in terms of aspects like what I’ve called stream splicing that were talked about, being introduced and seemed to have been sort of lost in the cut of the acquisition? Do you think that we’re going to see stream splicing?

Mr. TAYLOR: It is something that actually Paul and I have been talking a little bit about. And I think it just comes down to how difficult they will be technically to introduce. Because it is something I think that has a lot of potential value, but is also, you know, not applicable to a very large percentage of users. So Paul and I have been actively discussing it and I think it’s very possible or even probable that we do it soon. But if it turns out to be a real technical headache, we may have to reconsider it. So we’ll keep you posted on that.

Mr. GILLMOR: All right. Great. Robert?

Mr. SCOBLE: With the stream splicing, it’s about pages. The Facebook pages are still – you know, I can’t mix Oprah with Shaq’s page in an interesting way and that’s what I think we’re hoping you guys solved.

Mr. TAYOR: Oh, so I assume that Steve was talking about this particular feature of the FriendFeed API that he’s been asking for. Regarding the Facebook API, I think it is really an interesting concept, but it’s obviously a much larger in scope and so something that I’m interested in, but I can’t really say whether we will or won’t do right now.

Mr. GILLMOR: OK. And Kevin?

Mr. MARKS: Yup.

Mr. GILLMOR: Any last questions?

Mr. MARKS: Um, no. Nothing else comes to mind. I think we covered a lot of good stuff. I’m encouraged to hear that you reached the activity stream stuff and these flow-based things that we’re working on. Because I think bridging it between these different places is going to be increasingly important and it’s great to see you bringing that experience from FriendFeed into Facebook.

Mr. GILLMOR: All right. Well…

Mr. TAYLOR: Thank you for having me, Steve.

Mr. GILLMOR: As always, it’s been a pleasure and we’d like to keep, you know, keep your – holding your feet to the fire here as we move forward. I think it’s important. I think when Paul finally went on FriendFeed in the wake of MGs and Robert’s articles about the death of FriendFeed, I think it soothed a lot of fever browse and I think it’s important. It’s a testimony to what you created and also frankly, as far as I’m concerned, a testimony to the fact that there’s nobody else is doing anything like it and we certainly hope that that’s going to be continued as far as possible at Facebook. This is Steve Gillmor. This has been the Gillmor Gang. I want to thank everybody who showed up and I want to thank – this Tricast was produced in association with our sponsors, Rackspace and the Tricaster, which makes this possible, is a product of New Tech, and we appreciate their support as well. We’ll see you again next time. Bye-bye.

Stream Splicing — Threadsy’s Rob Goldman with Kevin Marks, Robert Scoble, and Dan Farber. Recorded live Thursday, October 22, 2009.

Full transcript below the video, courtesy of Simulscribe.

Mr. STEVE GILLMOR: Hi. This is Steve Gillmor and welcome to the Gillmor Gang. It worked this time. Oh, before I forget which I did the last time, I want to thank our sponsors Rackspace and the fabulous people at New Tech who have produced this wonder machine called the TriCaster. This TriCast is one of many that is starting to emerge on the network and we’re pretty excited about – about the technology and how it’s started to have an effect. Our show today is going to be about, of course how our assess is dead, but specifically another one shot. Scoble shakes his hand like, oh wait a minute, FriendFeed is dead not some …

Mr. ROBERT SCOBLE: It’s all dead. Everything is dead.

Mr. GILLMOR: Exactly. But that’s, you know, you have to turn things to oil in order to be able to get the new stuff in, right? So, we’re going to be talking about the death of email and to help us with that is Rob Goldman. Welcome, Rob.

Mr. ROB GOLDMAN (Creator, Founder, Threadsy): Thanks. Happy to be here.

Mr. GILLMOR: Rob Goldman, you have a software package called…

Mr. GOLDMAN: Threadsy.

Mr. GILLMOR: OK. And tell us a little bit about what Threadsy is.

Mr. GOLDMAN: Threadsy is the world’s first integrated communications client. So, we combine email, Facebook, Twitter and a bunch of – about 40 other social services into one integrated UI. So, it’s sort of a one stop that – that does more than just sort of aggregate things. It integrates them so it gives you a kind of holistic view of not just all of your communication services but the entire sort of online life of the people with whom you’re communicating because as sort of things progress and especially at social media and social network is kind of start to displays the place in our lives that we had for email, we’re finding the people we communicate with are spread out across a bunch of different surfaces. They got their Twitter accounts, their Facebook accounts, their Flicker accounts to their Picasa accounts and they’ve sort of left traces on themselves all over the social web. So, we try to pull those things together so that you – you get kind of a complete picture of the person that you’re talking to.

Mr. GILLMOR: OK. And speaking of one stop shops, Robert Scoble, welcome.

Mr. SCOBLE: Hey. How are you doing? So, I’m trying to get Threadsy loaded but it’s not loading for me today. So, but I’ve used it quite a bit and it’s pretty interesting service and that it’s – places together all your email and social networks into one – one long feed which makes it a – I find it interesting because I can just put it up on my vertical screen here and just watch the world go by and choose even more stuff to engage with.

Mr. GILLMOR: Also joining us on the phone are Kevin Marks. Welcome, Kevin.

Mr. KEVIN MARKS (British Telecom): Hi, there.

Mr. GILLMOR: And Dan Farber of CBS News. Welcome, Dan.

Mr. DAN FARBER (CBS News): Good afternoon.

Mr. GILLMOR: And Mike Arrington is not joining us. He is at – at the Web 2.0 Conference. I just saw him a little while ago. But I think this is going to be what the team will be for today’s show. So, Dan Farber, just before I forget, we had an interesting conversation last night with Tim Berners-Lee, didn’t we?

Mr. FARBER: Yeah, I thought it was, you know, good to catch up with him and kind of find out how he’s evolving as thinking in regards to semantic web and Twitter and other things.

Mr. GILLMOR: So, you know, it was way over my head what he was talking about. We were luckily joined by Nova Spivack of Twine Fame who was translating in both directions I think. But I think I can characterize one thing about that conversations that I think would be interesting for today’s show which is that there is definitely an interest on the part of Tim around the notion of the PubSub aspects of Twitter or not specifically Twitter but he was talking about Identica, for example, which has the ability to be able to emits or to at least transport RDF or you know, sort of so called semantic objects. And I’m not a big proponent of RDF mostly because I don’t understand it and I think that’s one of the reasons that I think it’s had some trouble in terms of adoption. But clearly as we get to a sort of the intersection of things like PubSubHubbub, and you know these micro messages being carried over, transported – could be integrated and federated. We’re getting to the point where there’s going to be tremendous opportunity for us to regain control of the micro message based than we have – just been sold down the river by Twitter to Microsoft and Google yesterday. So, anybody jump in and comment on what they think about the Twitter moves and what it imports for, you know, for the climate of micro messaging. Robert, I want to hear from you first.

Mr. SCOBLE: I think it’s huge because it brings a whole new audience to Twitter first of all. Saying all I got on the lot – another round of hype. I mean, I was listening to ABC News yesterday and all they were talking about was this – these two Twitter deals with Microsoft and with Google. But I’ve see – I talked about on my blog yesterday that I see a new place for real time news like Twitter because if you got a Google and search on Palo Alto Sushi for instance and then you look at Google, there’s a list of restaurants there but it’s very cold and there is nothing there that’s live or human and if Google can figure out how to add in, you know, information from both the restaurants and from users, I think that will make that list a lot more useful. And that’s what I’m hoping to see…

Mr. FARBER: Google also hopes…

Mr. SCOBLE: Go ahead.

Mr. FARBER: Google also did introduce social search.

Mr. SCOBLE: Yeah.

Mr. FARBER: Where they are, just kind of taking from your friends and adding it to search queries. and something they’ll be releasing in the next few weeks. I just wanted to add something about what Tim Berners-Lee was saying about things like Twitter offset(ph) which is – if he usually has a Twitter is the fact that there’s an ever – real URL and doesn’t have much meditated with it. And without that, you know, you really can’t drop it into the bigger stream to not able to use that content and in different ways, more semantic ways.

Mr. GILLMOR: Well, but I…

Mr. MARKS: Well, sir, I – I haven’t pushed back on that.

Mr. GILLMOR: Yeah, go ahead, please.

Mr. MARKS: Twitter does have real URL. The each (unintelligible) does have a family link. It has the cut back structure then can have its involvement.

Mr. FARBER: A short – a short URL which you know is not only (unintelligible)…

Mr. MARKS: Oh I think, obviously as the proper link, yet. The links are bad and I agree with. We’ve debated on it.

Mr. FARBER: Yeah, the links are. It’s not that, it’s the links out.

Mr. MARKS: OK, got you. Yeah but that’s – that’s I think that in fact that is a structural flaw but I’m – you know, I push back on Nova and it’s like, we need more meta data to go with the data. Well, the thing is we’ve – meta data – these things with meta data and data is many cases a mistake because if there – if they – suppose a meta data is hidden away from us in some parallel things we can’t see, then it ends up getting with out of sync with the real data and if it pushes us anything, is that even with a 140 characters, we can climb in a lot of intelligence pickling(ph) and later about the data which by using this – by using as tags, by using short links and so on. We’ve actually come up with a lot of ways of having a very compact discourse that is still human readable and machine readable. And that’s – and that’s the tension between the sort of the – that’s the hyper abstraction of RDF which is – is now abstracts to having develop abstraction. And that’s – as you said, that tends to be intention with people that are actually understanding what’s going on. And if you look at what’s – you know, what’s worked and what hasn’t, what’s worked is when you’re able to – when people are able to add data and singling themselves in useful ways but the data is not some sort of abstraction that stuck on the side of it. The people – the people can’t see and understand, if some of these articulated directly to them in a form that works for them. So, you know, so Scoble’s restaurant example that is – things like FourSquare work very well for that because you’re obviously articulating time at this place now or you’re running a little tip to it saying the fish is really good. And those stuff – that those stuff show back to other people and it’s not in some sort of gigantic abstraction. It’s in – so in a way that banks have used. So, I think there’s, you know, audience had seen the future of the web for a long time allegedly and in fact it has not – that it was on its promise over the last you know 10 or 15 years where it’s actually we spoke – what we have seen is more and more people incorporating richer data into the streams that they are already using and that’s the trend I see improving.

Mr. GILLMOR: Rob, why don’t you jump in here and translate some of this into your you know, coming from Threadsy.

Mr. GOLDMAN: Well, I mean I guess I view it a little bit less from the sort of technical prospective of the you know, the PubSubHub and sort of RDF and the standards and more, just the news yesterday struck me as important practically, you know, for two reasons and I think that it have, you know, indirect impact on what we’re doing at Threadsy but I think a much bigger impact on what’s happening with Twitter and sort of short messages in general. I guess the first thing is, I mean, I think it points the way for a business model for Twitter. You know, and suppose there – there was some, it sounds like pick out some interference there.

Mr. MARKS: Something like that.

Mr. GOLDMAN: Hello?

Mr. GILLMOR: Yeah, keep going.

Mr. GOLDMAN: OK. Yes, I think its points to – I mean, obviously I think there was some revenue involved in both of those deals. Probably meaningful revenue when your company decides a Twitter and I think more importantly, it sort of presents the sort of Twitter body as a really interesting application for search. And I think to the extent that people interact with tweets and the Twitter database in a search oriented way, that’s a good thing for their sort of a long term revenue prospects because with search comes intention and I think the pathways to delivering values for advertisers. And I guess on the other hand, on the downside I think for Twitter is, it’s going to bring a lot more traffic across the tweets and the fact that you know people can tweet and find themselves on a landing page on Ding or on Google. I think it’s going to attract even more spam and I think they already have a really big problem fighting the spam that is happening inside the Twitter. I think this is going to make it a lot worse. So, when you put this kind of high powered traffic on something, I think you need a high powered control system to make sure that everyone stays honest and I’m not sure that’s there.

Mr. SCOBLE: I think it’s coming with the invention of the new list feature but it will take a while for Google to figure that out and it will first of all, it will take a few more weeks at least before Twitter shifts it. But I’m finding that I can – I can dream of searches based on my lists that I’ve subscribed to and I’ve subscribed to about 100 different list with – which cover probably about 90 percent of the tech industry. You know, you don’t have to subscribe to too many list before you hit almost everybody and now I could – if I could say search on my lists for something, I would get absolutely no spam.

Mr. GOLDMAN: And do you think that will part of the search engine implementation, the kind of keeping it personal?

Mr. SCOBLE: Not at first but that’s where this is heading. I mean, if you – really if you talk to the Facebook people they keep using this word of, we believe it’s your friends that really are going to affect everything in your life. And so, I would expect, the reason they buy a FriendFeed and that I’ve still have some optimism about FriendFeed is the guys there understood this search far better than Twitter did, right? We’ve had this kind of list based search for quite a while. We could always go to, you know, search Obama, search the word Obama in a title based on you know Tim O’Reilly you know, what Tim O’Reilly wrote or based on what this list of friends that I’ve set up or list of people that I’ve set up. And if they move that to Facebook and Facebook gets it first and there – everybody in Facebook talks like this so I know they’re thinking about internally what is the impact of your personal friend graph or your personal social graph and why is that different than some guy you’ve never ever met before or is not closely related to you or closely related to your social graph. I think you’re going to see some really interesting things. The interesting thing yesterday on the Google search announcement was that they’re using a two level search based on you. So, you could – at least that’s what they’re saying is – and I haven’t seen the implementation so I’m going off of what (unintelligible) Mayor was saying on stage. But you could limit the search to only people within two levels of you and keep in mind for somebody like me, that’s a lot of people. I’m following 8,000 people and each of those people are following – some of them are following hundreds of thousands of people. Some of them are following tens of thousands. Some of them following just you know a few hundred. But if you take – you know, 8,000 people multiplied by even let’s say 200 people, that’s a lot people you can search through and that search will have very little spam because I’m adding my personal friend – you know people I know in the industry and brands I trust in the industry and that I’m seeing already an alternate universe from the regular Twitter that’s being built right in front of me. You know, there’s a guy who is one of the top iPhone app offers. He spoke to a list of all the app developers. And so you could just add his list and also you can get all the app developers in the world. It’s unbelievable like what you can do now and I’m sure Facebook is working on this as well. You know, everybody is on Facebook. It’s just how are they going to surface that social graph and make it useful. Right now, Twitter – I think Twitter is actually ahead. Most people probably don’t think that, right? I think what these search deals yesterday, that put them in the lead.

Mr. GOLDMAN: So yeah, I watched your walk-through of the list product the other day, the video you did, and I thought, I mean, this is the first I’ve seen, you know, an actual practice seeing the list product roll out.

Mr. SCOBLE: Yeah.

Mr. GOLDMAN: And what struck me, which I think is super interesting, is the real power in Twitter. And I think the reason that, you know, it had sort of Facebook on its (unintelligible) for quite awhile is that information can move so quickly through it because there’s no barrier, there’s no limit to the way that the information can move. There’s sort of no walls in the system. It’s just this giant wave and if something important happens right near you, you know, you see some armed guy walking into a hotel in Mumbai, you know, that information travels fast.

Mr. GILLMOR: Yeah.

Mr. GOLDMAN: And it can’t travel quite as fast inside the Facebook because you’ve got these kind of walls of your friends. In order to take a status of an event, have it move across the sort of broader universe, someone has to kind of appropriate it from me and re-share it sort of explicitly in a way we don’t have to (unintelligible). I think…

Mr. GILLMOR: Yeah, I think that’s over stated. I really do think that’s over stated.

Mr. GOLDMAN: What was that? I mean the speed, it get over stated, yeah. I think…

Mr. GILLMOR: Yeah. And just the issue of Facebook having this barrier that prevents it from competing ahead on in real time with Twitter, I just think that’s an artifact of, you know, what they’ve done to get to where they are, it’s not, you know, it’s not a technical problem.

Mr. GOLDMAN: I totally agree. And I guess what I’m saying is the list launch on the Twitter side is a step kind of in the other direction. It’s saying hey, let’s kind of erect some walls to kind of keep the spam out and focus the conversations and it feels like a different path down to smaller groups.

Mr. GILLMOR: Yeah, I’m not sure I agree with that either. I think that what less represent is Twitter’s attempt at monetizing at an early stage as sort of a hybrid between track, which they continue not to deliver in which they have now subsidized through Microsoft and Google and the, you know, sort of their client, you know, base of people including you, Rob, who are delivering, you know, a group functionality. What they’re trying to do is to sort of copyright the group functionality and make it a data type. And I think that will be somewhat successful, but the tension will increase on the part of their third party developers and entrepreneurs who want to access that programmatically over the APIs at which point, you know, Twitter’s differentiation becomes somewhat irrelevant. So I think that it’s a short-term way of, as Evan said on stage, boosting their flow again at a point where they’re plateauing a bit and beginning the task of setting up these sort of proprietary data types and I think they’re going to have a hard road ahead of them in terms of, you know, what happens when there was a problem that was starting to be talked about yesterday on FriendFeed about the pipe between Twitter items and FriendFeed slowing down and I, you know, basically just asked – in the common thread, I asked Paul and Brett to comment on that. And Brett replied basically saying that there’s some – I just spoke with him, so I’m not sure whether he said this in the comments or whether he said this to me. But basically, they’re a combination of economic program factors and just some technical issues that they’re working through and that they should be resolved in four or five days. So let’s say that what Robert hope’s going to happen with FriendFeed is that its capabilities are going to be absorbed into Facebook. There’s going to come a day pretty soon now where people are going to say oh, you mean Facebook can get high band, you know, full access to the pump, to the fire hose as a third party developer, you know, subject of course to (unintelligible) or whatever that is at the same level as FriendFeed did. I mean, effectively, ownership has already changed hands. So the question is, is Twitter going to allow that? And if they do, what is their differentiator? I mean, why do lists suddenly become important if anybody, including Microsoft, Google and third parties aggregating the other? If they can all do API access to these list formats, it’s, you know, its open season. Where is their value out there?

Mr. GOLDMAN: Well, so Steve, your take is that they want to box out the client apps by offering some differentiated functionality…

Mr. GILLMOR: No. I think that Evan was very clear about that, and he has been, you know, where the rubber has always met the road is that whether they thought that that’s what they want to do. They never really felt that they could pull it off because, you know, it would be abandoning the horse that brought them to the party, which is open access.

Mr. GOLDMAN: Yeah.

Mr. GILLMOR: So I don’t see how they get around that and when you do that with somebody like a Facebook, you got a real problem.

Mr. MARKS: I don’t see that. I think that the interesting positioning I had when I met him was he said twist some information that work another session at work. And I think what the goal of list is, is to expand on the – on following people who I’m interested in as opposed to I’m following people I already know. But with Facebook, Cheryl(ph) was saying, no, no. The social is the most important. It’s about your friends. It still – we’re focused on the friends list whereas, you know, Evan has grasp the power of a symmetric following of being able to follow sources as well as friends having a mix together.

Mr. GILLMOR: Yeah.

Mr. MARKS: And the list is where they’re expanding that, making that more straightforward. So that was what I think happened at those two pictures there.

Mr. GILLMOR: Yeah. But…

Mr. MARKS: And I also think that…

Mr. GILLMOR: I think that, you know, I think that posturing on Facebook’s part. That’s pondering to their audience to say that it’s all about social and that is not about what Twitter is doing. I mean, they can do both.

Mr. MARKS: But Facebook is coming from a different place. You know, they have said, no. We let you control who gets to see this.

Mr. GILLMOR: Yeah. If you say what this is is public – if you say what this is is public, then you’re saying exactly what you’re saying when you put something on Twitter.

Mr. MARKS: Right. There’s a question of whether – yeah, you know, the default performance is.

Mr. GILLMOR: So if there are 50 million public users on Facebook and 50 million public users on Twitter and, you know, and those two environments are synchronized and tools are used like Threadsy to normalize that flow, throw out duplicates, you know, add or keep and retain and maybe even thread, you know, cross talk among different services into, – I mean, that’s the big problem right now in Facebook.

Mr. MARKS: Yeah. And filters.

Mr. GILLMOR: Yeah, exactly.

Mr. MARKS: Yeah.

Mr. GILLMOR: That’s – we’re going there and we’re going there fast, yeah.

Mr. MARKS: Exactly. I mean, the other thing that we had last week was another set – round of activity streams and standard discussions and so on, and trying to come up with come away of expressing all these things so that they don’t balance to a particular supplier and that’s – you know, we can never expect Twitter as a lovely engagement from everyone including this space. So that’s – I think that’s a lot differently. It’s fairly clear to me that that’s something that lots will be very interested in making sense of and coming up with some standardization for that is a way forward.

Mr. GILLMOR: Scoble?

Mr. SCOBLE: I’m just playing around with Facebook and Twitter. I think Kevin is right. They’re coming at the world from a different place and that, – you know, in Facebook, I have all my friends and they’re personally-added friends and their friends who have added me and I’ve added them. It’s a two-way friendship, right? Now, that’s the private part of Facebook. In Facebook pages, you can just follow me without me being involved, but it’s hard to use your word of streams placing. Facebook hasn’t yet added streams placing from pages yet. I can’t splice the stream coming off of, you know, Oprah’s page and splice it together with…

Mr. GILLMOR: Yeah. But…

Mr. SCOBLE: The stream coming off of Kevin Mark’s page.

Mr. GILLMOR: But you’re assuming that – you know, I think pages is a broken concept. I don’t think that that works. I mean, why do I want to differentiate as a user between an activity stream and a so-called promotional stream or whatever pages are supposed to be? It just makes no sense.

Mr. SCOBLE: Because some things – if you want to go to your friends, your family, your – you know, you want privacy on some things. That’s why I really like Facebook, right? Because I can have a Facebook where I just have my personal friends and it’s not going to be become a public item when I, you know, I post my baby photos. On Twitter…

Mr. GILLMOR: But here is – this is where – this is the intersection with email. I mean, email is personal as well.

Mr. SCOBLE: Yup.

Mr. GILLMOR: Right. But, you know, I was supposed to have J.P. Rangaswami on the show, but the only way that I seem to be able to reach him is by direct messaging on Twitter.

Mr. SCOBLE: Yeah.

Mr. GILLMOR: And I ran out of time to do it, so – but, you know, we’re moving toward a model and this is where – why Rob is on the show today, you know, not to mention the fact that Threadsy is a great product.

Mr. SCOBLE: Right.

Mr. GILLMOR: Is because he is – you know, I’m starting to see stuff that shows up in my so-called inbox that I only subsequently realized it didn’t come in email. It came from say, Facebook, which is your point.

Mr. SCOBLE: Yeah.

Mr. GILLMOR: So you know, the user doesn’t have to make these decisions each time. You know, if I want to go from here to the store, I’ve got basically, you know, two or three alternatives of ways of doing it. I can walk, I can take a bus or I can drive.

Mr. SCOBLE: But that’s inbound. You’re talking about inbound there. I’m taking about outbound. If I’m putting a baby photo up, I wanted to go to a different group. Then if I put up Google just about, you know, just, you know, made a deal with Twitter, I want that to go to the public group where everybody can discuss it…

Mr. GILLMOR: But you can – you know, you’ve got a computer. It’s not coming from multiple computers.

Mr. SCOBLE: Right.

Mr. GILLMOR: I mean, it is in effect because you’re using your phone or whatever, but you’re making a distinction. You’re sending a gesture at some point about where you want this data to move to.

Mr. SCOBLE: Right.

Mr. GILLMOR: And that separate…

Mr. GOLDMAN: Robert…

Mr. GILLMOR: Go ahead.

Mr. GOLDMAN: You’re saying, if I’m understanding you right, that you like Facebook better just because the privacy controls there are a little bit sort of more developed.

Mr. SCOBLE: I actually am a Twitter guy because I live my entire life in public, right? But my wife is on Facebook because she lives her entire life in private. She doesn’t want her – you know, she talks to her elementary school friends on Facebook and that’s all she does really. She doesn’t want to be a public entity all the time. I love being a public entity that’s why I love Twitter, right? Because the publicness, the way it came about was Twitter was mostly public. Yeah, you can DM me there. But when I’m talking on Twitter, it goes to the public and everybody can see it and re-twit it or comment on it.

Mr. GILLMOR: But you’re making my point for me, which is that as the amount of email that we actually process, you know, other than spam or stuff that we have to read or sort of glance up because we know that it’s part of our jobs or whatever.

Mr. SCOBLE: Yeah.

Mr. GILLMOR: You know, as that starts to diminish, it starts to be factored into newer form factors like a Facebook or a Twitter when they adopt those tools. Now, Twitter is way behind in terms of email. They’ve got a huge reach because most people are on, you know, Twitter if there is – the nice thing about direct messages is they’re synchronized. In other words, if you want to send something to somebody, the chances are that you have a relationship with them and there is a reason why you want – it takes the spam out of the equation in the direct message requirement.

Mr. SCOBLE: Yeah, you can’t – DM is different than email because anybody in the world can send me an email. I don’t – you don’t…

Mr. GILLMOR: Anybody in the world can send you a ping that you have to respond to on Facebook as well.

Mr. SCOBLE: No. True. But on Twitter’s DM, you can’t send me a DM unless I’m already following it.

Mr. GILLMOR: I just said that. So what I’m saying is that there is – the percentage of people that you want to communicate with via a DM that are not, you know, synchronized relationship with you is small. There’s a – it’s a smaller sample, but it’s a lot higher value.

Mr. SCOBLE: Yeah.

Mr. GILLMOR: So the signal to noise is much higher and it’s easier to be able to do that and, you know, people – there’s a lot that’s said about differentiating the generations and the kids today are much more public facing and they’re less concerned about, you know, as Scott McNealy famously said, getting over the fact that we have no privacy.

Mr. SCOBLE: Yeah.

Mr. GILLMOR: You know, I don’t think that’s about kids. I think that’s about all of us who, you know, work and increasingly work and play in this digital realm. The point is is that we all endlessly are searching for some sort of simple roll up of all these services.

Mr. SCOBLE: Right.

Mr. GILLMOR: And that, you know, it’s like – why the RSS equation? It’s not that RSS is bad. It’s just that it’s slower. It’s for a different environment.

Mr. SCOBLE: Yeah.

GILLMOR: It doesn’t have an economic model that’s supported in this new real-time environment. And, you know, the best that they can do is to, you know, stand – you know, is to be stable and then slowly lose market share.

Mr. SCOBLE: Yeah.

GILLMOR: This isn’t a value proposition. This is an observation.

Mr. SCOBLE: Right. I think we’re not arguing with each other really, but Facebook today doesn’t support what I need to do. Well, for instance, here’s my new list of Tech news brands. You know, it has Wall Street Journal, and MacRumors and TechCrunch, and Daring Fireball and Wireless Week. And I’m not sure if you could see that too well. But I can’t do this very easily on Facebook. I can’t just subscribe to brands without having them friend me…

GILLMOR: But you can do it on FriendFeed, all right? You’ve been able to do it on FriendFeed for a longer than your career.

Mr. SCOBLE: Not really because a lot of these brands are – a lot of these brands aren’t done FriendFeed, and they’re not…

GILLMOR: That’s nonsense because you just pulled them in through Twitter.

Mr. SCOBLE: Yeah, but not really. They’re not easily addable, findable, like they are here. To it – now, with list, you don’t even need to search for them. You just need to come to my…

GILLMOR: Right. And that’s true not just for Twitter. Now, they’ll be easy to search for on FriendFeede or Facebook, you know. The (unintelligible) the entry is just dropping like a stone.

Mr. SCOBLE: I agree with you in the longer term but not in a shorter term.

GILLMOR: OK. We’re talking three months instead of like two weeks.

Mr. SCOBLE: OK. Bu they’re not there yet, you know. Go ahead.

GILLMOR: Go ahead, Rob.

Mr. GOLDMAN: Can I ask you a question? So, what is everyone think the sort of real motivation behind the Facebook username kind of a land grab was? I mean, my take is that that was completely about getting you public and sort of providing you with a forum through which you can share information much more broadly than to just your friend.

Mr. SCOBLE: Yeah, one thing Twitter did really well was that at name. I mean, how did I pimp the show today? I said, you know, follow@Steve Gillmor, you know, and his show is on it one at – and that @name becomes a link in my – in everybody’s, you know, tweet deck or Threadsy or – Threadsy makes it a link, right? So, you can just click on that at and go to Steve Gillmor’s account. I can’t do that really easily yet on Facebook. And the real name was so important way for me to communicate where to go into my friends, you know. Go to facebook.com/stevegillmor or, you know, my scobleizer page, you know. Go to facebook.com/ scobleizer. That was really an important step. But they haven’t yet linked it together to make it nice like Twitter has.

Yeah, I’m with you. And I think – I mean, I guess I’m with Steve as well, which I think that will happen really soon.

Mr. SCOBLE: Yeah.

GILLMOR: Well, I thought that this…

Mr. SCOBLE: Like I said, within six months, both of this move together, right? And Steve gets what…

GILLMOR: Six…

Mr. SCOBLE: You know…

GILLMOR: Six months. You really think it’s going to be six months? I mean, the second…

Mr. SCOBLE: It’ll take a while for…

GILLMOR: Of least word and that they stop, you know, fair(ph) well, you know, with it. It will be the – you know, the day that all of the third parties will start rolling it up and providing value-added services. And then, there’s going to be a discussion about what is the third party service. Kevin Marks. Is Google a third party service for Twitter now?

Mr. MARKS: Yeah. I think it is. I think, you know, Twitter has a very expensive(ph) user. I’ve heard that this week from both (unintelligible), which is that they see the multimodality of Twitter but doesn’t made (unintelligible) of the fact that there are lot of this while(ph) getting at it. I think that’s, you know, one more reason that the (unintelligible) work is that they route toward to SMSs. So, it gives you a way of explaining to people SMS you without being able to (unintelligible). Or without having a direct phone number, in some that you can route(ph), more than one way. And that’s – that does work very well. So, there’s I think a lot of this is – is about multimodality in both directions. And that’s sort of – for me, that’s a lot – a lot of the interesting part that is connecting these pieces together. I also, you know, getting back to the – it has the real time. I think it’s also getting back the interplay between immediacy and history. And that’ – a lot of that is where the interest into this kind of way. But if you got all the stuff learning part but you also got (unintelligible) you want to keep for later and that you want make a sense of, a bit of it that will come back and being able to point out of the instantaneous flow into something broader and gather that is a key part of that too. So, we’re starting to see this with the other. And, I think, yeah, the difference between the Facebook and the Twitter or (unintelligible) search was that Facebook were exclusively – I’m not saying that they will let you search them. You know, they were – they were – they’re so very weary of that.

Mr. SCOBLE: Yeah.

GILLMOR: Well, they were saying that when they released it that they – I think there’s some nuances about what they are saying about interaction with Google. I don’t think – I think that they have a congenital mistrust or a strategic sort of opposition to Google which I think is going to go away pretty quickly now the Twitter has basically leveled the playing field between the two major players. You know, Rob, do you agree with that?

Mr. GOLDMAN: I think it’s going to be super interesting to see how that plays because my take is that the Google’s kind of worst case scenario, you know, biggest fear is huge amounts of information accumulating in places where they can’t(ph) organize it. I mean, their mission is to organize the world’s information and if all of a sudden really important relevant information to me is starting to pile up in places that they can’t see, I think that’s the threat to their mission. And I think that was happening in a meaningful way on Facebook. And I think Twitter’s kind of public approach is creating a real wedge between what I think Facebook wants to do, which is to try to keep the information proprietary and organize it for you. And what Google wants to do which is to try to be this kind of thin layer on top of the world’s information that make sense to it. I mean, as long as the information is spread out I think there’s going to be a really important role for people who try to reassemble it. And, you know, that’s what Threadsy is trying to do. We’re trying to do it as a communications tool. And I think that’s what – of course, that’s what Google’s trying to do as a search tool. And I think right now the Twitter news this week I think is probably, you know, causing the Facebook execs to have some, you know, long emotional meeting.

GILLMOR: Yeah. Except that – that doesn’t take into account the FriendFeed acquisition. Because if there’s anything that FriendFeed is about, it’s about this kind of aggregation and the sort of blurring or the normalizing between different data stores. So…

Mr. GOLDMAN: Yup, I can’t wait to hear what FriendFeed’s up to. It may be that they’re the search team that’s going to try to figure out how to surface as much of the information as they can.

GILLMOR: Robert, go ahead.

Mr. SCOBLE: I totally agree. I can’t wait to see whether what Paulo is going to show me soon. He’s already said that he’s going to give me an interview and show me something he’s working on, you know…

GILLMOR: Before he does that, I hope he – that they deliver Stream Splicing which they promised from before the…

Mr. SCOBLE: Well, that might be what he is showing me, right? Because he has promised one other FriendFeed feature that he was supposedly thinking on for a while and Stream Splicing was one that he told me – you that he was working on so. I wouldn’t be shocked…

GILLMOR: But that was in the road map so I wouldn’t be surprised if, you know, the fact that Gary Burd has left the company may or may not have had an effect on that.

Mr. SCOBLE: Yeah.

GILLMOR: Either that means he’s ready or that is not happening.

Mr. SCOBLE: But I think Stream Splicing is really important for getting Facebook into this new world of giving me one feed of all the things I want to watch. I mean, why are we talking of Threadsy, right? Threadsy is doing stream placing of email and Facebook and Twitter into one stream that I can watch on my screen. It’s very useful. And right now, I can’t watch Oprah’s Facebook page along with, you know, TechCrunch’s Facebook page and mix them together into one stream that I watch. I can’t do that. I can sort of do that with, you know, some of these tools but not easily. Here, you know, here on Twitter I can just click, click, click, click, click, add them to a list and now I have those streams spliced together in a useful and easy to manage way.

GILLMOR: We you can’t splice list together.

Mr. SCOBLE: Not list yet but you can sort of see where that’s going to go.

GILLMOR: Right.

Mr. SCOBLE: You know, I’m guessing. You know, this is a race between both tech teams, right? FriendFeed is going to have things that Twitter can’t do easily. I mean, Facebook already has comments. Twitter doesn’t have comments and people keep complaining – I mean, that’s one legitimate thing that we’re still doing on FriendFeed, you know. Over here is my FriendFeed window with the Gillmor Gang. I can’t do that on Twitter and I can do that on Facebook to some extent before it rolls up. The problem is I can’t find that thing on Facebook again.

GILLMOR: The other thing.

Mr. GOLDMAN: I mean, I think the bigger question is just, is it going to end all centralizing in one place? And if it doesn’t, you know, what’s the role of the integrators who are going to try to connect this thing? I mean, to just look at it in practical terms over the last year. I mean, the number of people using social media and regularly updating their status is just – I mean, exploded. I mean, it’s probably 200 million people have come to this in the last 18 months with just huge volumes of new content. So, you’ve got lots of new stuff in lots of new places, and the places are open via API. And to me it’s just a natural – you know, it’s a natural opportunity for integration. And, you know, that’s where we’re playing at Threadsy. And, I think unless it all centralizes in one place, the people who are trying to make sense of it across your sources are going to have a really important role to play.

GILLMOR: So, when you say that that’s where you play, you know, what do you see as the landmarks for your company in terms of what’s you’re going to try and accomplish next?

Mr. GOLDMAN: Well, I think it’s – in a high level, what I can say, is our position is a very special sort of privilege spot on top of all of your communication services. And if we want to sort of deserve that position in your life, we have to add value that you couldn’t get by going to anyone of those services. You know, we’re never going to be able to be the best that everything we do, we’re not going to be the best email client, the best Twitter client, the best Facebook client,, the best social web browser. What we’re going to be is the best integrated communications experience. So, we’re going to try to do things that no single service could ever do. And I think, you know, if you look at great integrators, I think that’s what they’ve done in the past. So, Mint is a good – I think a recent example in the lots of our minds. You know, they had access to all of your financial accounts and they gave you things you couldn’t get at anyone of them. Play like for example your net worth, and so we want to do similarly. We want to integrate all the people you talk to and all the things you’re saying across your services and try to provide value that you wouldn’t be able to get anywhere else. I mean, to Robert’s point, maybe that’s just slicing streams between Facebook and Twitter. And, you know, who knows it might look like something much more complicated.

Mr. SCOBLE: Are you guys working on any curation features? Because once I get everything into streams and I get it my system all working really well and I’m really close to that with Twitter and I’m still working with that on Facebook, but I assume, let’s say that Steve is right, in the next three months we’re going to get all the toys we need to manage our friends and our streams and splice them together and make them usable and make search work and life will be great. The next step is curation. I want to take all that stuff coming across my stream. I want to pick this little tweet or this little Facebook item and shove it out to my audience and explain why that’s important and explain why the person is important who said it.

Mr. GOLDMAN: Yup, yup. So, you mentioned this yeah, once before. I mean, so, we’re very interested in the sharing aspect of your social media kind of command center. And we’re thinking a lot about sort of what the best ways to facilitate that. I mean, so far, we don’t have any meaningful sharing features of our own. We let you, you know, favorite a tweet through Twitter or like a post to Facebook, we’re using the underlying services.

Mr. SCOBLE: Yup.

Mr. GOLDMAN: And, we’ve been talking a lot about sort of what we might do to kind of make that happen with a lot of good kind of sharing tools that are out there, posters and the lots of other things. And so, you know, it’s on our minds but if not, at the top at the road map right now.

Mr. SCOBLE: OK.

Mr. GOLDMAN: I mean, what are you using and what would you like to see?

GILLMOR: Hold on a second.

Mr. SCOBLE: Go ahead.

GILLMOR: Kevin, send video, please. Sorry, Roberts. Just – OK, good. Thanks. Go ahead Robert.

Mr. SCOBLE: Yeah, there’s no good tool yet. You know, for instances, I’m looking at Twitter, right? And I want to share this tweet. My choice is to either re-tweet it out or click favorite on it which will put on my favorite list, or I have to copy – I have to make almost a screen capture of this image, copy the screen capture, and then put it somewhere like Flickr or something, and then link it in and then link in everything, which is really over on word press run posters or something like that. And then, I want to write a blog underneath that, you know, tweet. The tweet is the news. And it’s amazing how much news is breaking in Twitter now. I mean, Marissa Mayer announced the Google deal on Twitter, right? And that was the top – that should have been the top item on everybody’s blog is start there, that’s the news. And then we fill in the details where put in more screen captures, where if I met her in the hallway I’d ask her to demo it for me a record a video. Or I – how did I found about FriendFeed’s news, right? I was walking around the Alamo in Texas and I was looking at my tweets come really – and somebody said, you know, somebody said Twitter or Facebook just but FriendFeed. Well, I immediately re-tweeted that out. And then I immediately got on Blog Talk radio with Paul and the Facebook team and recorded an MP3 file which got put in to FriendFeed. But there was no real good way for me to put it all together as one, long stream and to keep adding on to in. So, as Techcrunch add an article or read, write web, or you know, or see or, you know, anybody in the community as they added more information on I can’t just keep adding on to that item. FriendFeed got really close that’s why it goes – I’m still…

Mr. GILLMOR: What do you mean it got really close? It is really close.

Mr. SCOBLE: FriendFeed does not give the ability to curate without other people involved. I’m sorry. It doesn’t. It does not let…

Mr. GILLMOR: I don’t know what that means.

Mr. SCOBLE: I want to write a blog post without you being able to put your comments in between.

Mr. GILLMOR: Oh, this is the fabulous control of the universe.

Mr. SCOBLE: Absolutely. Does TechCrunch let…

Mr. GILLMOR: As Craig Burton says, get over it.

Mr. SCOBLE: Does TechCrunch let me write a blog post? Give me a break.

Mr. GILLMOR: Get over it, Scoble. It’s just absolutely not going to happen.

Mr. SCOBLE: Do you let me enter into your blog when you’re writing a blog?

Mr. GILLMOR: Do we have to re-run that show for you to…

Mr. GOLDMAN: Yeah, again?

Mr. GILLMOR: I think you at the end of that show and said OK.

Mr. GOLDMAN: No, I didn’t say OK.

Mr. GILLMOR: Why didn’t you say you’re back to – tell me honest – how are you going to control…

Mr. GOLDMAN: So you could be your repress – Steve, can you give me your passwords so I can edit your blog while you’re writing it?

Mr. GILLMOR: It’d be fantastic. I don’t have to do any more writing.

(Soundbite of laughter)

Mr. SCOBLE: If you believe that…

Mr. GILLMOR: If you update everyday…

Mr. SCOBLE: There’s no feed…

Mr. GILLMOR: As long as you…

Mr. SCOBLE: Just give me your – just post your WordPress…

Mr. GILLMOR: You just have to keep, you know, a steady flow of content and I’ll give it to you right after the show.

Mr. GOLDMAN: OK.

(Soundbite of laughter)

Mr. SCOBLE: Just post in the form that -your password – just post it there so that we can all…

Mr. GILLMOR: No, I didn’t say I’m going to give it to everybody. I’ll say I’d give it to you.

Mr. SCOBLE: Oh…

(Soundbite of laughter)

Mr. SCOBLE: (Unintelligible) is a control, too, huh?

(Soundbite of laughter)

Mr. GILLMOR: No, I’m into free content.

Mr. SCOBLE: OK.

(Soundbite of laughter)

Mr. GILLMOR: Kevin Marks, what about Google Wave? Do you think that they’re a threat to Threadsy? I’ll ask you Rob in a minute.

(Soundbite of laughter)

Mr. MARKS: Yeah, potentially in some ways in terms of the e-mail cyber. The Wave is small group collaboration. That’s what is – that’s what its weak spot is. It’s not plugged in to the public, web in the same way. It has the – if you have my Wave address you can send me stuff issue. So, it’s not…

Mr. GILLMOR: Well, they actually do have a public thing that…

Mr. MARKS: They have this sort of send – yeah, (unintelligible) thing…

Mr. GILLMOR: You can add to public identity and it’s available to everybody who’s not – who’s on Wave.

Mr. MARKS: Right. But it doesn’t have…

Mr. GILLMOR: It’s kind of like that other thing that Scoble’s so freaked out about. Sidewiki.

Mr. MARKS: Sidewiki. I ran into Ward Cunningham this week at Web 2 Summit, who’s the mentor of the Wiki, had a chat about this. And he said Google has two parts they call. Wiki’s the arm – Sidewiki and Searchwiki – and one that is a Wiki which they don’t call a Wiki, which is Wave. So his take was that Wave is a Wiki and it feels very like, you know, the first iteration of Wiki that he built where the comments were into leave with the document you’re editing. And then you had to go back and clean them up by hand and so on. So, he was seeing it as sort of an evolution of Wiki Space rather than as an evolution of e-mail.

Mr. GILLMOR: Well, you know, we were – Alex(ph) and I – we’re visited by the Wave team this week. They were sort of, you know, giving us an update on what the progress and so on. And I was sitting next to, or behind Steph’s machine and this is just about the time of the Apple announcement broke. And then they kill this just for the plain(ph) to go by. Hang on a second. And the – it’s just her screen is – you know, she’s got 5,000 Waves that are – that she’s tracking. I mean, probably not that many but a lot. And it’s what Scoble is talking about. It’s kind of what Threadsy starts look like. It’s this – you know, you can see these stories kind of bubbling up and painting themselves at various points on the screen. It’s very interactive and, you know, I think too much is made of, you know, interruption problem and, you know, people jumping in as Scoble is talking about, and writing all over your blog. But, there is at some point what we’re looking for here, when we talk about stream splicing, we’re talking about, you know, what AJAX-enabled, which is this – you know, the stuff it goes back to what Robert care was doing with PubSub and, you know, opening an HTTP connection back on the peer to peer(ph) days. You know, and basically painting little bits on the screen that added up to provide an interactive, socially-aware reference into what’s happening. So, you know, this is where we kind of got bugged down with what Robert’s concern is, and I think they went it as well, about, you know, taking over your page. It’s not your page anymore. It’s the page of the user and how they orchestrate these bits to be able to provide information. It’s not under your control. It’s under their control.

Mr. MARKS: I think – I mean that was – to me that was the interesting thing about the (unintelligible) announced it was social search, which is saying everyone does not have to see the same results page for the same query, which has been true for a little while with local search and national-based result changing and geographic-based result changing. But to say that you now see different results depending on who you’ve told us your friends are that’s very important – for Google…

Mr. GILLMOR: Does that change the economics of – I imagined that it’s both less of a broad reach and also much more of that targeted, therefore, you know, more likely to click kind of audience. So, the – probably the economics go up.

Mr. MARKS: I – well, this is more the search side than the @ sign. So, the primary value there is that you get better search results, I think. Setting ad against social stuff has always been harder but with Google – with Google – when you’re searching on Google we do the term intent of saying I’m looking for X. So, drawing that through your friends that – that – it maybe a wash on the commercial side. You may actually find it, oh, I’m going through my friend’s click as much more compelling than this broader advertising-based on the other side they may see attention that cause it the other way. But overall it should provide more useful information for people searching.

Mr. GILLMOR: I don’t understand why people think that search is about – you know, social search is about your friends. It’s not about – for me, it’s not about what my friends think…

Mr. MARKS: So, you…

Mr. GILLMOR: It’s about who my friends are interested in and what they think. It’s like at least three, you know, separations removed.

Mr. MARKS: Right. But do you think what the – you think it’s about…

Mr. GILLMOR: I agree that is what the listing is about. Unfortunately, there’s no tools. Tthey’re (unintelligible) once again to the third parties to develop all those tools. And once the third party has named Facebook they’re going to have a real problem.

(Soundbite of laughter)

Mr. GILLMOR: Rob?

Mr. GOLDMAN: I mean, so there’s a lot there. I guess – well, so starting with Wave, if you wan to go back there, my take on Wave is very similar to Kevin that is primarily a collaboration tool. I haven’t seen anyone using it in the way you describe Steve where there’s, you know, hundreds of conversations kind of percolating. You know, I imagined that’s probably only the Wave PMs at this point who have that kind of used pattern for it. I think it would be….

Mr. GILLMOR: Well, you know, the reason that’s relevant is that they’re the ones that are designing the product. So, they’re designing from the perceptions of somebody who’s actually, you know, knee-deep in the environment. So, I mean…

Mr. GOLDMAN: Sure. I mean…

Mr. GILLMOR: Other the right and this is going to be a useful paradigm for the wrong, in which case we don’t have to worry about it.

Mr. GOLDMAN: Yeah. I mean, my take is that they’ve done really interesting things with the communication protocol underneath kind of building these Waves and message together, the ability to kind of see what happened over time, rewind and playback. What I think they’re missing is what Threadsy is trying to do, which is pull people together across their services and Wave, you know, say what you want about what it can do. It can’t do that, at least not yet. And I think there’s also something kind of important that they’re missing in the way that people are sharing concept today, which is by and large not through small group collaboration and more in the sort of broadcast model either the Twitter style or the Facebook style. And I was surprised to see that more or less missing from Wave. It’s kind of a very slight extension of the e-mail-sharing models as supposed to kind of whole field adoption of the new more sort of social-sharing models. You know, in terms of the way social search is going, I’m with Kevin as well. Again, you know, I think different search results based who your friends are is more interesting in many cases than searching your friend’s stuff. And I think Google is in a very unique position to be able to kind of experiment with that.

Mr. GILLMOR: And what about you? Are you starting to see synergies? What’s your user-based right now? I’m sure you’re not going to tell me but…

Mr. GOLDMAN: Web, the user-based?

Mr. GILLMOR: Yeah.

Mr. GOLDMAN: Oh, we’re still in private data and, you know, not talking about using up (unintelligible) anything like that but I guess I would say is that if anyone wants a second out(ph) go to Threadsy (unintelligible) and we’ll send out invites (unintelligible?).

Mr. GILLMOR: I think Google is trying to jam your signal when you said your – give your – say that once more. How do you get there?

Mr. GOLDMAN: Www.threadsy.com and sign up for an invite.

Mr. GILLMOR: So, that’s to be approved personally by you?

Mr. GOLDMAN: That’s to be what?

Mr. GILLMOR: Does that have to be approved personally by you?

Mr. GOLDMAN: Absolutely, not. No. We’re sending them out to, you know, everyone who’ve comes right now.

Mr. GILLMOR: But you won’t tell me how many?

Mr. GOLDMAN: I won’t say how many. Lots.

Mr. GILLMOR: And what are your plans in terms of going, you know, broader, so that people can – once they’re in this system they can invite people.

Mr. GOLDMAN: Well, so it has been fantastic to talk to these early passionate users and see how they’re using the products and what they want from the product, and we are trying to respond as quickly as we can. So, we just added last week the ability to talk back to Facebook so you can now comment back on your Facebook streams and like things directly from Threadsy. We’re bringing your wall post in now and that was a very frequent request from the users. And we have a bunch more of the sort of top-of-the-list needs that we want to take care of and then we’ll open it up.

Mr. GILLMOR: Can you pipe Facebook comments out to the broader network?

Mr. GOLDMAN: No – like re-tweet of Facebook comment essentially?

Mr. GILLMOR: Uh-uh.

Mr. GOLDMAN: Not right now.

Mr. GILLMOR: Is that a violation of the Facebook Connect terms of service?

Mr. GOLDMAN: You know, I think – that’s a good question. I mean, you can cut and paste and do whatever you want with what’s in your stream now. There are limitations about how you can store it on the server side. So, I mean, my sort of quick off-the-top-of-my-head answer is it would depend on the implementation.

Mr. GILLMOR: Well, if it was, you know, a status stream of somebody who is – declares themselves the every one status, in other words, open it would follow logically that somebody who’s commenting on that is essentially dealing(ph) that conversation element to the open space.

Mr. GOLDMAN: You would think….

Mr. GILLMOR: Right, so…

Mr. GOLDMAN: That you would think they spoke – would be, you know, excited about having that spread.

Mr. GILLMOR: Well, wouldn’t you like that, Robert, if there was some sort of way of being able to – I mean, I find these orphaned Facebook conversations incredibly annoying.

Mr. SCOBLE: Oh, they’re horribly annoying, you know. When you – when you, you know, chat in Facebook conversation – I was just doing that – it disappears and then you can’t get back to. You can’t even search for it. It’s ridiculous.

Mr. GILLMOR: Right. So, what do you think it’s going to happen there? Is there going to be a third party’s? I mean, even…

Mr. SCOBLE: No. That’s something on Facebook themselves has to solve and I think that’s why they bought FriendFeed. And that FriendFeed always left me get back to my old conversations. Every conversations had a permanently. Every conversation was searchable and I can’t do that on Facebook. It was very frustrating. It’s one reason I haven’t put a lot of effort into Facebook yet. When I do get that then I’m going to re-look at Facebook.

Mr. GILLMOR: So, Rob, what is the – how do you walk up to Facebook data? How do you manage this kind of confusing on ramp(ph)?

Mr. GOLDMAN: You mean, how do we integrate it into Threadsy?

Mr. GILLMOR: Yeah, I mean, you’re using Facebook Connect, right?

Mr. GOLDMAN: We’re using Connect and we’re being really careful to make sure we’re staying in compliance with all their terms of use. And we’re trying to give you as much control as we have kind of inside the playing field that they have set for themselves. And, you know, I think there are big limitations on what you can do with Facebook Content that don’t exist in the case of Twitter Content. And I think right now, that’s a challenge for Facebook.

Mr. GILLMOR: So, in terms of this Talk Back, you’ve just enabled the ability talk back into the Facebook stream, correct?

Mr. GOLDMAN: That’s right. And, you know, it wasn’t like a super straightforward easy API use case but it’s there now, it’s live and it’s working really well. So, yeah, you can comment. You can talk back on wall post. You can comment on things in the stream. You can like things, you know, all the sort of everyday use cases for Facebook you can do inside Threadsy.

Mr. GILLMOR: So, inside Threadsy, you’ve got what we’re all looking for outside of Threadsy.

Mr. GOLDMAN: I guess you could say it that way. I think you all wanted inside Threadsy.

Mr. GILLMOR: Well, that’s fine…

Mr. MARKS: So, what’s with me(ph) of Threadsy was that I go there and it says give me all your passwords and it’s not using delegated (unintelligible). And I went on that page and I thought, hmm, no, there are better ways to doing this – this way.

Mr. GOLDMAN: Yeah. Well, I saw your comment there. Well, so – I mean, we are implementing Twitter OAuth right now and we implement Facebook Connect. So, in the case of that social media service that has sort of developed, you know, password policies with OAuth, we don’t know your passwords. We don’t want to know your passwords. We just want to do whatever you want us to do with that content. In the case of e-mail, we’re kind of stuck in sort of yesterday’s, you know, authorization architecture. And there’s basically no way for us to get your e-mail without your password today and as soon as that’s available we’re all for it. I mean, we’re not – you know, we’re not anxious to fix things you don’t want give us. We just wanted to deliver the service and right now with e-mail there’s no other way to do it.

Mr. MARKS: I thought there was a pre-based API for e-mail.

Mr. GOLDMAN: I’m sorry?

Mr. GILLMOR: What did you just say, Kevin?

Mr. MARKS: I feel there was pre-based API for e-mail but I may be wrong there.

Mr. GOLDMAN: Well, so you can OAuth with Gmail but you can’t…

Mr. MARKS: Yeah.

Mr. GOLDMAN: Get messages and just get headers. And that – that doesn’t really do it if you want to be an email client.

Mr. MARKS: Right.

Mr. GILLMOR: Robert, you’ve been following the chat, right?

Mr. SCOBLE: Yeah.

Mr. GILLMOR: Any interesting questions that are bubbling up there that you want us to put here?

Mr. SCOBLE: One was that Ken Sheppardson asked if Facebook still prevent developers from caching data for more than 24 hours. What’s the terms of service – the state of the terms of service? We should do a blog post on that, by the way. What’s that – what’s that looked like…

Mr. GILLMOR: That was the Facebook Connect contract, wasn’t it? So is, right? Rob?

Mr. GOLDMAN: Yeah. So it’s covered in Connect, you should check the terms on. I can’t speak to what the current terms are in detail, but what I can say is Threadsy uses the client’s side version of the API so our servers are pretty much out of the loop when it comes to Facebook. It’s all happening down on the client.

Mr. GILLMOR: All right. I just want to walk around the table one more time and then we’re going to wrap this up.

Mr. GOLDMAN: We’re not going to talk about Windows 7 or Flickr tags or anything?

Mr. GILLMOR: Windows? How about server leg(ph), huh?

Mr. GOLDMAN: Looks pretty good.

Mr. GILLMOR: It’s getting better all the time.

Mr. MARKS: Flickr – Flickr people APIs do about – people (unintelligible) people tagging us it’s nice. But it does point out the issues that in each of these cases you could only point to a person whose number does the service. That makes that more obvious when it’s Flickr and with Facebook as well. Certainly what these – and got all these photo tagging things but they’re all bound to the members(ph) of a particular service, you know, the bridge across services that’s going to be a bit more important. That’s why – I thought what was exciting about Threadsy is potentially you’re getting a bundle of different identities from me and correlating them. I think that’s a very useful concept. But the fact that we’re doing it through giving all your passwords it was – it gave me a pause. That said, OK, that’s…

Mr. GILLMOR: Right.

Mr. MARKS: I’m not ready to give you the ability to impersonate me on Google yet.

Mr. GILLMOR: We walk before we run, right?

Mr. GOLDMAN: I promise we won’t.

Mr. GILLMOR: But I mean – you know, real question…

Mr. GOLDMAN: You would know my (unintelligible) account.

Mr. GILLMOR: I mean, the problem with that Flickr thing, I was sent an e-mail. They’ve got some new marketing campaign around this new tagging feature, right? And I wasted about half an hour trying to find out what my Yahoo! Id is and getting wrapped(ph) for the 10th year in a row.

Mr. MARKS: Yeah.

Mr. GILLMOR: I mean…

Mr. MARKS: Yeah, Yahoo! use two-week time out is already a bad idea.

Mr. GILLMOR: Well, how about a 10-year time out? When do I get my name back? I mean, I entered it on some email address that I’ve long since been fired from and…

Mr. MARKS: Yeah. We’ll that’s why, you know, she bundles. This is one of the things that frankly got very right, which was when you sign in with your old Google ID, your old Facebook ID and your old Twitter ID, it wraps them together and then you can use them again overtime with – and you (unintelligible) with anyone you need to pull it back together again. Which means that you don’t have – you don’t have this – oh, I don’t have that email address anymore because the bundles are wrapped together. I expect to see more of that every time as well.

Mr. GILLMOR: Well, I’m still – how’s that blocking of Scoble going? I block Scoble the other day just so we could test out the – whether or not that was, you know, propagated across Lists and it turns out that it’s kind of broken, right?

Mr. SCOBLE: Somewhat. First of all, I can still go to Steve Gillmor – you know, twitter.com/stevegillmor and I can still obviously see your page even though…

Mr. GILLMOR: Yeah, I can write Scoble too, but that doesn’t mean that it’s going to be…

Mr. SCOBLE: And I can’t – oh, this user has blocked me from following them. So, I can’t follow you and I can’t put you on a list ’cause there’s no list here because you blocked me. But, if I went to a list that you’re listed on – let’s see if I can find on that has a small number of people. So, this easy Julie trend has list – has put you on a list.

Mr. GILLMOR: All right. How do you spell that? I got to block them too.

Mr. SCOBLE: No, I’m not going to let you do that. And I can see you – you are still – I can still see that you’re on this list. And I can still click on you. I just can’t – you know, I can’t automatically, you know… I can see that…

Mr. GILLMOR: OK. So, there’s a hole there.

Mr. SCOBLE: I’ve (unintelligible) you’d blocked me. But it’s on like FriendFeed – on FriendFeed if you blocked me I couldn’t see you. I couldn’t – you wouldn’t show up in search…

Mr. GILLMOR: That’s why I mentioned in the context of what Kevin was talking about. FriendFeed really closed the holes in this architecture and Twitter continues to have these weird side cases.

Mr. MARKS: Well, I said the thing that I found wrong with the Lists stuff in Twitter is that if we make a Gillmor Gang list, it filters out as acting each other. It doesn’t show us talking to each other within that list, whereas, you know…

Mr. GILLMOR: As you know, I don’t really consider that to be a limitation since the @ sign I think is broken to begin with.

Mr. MARKS: You know, but that’s a separate – you know, that’s a separate debate. The point is that hiding a chunk of the stuff we say even if we’re talking to each other. So actually…

Mr. GILLMOR: Right. So, you have to put a period, and unless you’re like me and you just take the @ sign off and everything is fine.

Mr. MARKS: I think – that doesn’t look at all. Yeah.

Mr. GILLMOR: No, it works fine. And when you have clients like Threadsy respecting, you know, doing a look-up on Twitter for a name, a username, and lighting that up, then the @ sign goes away too. That’s then would rack a 139 characters.

Mr. MARKS: Yeah. But my point is that the way to do what List does at the moment is to make a new account and follow a bunch of people and then you can use that account as a proxy and you can share that with other people.

Mr. GILLMOR: Right I don’t understand it. That’s what Scoble says, right?

Mr. MARKS: So that’s – I mean – well, if you’re using what – if you’re using…

Mr. GILLMOR: To get over the 200 limit or the 500 limit or – what is it?

Mr. SCOBLE: For what? For numbers, it’s 500 officially, although I found out last night that Twitter can white list you into a longer least limit. So, we’ll talk about that…

Mr. GILLMOR: You know what? I can’t wait for – I can’t wait for the suggested user list list.

Mr. Mr. SCOBLE: Well, it’s not – it’s suggested they mark the special user list web…

Mr. GILLMOR: Yeah. There are two people on the suggested user list list, right now. Microsoft and Google.

Mr. SCOBLE: Yeah. They get their full feed. That what we all want, we want to feel those – suck down that 10 terabytes of a bit or a gigabytes of data a day and…

Mr. GILLMOR: Let them eat cake. All right. So, Rob, final thoughts?

Mr. GOLDMAN: You know, no, it’s been a great conversation. I mean, my take is that, you know, at a high level, everything we talked about is really kind of part of, you know, logical and expected sort of expansion of innovation as all of this communication stuff is kind of shifting underneath our feet. It’ll be interesting to see how that goes over the next couple of years and then it’ll probably comeback together we kind of have our patterns established and we have a kind of winners and losers. So, I think right now, you’re going to see lots of exciting new things and you know, Threadsy is just kind of one of the voices that are emerging to kind of put these things together.

Mr. GILLMOR: Robert?

Mr. SCOBLE: I’m having fun out there looking at all the stuff and playing a bit. I don’t have too much to say other than I have Windows 7 behind me and say, I want to go play with that.

Mr. GILLMOR: OK. And you got FriendFeed in front of you.

Mr. SCOBLE: FriendFeed, Facebook Twitter, and a few other things. Threadsy.

Mr. GOLDMAN: Threadsy.

Mr. SCOBLE: Yeah, I’m playing with it. First of all, I can’t get in for some reason even though I deleted the cookies like you suggested and the UI is still (unintelligible). And the other problem with U is I’m doing – I’m doing probably somewhere around 80% of my social networking on my iPhone. And it’s tough for me to see a role for Threadsy there until you get an iPhone client.

Mr. GOLDMAN: Oh, yeah. So, you know, you’re not the first person to have said that. We’re thinking a look about that.

Mr. GILLMOR: And what about support for FriendFeed?

Mr. GOLDMAN: Threadsy support for FriendFeed?

Mr. GILLMOR: Uh-huh.

Mr. GOLDMAN: Probably will happen first with RSS.

Mr. GILLMOR: How do you mean by that?

Mr. GOLDMAN: Well, I mean, all the FriendFeed search and lots of the FriendFeed stuff is just available via RSS so it’s just the easiest path in, I think.

Mr. GILLMOR: What’s the delta in terms of delay?

Mr. GOLDMAN: Oh, I don’t know. That’s a good question.

Mr. GILLMOR: So you haven’t explored South or PubSub PubHubbub?

Mr. GOLDMAN: Well, we looked at it but – I mean, not seriously. We just have too much on the plate.

Mr. GILLMOR: So, you don’t see yourself as competitive with them?

Mr. GOLDMAN: No. I mean, I think it’s an enabling technology that we could integrate and should, you know, especially once there’s some consensus.

Mr. GILLMOR: So, you might wait until some of those feature service in Facebook?

Mr. GOLDMAN: Yeah, I mean. I’m – I think we’re all, you know, waiting with bated breath to see what happens to FriendFeed.

Mr. GILLMOR: Well, the reason I asked you is that if you do come up with an iPhone client, there’s a hole you could drive a truck through for a decent FriendFeed iPhone client. So, you could solve a number of problems with a single shot. OK.

Mr. GOLDMAN: I’m making notes.

Mr. MARKS: So, I – have you looked to the activity stream stuff yet? That’s another push-push over the Threadsy is. The activity stream spec is designed to do this kind of intra-operation that has a chunk of interesting stuff and it’s already got MySpace, Facebook, NetFlix and a bunch of others who are outputting stuff in that format. So, I think that would make sense for you to look at that that may give you a way to do a sort of feed-based integration that you can then use in several places.

Mr. GOLDMAN: OK. We’ll look. We’ll take a look. Cool.

Mr. GILLMOR: All right. This is Steve Gillmor. This has been the Gillmor Gang. I want to thank everybody who showed up. Robert Scoble, Rob Goldman, Kevin Marks, a brief appearance from Dan Farber, driving my director crazy with – I never get this right. Again, I want to thank Rackspace for sponsoring the Gillmor Gang Live on Building43.com. And this TriCast is brought to you in conjunction with New Tech. And I want to thank everybody who showed up and especially those who didn’t. We’ll see you again next time. Bye-bye.

Mr. MARKS: Thank you.

Mr. GILLMOR: Thank you.