Sunday, May 18, 2008

An HIV-positive man was sentenced to 35 years in prison Wednesday, one day after being convicted of harassment of a public servant for spitting into the eye and open mouth of a Dallas, Texas police officer in May 2006. The United States Centers for Disease Control and Prevention says that no one has ever contracted HIV from saliva, and a gay-rights and AIDS advocacy group called the sentence excessive.

A Dallas County jury concluded that Willie Campbell’s act of spitting on policeman Dan Waller in 2006 constituted the use of his saliva as a deadly weapon. The incident occurred while Campbell, 42, was resisting arrest while being taken into custody for public intoxication.

“He turns and spits. He hits me in the eye and mouth. Then he told me he has AIDS. I immediately began looking for something to flush my eyes with,” said Waller to The Dallas Morning News.

Officer Waller responded after a bystander reported seeing an unconscious male lying outside a building. Dallas County prosecutors stated that Campbell attempted to fight paramedics and kicked the police officer who arrested him for public intoxication.

Prosecutors said that Campbell yelled that he was innocent during the trial, and claimed a police officer was lying. Campbell’s lawyer Russell Heinrichs said that because he had a history of convictions including similarly attacking two other police officers, biting inmates, and other offenses, he was indicted under a habitual offender statute. The statute increased his minimum sentence to 25 years in prison. Because the jury ruled that Campbell’s saliva was used as a deadly weapon, he will not be eligible for parole until completing at least half his sentence.

The organization Lambda Legal (Lambda Legal Defense and Education Fund), which advocates for individuals living with HIV, says that saliva should not be considered a deadly weapon. Bebe Anderson, the HIV projects director at Lambda Legal, spoke with The Dallas Morning News about the sentence. “It’s been 25 years since the virus was identified, but there are still lots of fears,” said Anderson.

The Dallas County prosecutor who handled the trial, Jenni Morse, said that the deadly weapon finding was justified. “No matter how minuscule, there is some risk. That means there is the possibility of causing serious bodily injury or death,” said Morse. Dallas County District Attorney Craig Watkins stated: “If you look at the facts of this case, it was clear that the defendant intended to cause serious bodily injury.”

A page at the CDC’s website, HIV and Its Transmission, states: “HIV has been found in saliva and tears in very low quantities from some AIDS patients.” The subsection “Saliva, Tears, and Sweat” concludes that: “Contact with saliva, tears, or sweat has never been shown to result in transmission of HIV.” On Friday the Dallas County Health Department released a statement explaining that HIV is most commonly spread through sexual contact, sharing needles, or transfusion from an infected blood product.

Monday, March 28, 2005

After facing criticism for being slow to act and initially giving too little after the December 26 Indonesian earthquake and tsunami, the United States government was quick to act when a massive earthquake hit Indonesia again March 28. U.S. State Department Adam Ereli said under orders of President George W. Bush, American embassy officials have been in contact with both Indonesia officials and the International Red Cross to coordinate international relief efforts and other foreign aid.

The two former U.S. presidents, Bill Clinton and the current president’s father, George H.W. Bush, already are heading up U.S. aid efforts in the region as the result of the last major temblor. “We still have people over there assisting from the first one, and they will be our first line of defense, once we know what kind of damage there is,” Pat McCrummen, spokesman for the American Red Cross told the Associated Press.

Although relief officials have been in contact with various governments, no specific pledge amount has been announced (as of 20:51, 28 Mar 2005 (UTC)).

Thursday, January 14, 2010

On Thursday, NASA officials confirmed that a small plastic bag of cocaine was found two days before in a secure space shuttle processing facility within the Kennedy Space Center located in Merritt Island, Florida.

An employee found the bag in Orbiter Processing Facility #3, where the Discovery is being prepared for a March launch to deliver supplies to the International Space Station. The man immediately notified security, and local police were soon called to the scene. From there, the bag’s contents were tested, and the results came back positive for cocaine.

The center’s director, Robert Cabana, assured the press that neither the Discovery nor the hangar in which it is being housed was compromised by the presence of the illegal drug. He went on to affirm that neither he nor his agency condone the use of any controlled substance by any employee while they are on the job, and that whoever is responsible will be fired and then prosecuted for the offenses.

Furthermore, Cabana stated that besides probing the criminal nature of what occurred, NASA will also conduct a full review of recent work performed on the Discovery as to make sure that there were not any other potential problems with the shuttle that investigators may have missed the first time.

Although a drug test was performed on each of the facility’s over two-hundred workers before they left Wednesday, “There was nothing obvious,” said the center’s public relations spokesman, Allard Beutel.

He goes on to say, “Nobody was obviously under the influence when they were working, because we have supervisors there, security in there. It wasn’t obvious somebody was under the influence of this substance, or any other, for that matter.”

Senator Bill Nelson, a former astronaut himself, says he is confident that the guilty party will be found, brought to justice, and then sent “out the door.”

Beutel concluded his statement by reaffirming NASA’s “zero-tolerance” policy for controlled substances, “People know how serious this is, and how serious^[sic] people take it,” Beutel said. “And it’s not acceptable. That’s the bottom line.”

Saturday, October 31, 2009

A man has been given a prison sentence of nine years for the manslaughter of his wife in Hampshire, England. 40-year-old Sally Sinclair was head of business analysis for mobile phone provider Vodafone and had been killed in August 2008 in her home in the village of Amport, after admitting to her husband that she had had an affair. When her body was found in the kitchen of the house, it was discovered that she had suffered a partially severed head and at least 40 stab wounds. Winchester Crown Court had heard during the trial that the attack was partly witnessed by children.

Alisdair Sinclair, who is 48 years old and caused the attack, was cleared of charges of murder, but was sentenced to nine years in prison for charges of manslaughter. Judge Guy Boney QC has been quoted as saying: “Your wife did everything she could to support and help you and indulge your eccentricities, including spending £100,000 (US$164,470) on three cars of the same model you hardly ever used.

“She wanted to make the marriage work and save it from collapse. These efforts cost her her life. Sally Sinclair appears to have coped with, and tolerated, your behaviour over a long period. When she could not take any more of your behaviour you exploded in a frenzy of brutality in reaction to certain information you forced out of her.”

Speaking about the case, Detective Sergeant Sarah Simpson from Hampshire Constabulary said outside of the courtroom: “A successful career woman had her life tragically and prematurely cut short and her family now have to lead their lives without her. Nothing can ever compensate for that.”

Friday, April 28, 2017

Debian, a free and open source (FOSS) Linux-based operating system, on Tuesday announced they are to shut down Debian’s public File Transfer Protocol (FTP) in November, via their official website. The public FTPs are to be redirected to Hyper-Text Transfer Protocol (HTTP) from November 1.

On Debian’s announcement list, Cédric Boutillier, a Debian developer, called the file transfer protocol “inefficient”, saying “FTP servers have no support for caching or acceleration.” Boutillier also added that FTP servers are rarely used. For over a decade, Debian installers have not supported FTP access on mirrors. This decision, however, would not affect the developer services, which would still support FTP.

FTP came into existence about 46 years ago for transferring files between two machines, without encryption. According to Boutillier, FTP “requires adding awkward kludges to firewalls and load-balancing daemons.” HTTP, which came after FTP, was designed for data flow between servers and clients. Popular Linux distros like Kali Linux and Canonical’s Ubuntu are based on Debian. The following websites are to be redirected to HTTP — rather than secure HTTPS — after October without changing the domain names:

1. http://ftp.debian.org
2. http://security.debian.org

Sunday, May 27, 2018

In the official result of Friday’s Irish referendum over the legality of abortion, referendum officer Barry Ryan announced yesterday 66.4% of voters favoured overturning the eighth amendment of the constitution. Introduced in 1983, the eighth amendment made abortion constitutionally illegal. Irish Taoiseach — Prime Minister — Leo Varadkar said supporting legislation, to be framed following the result of this referendum, is to be “enacted before the end of this year”.

More than 2.1 million people voted on the referendum on Friday. With a 64.1% turnout, 1,429,981 voted in favour of eliminating the abortion ban while 723,632 voted to keep it. The results were announced at Dublin Castle. About 6000 voters spoiled their votes. Calling it “an historic day”, Prime Minister Varadkar said it was “a great act of democracy.” Ministers said they would form laws allowing medical termination of pregnancy in the first trimester, twelve weeks, of pregnancy, and under special cases until the 24th week. The legislation is to be formed after discussion with medical experts.

Since the amendment, Article 40.3.3 of the Irish constitution, in 1983, which gave an unborn child equal rights to life as the mother, hundreds of thousands of women traveled to different countries for the medical termination of pregnancy, while some used medical drugs illegal in Ireland to terminate the pregnancy.

“Savita Matters, Women Matter” was one of the slogans used by the supporters who wanted to repeal the amendment. In October 2012, a 31-year-old dentist of Indian origin, Savita Halappanavar, died from sepsis at a Galway hospital after she was denied abortion for a protracted miscarriage. She was told by a midwife that termination of pregnancy would not be possible since Ireland was a “Catholic country”. Halappanavar’s photo was used for posters by supporters who wanted the 35-year-old amendment repealed. In 2016, the current Roman Catholic Pope, Pope Francis, described abortion as a “very grave sin” and a “horrendous crime”.

Halappanavar’s father Andanappa Yalagi told Hindustan Times, “We’ve got justice for Savita. What happened to her will not happen to any other family. I have no words to express my gratitude to the people of Ireland at this historic moment.” 39 of 40 Irish constituencies voted in favour of repealing the law, while voters in only one constituency, Donegal, voted against — 51.87% opting to keep the anti-abortion laws. After the result was announced, the crowd were chanting Savita’s name in front of Dublin Castle.

Cora Sherlock, an anti-abortion activist, said, “what we voted on today is the ending of human life.” “I will accept the will of the Irish people, at the same time I will make it very clear what I feel of the campaign that has taken place. We will now regroup and find out what our next move is”, she added. Another activist, David Quinn, said, “The result today is basically a reversal of the 1983 result. On that occasion the defeated side did not simply slip away.”

“The people have said that we want a modern constitution for a modern country”, Prime Minister Varadkar said. Canadian Prime Minister Justin Trudeau later congratulated Varadkar on Twitter, saying: “What a moment for democracy and women’s rights.”

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)