-
Website
http://www.scripting.com/ -
Original page
http://www.scripting.com/stories/2007/11/21/buildingTwittergramIntoARe.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
eas
55 comments · 4 points
-
AndrewBurton
134 comments · 10 points
-
Michael Markman (Mickeleh)
154 comments · 16 points
-
Rex Hammock
52 comments · 9 points
-
malatmals
81 comments · 3 points
-
-
Popular Threads
-
How I develop formats and protocols. (Scripting News)
1 day ago · 11 comments
-
Open is in the eye of the beholder. (Scripting News)
3 days ago · 13 comments
-
Store Twitter URLs in earth's oceans? (Scripting News)
5 days ago · 16 comments
-
Why today's Twitter is like Napster in Y2K. (Scripting News)
5 days ago · 15 comments
-
If you wrote the words you own the copyright. (Scripting News)
5 days ago · 7 comments
-
How I develop formats and protocols. (Scripting News)
But what really matters is what *you* think of it and TwitterGram, and where we should take it.
Last night Loic asked me why I don't bring the question to Scripting News readers, and I didn't really have a good answer, so I decided, what the heck, let's go.
http://www.loiclemeur.com/english/2007/11/daveu...
I think it's an interesting idea and would be interested in talking about it further. I think there is significant opportunity with all the different mediums and the different usages for different scenarios. I.e Twittergram/Utterz is great for on-the-go entry as audio input is easy. Output/playback is more complicated and requires more/different infrastructure than say Twitter. But that's okay because I'm much more likely to use Twitter when sitting in front of a computer.
OTOH if I want to put a lot of information in a short chunk, seesmic now becomes a/the desirable interface.
--Jauder
PS Not sure if you remember but I met you at the HP Garage visit..
Here is (crazy?) a workaround, based on client capabilities. First, you will have to generate your own "tinyurls", so that twitter is not tempted to shorten them (from what I read, you already do this). Second, your web app, should be able to respond with different data types depending on the "Accept:" field of the HTTP request.
Now, let's say twitteriffic (or any client) is "TwitterGram-savvy". Once it finds a url, instead of displaying it, it does an HTTP GET request to it, using "Accept: image/jpeg" and your server replies with an icon, a thumbnail (or whatever image you deside) that the client uses to link to the URL. This will work with other media types as well, a video icon for video links, a thumbnail of a photo, etc.
Non TwitterGram-savvy clients will keep working as usual, nothing breaks.
How about it?
Here's mine...
http://mp3.twittergram.com/davewiner/rss.xml
Anyway, I have a conference reporting gig I do and I'd love to have people call a phone number and have their messages posted to a twitter/feed right away - I'm sure there are a few ways to do this, but it needs to be dead-simple and to my knowledge most services out there aren't right now.
Here are my thoughts about twittergram in the form of an audio post http://www.utterz.com/~u-NDk3NjkzMw/utt.php
Here is an example of a post my friend did about computer classes in Uganda that I posted to my tumblr from utterz http://christianburns.tumblr.com/post/19811032 notice the replies from people that he does not even know.
This is separate from Twittergram or Utterz, but is a more general thought on how Twittercasting of any media type could be done (video, presentations, pictures, whatever).
Dave's Twittergram Tweet from earlier would be expressed as:
--- Phoned-in TwitterGram
url: http://tinyurl.com/yqxfl6
type: mp3
I've posted some more examples, caveats, a further explanation of YAML and some other thoughts at: http://tinyurl.com/yv435p
Like Alan Levy, I'm glad to see you are thinking about building a business around twittergram. My only suggestion is to make certain that you legally dot every "I" and cross every "T". Although it might seem contrary to the sense of community we seek to build, sound contracts with the people you decide to work with are essential. It's better to pay a few thousand dollars now rather than millions later.
But I was thinking if these people can call into a special number and record their interaction / update with a client as a twittergram, The data could be made available thru twitter to the followers, also the mp3 could be loaded into the CRM system for that particular customer reference, And if required the backend staff could access the same and make updates. Of course can evaluate speech to text and do some cool stuff with that as well and extend it further.
As a start Twittergram could set this functionality up with Salesforce.com as a part of the App exchange.
Would love to hear your thoughts?