Thursday, January 12, 2006

The Hospitality Club became the first hospitality exchange network to pass the 100,000 members milestone on January 11, 2006. Its closest competitors, CouchSurfing and GlobalFreeLoaders, have 40,000 and 30,000 members.

Hospitality exchange organisations are dedicated to putting travellers in contact with locals offering to host them in their house for free, or simply offer them a tour of their city or share a meal with them. Besides the obvious financial advantage, the Hospitality Club believes that “bringing people together and fostering international friendships will increase intercultural understanding and strengthen peace.”

Servas Open Doors, the oldest network, in fact formally views itself as a peace initiative, and there are also a number of smaller hospitality exchange networks which focus on specialized audiences, such as Agritourism.

w:Veit Kühne from Dreseden, Germany, who founded the Hospitality Club in 2000 while he was still a student, believes that “one day, everyone will have the opportunity to visit any country knowing that someone will be waiting to receive them with open arms. People will travel in a different way, meet each other and build intercultural understanding through personal contact.”

“There will be many members in places like Israel and Palestine, Northern Ireland, the Balkans, Chechnya, Rwanda, or Timor who will exchange hospitality with each other, and in small steps the Hospitality Club will have helped making peace a lasting vision for our wonderful planet,” he adds.

Hospitality Club was the first online organisation to offer on a major scale the possibility for travellers to find and contact locals open to cultural exchange. The whole system is entirely free, and hosting fees are supported by Google advertisements. The safe and efficient operation of the 30+ languages website and its database, forum, and chatroom depends on the work of hundreds of volunteers from around the world.

Anybody can become a member, but they must provide their full name and address, for security reasons. All members have a profile they can fill with information about themselves and their preferences, to help prospective visitors contact the person most likely to welcome them.

The most often mentioned drawback of the system is lack of security. The main difference between hospitality exchange networks and other social networking platforms such as Orkut or LiveJournal is that the former’s ultimate objective is to allow for face-to-face meetings. Users should realise that there is a risk involved, although according to Frenchman Jean-Yves Hégron, main software developer of the Hospitality Club, “By using the Club you have the same level of risk as the one you face whenever you get out from your home.”

Discussion about strategic or security issues is not allowed on the website’s forum, hence critics often mention lack of transparency in how they perceive decisions are taken by volunteers in Hospitality Club. Another point of critique is the fact that there is no legal organisation behind Hospitality Club, and the domain name is registered to the founder of the Club himself. Messages containing links to other hospitality exchange networks were at some point deleted without further notice though this policy has since then been reverted. Exponential growth of the network has also caused server failures alike to those observed in Wikipedia until recently.

The idea of free hospitality exchange is not new. Servas was the first organisation to develop it, right after World War II. It still exists to this day, with over 15,000 members, and is represented as an NGO in the United Nations. Because democratic, paper-based Servas is perceived as bureaucratic by some, Hospex was created as the first online network in 1991.

Hospitality Club succeeded to Hospex in August 2000, introducing innovative security features ranging from spam protection to passport control and a sophisticated feedback system, thus making online hospitality exchange available to travellers with higher safety concerns. From 1000 members in July 2002 to 10,000 in February 2004, it quickly grew to 100,000 on 11 January 2006 and is expected to reach the million in about two years.

Thursday, March 30, 2006

Charlie Sheen, appearing on cable television news network station CNN on March 24, questioned the credibility of the theory that 19 hijackers caused all of the destruction to the World Trade Center.

Sheen said; “It seems to me like, you know, 19 amateurs with box cutters taking over four commercial airliners and hitting 75 percent of their targets, that feels like a conspiracy theory… I am an American citizen that loves my country…. People want the truth. They want the truth. And what’s been offered to us resembles nothing of the sort.“

In recounting his reaction on the day of the event, Sheen said,”I was up early and we were gonna do a pre-shoot on Spin City, the show I used to do. I was watching the news and the north tower was burning. There was a feeling, it just didn’t look like any commercial jetliner I’ve flown on any time in my life and then when the buildings came down later on that day I said to my brother, ‘Call me insane but did it sorta look like those buildings came down in a controlled demolition?’”

Writer Marc Jacobson, of the New York magazine, who co-appeared with Sheen on the same program said in response: “Well, I think he’s doing a reasonable rendition of what other people that believe in this stuff say. And when he says he has his facts straight, I mean, I think the facts are in question. I mean, I think, just because you know what it says on all of these different Web sites doesn’t mean that that’s necessarily the fact. That’s the reason why the United States government, with their endless amounts of resources, let us down by not doing the proper work on the 9/11 Commission. That’s a real problem. Well, you know, but, I mean, it’s just one of those kind of things where you do this work and nobody really cares, but then Charlie Sheen is interested, so then everybody is interested, and that’s fine. You know, obviously, this material needs to be looked at again, because there’s been a lot of problems with the 9/11 Commission report. People feel it’s not adequate. Most of the people who had lost people during that time feel it’s not adequate. And it’s just I think we’re living in a truth vacuum, in a sense, that any time there’s a truth vacuum, these ideas — because people are smart. They put two and two together. Sometimes they get five; sometimes they get 12, but sometimes they get 11, like 9/11, but sometimes they get four. And the thing is that, if you have a situation where the so-called facts are covered up and aggressively covered up, then you’re going to get these conspiracy theories.” One website is claiming that Google had been censoring out any news articles relating to Sheen and 9/11 from it’s search engine.

Regarding the plane that hit the Pentagon, Sheen also has questions: “Just show us how this particular plane pulled off these maneuvers… It is up to us to reveal the truth. It is up to us because we owe it to the families, we owe it to the victims, we owe it to everyone’s life who was drastically altered, horrifically, that day and forever. We owe it to them to uncover what happened.”

Some supporters of Sheen’s theories have complained about the lack of mainstream media coverage. They point to CNN’s recent cancellation of Ed Asner’s interview on Showbiz Tonight, where he was expected to support Sheen’s position, as an example of the “media blackout”.

Marina Hyde of The Guardian proposed a theory of her own with regard to Sheen: “Frankly, with dentistry as expensive as yours, you simply can’t afford to let The Man stamp his jackboot down on your face, and so it is that when faced with the inquiry ‘did Lee Harvey Oswald act alone?’, you find yourself thinking: ‘God, I mean… do any of us? Like, he had to have people, you know? At least an agent and a publicist.'”

Wednesday, April 1, 2009

According to the payroll services company ADP, United States private sector employers cut 742,000 jobs in in March. The figures were almost 80,000 more than the average analyst prediction of 663,000 losses. This is the largest monthly payroll decline since January 2001, when the ADP began tracking job activity.

ADP also updated its job loss statistics for February, from 697,000 to 706,000.

“The sharp employment declines among medium- and small-size businesses indicate that the recession continues to spread aggressively beyond manufacturing and housing-related activities to almost every area of the economy,” said Joel Prakken, the chairman of the company that conducts the ADP survey, Macroeconomic Advisors LLC.

“Despite some recent indications that stock prices, consumer spending, and housing activity may be bottoming out, employment, which usually trails overall economic activity, is likely to remain very weak for at least several more months,” he added.

The US Labor Department‘s report for employment statistics for March is due to be out on Friday. Analysts predicted that the department will announce the unemployment rate increased to 8.5% with 660,000 jobs eliminated in March. However, the bad news from ADP has prompted some to think that the current forecasts are too optimistic.

Saturday, May 6, 2006

Early Saturday morning winds up to 90 miles per hour struck Waco, Texas and central McLennan County, United States, causing widespread damage and leaving many households without electricity.

No deaths or serious injuries have been reported; however, there is a tremendous amount of damage in 15 areas of the city, leading Mayor Virgina DuPuy to declare the city a disaster area.

The hardest hit area was Franklin Avenue, where the Coca-Cola bottling plant’s roof was peeled open as if by a giant can-opener. There were Sprite bottles spread out onto the street. The nearby Furniture Row shopping center was also hit hard. Some furniture was found as far as three-quarters of a mile away. Other hard-hit areas were Robinson, Hewitt, Woodway, and Speegleville. Densely populated Inner Waco was spared of any catastrophic damage, though hundreds, and possibly thousands, of trees have fallen, and roofs destroyed.

The main concern is restoring power to over 23,000 households and businesses. Many gas stations and grocery stores in the disaster areas were closed until power is restored. Those that remained open have had to throw out all perishable items. Also of concern is getting electricity to those with medical needs. The city has provided help to those without power at the Dewey Recreation Center.

The storm is the hardest to hit the area since the tornado that struck on May 11, 1953, which tore through downtown and killed 114 people.

Waco has seen more than its share of tornadoes recently. Only a week ago, an F1 tornado damaged many houses along Orchid and Kendall Lanes. No people were injured, though two horses were killed when their stable collapsed.

The National Weather Service confirmed this morning’s winds were a F2 tornado, where wind speeds may have reached 115 miles per hour in some locations.

Friday, May 19, 2006

This interview intends to provide some insight into OpenSync, an upcoming free unified data synchronization solution for free software desktops such as KDE, commonly used as part of the GNU/Linux operating system.

Hi Cornelius, Armin and Tobias. As you are now getting close to version 1.0 of OpenSync, which is expected to become the new synchronisation framework for KDE and other free desktops, we are quite interested in the merits it can provide for KDE users and for developers, as well as for the Open Source Community as a whole. So there’s one key-question before I move deeper into the details of OpenSync:

What does OpenSync accomplish, that no one did before?

Cornelius:

First of all it does its job of synchronizing data like addressbooks and calendars between desktop applications and mobile devices like PDAs and cell phones.

But the new thing about OpenSync is that it isn’t tied to a particular device or a specific platform. It provides an extensible and modular framework that is easy to adopt for application developers and people implementing support for syncing with mobile devices.

OpenSync is also independent of the desktop platform. It will be the common syncing backend for at least KDE and GNOME and other projects are likely to join. That means that the free desktop will have one common syncing solution. This is something really new.

How do the end-users profit from using synching solutions that interface with OpenSync as framework?

Cornelius:

First, the users will be able to actually synchronize all their data. By using one common framework there won’t be any “missing links”, where one application can sync one set of devices and another application a different one. With OpenSync all applications can sync all devices.

Second, the users will get a consistent and common user interface for syncing across all applications and devices. This will be much simpler to use than the current incoherent collection of syncing programs you need if you have more than the very basic needs.

How does OpenSync help developers with coding?

Cornelius:

It’s a very flexible and well-designed framework that makes it quite easy for developers to add support for new devices and new types of data. It’s also very easy to add support for OpenSync to applications.

The big achievement of OpenSync is that it hides all the gory details of syncing from the developers who work on applications and device support. That makes it possible for the developers to concentrate on their area of expertise without having to care what’s going on behind the scenes.

I have written quite a lot of synchronization code in the past. Trust me, it’s much better, if someone just takes care of it for you, and that’s what OpenSync does.

Tobias:

Another point to mention is the python wrapper for opensync, so you are not bound to C or C++, but can develop plugins in a high level scripting language.

Why should producers of portable devices get involved with your team?

Cornelius:

OpenSync will be the one common syncing solution for the free desktop. That means there is a single point of contact for device manufacturers who want to add support for their devices. That’s much more feasible than addressing all the different applications and solutions we had before. With OpenSync it hopefully will become interesting for manufacturers to officially support Linux for their devices.

Do you also plan to support applications of OpenSync in proprietary systems like OSX and Windows?

Cornelius:

OpenSync is designed to be cross-platform, so it is able to run on other systems like Windows. How well this works is always a question of people actually using and developing for this system. As far as I know there isn’t a real Windows community around OpenSync yet. But the technical foundation is there, so if there is somebody interested in working on a unified syncing solution on Windows, everybody is welcome to join the project.

What does your synchronisation framework do for KDE and for KitchenSync in particular?

Cornelius:

OpenSync replaces the KDE-specific synchronization frameworks we had before. Even in KDE we had several separate syncing implementations and with OpenSync we can get replace them with a common framework. We had a more generic syncing solution in KDE under development. This was quite similar from a design point of view to OpenSync, but it never got to the level of maturity we would have needed, because of lack of resources. As OpenSync fills this gap we are happy to be able to remove our old code and now concentrate on our core business.

What was your personal reason for getting involved with OpenSync?

Cornelius:

I wrote a lot of synchronization code in the past, which mainly came from the time where I was maintaining KOrganizer and working on KAddressBook. But this always was driven by necessity and not passion. I wanted to have all my calendar and contact data in one place, but my main objective was to work on the applications and user interfaces handling the data and not on the underlying code synchronizing the data.

So when the OpenSync project was created I was very interested. At GUADEC in Stuttgart I met with Armin, the maintainer of OpenSync, and we talked about integrating OpenSync with KDE. Everything seemed to fit together quite well, so at Linuxtag the same year we had another meeting with some more KDE people. In the end we agreed to go with OpenSync and a couple of weeks later we met again in Nuernberg for three days of hacking and created the KDE frontend for OpenSync. In retrospect it was a very pleasant and straightforward process to get where we are now.

Armin:

My reason to get involved (or better to start) OpenSync was my involvement with its predecessor Multisync. I am working as a system administrator for a small consulting company and so I saw some problems when trying to find a synchronization solution for Linux.

At that point I joined the Multisync project to implement some plugins that I thought would be nice to have. After some time I became the maintainer of the project. But I was unhappy with some technical aspects of the project, especially the tight coupling between the syncing logic and the GUI, its dependencies on GNOME libraries and its lack of flexibility.

Tobias:

Well, I have been a KDE PIM developer for several years now, so there was no way around getting in touch with synchronization and KitchenSync. Although I liked the idea of KitchenSync, I hated the code and the user interface […]. So when we discussed to switch to OpenSync and reimplementing the user interface, I volunteered immediately.

Can you tell us a bit about your further plans and ideas?

Cornelius:

The next thing will be the 1.0 release of OpenSync. We will release KitchenSync as frontend in parallel.

Armin:

There are of course a lot of things on my todo and my wishlist for opensync. For the near future the most important step is the 1.0 release, of course, where we still have some missing features in OpenSync as well as in the plugins.

One thing I would really like to see is a thunderbird plugin for OpenSync. I use thunderbird personally and would really like to keep my contacts up to date with my cellular, but I was not yet able to find the time to implement it.

Tobias:

One thing that would really rock in future versions of OpenSync is an automatic hardware detection mechanism, so when you plugin your Palm or switch on your bluetooth device, OpenSync will create a synchronization group automatically and ask the user to start syncing. To bring OpenSync to the level of _The Syncing Solution [tm]_ we must reduce the necessary configuration to a minimum.

What was the most dire problem you had to face when creating OpenSync and how did you face it?

Cornelius:

Fortunately the problems which I personally would consider to be dire are solved by the implementation of OpenSync which is well hidden from the outside world and [they are] an area I didn’t work on 😉

Armin:

I guess that I am the right person to answer this question then 🙂

The most complicated part of OpenSync is definitely the format conversion, which is responsible for converting the format of one device to the format that another device understands.

There are a lot of subsystems in this format conversion that make it so complex, like conversion path searching, comparing items, detection of mime types and last but not least the conversion itself. So this was a hard piece of work.

What was the greatest moment for you?

Cornelius:

I think the greatest moment was when, after three days of concentrated hacking, we had a first working version of the KDE frontend for OpenSync. This was at meeting at the SUSE offices in Nuernberg and we were able to successfully do a small presentation and demo to a group of interested SUSE people.

Armin:

I don’t remember a distinct “greatest moment”. But what is a really great feeling is to see that a project catches on, that other people get involved, use the code you have written and improve it in ways that you haven’t thought of initially.

Tobias:

Hmm, also hacking on OpenSync/KitcheSync is much fun in general, the greatest moment was when the new KitchenSync frontend synced two directories via OpenSync the first time. But it was also cool when we managed to get the IrMC plugin working again after porting it to OpenSync.

As we now know the worst problem you faced and your greatest moment, the only one missing is: What was your weirdest experience while working on OpenSync?

Cornelius:

Not directly related to OpenSync, but pretty weird was meeting a co-worker at the Amsterdam airport when returning from the last OpenSync meeting. I don’t know how high the chance is to meet somebody you know on a big random airport not related at all to the places where you or the other person live, but it was quite surprising.

Tobias:

Since my favorite language is C++, I was always confused how people can use plain C for such a project, half the time your are busy with writing code for allocating/freeing memory areas. Nevertheless Armin did a great job and he is always a help for solving strange C problems 🙂

Now I’d like to move on to some more specific questions about current and planned abilities of OpenSync. As first, I’ve got a personal one:

I have an old iPod sitting around here. Can I or will I be able to use a program utilizing OpenSync to synchronize my calendars, contacts and music to it?

Cornelius:

I’m not aware of any iPod support for OpenSync up to now, but if it doesn’t exist yet, why not write it? OpenSync makes this easy. This is a chance for everybody with the personal desire to sync one device or another to get involved.

Armin:

I dont think that there is iPod support yet for OpenSync. But it would definitely be possible to use OpenSync for this task. So if someone would like to implement an iPod plugin, I would be glad to help 🙂

Which other devices do you already support?

Cornelius:

At this time, OpenSync supports Palms, SyncML and IrMC capable devices.

Which programs already implement OpenSync and where can we check back to find new additions?

Cornelius:

On the application side there is support for Evolution [GNOME] and Kontact with KitchenSync [KDE] on the frontend side and the backend side and some more. I expect that further applications will adopt OpenSync once the 1.0 version is released.

Armin:

Besides kitchensync there already are a command line tool and a port of the multisync GUI. Aside from the GUIs, I would really like to see OpenSync being used in other applications as well. One possibility for example would to be integrate OpenSync into Evolution to give users the possibility to synchronize their devices directly from this application. News can generally be found on the OpenSync web site www.opensync.org.

It is time to give the developers something to devour, too. I’ll keep this as a short twice-fold technical dive before coming to the takeoff question, even though I’m sure there’s information for a double-volume book on technical subleties.

As first dive: How did you integrate OpenSync in KitchenSync, viewed from the coding side?

Cornelius:

OpenSync provides a C interface. We wrapped this with a small C++ library and put KitchenSync on top. Due to the object oriented nature of the OpenSync interfaces this was quite easy.

Recently I also started to write a D-Bus frontend for OpenSync. This also is a nice way to integrate OpenSync which provides a wide variety of options regarding programming languages and system configurations.

And for the second, deeper dive:

Can you give us a quick outline of those inner workings of OpenSync, from the developers view, which make OpenSync especially viable for application in several different desktop environments?

Cornelius:

That’s really a question for Armin. For those who are interested I would recommend to have a look at the OpenSync website. There is a nice white paper about the internal structure and functionality of OpenSync.

Armin:

OpenSync consists of several parts:

First there is the plugin API which defines what functions a plugin has to implement so that OpenSync can dlopen() it. There are 2 types of plugins:

A sync plugin which can synchronize a certain device or application and which provides functions for the initialization, handling the connection to a device and reading and writing items. Then there is a format plugin which defines a format and how to convert, compare and detect it.

The next part is a set of helper functions which are provided to ease to programming of synchronization plugins. These helper functions include things like handling plugin config files, HashTables which can be used to detect changes in sets of items, functions to detect when a resync of devices is necessary etc.

The syncing logic itself resides in the sync engine, which is a separate part. The sync engine is responsible for deciding when to call the connect function of a plugin, when to read or write from it. The engine also takes care of invoking the format conversion functions so that each plugin gets the items in its required format.

If you want more information and details about the inner workings of OpenSync, you should really visit the opensync.org website or ask its developers.

To add some more spice for those of our readers, whose interest you just managed to spawn (or to skyrocket), please tell us where they can get more information on the OpenSync Framework, how they can best meet and help you and how they can help improving sync-support for KDE by helping OpenSync.

Cornelius:

Again, the OpenSync web site is the right source for information. Regarding the KDE side, the kde-pim@kde.org mailing list is probably the right address. At the moment the most important help would be everything which gets the OpenSync 1.0 release done.

[And even though] I already said it, it can’t be repeated too often: OpenSync will be the one unified syncing solution for the free desktop. Cross-device, cross-platform, cross-desktop.

It’s the first time I feel well when thinking about syncing 😉.

Armin:

Regarding OpenSync, the best places to ask would be the opensync mailing lists at sourceforge or the #opensync irc channel on the freenode.net servers.

There are always a lot of things where we could need a helping hand and where we would be really glad to get some help. So everyone who is interested in OpenSync is welcome to join.

Many thanks for your time!

Cornelius:

Thanks for doing the interview. It’s always fun to talk about OpenSync, because it’s really the right thing.

Armin:

Thank you for taking your time and doing this interview. I really appreciate your help!

Tobias:

Thanks for your work. Publication and marketing is something that is really missing in the open source community. We have nice software but nobody knows 😉

Further Information on OpenSync can be found on the OpenSync Website: www.opensync.org

This Interview was done by Arne Babenhauserheide in April 2006 via e-mail and KOffice on behalf of himself, the OpenSource Community, SpreadKDE.org and the Dot (dot.kde.org).It was first published on the Dot and is licensed under the cc-attribution-sharealike-license.A pdf-version with pictures can be found at opensync-interview.pdf (OpenDocument version: opensync-interview.odt)