Author: Admin

Saturday, June 1, 2019

At around 12:20 p.m. local time on Wednesday (1620 UTC) in the United States capital city Washington DC, Arnav Gupta, 33-year-old of Bethesda, Maryland, set himself on fire in a publicly accessible area called the Ellipse, between the south lawn of the White House and the Washington Monument. Gupta was transported to a local hospital and originally listed in critical condition, according to officials, with burns over reportedly 85% of his body. He died that night.

Emergency responders included the Secret Service and US Park Police. Responders drove their vehicles onto the Ellipse where an officer used a fire extinguisher to put out the flames. The Secret Service confirmed a single male was transported to a local hospital and the response took place within seconds.

On Wednesday morning Gupta’s family members filed a missing persons report, according to the Montgomery County Police Department.

Tourists captured pictures and video of the incident. Once the white extinguisher smoked cleared the man had collapsed. Surrounding areas were reportedly shut down. As of Thursday, no official statement had been made on the man’s motivation.

Gupta’s self-immolation follows another attempt in April where a wheelchair-using individual attempted to set his jacket on fire along the north lawn fence line.

Wednesday, February 4, 2009

A new historic physics record has been set by scientists for exceedingly small writing, opening a new door to computing‘s future. Stanford University physicists have claimed to have written the letters “SU” at sub-atomic size.

Graduate students Christopher Moon, Laila Mattos, Brian Foster and Gabriel Zeltzer, under the direction of assistant professor of physics Hari Manoharan, have produced the world’s smallest lettering, which is approximately 1.5 nanometres tall, using a molecular projector, called Scanning Tunneling Microscope (STM) to push individual carbon monoxide molecules on a copper or silver sheet surface, based on interference of electron energy states.

A nanometre (Greek: ?????, nanos, dwarf; ?????, metr?, count) is a unit of length in the metric system, equal to one billionth of a metre (i.e., 10^-9 m or one millionth of a millimetre), and also equals ten Ångström, an internationally recognized non-SI unit of length. It is often associated with the field of nanotechnology.

“We miniaturised their size so drastically that we ended up with the smallest writing in history,” said Manoharan. “S” and “U,” the two letters in honor of their employer have been reduced so tiny in nanoimprint that if used to print out 32 volumes of an Encyclopedia, 2,000 times, the contents would easily fit on a pinhead.

In the world of downsizing, nanoscribes Manoharan and Moon have proven that information, if reduced in size smaller than an atom, can be stored in more compact form than previously thought. In computing jargon, small sizing results to greater speed and better computer data storage.

“Writing really small has a long history. We wondered: What are the limits? How far can you go? Because materials are made of atoms, it was always believed that if you continue scaling down, you’d end up at that fundamental limit. You’d hit a wall,” said Manoharan.

In writing the letters, the Stanford team utilized an electron‘s unique feature of “pinball table for electrons” — its ability to bounce between different quantum states. In the vibration-proof basement lab of Stanford’s Varian Physics Building, the physicists used a Scanning tunneling microscope in encoding the “S” and “U” within the patterns formed by the electron’s activity, called wave function, arranging carbon monoxide molecules in a very specific pattern on a copper or silver sheet surface.

“Imagine [the copper as] a very shallow pool of water into which we put some rocks [the carbon monoxide molecules]. The water waves scatter and interfere off the rocks, making well defined standing wave patterns,” Manoharan noted. If the “rocks” are placed just right, then the shapes of the waves will form any letters in the alphabet, the researchers said. They used the quantum properties of electrons, rather than photons, as their source of illumination.

According to the study, the atoms were ordered in a circular fashion, with a hole in the middle. A flow of electrons was thereafter fired at the copper support, which resulted into a ripple effect in between the existing atoms. These were pushed aside, and a holographic projection of the letters “SU” became visible in the space between them. “What we did is show that the atom is not the limit — that you can go below that,” Manoharan said.

“It’s difficult to properly express the size of their stacked S and U, but the equivalent would be 0.3 nanometres. This is sufficiently small that you could copy out the Encyclopaedia Britannica on the head of a pin not just once, but thousands of times over,” Manoharan and his nanohologram collaborator Christopher Moon explained.

The team has also shown the salient features of the holographic principle, a property of quantum gravity theories which resolves the black hole information paradox within string theory. They stacked “S” and the “U” – two layers, or pages, of information — within the hologram.

The team stressed their discovery was concentrating electrons in space, in essence, a wire, hoping such a structure could be used to wire together a super-fast quantum computer in the future. In essence, “these electron patterns can act as holograms, that pack information into subatomic spaces, which could one day lead to unlimited information storage,” the study states.

The “Conclusion” of the Stanford article goes as follows:

The team is not the first to design or print small letters, as attempts have been made since as early as 1960. In December 1959, Nobel Prize-winning physicist Richard Feynman, who delivered his now-legendary lecture entitled “There’s Plenty of Room at the Bottom,” promised new opportunities for those who “thought small.”

Feynman was an American physicist known for the path integral formulation of quantum mechanics, the theory of quantum electrodynamics and the physics of the superfluidity of supercooled liquid helium, as well as work in particle physics (he proposed the parton model).

Feynman offered two challenges at the annual meeting of the American Physical Society, held that year in Caltech, offering a $1000 prize to the first person to solve each of them. Both challenges involved nanotechnology, and the first prize was won by William McLellan, who solved the first. The first problem required someone to build a working electric motor that would fit inside a cube ¹/₆₄ inches on each side. McLellan achieved this feat by November 1960 with his 250-microgram 2000-rpm motor consisting of 13 separate parts.

In 1985, the prize for the second challenge was claimed by Stanford Tom Newman, who, working with electrical engineering professor Fabian Pease, used electron lithography. He wrote or engraved the first page of Charles Dickens’ A Tale of Two Cities, at the required scale, on the head of a pin, with a beam of electrons. The main problem he had before he could claim the prize was finding the text after he had written it; the head of the pin was a huge empty space compared with the text inscribed on it. Such small print could only be read with an electron microscope.

In 1989, however, Stanford lost its record, when Donald Eigler and Erhard Schweizer, scientists at IBM’s Almaden Research Center in San Jose were the first to position or manipulate 35 individual atoms of xenon one at a time to form the letters I, B and M using a STM. The atoms were pushed on the surface of the nickel to create letters 5nm tall.

In 1991, Japanese researchers managed to chisel 1.5 nm-tall characters onto a molybdenum disulphide crystal, using the same STM method. Hitachi, at that time, set the record for the smallest microscopic calligraphy ever designed. The Stanford effort failed to surpass the feat, but it, however, introduced a novel technique. Having equaled Hitachi’s record, the Stanford team went a step further. They used a holographic variation on the IBM technique, for instead of fixing the letters onto a support, the new method created them holographically.

In the scientific breakthrough, the Stanford team has now claimed they have written the smallest letters ever – assembled from subatomic-sized bits as small as 0.3 nanometers, or roughly one third of a billionth of a meter. The new super-mini letters created are 40 times smaller than the original effort and more than four times smaller than the IBM initials, states the paper Quantum holographic encoding in a two-dimensional electron gas, published online in the journal Nature Nanotechnology. The new sub-atomic size letters are around a third of the size of the atomic ones created by Eigler and Schweizer at IBM.

A subatomic particle is an elementary or composite particle smaller than an atom. Particle physics and nuclear physics are concerned with the study of these particles, their interactions, and non-atomic matter. Subatomic particles include the atomic constituents electrons, protons, and neutrons. Protons and neutrons are composite particles, consisting of quarks.

“Everyone can look around and see the growing amount of information we deal with on a daily basis. All that knowledge is out there. For society to move forward, we need a better way to process it, and store it more densely,” Manoharan said. “Although these projections are stable — they’ll last as long as none of the carbon dioxide molecules move — this technique is unlikely to revolutionize storage, as it’s currently a bit too challenging to determine and create the appropriate pattern of molecules to create a desired hologram,” the authors cautioned. Nevertheless, they suggest that “the practical limits of both the technique and the data density it enables merit further research.”

In 2000, it was Hari Manoharan, Christopher Lutz and Donald Eigler who first experimentally observed quantum mirage at the IBM Almaden Research Center in San Jose, California. In physics, a quantum mirage is a peculiar result in quantum chaos. Their study in a paper published in Nature, states they demonstrated that the Kondo resonance signature of a magnetic adatom located at one focus of an elliptically shaped quantum corral could be projected to, and made large at the other focus of the corral.

Tuesday, April 20, 2021

Wikinews extended invitations by e-mail on March 23 to multiple candidates running in the Texas’ 6th congressional district special election of May 1 to fill a vacancy left upon the death of Republican congressman Ron Wright. Of them, the office of Democrat Daryl Eddings, Sr. agreed to answer some questions by phone March 30 about their campaigns and policies. The following is the interview with Ms Chatham on behalf of Mr Eddings, Sr.

Eddings is a federal law enforcement officer and senior non-commissioned officer in the US military. His experience as operations officer of an aviation unit in the California National Guard includes working in Los Angeles to control riots sparked by the O. J. Simpson murder case and the police handling of Rodney King, working with drug interdiction teams in Panama and Central America and fighting in the Middle East. He is the founder of Operation Battle Buddy, which has under his leadership kept in touch with over 20 thousand veterans and their families. He was born in California, but moved to Midlothian, Texas. He endeavours to bring “good government, not no government”. Campaign manager Faith Chatham spoke to Wikinews on matters ranging from healthcare to housing.

An Inside Elections poll published on March 18 shows Republican candidate Susan Wright, the widow of Ron Wright, is ahead by 21% followed by Democrat Jana Sanchez with 17% and Republican Jake Ellzey with 8% with a 4.6% margin of error among 450 likely voters. The district is considered “lean Republican” by Inside Elections and voted 51% in favour of Donald Trump in last year’s US presidential election. This is down from 54% for Trump in 2016’s presidential election, the same poll stated.

Tuesday, March 21, 2006

David Parker resigned today from Cabinet, a day after he resigned his position as Attorney-General and after publicity around his filing of an incorrect declaration with the Companies Office on behalf of Queens Park Mews Limited.

The declaration said that the three shareholders had unanimously agreed not to appoint an auditor for the company; but according to Investigate Magazine, another shareholder, Russell Hyslop, had never been consulted about the matter.

Parker confesses to making a “mistake” over the returns. He says when Hyslop was declared bankrupt in 1997, he cleared it with the Official Assignee for the first two years. He then forgot to clear on other years.

Parker was saying early this morning that he would persist in holding his other portfolios.

Prime Minister Helen Clark released the news shortly before 11 a.m. (NZST) as she walked into a caucus meeting. She said, “I have this morning accepted Mr Parker’s resignation from all his portfolios.”

Knowingly authorising a false statement is an offence under the Companies Act. The maximum penalty under section 373(4) for filing a false return is a fine of $200,000 or five years of imprisonment.

Monday, February 15, 2010

Belgian authorities have confirmed that at least eighteen people died in a head-on collision between two passenger trains in the suburbs of Brussels. Other reports suggest that the death toll could be as high as 25. More than 125 passengers are reported injured, 11 of them “very seriously”. Rescuers were still trying to free bodies from the wreckage of the trains more than eight hours after the crash, which occurred in snowy conditions at 08:28 local time (0728 UTC) near the station of Buizingen in the municipality of Halle, about 15 kilometres southwest of the Belgian capital.

One of the trains involved was travelling from Quiévrain to Liège, while the other was travelling from Leuven to Braine-le-Comte. The collision saw the first two carriages of one train being forced upwards into the air over the first carriage of the second train. Eyewitnesses described the collision as “brutal”, with passengers being thrown “violently” around the carriages.

Television footage showed the two smashed locomotives forced up in the air, with passenger cars strewn over a wide area and dazed survivors wandering at the crash site. Train speed at the time of the crash was not immediately known. There are reports that one of the trains ran a stop signal.

Initial reports suggest that the Leuven–Braine-le-Comte train was on the wrong line. It is not known if the train went through a red signal or if there was a problem with the signalling. A “well informed source” quoted by French-language daily Le Soir suggested that there might have been an electrical failure in the signalling system.

The collision occurred on one of the main access lines to Brussels-South station, about 14 kilometres (9 miles) from the Belgian capital. It caused “major damage” to overhead power cables, especially on the Brussels–Mons and Brussels–Tournai lines, and high speed rail services between Brussels and France and the UK have been suspended. Thalys services were temporarily halted due to the accident, with four of its trains in the region being diverted to alternative stations. Thalys services between Brussels and Cologne have now resumed, but services to Amsterdam and Paris are still suspended.

One passenger on board, Christian Wampach, described conditions on board the train, “It was a nightmare. We were thrown about for about 15 seconds. There were a number of people injured in my car but I think all the dead were in the first car.” Wampach was in the third car.

Another passenger, Patricia Lallemand, said, “When we came out we saw dead bodies lying next to the tracks, some mutilated.”

Thursday, December 24, 2009

The United States Senate has approved a hard-fought measure to overhaul the health care system. The vote will be followed by the difficult process of reconciling the Senate-passed bill with one approved by the House of Representatives, in order to get a final measure to President Barack Obama.

“The yeas are 60, the nays are 39. H.R. 3590 as amended, the Patient Protection and Affordable Care Act is passed,” Vice President Joe Biden announced. Senator Jim Bunning of Kentucky did not show up for the vote leading to the 39 nays. Mike Reynard, a spokesman for Bunning, said in an e-mail that “The senator had family commitments.”

The vice president presided over the Senate at the time of the vote in his role as President of the United States Senate.

As expected, Republicans voted against the bill while all Democrats and two Independents, Joe Lieberman of Connecticut and Bernie Sanders of Vermont, voted for it.

At an estimated $87 billion, the measure would expand health insurance coverage to about 30 million more Americans currently without it, and create new private insurance marketplaces, or exchanges, to expand choice.

And, like the slightly more expensive measure passed by the House of Representatives, the Affordable Health Care for America Act, it would end a practice by private insurance companies of denying coverage to individuals with existing health problems.

Both the Senate and House measures would require nearly all Americans to purchase some form of insurance, while lower-income Americans would receive help from federal government subsidies.

In remarks before the vote, Senate Majority Leader Harry Reid, Democrat from Nevada, said opponents had done everything they could to prevent the vote from taking place.

Speaking to reporters, Reid and others hailed the vote as a victory and a major step toward providing millions more Americans with access to health care. “This is a victory because we have affirmed that the ability to live a healthy life in our great country is a right and not merely a privilege for the select few,” Reid said.

Reid and others including Robert Byrd, the 92-year-old Democrat from West Virginia, paid tribute to Senator Edward Kennedy, who died this past August after spending decades of his career in the Senate pursuing health care reform.

When casting his vote Byrd said, “Mr. President, this is for my friend Ted Kennedy. Aye.”

Victoria Reggie Kennedy, the widow of Senator Kennedy, watched the proceedings from the Senate visitor’s gallery, as did Representative John Dingell, Democrat from Michigan, who has been a long time advocate of health care reform and who sponsored and introduced the House version of the health care reform bill.

In the final hours of debate on the Senate bill, Republicans asserted it would be ineffective and add sharply to the U.S. budget deficit.

Senator Jeff Sessions, Republican from Alabama said of the bill, “This legislation may have a great vision, it may have a great idea about trying to make the system work better. But it does not. These are huge costs [and] it’s not financially sound.”

Senate Minority Leader Mitch McConnell vowed to defeat the bill when the Senate reconvenes in January saying, “This fight is not over. This fight is long from over. My colleagues and I will work to stop this bill from becoming law.”

Senator Olympia Snowe, a moderate Republican from Maine who helped approved the Senate Finance Committee’s version of health care reform, the America’s Healthy Future Act, earlier in the year and who remarked she may not vote on the final bill, said, “I was extremely disappointed,” noting that when the Democrats reached their needed 60 votes to overcome a filibuster, “there was zero opportunity to amend the bill or modify it, and Democrats had no incentive to reach across the aisle.”

Ahead are difficult negotiations with the House of Representatives to craft a final bill President Obama would sign into law. These talks, which will formally get under way early in the new year, will take place amid anger among many liberal House Democrats the Senate bill failed to contain a government-run public health insurance option.

Members of the House Progressive Caucus have vowed to fight to keep this public option in any final legislation that emerges, along with other provisions they say are needed to protect lower and middle-income Americans and hold insurance companies accountable.

In a statement, the Democratic chairmen of three key House committees said while there are clear differences between House and Senate bills, both will bring fundamental health care coverage to millions who are currently uninsured.

Obama administration officials have been quoted as saying they anticipate negotiations on a final bill would not be complete until after the President’s State of the Union Address in January, and could slip even later into the new year.

President Obama issued a statement to the press in the State Dining Room in the White House saying that the vote is “legislation that brings us toward the end of a nearly century-long struggle to reform America’s health care system.”

He also pointed out the bill’s strengths, noting, “The reform bill that passed the Senate this morning, like the House bill, includes the toughest measures ever taken to hold the insurance industry accountable. Insurance companies will no longer be able to deny you coverage on the basis of a preexisting condition. They will no longer be able to drop your coverage when you get sick. No longer will you have to pay unlimited amounts out of your own pocket for the treatments you need. And you’ll be able to appeal unfair decisions by insurance companies to an independent party.”

He also noted how historic the bill is, saying, “If passed, this will be the most important piece of social policy since the Social Security Act in the 1930s, and the most important reform of our health care system since Medicare passed in the 1960s.”

Obama noted the potential social impact, saying, “It’s the impact reform will have on Americans who no longer have to go without a checkup or prescriptions that they need because they can’t afford them; on families who no longer have to worry that a single illness will send them into financial ruin; and on businesses that will no longer face exorbitant insurance rates that hamper their competitiveness.”

Obama afterwards made phone calls to various Senators and other people, including Victoria Kennedy and David Turner of Little Rock, Arkansas. Mr. Turner had his health insurance rescinded in January of last year, after his insurance company went back into his record and alleged that he failed to disclose his full medical record at the time he applied for coverage. Turner was First Lady Michelle Obama’s guest during her husband’s speech to a joint session of Congress on health care reform back in September.

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)