|
Thursday, June 13, 2002
Combating Spam
osOpinion writes about using Reverse Filtering for fighting spam. Its an interesting idea, and worth considering (and even implementing). Spam is problem no. 1 for Email.
Linux vs Microsoft in Countries
IDG writes about the status in various countries on the Linux-Microsoft battle: "Government officials the world over are getting drawn into the debate over the relative merits of using open source software rather than Microsoft Corp.'s Windows applications and other software developed by vendors who closely guard the intellectual property of their source code. Some countries, such as Germany, have decided to replace Windows and other commercial software products with open source applications. Other countries remain committed to commercial software, and yet others are straddling the fence." There is really no excuse for low-income countries to use Microsoft software. This is the opportunity has -- on desktops and servers for the next set of users. Also see: Slashdot discussion
Hot Portals
This is what Emergic's Digital Dashboard will do: by combining Blogs, Outlines and RSS Aggregation. I will be writing more on this in my Tech Talk column next week.
Enhancing Emergic.org
Recently, we added the Search feature to Emergic. A few more things I'd like to do in the coming few days to enhance the weblog and increase its navigability: - Add RSS NewsFeeds (headlines) on the Top Page to provide context of what's happening in the world. Its an idea I have learnt from Samachar. There is a lot of value in providing an aggregate on a single page. Initially, we will begin with feeds from Moreover, but later we'll go direct to the sources. The three sub-segments will be Emerging Technologies, Emerging Enterprises and Emerging Markets. Here's a initial version. Its currently on a separate page. We need to put it on the home page and the Archives page (related to the date, so there's a memory built in of the day's top stories). - Show comments in-place with the blog post: people don't like clicking once more to read the comment. Also, by adding comments in place, they'll also get indexed for search. - Outlines on the Month Pages: the Month pages (for May and June) carry all the posts. What I really want is a listing and abstract of the posts, with a link to the actual post. Need to be able to scan dozens of titles quickly. We have written an Outline Web Service which we should use for this. - Recent Entries links need to be to the Permalink and not the date. - Integration with an RSS Aggregator: we are checking out a few RSS aggregators. Need to combine so I can post directly from the Aggregator, the way Radio does. This will dramatically improve my information processing speed. - The RSS feed which gets put out currently takes 50 words. Need to change that so it takes 1-2 sentences. The 50-word limit means it gets cut midway in a sentence which looks bad. - Give each post a unique name (the "a name" rather than the 6-digit ID which is currently being generated). - Upload all my earlier writings from 1995 on the blog (or perhaps start a separate one under rajeshjain.com). Currently, my writings are spread across Samachar, IndiaLine and Google's archives. They need to be consolidated in one place under my control. Just for posterity's sake. - Relook at the Blog Daily concept I had...its a good idea. - See how to leverage referers and backlinks. Am not using this info at all right now.
Comment from John Robb
I got a comment from one of the people I respect deeply (he's #3 on my BlogRoll) and who probably doesn't know that because I haven't ever told him that (and neither have I met him). He is John Robb of Userland. John's weblog is a daily must-read for me, for his incredibly thoughful (and thought-provoking) postings. John has been advocating the concept of K-Logs for quite some time, and I like it very much. So much so, that it's going to be one of the key pillars of Emergic as part of the Digital Dashboard. John wrote in on the RSS post. His comment:
John, you made my day! And yes, I am a member of the K-Logs group though I haven't posted there yet. Regarding the software on the desktop point, our viewpoints are different because our target markets are different. Your audience is the hundreds of millions of existing users who have thick desktops and are primarily in the developed markets of the world. They need Radio on the desktop. My target are the hundreds of millions of new users who cannot pay for the thick desktops -- they need computers and software at a tenth of the prices that they are available at today. These emerging set of users (the next 500 million) are in the world's low-income countries, the developing markets of the world. Emergic is all about making computing affordable to them. They will use Thin Clients (second-hand/used computers) with Thick Servers. But we need to make the latest software available to them -- they too want to become real-time enterprises. These are the themes I write about here in Emergic.org and Tech Samachar.
Digital Dashboard
| PermaLink
| Comments (5)
I think this RSS aggregator stuff is cool! In fact, thinking further, I see a time when there could be "Aggregator" services for a "fee". People and (especially) businesses, would pay to get information to their desktop, minus the "noise" with its obvious cost, both in terms of time and productivity. Nice site you have! Posted by lolitaHUH ) Posted by PreteenGreetengs Posted by UnderageViagra
Thick Server at ISPs?
One idea which came up as I was discussing the Emergic ideas with a business partner recently was putting the Thick Server(TS) at ISPs. My initial reaction was No, thats like the ASP thing -- we want the TS on the LAN. But, as the partner explained, the speed offered by an ISP who is using Cable or Ethernet (or in future, even 802.11b) for last-mile access is 10 Mbps or more to the ISP premises. This is just like a LAN. Beyond the ISP of course the speed goes down quite a lot (to the Internet). But if the Thick Server can be remoted to the ISP, then the Thin Client (TC) can be placed at many more locations which previously we had not thought. For example, the TC-TS can be used to offer applications in a residential access -- the individual apartments are being wired for Internet access, but where's the device to connect to the Internet? The PC is still too expensive for most people. Also, shopkeepers could be connected in a chain to the TS at the ISP. It again goes back to the basic theme of Emergic: providing computing solutions to new users. The price-point of Rs 750-1,000 per month (USD 15-20) for hardware, software, training and support is unmatchable and opens up segments which hitherto haven't been imagined. The key of course here (besides the attractive price point) is the sharing of the Thick Server across multiple Thin Clients. This becomes possible because of the LAN-like speeds (10 Mbps) for the last hundred feet.
Thin Client-Thick Server
| PermaLink
| Comments (1)
One of the issues with locating the TS with the ISP / Data Center and giving it out as a ASP service, is the fact that whoever uses that service would have to use the tools provided on the TS at the ISP end. The current freedom of choice, that a user has when it comes to choosing a software they are comfortable with, will no longer be available. Another issue, from a business point of view, is the fact that all businesses are different and each would like to use software that they find most closely approximating their style of work. Hence, in their case, except for generalised accounting software, using an ISP services would not be acceptable. The solution would be for them to host their own TS through colocation at a data center, if they want WAN coverage. This means a little more expensive solution, but to get a WAN coverage any other way, would just be more expensive anyway. The third issue is language. How do you address the needs of a multi-lingual community (especially in the case of a residential locality), through a single TS? Otherwise, I fear this concept, however good it may be, would be restricted only to the English-speaking world.
Thin Client - Migrating Mail
Have been using a Thin Client (on my 2+ year Fujitsu notebook) for the past few days. The bottleneck on the complete switchover was migrating my Mails and Address Book to the Thick Server. I had been using Outlook Express for the past few years and had accumulated 1 GB of old emails and a 1000+ address book. To move the mails, we created first an IMAP account for me on the Thick Server. Then, we imported my Outlook Express mails and address book into Outlook under Windows. Final step was moving the folders from Outlook to the IMAP accout on the Thick Server in Outlook. The address book was a bit more complicated as we had to write a few utilities to convert from the Outlook Express format to the one Evolution needed. All that is now left is another 1 GB of mails in another "identity" on Outlook Express (these are mails from 1.5 years and more ago, which I rarely refer to). We will do that in the near future also. The Thin Client overall works fine -- I mainly use the Browser (Mozilla) and Mail Client (Evolution). We still need to iron out some server stability issues, but thats to be expected. The key challenge was to move a person like me who had become quite used to Windows in the last 3 years (had earlier been using Linux and Unix before that). Come to think of it, the transition is quite easy provided one has an open mind. These are early days, and I'll need to see how OpenOffice shapes up. But I think the hard part (migrating the mails) has been done.
TECH TALK: Rethinking Enterprise Software: The Solution Framework
The four key trends we discussed in the past few columns were:
There are four key ideas in thinking about enterprise software framework for small and medium enterprises in emerging markets.
Even though the ideas may seem from the past, what is needed to take all these ideas together such that the whole is greater than the sum of the parts. The technologies of today and tomorrow are going to play a critical role in making this vision a reality. I will elaborate on each of these points in the coming columns. Tomorrow: Software Components
|