Archive

Posts Tagged ‘service’

Simultaneously Publish Your Content to the Web, Facebook, iPhone and iPad

July 10th, 2010 No comments

Quick Pitch: Publisha is a free browser-based solution that allows integrated publishing across digital platforms with built-in social media, analytics and revenue streams.

Genius Idea: Publisha is a free new platform that enables users to simultaneously format and publish content to the web, Facebook (Facebook), RSS, iPhone (iPhone) and iPad from a single dashboard.

You can import and host your blog or online publication on publisha.com, or keep it at its current domain and simply take advantage of the service’s Facebook, iPhone and iPad publishing features.

The Facebook app is particularly robust. It creates an articles tab you can add to your Facebook Page, complete with a searchable archive, polls and other interactive content. Readers can like, rate and comment on the articles, and respond to polls.

You can also use the platform to publish your content on Publisha’s iPhone and iPad apps; the company has also offered to help “qualifying early adopters” create their own branded apps and drive traffic to their content. The apps host all participating publications on Publisha’s network. To minimize the size of the app, audio and video content are not supported.

Although Publisha is free to use, the company will take a 20% cut of all ad, affiliate and subscription revenue, and charge $2 per every GB of bandwidth used beyond 10GB if you decide to host your publication on Publisha’s website. It will also use 20% of your ad space if you have a free account. Publisha eventually plans to offer two premium packages — priced at $50 and $250 per month, respectively — that offer more bandwidth and take a smaller share of revenue.

Publisha’s Head of Marketing Anna Sjostrom also told us that an aggregated ad service is in the works, which will help match publishers with advertisers. The company also plans to add support for the Kindle and other e-book readers, as well as Ping FM and podcasts.

While we think the costs of Publisha’s services are pretty steep for users who want to build up a publication on publisha.com, we think many could take advantage of Publisha’s Facebook app and keep their sites on a blogging platform like Wordpress (WordPress) or on their own domains. It also couldn’t hurt to push your content to Publisha’s iPhone and iPad apps in the interest of attracting new readers.

What do you think of Publisha’s offerings? Do you plan to use them for your online publication?

from here

, ,

Powered by ScribeFire.

The rest is here:
Simultaneously Publish Your Content to the Web, Facebook, iPhone and iPad

Share/Save/Bookmark

Thoughts on Opera Unite

June 17th, 2009 No comments

Thoughts on Opera Unite

Opera UniteI met today’s news about Opera’s new initiative — called Unite — with a mix of shock and awe.

On the one hand, I was sickened by the lack of analysis from the echolalic blogger news corps. It appeared that Opera PR had successfully reached out to all of them, shoved a news release down their throats and waited to give them the go-ahead to regurgitate it on their blogs, using the same screenshots, same content, and differing only in the pithiness of their post titles.

Of course, I could have gotten the same depth of analysis from half a dozen tweets.

Maybe they long ago wrote off Opera and aren’t interested in providing any kind of depth of insight but whatever, who knows — the nouveau press corps blew it. Social media proves its vapidity once again.

But, I digress. I’ll tell you what I think, since there’s a lot in the details of Opera’s announcement that bear inspection, even if I’m the only one to do it.

I’m going to talk about six topics:

* What is Unite?
* The Marketing Pitch
* Why isn’t Opera open source?
* Is Unite really decentralized?
* Owning Your Namespace
* Unite & Activity Streams

Let’s get to it.
What is Unite?

Like Flock before it (Disclaimer: okay, I’m just stroking my own ego here. Note to self: get over yourself), Opera is attempting to take advantage of the rise of social networking (the verb) and bake it into the browser, as a personal extension to one’s computing experience.

They accomplish this by embedding what amounts to a web server in the browser, and making it possible to share files, music and photos and to post notes or chat directly with your friends (or anyone who knows the URL to your account and in some cases, has the right password).

You can download an Opera Unite alpha build to try it yourself.
The Marketing Pitch

Opera Software

The marketing hype for Unite started recently, with a bright red page (above) hosted at opera.com/freedom. Of course this inspired a bit of buzz, and Kas Thomas from CMS Watch even guessed correctly what it was all about:

Folks, let me tell you what’s going to happen. I have a pretty strong hunch (but no inside info, I assure you) on this one. This is something I’ve thought about for years — it has needed to happen for years — and I’ll be thrilled if Opera pulls it off, although whether people will flock to adopt it is another question.

The answer is that Opera is going to embed a web server in itself.

When you fire up Opera, you’ll be operating a secure server and you will be able to serve all kinds of content (whatever you want, basically: bookmarks, contacts, cached content, arbitrary files from a roped-off area of your local storage, web pages of your own) to other Opera users, at the very least, and maybe all browser users, at the very most.

The mystery seems to have paid off, as Unite is topping Techmeme today.

They released a stylized video explaining Unite, remniscent of the Data Portability promotional video from several months ago:

What I find so fascinating about this marketing message is that it presumes that owning one’s own data and “connecting directly” with friends is somehow relevant to people — as though it’s a big problem that people have been complaining about for years, and that Opera has finally answered the call.

But I think they’re missing the big picture here — or intentionally obscuring it — which is that, while the idea of owning your own data may be attractive to neo-libertarians and open source geeks — most people really don’t care and are happy to outsource storage of their data to someone else who can be responsible for backing up their data and fending off hackers. 200 million Facebook users can’t be wrong, right?

People have embraced social networks because they make it easy to share and collaborate using the browser that they already have — and answering the question: “what do I do with all these stupid digital photos sitting idly on my harddrive?”

Let’s face it, bookmarks were pretty lame before we could peak over our friends’ shoulders at what they were reading.

So while Opera is right to seize on to the social networking meme, they’re doing so largely to increase the waning relevance of their browser — not to support freedom as they claim — especially at a time when Google’s Chrome and Apple’s Safari have entered the ring as the new twin contenders for the browser crown (even though no one knows what a “browser” is).

Furthermore, their whole pitch about owning your own data and disintermediating the large social networks will likely resonate much more with a European audience (i.e. one that would give 7.1% of their vote to the Pirate Party) than a mainstream, social network-obsessed American one.

If you consider how Lawrence Eng (Opera’s product analyst) puts Unite into context talking about “the Internet’s unfulfilled promise”, you’ll see what I mean:

Our computers are only dumb terminals connected to other computers (meaning servers) owned by other people — such as large corporations — who we depend upon to host our words, thoughts, and images. We depend on them to do it well and with our best interests at heart. We place our trust in these third parties, and we hope for the best, but as long as our own computers are not first class citizens on the Web, we are merely tenants, and hosting companies are the landlords of the Internet.

Social networking is important, but who owns it — the online real estate and all the content we share on it? How much control over our words, photos, and identities are we giving up by using someone else’s site for our personal information? How dependent have we become? I imagine that many of us would lose most of our personal contacts if our favorite Web mail services shut down without warning. Also, many of us maintain extensive friend networks on sites like MySpace and Facebook, and are, therefore, subject to their corporate decisions via “Terms of Service” and click-through agreements. Furthermore, what does it mean anyway to be connected to hundreds of our “closest” friends? What about our real social networks, the people we want to interact with on a regular basis (like once a week, or even every day)? Why are online solutions to help us with our real-world social needs so few and far between?

We are connected to a Web that has democratized much and is an amazing source of information. However, “the wisdom of the crowd,” along with the notion that our data ought to live on other people’s computers that we don’t control, has contributed to making the Internet more impersonal, anonymous, fragmented, and more about “the aggregate” than the individual. In fact, quite the opposite of the original promise. For too long, we’ve been going online to connect to each other, but sacrificing intimacy as a result.

With Opera Unite, I think we can start moving in a different direction.

Now, it might sound ironic coming from me that I think Opera was wrong to paint their pitch with the paint of libertarian ethos, but if they’re going to succeed, they have to go beyond “owning your own data” to talking about why owning your own data is better or easier. Philosophical rhetoric will only get you so far, as I’ve learned.

Speaking of…
Why isn’t Opera open source?

So, with all that raging neo-libertarian angst, why isn’t Opera open source?

Quite frankly, I have no fucking clue. And with Webkit giving everyone — including Mozilla — a run for dominance over the personal viewport to the web, I simply don’t see why anyone would build on the Opera platform (albeit, their platform is largely the web — though their rendering engine remains proprietary).

Could it be failure of imagination? Is it that Opera hasn’t figured out that the future of the web is in hosted and delegated services? Or, is it that they did figure that out, but desperately want to defeat that future in order to write an alternative future with their browser at its center?

In 2006, Opera didn’t see a business model for open source browsers. Little has changed since then, except that they now have three formidable open source challengers to contend with that have shipped “cloud services”: Mozilla Weave, Google’s Apps and Apple’s MobileMe.

So, although you can build widgets for Opera Unite, you’re still relying on a third party to stay in the room with you… namely, Opera. And Opera isn’t exactly an organization that has behaved favorably towards the open source community in the past. Though that seems unlikely to change, it still begs the question why they believe there is more value is staying proprietary than opening up their browser to outside contributors.

Still, regardless of the decision that they make for their business about open source, there’s a bigger elephant in the room that needs to be addressed:
Is Opera Unite really decentralized?

Opera United

Opera’s CEO Jon von Tetzchner claims that “Opera Unite now decentralizes and democratizes the cloud”, illustrated like this:

Data sharing with Opera Unite

I call bullshit.

Opera Unite does indeed rely on a P2P-like network to function, but the big problem is that you must push all your traffic through Opera’s proxy service:

The set up when using the Opera Unite server in your browser

Not exactly “decentralized” (more on this in the next section).

Furthermore, if you read through the Opera Desktop End User License Agreement (which you had to if you installed the browser — shame on you if you didn’t!), you would have read section 7: USE OF SERVICES (emphasis mine):

Opera Unite and Transmission and Receipt of Content: Certain features of the Software and Services, including Opera Unite, may allow you to post or send content and/or links to content stored on your computer, that can be viewed by others (”User Generated Content”). Opera Software ASA exercises no control over User Generated Content passing through its network or equipment or available on or through the Services. You agree that Opera Software ASA is not liable for any loss of data. YOU MAY ONLY POST OR SEND USER GENERATED CONTENT THROUGH THE SERVICES THAT YOU CREATED OR THAT YOU HAVE PERMISSION TO POST OR SEND.. You agree not to use Opera Unite to upload, transfer or otherwise make available files, images, code, materials, or other information or content that is obscene, vulgar, hateful, threatening, or that violates any laws or third-party rights, hereunder but not limited to third-party intellectual property rights. We do not claim ownership of any User Generated Content. However, by submitting User Generated Content to us, you grant us and our affiliates the right and limited license to use, copy, display, perform, distribute and adapt this User Generated Content for the purpose of carrying out the Services.

You agree that we are not liable for User Generated Content that is provided by others. We have no duty to pre-screen User Generated Content, but we have the right to refuse to post, edit, or deliver submitted User Generated Content. We reserve the right to remove User Generated Content for any reason, but we are not responsible for any failure or delay in removing such material. We reserve the right to block any user’s access to any content, web site or web page in our sole discretion. Opera Software ASA reserves the right to terminate your account if you use your account privileges to unlawfully transmit copyrighted material without a license, valid defense or fair use privilege to do so.

Disputes may arise between you and others or between you and Opera Software ASA related to content or commerce, including User Generated Content. Such disputes could involve, among other things, the use or misuse of domain names; the infringement of copyrights, trademarks or other rights in intellectual property; defamation; fraud; the use or misuse of information; and problems with online auction or commerce transactions. You agree that all claims, disputes or wrongdoing that result from, or are related in any way to, the content of information that you post, transmit, re-transmit or receive through the Services, Opera Software’s network or Software are your sole and exclusive responsibility. Opera Software ASA may at it’s discretion, block certain web sites or domains and re-route you to other pages. By accepting these Terms of Use, You hereby consent to this.

Besides this hands-on approach to their centralized proxy service, Opera also reserves the right to filter the apps that you can install, a la Apple and their approach to the AppStore (because everyone wants an AppStore, right?):

What are the guidelines for approval of an Opera Unite Service?

These are some of the guidelines that apply to services:

* The service must have a sensible name and description
* The service must not have obvious bugs, so ensure that you test it before uploading
* The service must not contain malicious or destructive code
* The service must not contain or use copyrighted information for which you do not hold the rights
* The service must not contain or point to adult or hateful content
* The service should comply with the Opera Unite Service UI guidelines. Any reason for diverging significantly from the guidelines should be documented in the submission
* The service should serve standards-compliant HTML pages that are viewable in all modern browsers on a variety of devices.

I fail to see how this changes our reliance on “large corporations — who we depend upon to host our words, thoughts, and images” of whom Lawrence Eng spoke so disparagingly.
Owning Your Namespace

So, if it isn’t enough that you have to tunnel your connection through Opera’s proxies and place your service’s existence at the mercy of Opera’s filters, they also want to own your identity, something that everyone also wants to do lately.

In order to use Opera Unite, you have to have a my.opera.com account — perhaps not a big deal until you realize that you’ll be assigned a URL like http://notebook.username.operaunite.com/ to access your “self-hosted” outpost on the web.

Chris Mills, Opera’s Developer Relations Manager, explains:

To use Opera Unite Services, you need to log into Opera. This is the same login that you use to log in to My Opera, Dev Opera, or Opera Link.

Choosing an Opera Unite name for your computer

This name is basically your computer’s identity on the Opera Unite system — this is the URL that your contacts can go to if they want to make use of your Opera Unite Services, and share them with you.

So, while it’s true that your friends can access your Opera Unite homepage without an Opera account, if they want to host their own Unite server, they’re going to have to both download Opera and obtain an Opera account (and no, they don’t support OpenID).

While there are technical reasons that why this makes some sense (mostly to make it easier to get things up and running), it contradicts the whole promise of obviating central control. Indeed, AllPeers (now defunct) and others offered similar solutions previously. Why did Opera not launch with the ability for me to choose my own URL, or at least mask my homepage URL with something that didn’t tie me to Opera…? Oh yeah, that’s right — it’s all about owning the namespace.

At least Google was smart enough when they launched Wave to build in true decentralization from the start, and to choose a patent license for the Wave protocol that demonstrated that their desire was not to own the network, but to compete on it.
Unite & Activity Streams

Now, I know I sound like a curmudgeon, but I’m mostly just disappointed that few other people took Opera to task over the reality distortion field that Opera’s PR machine generated around this technology launch. But, as someone in the office said to me today, maybe no one cares enough about Opera to bother. Yeah, exactly, like I said before.

Still, there is a silver lining to this cloud computing fiasco which NO ONE else covered: Opera Unite supports activity streams!

It turns out that tucked within the Opera application is a directory called “unite” (on the Mac you can find it at Opera.app:Contents:Resources:unite) which contains a bunch of files with the .us extension (presumably for “Unite Service”). Like Mozilla .xpi files, these .us files are just zip files and can easily be decompressed by changing the extension.

In just about every bundle, there are several pertinent JavaScript files either in a folder called “asdstream” or with “activityStream” in the filename. The one that’s most interesting to me is the “activitystreamparser.js” file in the fridge.as bundle, which starts like this:

activitystreamparser.js — unite

Now, I’m not sure how this is being used, but I imagine it’s being used to output updates on the personal homepage of the site… which is awesome.

I wish that Opera had reached out to the Activity Streams mailing list about this work, but I can also understand that they probably didn’t want to jump the hype stungun. Anyway, it’s a huge opportunity (in my eyes!) for them to join the discussion about the open social web (since they have been essential proponents of web standards on the open web to date) and I invite them to share their goals and ideas for this work.
Conclusion

Okay, so I shit all over Opera Unite, but you can’t come out and promise all kinds of world-changing, freedom-enhancing goodness and then not deliver! — worse, to do so when their newest competitor (Google!) is schooling everyone with the perfect example of how to do it right (see: Wave).

While I have problems with Opera’s marketing approach, I do think that it’s useful to have Unite in the marketplace so that I can point to it as an example of what I want to see happen with the Diso Project — though I’m not willing to rest my success on the fate of any particular browser.

Through a combination of technologies like OpenID, OAuth, XRD, Portable Contacts, Activity Streams and microformats, we’ve been moving in this direction for some time, without having to alter the browser. Of course that’s meant that the browser has been conspicuously missing from the conversation, but that too is changing (see Mozilla’s experiment baking OpenID into the browser with Weave), and with Unite, we have yet another vision to contemplate — though I would have loved to have seen Opera embrace more than just Activity Streams out of all the technologies from the Open Stack.

I’ll give Opera some credit — both for using Activity Streams instead of inventing their own protocol — and also for launching a fairly polished demonstration of Unite concept as an alpha. If they really want to offer transformative technologies, though, I think it’s critical that they align their business policies with their marketing rhetoric and technological objectives, down to the code level. Anything less will result in confusion and worse, more posts like this one!

Posted by Chris Messina on Jun 16th.

Read more:
Thoughts on Opera Unite

Share/Save/Bookmark

Microsoft debuts Vine in Seattle: Twitter+Facebook on steroids

May 2nd, 2009 No comments

Microsoft debuts Vine in Seattle: Twitter+Facebook on steroids

Posted by Brier Dudley

It’s been awhile since Microsoft introduced a game-changing social Web application, but Vine — a service that’s debuting today with a beta test in Seattle — could be a contender.

Vine is a hyperlocal, personalized message and alert system. It’s intended to be a dashboard that people can use to keep tabs of their family, friends, activities and major events in their community.

The dashboard — which appears as a widget on a PC screen — displays a map of the user’s community and the status of their contacts. It also has buttons to send alerts or reports, which can be sent and received on the PC or as text messages on a cellphone.

dashboard_01.jpg

Vine could be used by families, schools or soccer teams to notify people of schedules and changes. Individuals could use it as a central hub to keep track of local news and data feeds and updates from services such as Facebook.

But Microsoft’s main emphasis now is providing Vine to emergency management officials, who are intrigued by a new tool that could be used to broadcast and receive information during a disaster or other major event.

“I think long-term this is probably going to be a very valuable tool to help people keep connected, not only during times of crisis but on a daily basis,” said Hillman Mitchell, the city of Tukwila’s emergency management coordinator.

Mitchell, who has reviewed the product and will participate in the public testing, said emergency management officials are already trying to glean information from services such as Twitter and Facebook, but it’s challenging because they’re basically sending limited streams of text. Vine “provides an avenue to consolidate some of that information and analyze it in a more comprehensive way.”

“The underlying technology, where it provides a more structured data form, will long-term be a very valuable asset, whether it’s generated from Microsoft or others,” he said.

Seattle is the first place Vine will be publicly available. During a testing period that begins today, people can sign up at www.vine.net to be among more than 10,000 testers the company hopes to enlist. Similar tests will begin shortly in a rural community in the Midwest and an isolated island community, the locations of which haven’t been disclosed yet.

Inspiration for Vine came from the confusion during Hurricane Katrina. Tammy Savage, a Microsoft manager who has led experimental Web efforts for the company, spent two years researching technologies for communities to communicate and prepare for emergencies. That led to a concept Microsoft calls “societal networking.”

dashboard_03.jpg

Then she spent two more years developing the product and the business, which is an experimental venture under the guidance of Chief Research and Strategy Officer Craig Mundie. That means it’s not allied with any particular product group, giving Savage’s 25-person team leeway to easily blend technologies from across the company.

It’s a little hard to see how Vine will stand out from the multitude of networking and communication services available already, not to mention the carcasses of similar projects such as Seattle startup Trumba, an online calendar and notification service..

But Savage still sees a need and an opportunity for a comprehensive service like Vine, which is designed to become a hub or console for various services that people use.

“We don’t want to re-create things that already exist,” she said. “We’re looking for the opportunities that are particularly appropriate for Microsoft to bring its resources to bear.”

For example, the service is debuting with data feeds from more than 20,000 media sources and public safety organizations, including NOAA and the National Center for Missing and Exploited Children.

Vine could end up competing with local media outlets, which are among the primary places people go for local information during a disaster or emergency. Microsoft is offering government agencies a way to directly communicate with residents during these events, but I wonder if users will be overwhelmed by the flow of data from emergency response agencies and miss the context, analysis and filtering of media sites.

It’s unclear where Vine could end up within Microsoft when it graduates into a full blown business, but it’s mostly likely to complement Microsoft’s suite of e-government software and its Sharepoint collaboration server.

Local officials who have seen the project are enthusiastic about what they’ve seen, but they’re waiting to see how it works and whether it’s widely accepted. Another big question is the cost, especially if Microsoft charges a significant amount for every home and business in their jurisidiction that uses the system.

“They’ve been talking about a few dollars per user ID for a period of time, maybe a month or a year,” said Seattle’s chief technology officer, Bill Schrier. “That doesn’t sound like much but if you spread it out across 300,000 premises, that’s a fair chunk of change.”

Schrier, an avid user of social networking tools such as Twitter and Facebook, said Vine has “really intriguing potential” for community communications and disaster preparedness. After talking to Microsoft about Vine for about five months, he’s planning to see how the service could work with Seattle’s block watch and neighborhood emergency management programs.

UPDATE: A few commenters asked about locking into a proprietary system.

I asked the public officials interviewed about this and whether it was appropriate for municipalities to use a system that requires using Microsoft’s platform and Live ID registration.

Tukwila’s Mitchell said Vine is probably part of “a new wave of technology that we’re going to see from a variety of vendors.”

Schrier said Seattle is particularly concerned about using a system that displays advertising, such as Facebook, because it could appear the city is endorsing advertisers.

Advertising is just part of the equation though. The bigger question surround propagation of Live ID registration/customer acquisition through governments.

SOURCE

Source:
Microsoft debuts Vine in Seattle: Twitter+Facebook on steroids

Share/Save/Bookmark

Twitter creator Jack Dorsey illuminates the site?s founding document. Part I

February 19th, 2009 No comments

Twitter creator Jack Dorsey illuminates the site’s founding document. Part I | Technology | Los Angeles Times

Twitter founding document
Twitter’s prehistoric document, circa 2000. An early temporary name was “Stat.us.”
Credit: Jack Dorsey.

Sitting in the Flickr archives is a nearly 10-year-old document uploaded a couple of years ago by its author, Jack Dorsey (@jack), who started Twitter in 2006 along with co-founders Evan Williams (@ev) and Biz Stone (@biz).

The legal-pad sketch of the idea that would become Twitter has been noticed before, but given all the recent hype, we thought we’d track down Dorsey and ask him about it in a little more detail. In the following interview, Dorsey uses the document to touch on aspects of the micromessaging service’s history, including the inspirations and constraints that came to define one of the Web’s most rapidly growing information channels.

Twitter didn’t just fly out of thin air and land on a branch. As Dorsey explains, it has conceptual roots in the world of vehicle dispatch — where cars and bikes zooming around town must constantly squawk to each other about where they are and what they’re up to.

It was when Dorsey saw these systems through the eyes of the social, mobile Web, where anyone can squawk from anywhere, that Twitter’s Big Idea was born.

We’ll post the second part of the interview Thursday.

Is this the founding Twitter document?

It has very special significance — it’s hanging in the office somewhere with one other page. Whenever I’m thinking about something, I really like to take out the yellow notepad and get it down.

Twitter has been my life’s work in many senses. It started with a fascination with cities and how they work, and what’s going on in them right now. That led me to the only thing that was tractable in discovering that, which was bicycle messengers and truck couriers roaming about, delivering packages.

That allowed me to create this visualization — to create software that allowed me to see how this was all moving in a city. Then we started adding in the next element, which are taxi cabs. Now we have another entity roaming about the metropolis, reporting where it is and what work it has, going over GPS and CB radio or cellphone. And then you get to the emergency services: ambulances, firetrucks and police — and suddenly you have have this very rich sense of what’s happening right now in the city.

But it’s missing the public. It’s missing normal people.

And that’s where Twitter came in. What really brought me to that conclusion …

… was instant messenger. This aspect where you can just locate your buddy list and at a glance locate what your friends are up to, or what they say they’re up to. I found the same parallels in dispatch — here’s a bunch of ambulances and couriers reporting where they are, and here’s my friends. Now, the problem with IM is that you’re bound to the computer, so it really limited the interestingness of the messages.

So that document was around 2000-2001 when I really got into IM and a service called LiveJournal. And it was crystallizing the thought: What if you have LiveJournal, but you just make it more live? You have these people watching your journal, but it all happens in real time, and you can update it from anywhere. That document was an exploration of that concept.

When did you first try to build out the idea?

I tried it back in 2000 with the first device that RIM made — the RIM 850, which was the predecessor to the BlackBerry. A very simple squat little e-mail device. It had four lines of text and a typical BlackBerry keyboard. They were like $400, and it would just do e-mail. I wrote a very simple program to listen to an e-mail address and take any updates from me and send them out to a list of my friends. And my friends could reply to that e-mail and tell me what they’re doing.

But the problem was that no one else had those devices –- so again, it limited the experience of that. We were limited until 2005-2006 when SMS took off in this country and I could finally send a message from Cingular to Verizon. And that just crystallized — well, now’s the time for this idea. And we started working on it.

It was really SMS that inspired the further direction — the particular constraint of 140 characters was kind of borrowed. You have a natural constraint with the couriers when you update your location or with IM when you update your status. But SMS allowed this other constraint, where most basic phones are limited to 160 characters before they split the messages. So in order to minimize the hassle and thinking around receiving a message, we wanted to make sure that we were not splitting any messages. So we took 20 characters for the user name, and left 140 for the content. That’s where it all came from.

For any potential Twitter historians out there, can you offer a few more details about the drawing — the little googly eyes, for example?

The little eyeballs were “watching.” The concept was watching before we kind of switched it and developed it into “following.” So you could watch or unwatch someone — but we found a better word — follow or unfollow. The important consideration there was that on Twitter, you’re not watching the person, you’re watching what they produce. It’s not a social network, so there’s no real social pressure inherent in having to call them a “friend” or having to call them a relative, because you’re not dealing with them personally, you’re dealing with what they’ve put out there.

The document’s user interface metaphor is very similar [to how Twitter turned out]. You have a little box to “set” your update, and past updates would go down into the timeline below.

Immediately the idea was device-agnostic. You could deliver over e-mail or deliver over Jabber, because IM was a real-time mechanism — and eventually you could deliver over SMS as well. And the only other aspect on that page was how to find other people. If you know someone, you type in their name or e-mail address, and you can immediately start following their updates.

What are the “authentication triples” on the upper left there?

I was trying to be a little bit too smart, and was trying to figure out ways to do everything without a password. But that’s very difficult and requires way too much thought. So we punted on that. But someone will figure it out. [laughs]

Then when did the service’s name morph from “Status/Stat.us” to “twittr” to Twitter?

The working name was just “Status” for a while. It actually didn’t have a name. We were trying to name it, and mobile was a big aspect of the product early on … We liked the SMS aspect, and how you could update from anywhere and receive from anywhere.

We wanted to capture that in the name — we wanted to capture that feeling: the physical sensation that you’re buzzing your friend’s pocket. It’s like buzzing all over the world. So we did a bunch of name-storming, and we came up with the word “twitch,” because the phone kind of vibrates when it moves. But “twitch” is not a good product name because it doesn’t bring up the right imagery. So we looked in the dictionary for words around it, and we came across the word “twitter,” and it was just perfect. The definition was “a short burst of inconsequential information,” and “chirps from birds.” And that’s exactly what the product was.

The whole bird thing: bird chirps sound meaningless to us, but meaning is applied by other birds. The same is true of Twitter: a lot of messages can be seen as completely useless and meaningless, but it’s entirely dependent on the recipient. So we just fell in love with the word. It was like, “Oh, this is it.” We can use it as a verb, as a noun, it fits with so many other words. If you get too many messages you’re “twitterpated” — the name was just perfect.

But you needed that short code -– in order to operate SMS you need the short code to operate with this cellular administration. So we were trying to get “twttr” — because we could just take out the vowels and get the 5-digit code. But unfortunately Teen People had that code -– it was ‘txttp’ [Text TP]. So we just decided to get an easy-to-remember short code [40404], and put the vowels back in.

So Twitter was it, and it’s been a big part of our success. Naming something and getting the branding right is really important.

Tune in tomorrow for the second part of the interview, in which Dorsey talks about the growing Twitter ecosystem, the service’s effect on news gathering and why he doesn’t like to “go back in time.”

– David Sarno [follow on Twitter]

SOURCE

Read the original:
Twitter creator Jack Dorsey illuminates the site?s founding document. Part I

Share/Save/Bookmark

TinyChat – Disposable Chatrooms for the Twitter Generation

February 17th, 2009 No comments

TinyChat – Disposable Chatrooms for the Twitter Generation – ReadWriteWeb

Even though we live in an age of instant Qik streams, video chats on Skype, and micro-blogging on Twitter, sometimes all you need is a simple chatroom for real-time text chats. TinyChat solves this problem by creating simple, disposable chatrooms. Tinychats works exactly as advertised. It’s a disposable, no-frills chatroom, with a deliberately limited feature set. There are no accounts to sign up for and whenever you open up a new room, TinyChat will simply create a new URL for you.

While you don’t have to create an account on TinyChat, you can (and will!) alert your Twitter followers when you open a new chatroom and sign in with your Twitter login. It is important to note that you can’t turn this message off – if you sign in with your Twitter account, that message will go out to all of your followers!

Besides the basic chat function, TinyChat also features the ability to add a badge with your chatroom status to your blog or social networking profile. You can also save a copy of your chat log by saving it as a text file, or by forwarding it to your email account.
Hidden Features: Choose Your Own URL and Private Chat

If you don’t want to use TinyChat’s cryptic names for your chatroom, you can also choose your own by just appending it to the TinyChat URL. If you want to send a private message, just click on the person’s name and your message will be invisible to the rest of the room.

The chatroom concept does feel a bit retro, and it would be nice if you could receive some kind of audio or visual notification whenever a new message was posted to your room, but overall, the service just does what it say it does, and it does it well.
iPhone and Flash Coming Soon

Dan Blake, TinyChat’s developer, tell us that they are also currently working on a simple iPhone app and a flash widget. If you like TinyChat, you should also check out TinyPaste (short URLs for long quotes) and iOJ (file uploading and sharing app) from the same developers.

Come chat with us!

SOURCE

Powered by ScribeFire.

Go here to see the original:
TinyChat – Disposable Chatrooms for the Twitter Generation

Share/Save/Bookmark

How Twitter Was Born

February 1st, 2009 No comments

Twitter was born about three years ago, when @Jack, @Biz, @Noah, @Crystal, @Jeremy, @Adam, @TonyStubblebine, @Ev, me (@Dom), @Rabble, @RayReadyRay, @Florian, @TimRoberts, and @Blaine worked at a podcasting company called Odeo, Inc. in South Park, San Francisco. The company had just contributed a major chunk of code to Rails 1.0 and had just shipped Odeo Studio, but we were facing tremendous competition from Apple and other heavyweights. Our board was not feeling optimistic, and we were forced to reinvent ourselves.

“Rebooting” or reinventing the company started with a daylong brainstorming session where we broke up into teams to talk about our best ideas. I was lucky enough to be in @Jack’s group, where he first described a service that uses SMS to tell small groups what you are doing. We happened to be on top of the slide on the north end of South Park. It was sunny and brisk. We were eating Mexican food. His idea made us stop eating and start talking.

I remember that @Jack’s first use case was city-related: telling people that the club he’s at is happening. “I want to have a dispatch service that connects us on our phones using text.” His idea was to make it so simple that you don’t even think about what you’re doing, you just type something and send it. Typing something on your phone in those days meant you were probably messing with T9 text input, unless you were sporting a relatively rare smartphone. Even so, everyone in our group got the idea instantly and wanted it.

Later, each group presented their ideas, and a few of them were selected for prototyping. Demos ensued. @Jack’s idea rose to the top as a combination of status-type ideas. @Jack and @Noah were assigned to build version 0.1 while the rest of the company focused on maintaining Odeo.com, so that if this new thing flopped we’d have something to fall back upon.

The first version of @Jack’s idea was entirely web-based. It was created on March 31st, 2006. My first substantive message is #38:

oh this is going to be addictive

Standing Room Only We struggled with a codename and a product name. “It’s FriendStalker!” joked @Crystal, our most prolific user. The userbase was limited entirely to the company and our immediate family. No one from a major company of any kind was allowed in. For months, we were in Top Secret Alpha because of competing products like the now-defunkt Dodgeball. We operated using a “long code”, or a full 10-digit phone number linked to a small-potatoes gateway. The original product name / codename “twttr” was inspired by Flickr and the fact that American SMS shortcodes are five characters. We prototyped with “89887? as our shortcode. We later changed to “40404? for ease of use and memorability. Twttr probably had about 50 users in the long code days.

I was following everyone on the system. We had an admin page where you could see every user. As Head of Quality for the company, it seemed like my duty to watch for opinions or issues from our users. This caused confusion, though, when family members of our team were suddenly being followed by a seemingly random person. Thus, Private Accounts were born. @Jack and @Florian created a means for users to mark themselves private, and we admins had the ability to tell who wanted to be private so we’d know not to follow them. Actual, real privacy with secure protection came a bit later. I’d say there were about 100 users when Private was invented.

Later Twttr Design The interaction model and the visual metaphor for the service were constantly in flux. The meaning of being someone’s “Friend” versus “Following” someone changed regularly. At that point, you could either get all SMS messages or get none. There was no Twictionary back then; data in the system were referred to as “posts” or just “messages”. The lack of clear terminology led to some pretty spirited debates leading up to the Spring of 2006.

We launched Twttr Beta on @Ev’s birthday. We could now invite a slightly larger circle of friends, but still excluding any large companies (with a few trusted exceptions within places like Google). I’ll never forget the family-friendly feeling of that day. We all knew that we were going to change the world with this thing that no one else understood. That day stands out in memory as the deep breath before a baby’s first cry.

Meanwhile, Odeo and the corporate board were at a tension point. Not only was the value of Twttr difficult to describe, the relevance of Odeo was declining monthly. Drastic cuts were recommended. One day in early May 2006, @Ev let four of us go: @Adam, @TonyStubblebine, me, and @Rabble. @Noah and @TimRoberts would later be asked to leave as well. It was a tough decision and huge shock to each of us. We all handled it differently. Looking back on it, I think Twitter allowed us to stay connected when we might not have otherwise been. After all, we weren’t even public with the site yet, so each of us continued to add value just by using it with each other.

Twttr, directly. During this transition, Twttr.com launched to the public. Still, very few people understood its value. At the time most people were paying per SMS message, and so wouldn’t Twttr run up our bills? Also, how were we supposed to use this thing and who cares what I’m doing? Each one of us original users became a kind of personal evangelist for Twttr, trying to get our coworkers and friends to use it. At this point, Obvious Corp was born as an incubator with Twttr as its sole project.

Twitter Friends@Jack was still just an engineer, and the service was only a few months old when the group acquired Twitter.com and re-branded. Back then, we had no character limit on our system. Messages longer than 160 characters (the common SMS carrier limit) were split into multiple texts and delivered (somewhat) sequentially. There were other bugs, and a mounting SMS bill. The team decided to place a limit on the number of characters that would go out via SMS for each post. They settled on 140, in order to leave room for the username and the colon in front of the message. In February of 2007 @Jack wrote something which inspired me to get started on this project: “One could change the world with one hundred and forty characters.”

Just in time for SxSW, @RayReadyRay rigged a very sweet Flash-based visualizer that ended up on display on the halls of the conference. I wasn’t working there, but I used to visit regularly to see how our baby was doing. I happened to be at the office in SF when the visualizer went live on site in Austin. I remember finding a bug just before showtime, as @Biz and @Jeremy talked over the phone. Everything miraculously fell into place by the time people filtered out of the sessions to see their comments floating along the hallway screens. Boom #1: Twitter won an award in the Blog category, and @Jack thanked everyone in 140 characters.

MTV Music Awards: Boom #2.

Apple WWDC 2007, and then TV, and then print and pretty soon Cable news: Boom #3.

@Jack became the CEO of a newly spun-off Twitter, Inc. during the Boom Times. People still didn’t quite “get it” but at least some people had heard about it. The team created permalinks and RSS feeds. @Blaine pushed for IM integration. Each major feature added tremendous gains in users, and in usage per user. Still small by social networking standards, Twitter delivered something immediate and vital that no other service could attain.

For a lot of people, the entire API launch was really the time when Twitter first left the nest. But that is another story, for another time.

If you liked this post, you might enjoy following me: http://twitter.com/dom

SOURCE

Go here to see the original:
How Twitter Was Born

Share/Save/Bookmark

Google Shutters Its Science Data Service

December 20th, 2008 No comments

Googlescience

Google will shutter its highly-anticipated scientific data service in January without even officially launching the product, the company said in an e-mail to its beta testers.

Once nicknamed Palimpsests, but more recently going by the staid name, Google Research Datasets, the service was going to offer scientists a way to store the massive amounts of data generated in an increasing number of fields. About 30 datasets — mostly tests — had already been uploaded to the site.

The dream appears to have fallen prey to belt-tightening at Silicon Valley’s most innovative company.

“As you know, Google is a company that promotes experimentation with innovative new products and services. At the same time, we have to carefully balance that with ensuring that our resources are used in the most effective possible way to bring maximum value to our users,” wrote Robert Tansley of Google on behalf of the Google Research Datasets team to its internal testers.

“It has been a difficult decision, but we have decided not to continue work on Google Research Datasets, but to instead focus our efforts on other activities such as Google Scholar, our Research Programs, and publishing papers about research here at Google,” he wrote.

Axing this scientific project could be another sign of incipient frugality at Google. Just a couple weeks ago, Google CEO Eric Schmidt told the Wall Street Journal that his company would be cutting back on experimental projects. First described in detail by Google engineer Jon Trowbridge at SciFoo 2007 — the slides from a later version of the talk is archived on the Partial Immortalization blog — the project was going to store, for free, some of the world’s largest scientific datasets. In Trowbridge’s slides, he points out the 120 terabyte Hubble Legacy Archive and the one terabyte Archimedes palimpsest.

“‘It’s a sad story if it’s true,” wrote Attila Csordas, a stem cell biologist and author of Partial Immortalization who recently moved to Hungary from Tulane University, in an email to Wired.com. “Assuming it is true that might mean that Google is still a couple years away from directly helping the life sciences (on an infrastructural level).”

Other scientists remained hopeful that the service might return in better times.

“The Space Telescope Science Institute has had a long positive relationship with Google that started with our partnership in GoogleSky in early 2006,” said astrophysicist Alberto Conti of STSI. “We were looking forward to Google’s commitment to helping the astronomical community with the data deluge, and we are sure Google will reconsider this decision in the future. While perhaps understandable in this economic climate, it’s sad to see Google leave the field.”

And Conti noted, other companies may step up to help scientists manage their information.

Amazon is doing exactly the opposite and they might actually fill the void,” he said.

Google representatives did not respond immediately to request for comment.

Image: flickr/DannySullivan

See Also:

WiSci 2.0: Alexis Madrigal’s Twitter , Google Reader feed, and project site, Inventing Green: the lost history of American clean tech; Wired Science on Facebook.

SOURCE

Originally posted here:
Google Shutters Its Science Data Service

Share/Save/Bookmark

Greenpeace protests electronic waste

June 16th, 2008 No comments

Protestors from the environmental group Greenpeace boarded a ship in Hong Kong Port on Saturday that they say was carrying three containers of electronic waste from the U.S.

Read more here:
Greenpeace protests electronic waste

Share/Save/Bookmark

CEA hosts Digital Downtown show

June 16th, 2008 No comments

The Consumer Electronics Association hosted Digital Downtown in New York City and while the show was tiny compared to the annual mega show, analysts were on hand to talk about the industry and how its fairing in the worldwide economic downturn.

See more here:
CEA hosts Digital Downtown show

Share/Save/Bookmark

Week in Review – 6/13

June 13th, 2008 No comments

Deadly attack in Tokyo’s electronics district, Apple’s iPhone 3G launches, Roadrunner smashes petaflop barrier, Telectroscope lets London see New York, Enterprise 2.0 pushes social networking applications and paperless boarding passes speed travel.

Continued here:
Week in Review – 6/13

Share/Save/Bookmark

An Internet-connected Grand Piano

June 12th, 2008 No comments

For those wanting to learn piano or just want a nice (really nice) player piano for their living room, Yamaha’s Internet-connected Disklavier fits the bill. Maybe this time Keith will actually learn to play.

Source:
An Internet-connected Grand Piano

Share/Save/Bookmark

More than chips at Intel research day

June 12th, 2008 No comments

Intel went to the home of technology past to show off what it’s working on for the future.

Read more here:
More than chips at Intel research day

Share/Save/Bookmark

Enterprise 2.0 conference

June 11th, 2008 No comments

At the Enterprise 2.0 conference in Boston this week vendors and attendees mixed and mingled with vendors pushing new social networking and collaboration applications and attendees trying to figure out if they actually need them.

Originally posted here:
Enterprise 2.0 conference

Share/Save/Bookmark

3G iPhone coming July 11

June 10th, 2008 No comments

Introduced by Apple CEO Steve Jobs at the company’s Worldwide Developers Conference in San Francisco, the iPhone 3G is slightly thicker than its predecessor but includes built-in GPS, black plastic on its back and a jack for standard headphones.

Excerpted from:
3G iPhone coming July 11

Share/Save/Bookmark

iPhone 2.0 offers a number of new applications and features

June 10th, 2008 No comments

The iPhone 3G dominated the first day of Apple’s Worldwide Developers Conference on Monday, but attendees also got a glimpse of new software coming for all iPhones.

Read more:
iPhone 2.0 offers a number of new applications and features

Share/Save/Bookmark