The World Wide Web Consortium has published a draft of an interface that browsers can use to manipulate files better, one of a series of steps aimed at gradually improving the sophistication and polish of Web site interfaces.
The draft File API (application programming interface) defines a number of ways that browsers and Web sites can handle files better. One big part of it: being able to select multiple files for upload, such as on photo-sharing sites or Web-based e-mail, a task that often relies on Adobe Systems' Flash today.
But there are other aspects, too. For example, the Files interface governs the use of "blobs," or packages of raw binary data such as video files. Google has touted blobs for its Gears browser plug-in as a way to divide large videos into small chunks so that uploads can be more easily resumed if a network problem interrupts the process.
Another benefit: files are handled asynchronously, which means the browser won't freeze up while a file is being uploaded or otherwise handled, and the browser reports progress on file transfers.
The technology is one example of work to transform the Web into a better foundation for interactive applications, a move that usurps some power from computer operating systems such as Windows and that's embodied most boldly in Google's Chrome OS project.
Here's one example of use of the Files interface provided by Mike Smith, who works for the W3C on matters relating to HTML--Hypertext Markup Language, the language used to describe Web pages:
A user uses a Web-based application for reading and sending e-mail. She wants to attach multiple files to particular messages. The Web application provides an user interface that allows her to select multiple files to attach at the same time. After she selects the files, they are uploaded to the Web application asynchronously, allowing the user to perform other actions while they are uploading (for example, finishing the rest of the message she was composing before you added the file attachments). As the attachments are uploaded, the Web applications shows progress bars to indicate how much of the contents of the files have uploaded thus far.
The interface can work in conjunction with various standards including the drag-and-drop support in the HTML 5 now under development and the Web Workers technology that lets browsers better perform multiple operations simultaneously.
The interface also can help Web applications process the contents of files. For example, Smith describes a lyrics finder:
A user has on her local file system a playlist file from her favorite desktop music player. The playlist contains a list of song titles and information, and she wants to be able to easily fetch the lyrics for particular songs without needing to manually search for the lyrics on the Web. So a site can provide a Web-based application that allows her to upload her playlist. The Web application then parses the file and then presents a user interface to her, show in the contents of the file as a hyperlinked, sortable list. She can then retrieve the lyrics for any given song just by clicking on a particular song title.
Arun Ranganathan, Mozilla's standards evangelist and chairman of the WebGL working group, wrote the specification, according to Chris Blizzard, Mozilla's director of developer relations.
Standards for the Web are advancing rapidly with W3C representatives including Microsoft working in conjunction with a parallel effort, WHATWG. New standards require actual implementation in browsers before they are accepted as finished, a fact that can lead to some chaos but that helps ensure the new ideas are tested in the real world.
Firefox 3.6, in beta testing now, will support most of the Files API, according to Blizzard.
Professional networking site LinkedIn's platform, previously a closed offering for select partners, has opened up to developers at large, according to an announcement Monday on the company blog.
Well, sort of. Building an embeddable widget on LinkedIn, unlike Facebook's, still requires a stringent application process. But LinkedIn's own code has now been opened up so that developers can integrate it into their own sites. It's launched a developer site for those interested in features that let site users access their LinkedIn profile and contacts externally. They still have to request a key to get into the platform's application program interface (API), which means that LinkedIn widgets likely will not be coming to office prank-calling Web sites any time soon, despite that they could make it much easier to robo-call your boss and ask if his refrigerator is running.
One of the first participants, for example, is desktop Twitter client TweetDeck, which says that it will soon allow users to plug in their LinkedIn contacts' status updates alongside Twitter, Facebook, and MySpace contacts.
LinkedIn has about 50 million users as of last count.
Iron Mountain, a longtime provider of physical- and digital-records management, on Wednesday announced a cloud storage API that enables developers to take advantage of Iron Mountain's off-site storage facilities.
Despite the recent issues related to T-Mobile/Danger/Microsoft's data loss, cloud-based storage is not only here to stay, it's a good use case for organizations that don't have the internal processes or means to deal with off-site data management.
And while you can never know all of the things that can go wrong with your data (meaning that no one would have expected Danger to lose the T-Mobile data), established vendors like Iron Mountain have not only the customer base to support their abilities but also the processes to support customers effectively.
Iron Mountain's cloud storage application programming interface is the next evolutionary step beyond a cloud NAS (network-attached storage) that we've seen from providers like Mozy and others. The cloud storage API is similar in function to Amazon's Simple Storage Service interfaces, enabling developers to access data using restful interactions.
... Read more
A mockup of Twitter's new 'retweet API' interface
(Credit: Twitter)The development team at Twitter has released a mockup of its forthcoming "retweet API"--basically, the first formal way that Twitter has baked retweets, the copying and attribution of other Twitter users' posts, into its own product. It displays the user avatars of members who have retweeted a given tweet below the original, "collapsing" them into a single space.
Some background detail on the forthcoming new API: Retweets have been a mainstay of Twitter for some time now, but the feature was created by users rather than officially. Several third-party Twitter clients have built in retweet buttons, and some apps, such as Tweetmeme, have created a way to tabulate them like a Digg count, but it's never been worked into Twitter's Web site or API.
What's interesting is that the new format, assuming that this is how the timeline ends up looking, can provide a quick, one-glance way to see just how influential a given Twitter user or individual tweet is, adding a new dimension to measuring Twitter influence beyond the follower count. If you see a lot of little retweet icons, for example, you might stop and take a closer look at a tweet (or the user behind that tweet) that you might otherwise have skimmed past.
What's also interesting is that it looks like retweet counts get cut off at 100, with higher ones displayed as simply "100+." I'm guessing that, say, CNN Breaking News generally gets a lot more than that.
When they were announced, the changes to Twitter retweets weren't met with a thoroughly warm reception. "Asking developers to collapse retweets in timelines is onerous, complicated, and confusing," the forum post by Twitter's Marcel Molina said in response to developer concerns that the collapsed-retweet format would do more harm than good. "We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines, you will get only the first retweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it."
On Thursday night, Facebook announced that it's launched its first official Twitter app--sort of. In a post on the company blog, Facebook announced that updates to "fan pages," public profiles for celebrities, brands, organizations, and what-have-you, can now be sent out through Twitter.
"Public figures, musicians, businesses and organizations of all types who've created Facebook Pages often want to share a status update, a photo or an event with as many of their supporters as possible," the post by Facebook employee Michael Gummelt read. "Celebrities may want to share personal news or charities may want to put out calls for help to both their Facebook fans and their Twitter followers, all at the same time."
This is basically something that many blogging and publishing services already do: offer a way to automatically syndicate a short blurb and a link onto Twitter. It's a no-brainer. But Facebook and Twitter have a complicated history. Facebook attempted to acquire Twitter last year, and Twitter turned the offer down. Then, earlier this summer, Facebook did acquire FriendFeed, a social-network aggregator that failed to gain mainstream traction but pioneered many of the real-time, streaming features that are now central to both Facebook and Twitter.
Relations between the two companies still seem to be a bit shaky. Facebook continues to roll out Twitter-inspired features like a souped-up search engine, a revamped "publisher" tool that can make status updates selectively public, and soon a stripped down "Facebook Lite" site that looks quite a bit like the ultra-basic Twitter.
Much has been said about Facebook and Twitter as the two forces vying for control of the real-time social Web, but little light has been shed on just how central a role the marketing industry has. The fact that Facebook's first Twitter app is exclusively for its brand-marketing "fan pages" highlights this. In the digital marketing world, the buzzworthy place for brands to be right now is Twitter--especially since this week Twitter started to elaborate plans for the paid accounts it's going to offer to businesses by the end of the year. If Facebook is going to continue to court brands effectively, it has to offer a quick and easy way to plug into that all-important "Twitter strategy."
What's less clear is whether Facebook will let ordinary users syndicate their profile updates to Twitter. Currently, they can bring in plenty of data from elsewhere thanks to Facebook's third-party developer API. You can import a Twitter feed into Facebook status updates or use third-party clients like TweetDeck to update Twitter status and Facebook status simultaneously, but you still can't opt to publish your Facebook profile updates elsewhere.
PayPal, eBay's well established but aging mechanism for online payments, is trying to rebuild itself for a new generation of online commerce possibilities.
At an event for press and developers on Thursday, PayPal and its partners described several new programming interfaces that are part of the company's upcoming Adaptive Payments Service and showed what developers can do with them.
For example, Microsoft will use the interface to enable payments within its forthcoming Azure cloud-computing service. And LiveOps' on-demand outsourcing service will use it to automatically handle fluctuating payment amounts and changes to who's being paid. Finally, the interface takes PayPal beyond the browser, opening it up for use on mobile phones, set-top boxes, and other increasingly smart devices.
"It's truly disruptive," said PayPal CEO Scott Thompson at the event. "It puts developers in the driver's seat by allowing you to do what you want to do and (choose) how you want to get paid."
The new service will be available to 300 PayPal partners starting Thursday, with a public beta this November--just in time for PayPal X Innovate 2009, its first developer conference.
PayPal is pitching the Adaptive Payments platform to developers as a way to more easily build PayPal-powered payment options into their applications. It's also a more streamlined version of PayPal's existing program for letting businesses manage transactions between several different parties.
The new payments service is a key part in PayPal's plan to double its revenues within the next three years. Back in March, PayPal's president Scott Thompson promised as much, saying that by 2011, the company should be doing somewhere between $100-120 billion in annual payments. PayPal has also had a fire lit underneath it since Amazon rolled out its own online payments service around this time last year. It let users make online purchases using billing information that was stored on Amazon.com
PayPal isn't just central to eBay's future. It will eclipse the company's auction and commerce operations, the company says.
"PayPal is a business that will be bigger than eBay," eBay Chief Executive John Donahoe said Thursday at the Fortune Brainstorm conference.
PayPal is a force to be reckoned with. On average, more than $2,000 goes through PayPal every second of each day. It has 75 million active accounts, and it's available in 190 markets and 19 different currencies.
Beta testing
Before the announcement, PayPal had been working with a handful of companies to test the new APIs (application programming interfaces). One of those companies is Microsoft, which is tapping PayPal for online payments in the Web applications built for the company's upcoming Azure platform.
At the unveiling, Yousef Khalidi, a Microsoft distinguished engineer, demonstrated an application that integrated PayPal's payment and billing functionality. It took only two days to integrate it into the existing product, Khalidi said.
Khalidi said that Microsoft plans to offer a simple way to build PayPal's mechanism into hosted applications as part of Azure's full release later this year.
Microsoft probably had an easier time choosing PayPal for its payment service than some of the alternatives: Amazon Flexible Payment Services and Google Checkout both come from companies in direct competition with Microsoft's Azure cloud-computing service.
Michael Ivey, CEO and co-founder of TwitPay, also took the stage to show his company's use of the new PayPal API--specifically to let people pay multiple people at once.
"In one transaction, I'm paying four different people," he said. Before the new APIs, the service would require users to make each payment as its own transaction.
Sites already using the new API include: Webassist, GroupCard, Lottay, Rainfall of Envelopes, and MedPayOnline.com
"PayPal will help you get paid for your innovations--your business will become our business," Thompson told the developers. "We view you as our third set of customers."
New features
The new payment service has a handful of new features designed to make it easier for developers to make money with their applications and services.
Thompson said that even if developers were acting as an intermediary between the person sending the money and the recipient, they would now be able to take their cut of that transaction--just as PayPal does.
Part of getting that to happen involves a new API that lets developers create peer-to-peer and business-to-business money-sharing applications. They can now also split up payments into several transactions and let users authorize a payment after the transaction's been made. Those two mechanisms can speed purchasing, regardless of whether the buyer is ready to pay the full amount at the outset.
As part of the new platform, PayPal also is changing the way fees are charged. Application developers can choose to have the sender of the money, not just the recipient, pay the fee.
In addition, the fee rates can be changed based on the type of purchase, which should ease the chore of handling both high-value transactions and micropayments (transactions below $12) within the same application. As it stands today, PayPal currently requires sellers to have two different accounts open, one for bigger payments and another for micropayments--and each has different rates.
People use PayPal today through a Web interface, but a new API will bring PayPal to nontraditional computing platforms including mobile phones, set-top boxes, and gaming consoles. That's important, given that those devices increasingly are networked and have their own ecosystems of applications. And moving to a browser can be disruptive to a user who just wants to make a quick payment.
Using PayPal that way also means that a developer must build the necessary user interface, though. PayPal didn't provide specifics on that element of the new payments system.
Overall, Thompson said the new payment system will help PayPal keep pace with changes in technology and business.
"The pace of innovation is just staggering," he said. "And the next wave of innovation is poised to move that much faster. "
CNET News reporter Ina Fried contributed to this report.
Is Twitter getting possessive of its own name? Maybe.
A developer building an application using Twitter's API was told via e-mail that Twitter took issue with the user interface of his application, allegedly very similar to Twitter's own, as well as his use of the word "tweet" in the application's name.
The developer forwarded the e-mail to TechCrunch: "Twitter, Inc., is uncomfortable with the use of the word Tweet (our trademark) and the similarity in your UI and our own."
Uh-oh. If Twitter is staking a claim to the word "tweet," that could mean a problem for TweetDeck, TweetMeme, PoliTweets, and some of the other extremely popular businesses built atop Twitter.
A few things to keep in mind here. One, the developer was also creating a service that looked a lot like Twitter, the TechCrunch post explains, which means that the use of the word "tweet" may really have been less important than the e-mail made it out to be. Second, it's a personal e-mail coming from a Twitter employee--not a company representative or executive--which means that it may not be perfectly aligned with the company's official stance on things.
(Case in point: A Twitter investor hinted to The New York Times that the company would be making money with virtual coupons. One of Twitter's co-founders said in a comment on a blog that the investor was "brainstorming on his own.")
But the tech industry does have a history of getting into one skirmish after another over names similar to their trademarks. Several years ago, Apple started sending cease-and-desist letters to some third-party equipment companies and fan blogs that were using the word "pod" in their names. Google, too, has taken issue with the word "googling" being used as a generic verb.
And as TechCrunch points out, Twitter has filed for a trademark on the word "tweet." On the other hand, being possessive of this term (which, it goes without saying, has been a dictionary word for centuries) might not be the smartest strategy, if Twitter indeed wants to be a Digital Age communication standard "like electricity," as one executive said last month. So we'll see how this one unfolds.
UPDATE at 11:49 a.m. PT: Twitter co-founder Biz Stone has, as the company's executives often do when there's a rumor flurry about something Twitter's doing, put up a blog post to clarify. The answer, not surprisingly, is that these things are handled on a case-by-case basis.
And "tweet" is not a target, he said.
"We have no intention of 'going after' the wonderful applications and services that use the word in their name when associated with Twitter," Stone assured readers. "In fact, we encourage the use of the word Tweet."
It's more complicated when developers choose to use the word "Twitter," though it had been a dictionary word long before the microblogging company adopted the term.
"Regarding the use of the word Twitter in projects, we are a bit more wary although there are some exceptions here as well," Stone wrote. "After all, Twitter is the name of our service and our company so the potential for confusion is much higher. When folks ask us about naming their application with 'Twitter' we generally respond by suggesting more original branding for their project. This avoids potential confusion down the line."
Personal bookmarking service Read It Later has some nice new features this week for both users and developers.
On the user side, there's now an updated version of its reading application for the iPhone, which lets users access their saved reading list even when they're not near a data connection. The new version supports both password-protected sites and articles that are spread out over multiple pages. Once you've plugged in your password to a site that needs it, the app stores the password so you don't have to enter it each time the app needs to fetch a full article. And for stories that span multiple pages, the application will automatically detect this and download the content from the remaining pages.
Other small tweaks include an easier way to turn the auto-ration lock on and off, a currently-reading and recently-read list, as well as a scroll bar that lets you quickly jump to a later part of an article without having to do the Running Man with your fingers. It even shows you how far you've scrolled down in any given article, so you can hop back to where you were. These are small touches, but they can speed up how you navigate to and from each piece of content.
For developers, the service has updated its API to allow third parties to pull user data. Previously they could only write to it. This could make for some exciting apps in the future; one being a version of the software that can download article data in the background, even when you're not running it. As it stands with Read It Later for the iPhone, it can't download new article data for offline reading until the next time you launch it and have a data connection. Other platforms that allow background processes may see richer, fuller apps because of this.
Some of Read It Later's new iPhone features in screenshot form. Click to see in full-size.
(Credit: CNET)
On Tuesday Digg announced big changes to its API that should make third-party developers happy--and maybe even rich.
The most major one being that the company has let up on its use for commercial applications, meaning that developers will be able to create services that take advantage of Digg's content and community without first having to ask for permission from the company. This includes pulling in content from the service and either charging to do so, or including on-page advertisements--two things which kept application developers from making a profit, or even charging for their creations.
The old and new grant of license for the Digg API. (Click to enlarge.)
The updated application programming interface also includes:
- • Access to the site's search engine which was overhauled back in early April. This lets developers add search to their own apps, and use all of the specific modifiers and domain filters that are found on Digg proper.
• Access to stories people have marked as favorites, as well as the related stories and keywords on any item they may be viewing. This is something that Digg rolled out late last year on its story pages and has kept more users clicking on other stories within Digg
Digg VP of engineering John Quinn says that following this release, the Digg API will finally be updated to allow third-party applications to "participate" on items on the site. This includes digging and burying stories, along with commenting, "favoriting," and marking stories as inaccurate or lame. Until then, even with these updates, all third-party applications are simply viewing activity from users who are accessing the site from Digg or Digg mobile.
After watching other photo hosts create simple tools for Twitter users to post pictures, Flickr has finally wised up and pushed out its own solution. By divining the popular photo service with access to your Twitter stream, you can now post individual shots there right from Flickr, complete with a fancy Flic.kr shortened URL.
Instead of adding a new button to do this, Flickr users simply set up Twitter as if they were adding another blog to post photos to. Clicking the "blog this" button takes you to a page where you can type in the remaining 116 characters, and see the shortened Flickr URL which is added to the end of the Tweet. You also get a special variation of your Flickr posting e-mail address that directs e-mailed shots directly to your Twitter stream at the same time they're hosted on Flickr.
Flickr users can now Twitter straight from Flickr without any hacks or third-party add-ons.
(Credit: CNET)Flickr still has a ways to go before its a part of third-party Twitter apps. Part of the problem is that most competing services, like YFrog, and TwitPic, don't require users to create accounts. In many cases they simply create them automatically based on Twitter credentials. Flickr, on the other hand, is a service you have to sign up for in order to use. I'm not so sure it would be willing to lift that restriction just for Twitter users, but it would certainly be a great way to woo new ones.
See also:
TwitPickr cross-posts TwitPic images to Flickr
Tweet your favorite Flickr shots with Autopostr
