Comments on: Social Observations, OraTweet Edition

By: SV iPhone Developer Meetup - Oracle / Linkshare | stuart henshall

SV iPhone Developer Meetup - Oracle / Linkshare | stuart henshall — Wed, 18 Mar 2009 04:58:36 +0000

[...] Oracle provided an Enterprise view to a group that largely seems to be busy with consumer concepts. While simple the app had to deal with a [...]

By: Yammer Gets Bronx Cheers from the Blogosphere. Why? « I’m Not Actually a Geek

Mon, 15 Sep 2008 14:59:44 +0000

[...] Yammer is more likely to bump up against SAP’s ESME and Oracle’s OraTweet. [...]

By: Enterprise Alley mobile edition

Enterprise Alley mobile edition — Thu, 11 Sep 2008 13:07:09 +0000

[...] context and purpose are aligned. You’ve got a new Twitter? Get in line. So has everyone else. Even Oracle. Therein lies the conundrum. Developing a new Twitter is easy. Developing one that as enterprise [...]

By: Time to stop talking about talking « TalentedApps

Time to stop talking about talking « TalentedApps — Fri, 29 Aug 2008 20:39:59 +0000

[...] are embracing social media for individual, corporate and customer [...]

By: Jake

Jake — Wed, 27 Aug 2008 20:53:50 +0000

Groups actually covers a few use cases that are not entirely related.

1) Grouping my own contacts so I can listen to channels and control the noise. Twitter doesn't do this, but TweetDeck does. This is a UI problem.

2) Group tweeting, e.g. AppsLab, means membership and probably privacy controls. Think of groups in Connect, public or private with members. Join the group and you receive any tweets @ that group. Your solution now meets the public side of this, but not the private one that I can tell.

3) Tweeting as a group is lower on my list since it hides the identity of the tweeter, but it would be useful for broadcasts and information.

We can discuss more if you like. You might want to get Matt Topper involved too, since he's been using Twitter for a long time and has enhancements to it in his head.

By: Jake

Jake — Wed, 27 Aug 2008 20:44:29 +0000

There's definitely overlap with IM and group chat, but what I like about Twitter is its asynchronous nature. You don't expect immediate responses, which is born of Twitter's original use as a micro-blogging tool.

Another difference: RSS allows you to eavesdrop on a stream without participating, making it a good status collecting application.

It definitely has useful applications inside the firewall, and I'm sure someone will come up with new ways to use it, e.g. as a bot like Firebot.

By: noelportugal

noelportugal — Wed, 27 Aug 2008 06:23:18 +0000

Here is what i see…you say no groups, suppose I “subscribe” to a group you belong, If I understand correctly what your are saying is that if we belong to the same group all your tweets will be received by me regardless the topic, right? Now when using @Group if i follow that group i will get the tweet regardless if I'm following you or not…therefore clearing the air for me…The way is setup now, lets you follow groups and individuals in that way if I only care to “listen” for @AppsLab topic i just follow that group…what do you think?

By: Ed

Ed — Wed, 27 Aug 2008 06:20:45 +0000

Yeah, it was me. A while back on OraTweet. I think me and Carl and Noel and someone else (I forget who, sorry) talked about it a bit. As you say, got lost in the noise!

Not being fully clued up on all this Twitter stuff, perhaps I can ask; if OraTweet adds groups and (possibly) the ability to Tweet specifically at a certain person, then doesn't it begin to converge with IM and the Chat Rooms therein, or some sort of IRC? As far as I can see it's just the web interface and possible phone/SMS integration that differentiates it.

By: Jake

Jake — Wed, 27 Aug 2008 05:41:13 +0000

I don't know honestly, but I assume it's you? Where? On OraTweet? I must have missed that. No groups, no way to control the noise.

By: Ed

Ed — Wed, 27 Aug 2008 05:33:13 +0000

> So, +1 for 140. I would apply it only to the message payload…

Hmm, someone else suggested that recently. Now who could that have been?

By: Jake

Jake — Wed, 27 Aug 2008 02:19:44 +0000

I don't have that problem. We're also talking about very niche networks, i.e. Twitter, Friendfeed, so I suppose it doesn't really matter. People come to the party without that expectation.

By: carlback

carlback — Wed, 27 Aug 2008 01:58:22 +0000

Yeah is a hard choice, I just hate having to split up comments or worse sending something out that gets cut without me knowing.

Freindfeed allows for more and I don't see too many uber huge posts.

By: Jake

Jake — Wed, 27 Aug 2008 01:43:54 +0000

Hmm, I like the 140 character limit, if only for its history as the standard. It does keep brevity top of mind. I've never enjoyed IM'ing with paragraph writers, too much work for both sides.

So, +1 for 140. I would apply it only to the message payload, since the handles are longer, or bump it up to accommodate them, but not too much to keep it brief.

By: carlback

carlback — Wed, 27 Aug 2008 01:35:20 +0000

Since we aren't constrained by SMS the char limit will probably go away. We won't be broadcasting out 800chr posts but you will be able read them through the web interface, and whatever interface you make with the API.

By: Jake

Jake — Wed, 27 Aug 2008 01:24:05 +0000

Very cool. That helps a lot. Let me know when it's ready, since I'd rather type @AppsLab than @ all of our IDs.

Also, the 140 character constraint shouldn't apply to user names, due to their length IMHO.

Can't wait to do OS and roll it into my Connect home page.

By: noelportugal

noelportugal — Wed, 27 Aug 2008 01:09:23 +0000

Jake, regarding groups, we do have the functionality to send tweets as a group but it's part of the unreleased update API. Basically the owner of the group that has the right credentials can post updates as a Group…this will be useful for triggers say on this blog…This post title can be posted on the @AppsLab group by AppsLab..then all the group “followers” will be notified.