Friday, November 30, 2012

Qatari non-profit organization Gulf Organization for Research and Development (GORD) launched a low emissions car at the 2012 United Nations Climate Change Conference (COP 18) in Doha. The car was designed and developed in Qatar.

Revealed during a press conference at the Qatar National Convention Centre, the car in addition to an internal combustion engine, includes an automotive thermoelectric generator designed to capture waste heat to produce hydrogen. GORD expects the heat waste collecting system to be compatible with any gasoline or compressed natural gas car.

GORD chairman Dr Al-Horr summarised the key concepts of the invention in a statement saying, “Our car produces electricity at no cost by capturing thermal waste energy, reducing costs and eliminating the need for an external source of electricity. Also, bulky compressed-hydrogen cylinders are a thing of the past, as our concept accomplishes the production of hydrogen by using water through fuel cells integrated within the car.”

Most of the energy in Qatari vehicle comes from the the car’s gasoline tank, supplemented by a thin film photo-voltaic panel on the roof. Normally in a combustion engine, chemical energy stored in a fuel, such as gasoline, is converted into heat energy through combustion. This heat energy is then converted into mechanical energy, manifested as an increase in pressure in the combustion chamber due to the kinetic energy of the combustion gases. The kinetic energy of these combustion gases are then converted into work; because of the inefficiencies in converting chemical energy into useful work, internal combustion engines have a theoretical maximum effiecincy of 37% (with what is achievable in day to day applications being about half of this). Of the chemical energy in the consumed fuel used by an internal combustion engine 40% is dissipated as waste heat. However, the Qatari vehicle uses a thermoelectric generator to convert this waste heat into electricity. Such generators are used in space vehicles, and produce electricity when thermoelectric materials are subjected to a temperature gradient, the greater the gradient the greater the amount of electrcity produced. In the GORD vehicle the electricity produced is used to electrolyse potable water to produce hydrogen which can be introduced into the vehicle’s existing fuel system.

The researchers showed that the heat waste collection engine caused a decrease in the car’s emissions, including a decrease of carbon monoxide and nitrous oxide emissions by more than 50%, the fuel efficiency increasing by 20%. On its website, GORD said that the heat waste collector engine is universal, “Any car can be adapted to accommodate the system as it doesn’t alter any electro-mechanical systems”.

Wednesday, April 9, 2008

Flickr, the online photo sharing service owned by American internet company Yahoo!, today launched a new video-sharing service for “Pro” users. After 4 months of waiting since an unofficial “coming soon” on the Flickr forums, subscribers to the service are now able to upload videos of up to 90 seconds in length, or 150 MB in size.

After some criticism over the website diversifying too much, Flickr Community Manager Heather Champ, and Yahoo! spokesperson George Hadjigeorgiou responded by calling these 90-second videos “long photos”, which capture a “slice of life to share”.

Mr. Hadjigeorgiou elaborated, by saying that “digital media has led to new behaviour with digital photography fans and we’ve seen a huge growth in people taking short video clips, essentially ‘long photos’, with their digital still cameras and mobile phones.” He added that he could see “a great resonance between this new category of content and with the kind of authentic, personal moments already being shared on Flickr.”

“Pro” users, who pay a yearly subscription of US$24.95 for unlimited file uploads, have also had their filesize limit increased to 20 MB for each individual photo, and other members, who do not pay a subscription, have had their limit raised to 10 MB per photo. “Free” members are currently unable to upload videos.

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)

Saturday, September 12, 2009

This past week, British Commandos saved a British journalist, Stephen Farrell from what could have been a very dangerous situation as he had been abducted by Taliban insurgents in Kunduz Province, Afghanistan last weekend. During the raid, one of the rescuers and the journalist’s translator were killed in addition to about three others according to conflicting reports.

Farrell, a journalist from The New York Times and dual British-Irish citizen, and his Afghan interpreter, Sultan Munadi, were taken captive by the Taliban while covering a September 4th bombing by coalition aircraft not far from Konduz City, Afghanistan. A local Afghan reported that while Farrell was interviewing individuals that witnessed the bombing, he received a warning from another Afghan that he should leave the area. Soon after, gun-shots were heard and the Taliban was said to be approaching. Reportedly, police warned journalists covering the strike that insurgents controlled the area surrounding the tanker and that they should take precautions for their personal safety.

	“We feared that media attention would raise the temperature and increase the risk to the captives.”

When Farrell was taken, few major news outlets reported his capture for security reasons. NY Times Executive Editor Bill Keller earlier said “We feared that media attention would raise the temperature and increase the risk to the captives.”

According to Farrell, while he was treated well — given food, water, and other provisions — his captors taunted Munadi. During their captivity, Farrell commented that his captors would drive within 1500 feet of NATO and Afghan outposts with weapons displayed to prove their daring. Six to eight guards took turns monitoring the captives.

Farrell is the second NY Times journalist to be taken captive in Afghanistan in less than a year. In November 2008, reporter David S. Rohde and his colleague Tahir Ludin were taken captive south of Kabul and moved to Pakistan before they managed to escape in June of this year. Farrell was also kidnapped in April 2004 while on-assignment in Fallujah, Iraq.

Kidnappings are done for ideological reasons by some Taliban members but are also conducted by local insurgents for ransom. At least 16 journalists have been kidnapped since the beginning of the Afghan war.

	“The tragedy that took place this morning in northern Afghanistan raises many questions.”

According to Keller, the possibility had arisen that Farrell and Munadi would be moved, possibly to Pakistan, which may have caused the military to act much sooner. On the morning of September 9th, Mohammad Sami Yowar, a spokesman for the Konduz Governor’s Office, briefed that British Commandos conducted a helicopter assault on the house in which the captives were held and subsequently a gun-battle erupted. A Taliban commander inside the house where Farrell and Munadi were being held was reportedly killed during the raid. Munadi was killed during the firefight and British officials said that they could not rule out the possibility he was killed by one of the Commandos. The Konduz Governor, Abdel Wahid Omar Khil, indicated that a woman and child probably caught in the crossfire were also killed during the raid. Farrell indicated that he was not harmed.

Reporters Without Borders has called for an investigation of the Munadi killing stating that “The tragedy that took place this morning in northern Afghanistan raises many questions.” U.S. military officials confirmed the raid was carried out by NATO and Afghan soldiers; no further details were provided.