Thursday, March 29, 2007

Scripts on the Internet

I am back from the ICANN conference in Lisbon and, I have the T-shirt to prove it :) At a meeting the BSI proposed to create a standard that will describe how a mandated list with a ccTLD for every country or territory is to be produced in other scripts. This would be an industry standard that would eventually be adopted by ISO. Having such a list would be truly beneficial to get to the stage where the registrars for these registries know what codes to use. I have been told that a list has already been compiled for the Arab and the Cyrillic script.

On the BBC-news website there was a great story that explains why it is so important to allow for content in the language that people speak ..

One other thing I learned is that you can already have a .org domain name that is in an UTF-8 script. To me this is quite important because it proves that supporting UTF-8 is something that can already be done. It would make such a difference if the Internet was as functional as it is for us people who read and write the Latin script.

Thanks,
GerardM

Monday, March 26, 2007

Cryptography

Today I am at the ICANN conference in Lisbon. For me it is quite special to be here. One of the nice surprises was a gentleman editing on the Wikipedia article on Implicit Certificates. These are some special certificates for use in smaller devices. He mentioned that after writing this article, within the hour relevant edits were made to the topic.

The great thing for cryprographers is that Wikipedia provides both support for LaTeX and as relevantly, it can be updated when new developments happen. This makes Wikipedia an excellent environment to maintain information on this domain.

Thanks,
GerardM

Thursday, March 22, 2007

Citizendium and licensing

In yet another diatribe Dr Sanger informs us about the differences between Wikipedia and Citizendium.

The thing that struck me most are two things; contributors have to give a non-exclusive license to Citizendium AND the license is now to be the Creative Commons CC-by-nc license. The consequence is that only the Citizendium organisation can license commercial use, obviously for a price. They assume that as it is to be written by experts it will have value. It also means that once licensed, the licensee can do whatever.

When you compare Citizendium with Wikipedia, you have an English only versus a multi-lingual project. You have a project that covers almost everything and a project with a few thousand articles. You have a Free project and a project that is increasingly restrictive. You have a project that informs the world with NPOV information and a project that is to be written by experts.

Really I think Dr Sanger is doing a great job promoting Wikipedia by increasing the differences.

Thanks,
GerardM

Wednesday, March 21, 2007

Supporting the visually impaired

The content that is created in many Wikis is really relevant. Wikipedia for instance provides you with unsurpassed encyclopaedic type of information. This popularity can be deduced by Alexa's current ranking for today .. number 9. For us users and editors of Wikipedia it is like a roller-coaster; it is exhilarating :)

For people who are visually impaired, several of the Wikipedias have projects where people record the articles .. Really nice, really relevant.

Today I learned about new software promoted by UNESCO called Sakrament Libreader, it allows for text to speech conversion for English, Russian and Belarussian. Just consider, the English Wikipedia takes, according to Alexa, 53% of our traffic. There is a certain percentage people that are visually compared to the unimpaired.

Consider what would happen if the Wikimedia Foundation would support and promote this kind of functionality. Not only would many people be helped by this, it would also give an impetus to make this functionality available for other languages..

Thanks,
GerardM

Saturday, March 17, 2007

IATE became available

IATE or the Inter-Agency Terminology Exchange became available as a resource on the Internet. An introduction to IATE explains nicely what IATE is about; it is about the terminology of an organisation; the European Union. It aims to demystify the jargon used by the organisations of the EU.

In the past IATE was accessible as well; it proved popular and it was quickly hidden behind a password. This time you can get access by using the URL http://iate.europa.eu and it hopefully means that this resource is now officially available.

When you compare IATE to what it replaces, it is a massive step backwards from a copyright point of view. EURADICAUTOM was available under a much less restrictive license. It would be nice if the EU would steal a page out of the US book; most of the information provided by that government is available without restrictions.

Thanks,
GerardM


Tuesday, March 13, 2007

Google Summer of Code

Google has announced its third Google Summer of Code. This is an annual event where students develop on Open Source projects. This is definetly one of those activities that does a lot of good. It is one way whereby Google makes its mantra of "do no evil" work well.

For Open Progress, we have entered for a first time; we have a nice mix of MediaWiki and OmegaWiki based projects. All these projects are dear to us. We have shown Brion our list, and we are likely to work together on these.

What struck me is that when you apply for the GSOC, it is compulsory to have a mailing list. This is the traditional way of doing things. I am subscribed to many mailing lists. I think mailing lists suck big-time. There is so much repetition, the signal to noise ration is typically quite bad. I do not understand why people do not use a wiki to document and discuss.

I think this is one of those instances where software development proves to be conservative. When you follow the subjects you are interested in on a wiki, you can use watch lists to make a selection, you can use RSS to follow the changes on a low bandwidth wiki.

Because you refactor what is there, there is no need to repeat so much. When you have discussions that are getting out of hand, backrooms can be opened for those quarrelling. Maybe I am an idealist that I see it in this way .. oh well ..

Thanks,
GerardM

Sunday, March 11, 2007

Fon or Meraki .. I want the functionality of both !!

In the field of Internet connectivity, WIFI is the thing that keeps a road warrior and Internet junkie sane. It also keeps him poor. The amount of money some companies dare to charge for connectivity is tantamount to high-way robbery. Particularly at places where you have to spend lots of time, like hotels and airports are really unfriendly places. Particularly in airports it is galling; you have to be there so many hours in advance, you are often delayed .. it would make more sense to provide it for free and in that way keep the punters happy.

With many Internet organisations increasingly dictatorial in what you can and cannot do, with intellectual property organisations only interested in filling the pockets of the big companies, WIFI is a next place where the people can create a commons away from these established malpractices.

Fon is a WIFI sharing organisation where you provide access to other fonistas by sharing the Internet connection. In one of the more innovative approaches they are targeting the neighbours of Starbucks with free routers. The business model is that you can pay a small amount for access to the network.

Meraki is a WIFI sharing organisation where you provide Internet connection to an area using a mesh network. By including repeaters in strategic places, the area covered can be quite extended and, multiple Internet access points can be part of the same network. When you operate a network, you can determine who can access the network and even provide access for money.

I would like to have a mix of both. At home Meraki would be ideal because my ISP uses a different technology from the ISP of my neighbour. This means that I will improve the connectivity both for myself and for my neighbours. It also allows for providing truly local information. Fon would be ideal when I am away, with an increasing number of fonistas it means that me providing connectivity is the assumption of good faith that will find its sweet rewards.

Combining the two would be awesome. I would not hesitate long to go that way.

Thanks,
GerardM

Wednesday, March 07, 2007

Localisation of MediaWiki

There is a policy for new languages in the Wikimedia Foundation. One of the key things is that we want to prevent new abominations of projects where the language is not what is advertised. We have seen these in the past; one of the worst in this is what is called the Belarus Wikipedia; the people in control of this project prevent the use of the Belarus language as it is used in Belarus. This is a really awful situation and the language commission has asked the board repeatedly to act on this.

What we want to achieve is that new projects will promote cooperation in stead of establish division. Even though linguistically there is a substantial difference between the different forms of English, it is generally accepted that there will be only one English Wikipedia. This means that when the differences between two languages are less than for the different forms of English, the language committee is not likely to approve a new project.

When there is merit for a project in a new language, the people promoting this language have to show their commitment in the Incubator. This is where the environment in that language for the requested project is set up. What is expected, is that there will be a number of well written articles about different types of subjects, there should be a main page and, the most visible parts of the user interface should be localised.

The sad thing is that the aspiring projects cannot conform yet to the requirements; when a new Incubator project is set up, the message file for the new language is not created. What is needed is for one of the developers to create the necessary files so that the localisation can start.

For many languages in the past, there is no message files either; it means that the localisation is done locally and that this effort does not lead to the localisation of the MediaWiki software.
I am really pleased that for one language, Marathi, many of the messages have been imported into SVN by Nikerabbit. In a few days Marathi will be supported in all WMF projects. :)

I would welcome it when the Wikimedia Foundation gives the support of the minor projects a priority. At this moment it has none. The creation of message files in the Incubator for all languages and, when a language becomes a project, the inclusion of the first localisation into the MediaWiki software is the bare minimum. When we boast that we have localisations in some 250 languages, it should be a verifiable truth.

Thanks,
GerardM

About dictionary writing

Connel MacKenzie is one of the English language Wiktionarians who has had a big influence on the development of the Wiktionary project. He published his notions about what a dictionary should be. As I have posted a response to what Erin McKean, the current editor in chief for the NOAD, said in a presentation at Google, it is nice to write about in response to this as well.

For Connel, the project is about the English language. This is a big difference in approach to what Wiktionary is said to be about. He wants to limit it to those words that are part of the 600.000 most common terms. This is problematic because how do you judge something to be common and, what is common in one branch of the English language might not necessarily be common in another. He is of the opinion that "freak" terms should only be there in a sanitized form. To me it is important that a term is clearly and fully explained. When you "sanitize", it is not clear if the full meaning survives for someone who does not know the term. By disallowing multiple word entries, you loose the connection to those entries that are single entries in another language..

In his commentary, Connel writes about the restrictions that faces Wiktionary that are the consequence of its flat file format. You can not segregate different types of content when the basic technology does not support it. At that he would be better off being part of OmegaWiki as its technology allows for all the things he is looking for.

He hopes to get a useful Wiktionary when he has a dozen programmers available for such a project. At the same time he despairs because of "the current anarchy" it may take ten to twenty years..

I do admire the constructive work Connel has put into Wiktionary. I doubt that Wiktionary will ever become useful other than as a resource where you can look things up on the Internet.

Thanks,
GerardM

Tuesday, March 06, 2007

Upper ontologies

"An upper ontology attempts to create an ontology which describes very general concepts that are the same across all domains". As almost always there is a Wikipedia article about this. Given that the subject is difficult, there is since August 2006 a request to clean up this page .. I have to agree that the subject is interesting and potentially controversial.

For OmegaWiki, an upper ontology is one of those things.. An upper ontology defines the broad strokes, and while it descends downwards more and more aspects may be inherited from higher levels. This means that an upper ontology has practical implications. It also means that we will eventually have in effect an upper ontology by default.

As an upper ontology creates the concepts that are true across domains, Wikis for Professionals will want to define how their ontologies fit into the upper ontology. As they are bound to have overlaps with other domains, there will regularly be found to be in conflicts between domains. As one WfP needs to link into other domains, the question of primacy will raise its ugly head. One WfP was there first, but this other domain is not its competency... A new WfP does have the competency but is disrupts the existing WfP...

An initial selection of an upper ontology will be crucial, its evolution will be exceedingly important when OmegaWiki will is to be bound by the integration into it. Personally I expect that a different model will arise; one where on the one hand great care will be given to the evolution of the upper ontology while on the other hand functionality will be created irrespective of the upper ontology.

Consider, when you know that something is a plant, you can infer all kinds of things about it. It is not really necessary to know how it fits in the greater scheme of things. It would be nice, but it is not required. When a lot of functionality is determined in such a way, there will be the question how this will fit together; it is therefore my prediction that these two forces will eventually find a balance. As OmegaWiki matures, this balance will become increasingly stable.

Thanks,
GerardM

Wednesday, February 28, 2007

NIH Wiki Fair

The National Institutes of Health organised a Wiki fair today. There have been great presentations; the line-up of speakers and subjects was impressive, many of the presentations are on line and the whole presentation can be seen as a video as well ... all 5:41 hours off it...

For Wiki aficionados particularly interesting are a presentation of Dr Larry Sanger, and Dr Barend Mons. Larry is part of the Wikipedia history and Barend is part of the OmegaWiki presence.

Larry's presentation is self serving; he gives a selly presentation about Citizendium and he urges the people from the NIH to join in his project. That is in and off itself OK as he just what he has to do. As the raison d'être of Citizendium is in doing a better job than Wikipedia there are loads of comparisons with Wikipedia.. It is not surprising that you find no nicks when that is your policy, it can not be considered something that is "good" in comparison. Given that Larry finds it relevant to be known as Dr Sanger, I would expect a more scientific approach to his presentation. Given the small size of the project, it is not so strange to find that there is a lot of harmony around. This is very much the experience of all Wiki projects. It has been well documented in many scientific papers and, I am sure is Dr Sanger aware of this.

Being part of the history of Wikipedia and having created Citizendium as a reaction to what is considered "wrong" in Wikipedia means that Citizendium will always be compared to Wikipedia. I think that having started from scratch is daring.. It is the right thing to do. There are certainly more scientists working on Wikipedia, and given that Wikipedia has more than 1000 times more articles, it will be interesting to see what kind of attention this project will get.

Thanks,
GerardM

Saturday, February 24, 2007

Open Access

Given that I am very much in the open source and open content world, it will not be a surprise that I am very much in favour of open access and that I do not think highly of the patent system.

I think that it is easy to argue that patents kill. My argument goes like this; the pharmaceutical industry is documented to be only interested in patentable medicine. When a medicine is not patentable, they do not have an incentive in researching its application for particular purposes. Recently the university of Alberta found by accident that dichloroacetate (DCA), appears to suppress the growth of cancer cells without affecting normal cells. The problem is that there is no funding for doing the research to prove the efficacy of this medicine. It is therefore easy to understand that only substances that are patentable are considered in much of the bio-medical research.

I think that is is easy to argue that the classic business model for scientific publishing kills. The cost of reading scientific articles is staggering. The article published in Nature about what is demoed on wikiprofessional.info, for me it is a really exciting article, for me this really relevant article costs $30,- to read. I can not lawfully send it to my mother to read. I can only tell her. Scientific journals assume that the only people who need to read their papers are scientists; the scientific libraries will have a subscription and that is how it has always been. Except that it is not true. Laymen have as much a need to read bio-medical science papers; they or their loved ones are affected by all kinds of afflictions. They have a need to understand what is happening to them. Often doctors do not know all the details that are available and , there are enough documented cases where research on the literature by laymen made a difference. One famous example is known as "Lorenzo's oil", a story about a disease called adrenoleukodystrophy or ALD.

Not only laymen are denied access to literature, many universities cannot afford the cost of literature. With the science results owned by business, it is important to understand how vital the whole "open" movement already is. A new, a different business model is needed and many organisations are developing these. The big challenge is for science to become science again; to be able to research without having the public pay again and again and some companies walking away with only an eye for profit.

The challenge will be to find a balance that does justice to all parties involved.

Thanks,
GerardM

Thursday, February 22, 2007

Mother language day

Yesterday, it was the International Mother Language Day. There is a program in Paris with all kinds of speeches and happenings. I read the program, I know some and I know about some of the people involved. I wish I was there. I wish they recorded some of the speeches, presentations.

One thing I find funny is that UNESCO indicates that there are some 6000 languages where SIL indicates the existence of over 7000 languages and where the ISO-639-6 will know at least 25.000 linguistic entities .. :) I wonder if they need to be emancipated so that UNESCO will feel a need to at least acknowledge their existence..

It would be cool if International Mother Language day had hit the Internet; a podcast would have been nice ..

Thanks,
GerardM

Sunday, February 18, 2007

A root canal treatment anyone ?

Yesterday, I had an appointment with a dentists specialised in the noble art of endodontics. I had a molar that had already had a root canal treatment before and it needed some more work. I was nervous. Actually I am terrified of dentists and consequently I am my own worst enemy as a person suffers most from the suffering that he fears and that often never materialises.

So I went to my appointment and I was wearing a Wikimania 2006 t-shirt. A person waiting in the reception reacted to this and, we got to talk about science, creating educational content in a collaborative way, licenses and copyright, OmegaWiki, the Nature article and the Wikiprofessional demo.

When it was my turn to sit in the "chair", the doctor had heard much of the conversation and asked several questions.. There was no time gap between being operated on and talking about the things that are so dear to me. One big difference between what an endodontist does and what a dentists does is in the tools of the trade; an endodontists uses microscopes and a lot of digital imagery. It really gave me the feeling that I was operated on. Anyway, after the operation I gave a demonstration to my endodontist.

The good news is; I did not have time to be nervous.. Two more people may have a good look at OmegaWiki. It feels good even though my molar is still sensitive .. :)

Thanks,
GerardM

Friday, February 16, 2007

A friend of my is a scientist...

A friend of my is a scientist. He is a terminologist. He has published a lot of papers and, he is considered one of the best in the field by some other people I know.

I told him about wikiprofessional, what kind of things we are doing in the bio-medical field. What we could do for other fields as well when we have the terminology available to us. This was two days ago. Today I learned that much of his work was once available on diskettes. These diskettes were no longer there .....

I discussed this with another friend. She has some great OCR-software. We know each other, so when the terminologist scans his paper paper, the translator can translate it from a analog into a digital format. The terminologist can define his terminology, his papers will be known but as relevant, we will have started supporting the terminology of terminology in OmegaWiki.

It is great to have friends ...

Thanks,
GerardM

Friday, February 09, 2007

Cleaning a bit on the sk.wiktionary

Many of the Wiktionary projects have a moribund existence. At some stage people worked on it. They left the project, things changed and where never properly taken care off. Today I was in an extended chat and I was not the lead talker, so I had some time to do some stuff that does not take much attention.

I cleaned up a bit on the sk.wiktionary. At some stage all Wiktionaries supported proper casing. This meant for the acronyms like ADHD that they became aDHD. Somebody needed to go and fix these so that they became properly ADHD. Today I fixed more than sixty acronyms that started with a, there are many more of these that need fixing and, not only but also on the Slovak Wiktionary.

I am really pleased that at OmegaWiki we only need to fix things once..

Thanks,
GerardM

Thursday, February 08, 2007

The Shtooka recorder

I was told to have a look at the Shtooka recorder. It is a tool that makes it really easy to record the pronunciation of words. You provide it with a list of words, you provide the meta data and, it creates an .ogg file for you in the directory of your choice. It makes it really easy..

For me the challenge was to understand how to use it. There is no user manual and mostly it is self evident. So when I understood that I had to press on the "record" button, it started to work.

This software does do wonders when recording words that are provided in a Latin script. I tried it to record a Persian word, کم حرف and it failed. I checked it with something Russian and it failed as well.

For me it is a big improvement, I did some 15.000 words with Audacity.. It would have saved me a lot of time when I would have had Shtooka.. The next thing to automate; the uploading to commons...

Thanks,
GerardM

Friday, February 02, 2007

Ten things you want to know about dictionaries

I met Erin McKean at the Wikimania 2006, I loved her presentation then and I was really happy when I found her presentation in the Google Author series titled "Ten things you want to know about dictionaries". I loved it, I have seen it twice now. I may even have added value to it by adding the "dictionary" label to the presentation. Here I am going to react it with my OmegaWiki hat on. So yes, please watch the presentation (almost an hour and well worth it) as I hope it will improve the understanding of my reaction.

There is no one dictionary; it is a tool
OmegaWiki as a resource is very much a child of the Internet; consequently it has the potential to configure its use. When people do not care for particular information; they should be able to make it invisible or turn it off. In a way it is like the cordless drill, by replacing the drill with a different thingie it becomes an other tool. The same is true for pronunciation; we love to include IPA, but we can also record pronunciations this way people do not need the understanding required when reading IPA.

Please read the "front matter"
People indeed assume that they understand tools like dictionaries and wikis for that matter not to RTFM. For a consumer good like a read only lexical resource, it is pretty safe when the introductions have not been read. As OmegaWiki allows people to add/edit to the information that is in there this proves to be much more problematic.

Inclusion in the dictionary is because it is useful
As we do not have all the functionality that we need to be a credible lexical resource, this is very much a state we hope to get at. However, our aim to include all the lexicological, terminological and ontological sounds pretty like megalomania. Our standard excuse is that we use is that is already less problematic because we only want to do this once and this is where we came from. The data will only be useful when there are people who care about particular categories of data. I am totally with Erin that only data that is useful should be included. Getting rid of unnecessary cruft is hard work.

Horrible words make it in their too
I am a fan of swear words in dictionaries, particularly when there is some etymology to it. Most often people use swear words as an expletive without much understanding for their actual original meaning. As English is for me a second language it is relevant for me to understand why I would rather be a bigot than a racist or someone who discriminates.

The other part of horrible words are those words that are actually used and offend the aesthetic sensitivities. In several medical resources you find stuff like MALARIA and Malaria. UGLY. However as it is useful to these folks, it makes sense to include them anyway. As they are exactly the same as the preferred English expression of malaria, it does not hurt.

Words like "irregardless" well being a non native to the language, I just want to be able to find them.

You have to look at all definitions to find the REAL meaning
The way the New Oxford American Dictionary does this is exquisite. They use a core sense / sub sense approach. To me this seems an approach that is very much language specific. For OmegaWiki to have such an approach, it will need quite a lot of thinking on how to build this.

Approaching the understanding of an expression with core senses / sub senses could be one way of stretching the number of concepts that people can juggle with. For Operational Definitions there is currently this practical limit of some 7 different meanings.

Dictionaries have a sell by date
For OmegaWiki this is not an issue as it is web based resource. However, the same issue still applies; a Dutch book printed in 2003 will use the orthography of 1995 and not the 2005 orthography. People will still want to be able to understand what this word means; annotating them as not being the official spelling since 2005 is relevant.

When words are tagged as used in earnest up to a certain date, I could even include 15th century German words and not have people be confused.. filtering would also help here ..

Facts are good
Referring to actual usage seems obvious, what we intend to do is link OmegaWiki's content to Wikipedia, this will be the most obvious resource to start of with; we aim to have a Wikipedia in all languages. The language is modern usage, so given our Wiki credentials it is the obvious corpus. I totally agree when it is said that we are limited in this way; it is however a great start. When we gain a community with people, organisations that introduce us to other resources, it will be great.

At this moment OmegaWiki is still very much like a "stamp collection"; it is a nice collection, and at some stage it will even become useful.

What we do is like an iceberg
The work done on the New Oxford American Dictionary may be in preparation for the moment when other information like thesaurus information will be included. For OmegaWiki, including information from thesauri is what we did from the start by including the GEMET data, OmegaWiki at this moment is very much "you get what you see", there is little of an iceberg yet. In a way this prevents the usefulness of our data because there is often too much to take in.

Etymology
Technically etymology is one of the hardest nuts to crack. When a word has its root in Latin, it often came to the English language through a French or Spanish connection. I wonder how the NOAD does this, indeed I do not have a copy so I have not read the "front matter" either :) .

Neologisms
At this moment there is not much of a problem about neologisms yet. Our community is still small and sane.. sort off (you must be weird to involve yourself in a project like this). My current thinking is that this problem can be solved using annotation. When a word is tagged as "Neologism; this word is not used except by the author" it will be pretty devastating to the prestige of the word and or the author on OmegaWiki.

The bonus: Using Google and other resources
Erin explains that the resources for building a resource like the NOAD are hardly as much as she would want. Given that this is true for a successful resource for the American English market, consider what this means for languages like Kituba, Stellingwerfs or Seeltersk. Consider what it means when you want to use a translation dictionary for such languages.. These resources become a reality when there is the necessary cooperation; this is what OmegaWiki hopes to achieve.

There is a need for people to work on their terminology and indeed we would like to include the terminology of falconry, tennis, and ships. It will happen when it does.

Q&A
*OmegaWiki does want to include out of copyright content as well. For us it is a start. Collaborating with for instance WordNet would be however more important and relevant.
*Proper names; yes we want them; we have George W. Bush already for quite some time.
*We would retire words by indicating them with a date indicating when they went out of use
*Circular definitions are even more problematic in OmegaWiki, this is a great example why.
*Context .. yes, I wish this was a problem that we have to deal with.. we need more functionality
*Print versions .. this is at this stage no issue. Nobody has indicated that they want to work on this.

Conclusion:
I really enjoyed Erin's presentation. It helps me to get my mind around issues that have not popped up for OmegaWiki. As many are quite will make their appearance, it is best to be forewarned, it allows us to get forearmed.

Thanks,
GerardM

Thursday, February 01, 2007

Google defuse the googlebomb .. GREAT

When you are of the opinion that George W. Bush or "Shrubya" is a "miserable failure", you could find confirmation for this by googling for this and this truth would be on top both in the Google, Yahoo or Microsoft search engine. Effectively it is a prank. It is not what you really want to find and Google announced it has worked on an algorithm that will prevent a Googlebomb in future. Effectively making the word a misnomer it is now more correct to call it a Yahoobomb or even better, a Microsoftbomb.

In an article in the Guardian, the fear is expressed that by manipulating rankings in this way, Google will exert its power and be able to manipulate what is seen as true. At issue is that the reason why Google defused this bomb was because people believed it to be true because Google said so... (there is no such thing as common sense as common sense ain't common)

In many content projects, bots create links to websites they hope to make more relevant in the eyes of the search engines. This type of vandalism resulted in a backlash where Wikipedia now indicates to search engines to disregard any and all links and thereby invalidating the basis on which search engines operate. When Google were to have algorithms that filter and punish this type of SPAM, it would lead to a more sane environment.

Google is open about its intentions. Microsoft is open about its intentions as well; as long as it discriminates against its competitors like Wikipedia I will be happy to use Google knowing that Google is kept honest by having competitors.

Thanks,
GerardM

Wednesday, January 31, 2007

To skype or not using Skype

Skype is one of the most important tools for me. I have loads of people I do contact this way, they are all over the world. OmegaWiki is possible because of using VOIP is easy. I talk with people on every continent except for Antarctica. For me it proved to be an essential tool.

The problem is that several of my most relevant contacts do use Windows and the quality of the Linux implementation does not cut it. Skype freezes the sound system erratically or it just does not install. One of my friends wants me to use SIP; he threatened me not to talk to me any more.. Remember, this is a relevant contact to me.

We had a look around and we found that we can connect a SIP service to Google talk. This worked great; I can connect using Google talk. If there is one thing lacking, it is that I can not initiate the connection to the SIP servers, they have to connect to me.

As I needed to find out if SIP would work for me, I installed Gizmo project. It basically does everything that Skype does, it uses a Standard protocol, in stead of a proprietary protocol.

My conclusion; to skype I do not need Skype. I would probably be better off when all of my contacts would not be using Skype at all. The message to Skype is simple; the one thing they have is a user base. The support for Linux sucks and this makes people look for pastures green. So, FIX IT !!!

Thanks,
GerardM