Sure enough, two posts from developer Noel Portugal’s Oracle Application Express blog describe OraTweet’s origins:
- Post Updates to Twitter from APEX (PL/SQL) “It is an Oracle internal “Twitter” with some key advantages such as the ability to follow groups and IM (XMPP/Jabber) integration.”
- OraTweet – Tweeting on the Enterprise on August 26th It’s connected to their internal IM, so users can tweet from their existing IM clients.
Eventually one of their teams “stumbled over OraTweet while looking for a solution to bridge the communication gap within their global team.” They began to pilot test it and others stepped in to help with development.
“After one week of alpha/beta life and not much internal advertisement OraTweeters numbers went from a dozen to the hundreds and is still growing, which shows that there is a hidden demand for internal communication tools like this. I like the fact that OraTweet flattens enterprise hierarchies and opens communication between all levels.”
Jake Kuramoto’s Oracle Apps Lab post fleshes out how groups work (“more like topics than groups”) and describes the hidden demand they are noticing:
The warm fuzzy of having an app behind the firewall brings out the hidden demand. Hidden demand opens a new user profile to your app too, since most hidden demand users won’t use the consumer version of your social network or micro-blogger, they bring a clean slate of experience to the party. As a designer/develoer, this helps focus the tool.
Jake’s post has the most narrative about how the tool is working and what it integrates with (no longer with Twitter).
I’m also talking with some of the grassroots internal user-advocates by email, and will post those remarks when available.
Humorous aside, someone on OraTweet (wisely) reads TwitterKarma developer Dossy Shiobara. His August 19th tweet: “My blog’s referrer log just picked up oratweet.us.oracle.com – I wonder what _that_ web host does. ”