|
Monday, March 3, 2003
Rural Tech Innovations
The reality about rural areas in India (and perhaps other emerging markets) is that power (electricity) is scarecely available, and telephone lines are either not there or don't work most of the time. In this context, if we want to set up teleinfocentres with 3-5 computers per village (thin clients with a thick server, and using open-source software), how do we do it? I have been thinking of some of the innovations we will need in technology to take computing to the rural areas of countries like India. 1. Power: Pedal Power (Car battery, powered by bicycling - Pedal Power, like what's being used by the Jhai Foundation in Laos), Solar or Wind Energy 2. Power Supply: Think of using a 12 Volt supply for all the PCs directly, rather than stepping down the 230 V supply for each PC as we do now. 3. Connectivity: WiFi as a wide area network, or perhaps, Wireless Mesh Networks. The key challenge is the distance - to make a wireless WAN solution work, we need it to work over distances of about 15-25 kms (10-15 miles). It would be nice to get an always-on connectivity via wireless, because then the village can just have the thin clients and the thick server could be a shared infrastructure across multiple villages. 4. TV as Monitor: The monitor is now turning out to be the most expensive part of the "thin client". A new monitor costs about USD 100 (Rs 4,500-5,000), while an old monitor costs about half of that. A TV is already available in most rural areas, and is probably cheaper. How can we get TVs to work as computer monitors - such that we can get higher resolution displays? Any ideas or examples of what is happening elsewhere in the world?
Microsoft Middle Age
Seattle Times story, with a Bill Gates interview, industry market shares and a timeline chart. [Slashdot thread] It is interesting that people talk of the "post-PC era" even as 90% or more of the people in the world's emerging markets do not have access to computing. The PC era hasn't even touched them. This is the opportunity being overlooked by Microsoft as it seeks to retain its margins. This is the biggest invisible market of them all, and one which needs companies to work with 10-20% margins, not 80-90%.
Sony's Dreams
Economist writes about the breadth and depth of Sony's ambitions: Related Entries: [All]
Overture and Search
The most successful search company is - maybe hard to believe - is Overture. We may search at Google, but Overture makes more money. It has a simple business model: it sells search terms to the highest bidder. Recently, it bought AltaVista and the Web search division of Norway's Fast Search & Transfer. News.com has more:
I was among the skeptics of Overture (then GoTo). But I've been proved wrong. Now, as consolidation in the search business is underway (Yahoo recently bought Inktomi), it is interesting to see how the various players (including Google) evolve.
Swarm Intelligence
A topic I am fascinated with is emergence, where simple rules can generate complex behaviour (and the whole is much greater than the sum of the parts). Swarm Intelligence deals with applying these ideas of self-organisation from the world of insects to business problems. O'Reilly has an interview with Eric Bonabeau: Some quotes: Related Entries: [All]
TECH TALK: RSS, Blogs and Beyond: RSS Mailbox
Last week, we saw how RSS and Blogs are bringing forth a new era of microcontent and nano-publishing. This week, we will discuss a few ideas revolving around RSS and Blogs. RSS Aggregators (also known as News Readers) have been around for some time. Their popularity has been largely limited to bloggers. How can they be made to have greater mass-market appeal? It does make sense for each of us to get information (or events) pushed to us through RSS feeds that we subscribe because it amplifies our ability to process information. The idea I’d like to propose is a Hotmail-like hosted RSS Mailbox service. What this RSS Mailbox does is provide a POP/IMAP account into which RSS feeds that a user subscribes to are delivered. The user can add this account into his mail client. There it just shows up as another mail account. The user can then use client- or server-side filters to separate incoming RSS feeds into folders. The mailbox is also accessible from a browser-based front-end, just like a Yahoo or Hotmail account. So, in a sense, it looks and feels just like a mailbox, but is free from spam because only the feeds that the user subscribes to are delivered. What the RSS Mailbox does is to enable the use of the email client as an RSS feed viewer. In fact, if one sees the RSS Aggregators, most of them use a 3-pane format, with the left pane showing the list of subscribed feeds, the top right pane showing the item headlines,and the bottom right pane showing the actual item, with the appropriate permalink for the item. With this kind of similarity in look-and-feel, why not just use the email client as the viewer? This eliminates the need for users to download and install a separate News Reader program. All that is needed to access the RSS Mailbox is to add an account into the email client. If this is the case, then why not just set up an RSS2Mail feed? This way,the RSS feeds can be emailed directly to a user’s existing email account and the user can equally well set up the appropriate filters. The reason I have not advocated this approach is that we are getting too many emails anyways in most of our existing accounts, so separating RSS feeds may not be easy (they could be spoofed by spammers). Also, by setting up a separate hosted service, the RSS Mailbox is accessible even outside corporate firewalls and through a browser. Of course, organisations could set up their own RSS Mail Servers internally. On the backend, the RSS Mailbox Server would become a Google-like collector and sorter of RSS feeds. It would fetch the RSS feeds from news sites and blogs as soon as they are updated (if the sites ping it) or would do the botting periodically. It would then parse the feeds into the individual items, and distribute them (using a local mail infrastructure) into the mailboxes of the users who have subscribed to the feed. The RSS Mail Server would thus need to fetch a feed only once per site, unlike today when every blog which subscribes goes out and gets the feed. Of course, this means that the RS Mailbox Server would need to have plentiful bandwidth and storage. The side-effects of this approach are many. From the user’s point of view, there is a convenience. Just as one goes to Google when one is searching for content, one would go this RSS Mailbox Server for searching and subscribing to RSS feeds. In addition, by using collaborative filtering techniques (the way Amazon does), the service could also recommend other feeds and items that the user may be interested in based on what others with similar interests are reading. Take this further, and it could create clusters of like-minded readers. The RSS Mailbox Server could this become the ultimate reader-driven content-filter. Tomorrow: Events Horizon Related Entries: [All]
|
If most rural villages have TVs, how are they powered since you say electricity is scarecely available? Are they 12-volt? If not, you may also have a problem of powering the TVs.
Posted by Tom ChaseRajesh:
The points you have mentioned is the most important stuff to work on a priority basis.
I will try to provide some examples for the TV as Monitor issue.
The best example of somebody working on this is Microsoft. Microsoft provides the MSN Internet service on TV using a Set Top box. They have worked a lot on trying to address this issue.
The site http://developer.webtv.net/designing/default.asp provides "cross-platform design" needed to get the sites function on TV.
The site lists the main problems of the resolution
1.Resolution as Screen Size
2.Resolution as Sharpness
The next problem is the Text on TV. the Set top browser of Microsoft works by providing the following solution:
The set-top box browser performs two adjustments:
* Scaling: Text is rendered in a font roughly equivalent to 18-point Helvetica. This helps keep the text readable despite the flickering and fuzziness inherent to a TV screen, though it also means much less text fits on the screen.
* Arranging: The browser adjusts the wrapping of text elements to fit in the overall window and in the column assigned to it. For this reason fixed line breaks can make text hard to read. Moreover, since the text is displayed in a large font, text in narrow columns looks bad, with only one or two words per line.
Graphics:
Here Microsoft proposes a clever solution to the developers who create the websites.
One tool the developer can use is to display a message in the status bar in response to a mouseover. The status bar is prominent on the TV browser, and normally is limited to showing the page title. The bar can hold approximately 35 characters and displays in the default Helvetica font. If your site relies on small graphics for navigation, simply putting the link's text in the status bar can make a huge difference when your site is viewed on television.
The final solution Microsoft proposes
Content Across Platforms
Our platform generally does a good job of resizing and displaying HTML text-"normal" Web page text with HTML tags such as bold, italic, or headline-so that it's easily readable on a TV screen. To make your Web pages work well on our platform as well as other platforms, you need to find and fix the problems that do occur. Most problems occur in the following three areas:
* Small Text in Embedded Graphics
* Layout Problems
* Inappropriate Color for TVs
There are two solutions to making content work across platforms. Developers can simplify the layout and style sheets so pages work well across platforms; for instance, convert a three-column layout to a two-column layout. Or, adjust an existing site that works on a standard browser to get it to display more or less correctly on a set-top box browser.
The recommended solution is to create separate content for both platforms, as was common in the early days of Web design when Netscape Navigator and Microsoft Internet Explorer required specialized content. This way you do not have to compromise the site design for computer users, while still giving the set-top box viewer the most positive experience. By using design efficiencies and dynamic content the task is not as difficult as it was in the past.
For testing this stuff we can use the "The MSN TV Viewer" for the PC. The MSN TV Viewer simulates the TV browser on your personal computer. It can tell you if your Web content is appropriate for the receiver. It has tools to show you how content is altered to look the best on a television screen.
We can download (http://developer.webtv.net/Tools/MSNTVVwr.asp) this stuff and check out how best to make of it.
But the most important thing here is that Microsoft is providing a solution which all the developers need to work on who design websites which may be challenging.
Posted by Suhit AnantulaRajesh:
Continuing on the previous comment I found these on the Web
Opera Browser Makes Its Way to TV
http://www.idg.net/ic_711539_5035_1-2797.html
"We have a very small and fast browser, and there is not too much memory in those boxes; in order to have an efficient browsing experience, you need a small and fast browser, and that's what Opera has always delivered. Our focus has always been to offer a small and fast browser, instead of adding a lot of extra features."
I have also found a lot of companies which have started TV browsers but are closed now. Spyglass which is the owner of Mosaic is also one. Then you have ICTV.
The solution looks like take a TV Browser and then adapt it and use as the default for all the Emergic solution.
Posted by Suhit Anantulai think that we should know the correct usage of pedal power and the advantages in it.since we are in a highly populated and one of the major cities some of us donot know the importance of pedal power and other conventional sources.so in my view each and everyone should have a clear knowledge about things like this.
Posted by Ravi Tej