marathon06.org

Saturday, September 4, 2021

Since June 2019, the people of South Gippsland Shire, located at the southernmost tip of Australia, have been without a local council, after a state government inquiry found “high levels of tension” within the council. Administrators were appointed by the Victorian state government in July 2019, who have governed the shire since then. However, South Gippsland’s council is scheduled to be restored with an election to be held via post from October 5-22, 2021.

Wikinews interviewed one of the candidates standing in this election, Sue Plowright. She is an independent contesting the Coastal-Promontory ward, which covers towns such as Venus Bay, Waratah Bay, Yanakie, Foster, Port Welshpool, and Toora. The Coastal-Promontory Ward elects three councillors to the South Gippsland Shire Council.

Thursday, October 21, 2010

One of Australia’s leading jockeys Stathi Katsidis has been found dead at the age of 31. He was found dead on Tuesday morning by his fiancee, Melissa Jackson.

Katsidis died less than a week before he was due to ride in the Cox Plate and was set to ride in the Melbourne cup in November. He was going to be riding former Australian Derby winner Shoot Out.

Born in Toowoomba, Katsidis had recorded over 170 victories last season. He had success in both the Australian Derby and the Group One Randwick Guineas. He suffered a knock back in 2008 when he was banned for nine months after testing positive for ecstasy. He had previously battled drug and weight problems in the past.

Tributes have been paid to Katsidis both jockey’s and trainers. John Wallace, the trainer of Shoot Out said “He told me he couldn’t wait to get to Melbourne and that he’d be down on Thursday. It’s a total shock.” Jockey Corey Brown said “He was a terrific guy, loaded with ability and is going to be sadly missed.”

Police have said that no suspicious circumstances surrounding Katsidis death. His fiancee has said that she suspects alcohol to be a factor in his death. Katsidis had been out drinking with friends on the night before his death. “Jockeys have to lose so much weight. Their bodies are drained like anorexic young girls. Then some of them go out and try drinking like men with big, strong bodies. It hits them like a brick wall. I just hope some of the other jockeys get a message from this.”

His funeral has been set for next Tuesday; exact plans have yet to be released.

Thursday, April 22, 2010

A luxury train derailed in South Africa outside the capitol of Pretoria yesterday, killing at least two people and leaving 25 injured.

The train had been entering a station in Pretoria when seventeen cars derailed, apparently during a switch between steam and electric locomotives, although the exact cause is not known. The train had been coming from Cape Town, with 55 passengers and an unknown number of crew on board.

None of the dead were identified, and nationalities were not released. However, a spokesperson for the operator of the train, Rovos Rail, said that passengers were from several different countries, and that most customers of the railroad were from the US or Europe.

Chris Botha, an emergency worker at the scene said that the derailment had produced “absolute carnage.” According to him, “[s]ome of the railway coaches are lying on top of each other and absolute wreckages. They had to use hydraulic rescue equipment to cut some of the people free.” The section of track where the incident occurred has been closed off.

Monday, November 2, 2020

The following is the sixth and final edition of a monthly series chronicling the 2020 United States presidential election. It features original material compiled throughout the previous month after an overview of the month’s biggest stories.

This month’s spotlight on the campaign trail: the Free and Equal Elections Foundation holds two presidential debates, three candidates who did not participate in those debates give their final pleas to voters, and three political pundits give their predictions on the outcome of the election.

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)

Thursday, February 22, 2007

Denial. Anger. Bargaining. Depression. Acceptance.

Originally formulated in 1973 by Elisabeth Kübler-Ross, these five stages are well-known to many as the “Five Stages of Grief“. However, despite their familiarity, the five-stage theory had remained untested empirically, until Paul K. Maciejewski, Ph.D., assistant professor of psychiatry at the Yale University School of Medicine and the Yale Bereavement Study completed several years of research, findings for which were published in the February 21 issue of the Journal of the American Medical Association (JAMA).

According to Dr. Kübler-Ross’s theory, denial is the first and most defining indicator of grief. The Yale Bereavement Study’s findings, in contrast, show acceptance to be the most common indicator, and yearning the strongest negative indicator.

The authors explain, “Disbelief decreased from an initial high at one month postloss, yearning peaked at four months postloss, anger peaked at five months postloss, and depression peaked at six months postloss. Acceptance increased steadily through the study observation period ending at 24 months postloss.”

Study author Holly Prigerson, associate professor of psychiatry at Harvard Medical School and director of the Dana-Farber Cancer Institute‘s Center for Psycho-Oncology and Palliative Care Research, says, “This would suggest that people who have extreme levels of depression, anger or yearning beyond six months would be those who might benefit from a better mental health evaluation and possible referral for treatment.”

The Yale Bereavement Study followed the progress of 233 participants from January 2000 through January 2003 who had lost family, most often a spouse, and was funded by the National Institute of Mental Health, the National Cancer Institute, the National Institute of Neurological Disorders and Stroke, the Center for Psycho-Oncology and Palliative Care Research, Dana-Farber Cancer Institute, and Women’s Health Research at Yale University.

Thursday, June 23, 2011

NASA’s Cassini–Huygens spacecraft has discovered evidence for a large-scale saltwater reservoir beneath the icy crust of Saturn’s moon Enceladus. The data came from the spacecraft’s direct analysis of salt-rich ice grains close to the jets ejected from the moon. The study has been published in this week’s edition of the journal Nature.

Data from Cassini’s cosmic dust analyzer show the grains expelled from fissures, known as tiger stripes, are relatively small and usually low in salt far away from the moon. Closer to the moon’s surface, Cassini found that relatively large grains rich with sodium and potassium dominate the plumes. The salt-rich particles have an “ocean-like” composition and indicate that most, if not all, of the expelled ice and water vapor comes from the evaporation of liquid salt-water. When water freezes, the salt is squeezed out, leaving pure water ice behind.

Cassini’s ultraviolet imaging spectrograph also recently obtained complementary results that support the presence of a subsurface ocean. A team of Cassini researchers led by Candice Hansen of the Planetary Science Institute in Tucson, Arizona, measured gas shooting out of distinct jets originating in the moon’s south polar region at five to eight times the speed of sound, several times faster than previously measured. These observations of distinct jets, from a 2010 flyby, are consistent with results showing a difference in composition of ice grains close to the moon’s surface and those that made it out to the E ring, the outermost ring that gets its material primarily from Enceladean jets. If the plumes emanated from ice, they should have very little salt in them.

“There currently is no plausible way to produce a steady outflow of salt-rich grains from solid ice across all the tiger stripes other than salt water under Enceladus’s icy surface,” said Frank Postberg, a Cassini team scientist at the University of Heidelberg in Germany.

The data suggests a layer of water between the moon’s rocky core and its icy mantle, possibly as deep as about 50 miles (80 kilometers) beneath the surface. As this water washes against the rocks, it dissolves salt compounds and rises through fractures in the overlying ice to form reserves nearer the surface. If the outermost layer cracks open, the decrease in pressure from these reserves to space causes a plume to shoot out. Roughly 400 pounds (200 kilograms) of water vapor is lost every second in the plumes, with smaller amounts being lost as ice grains. The team calculates the water reserves must have large evaporating surfaces, or they would freeze easily and stop the plumes.

“We imagine that between the ice and the ice core there is an ocean of depth and this is somehow connected to the surface reservoir,” added Postberg.

The Cassini mission discovered Enceladus’ water-vapor and ice jets in 2005. In 2009, scientists working with the cosmic dust analyzer examined some sodium salts found in ice grains of Saturn’s E ring but the link to subsurface salt water was not definitive. The new paper analyzes three Enceladus flybys in 2008 and 2009 with the same instrument, focusing on the composition of freshly ejected plume grains. In 2008, Cassini discovered a high “density of volatile gases, water vapor, carbon dioxide and carbon monoxide, as well as organic materials, some 20 times denser than expected” in geysers erupting from the moon. The icy particles hit the detector target at speeds between 15,000 and 39,000 MPH (23,000 and 63,000 KPH), vaporizing instantly. Electrical fields inside the cosmic dust analyzer separated the various constituents of the impact cloud.

“Enceladus has got warmth, water and organic chemicals, some of the essential building blocks needed for life,” said Dennis Matson in 2008, Cassini project scientist at NASA’s Jet Propulsion Laboratory in Pasadena, California.

“This finding is a crucial new piece of evidence showing that environmental conditions favorable to the emergence of life can be sustained on icy bodies orbiting gas giant planets,” said Nicolas Altobelli, the European Space Agency’s project scientist for Cassini.

“If there is water in such an unexpected place, it leaves possibility for the rest of the universe,” said Postberg.

Sunday, June 25, 2006

United State president George W. Bush kicked off the 2006 Tee Ball on South Lawn season Friday, June 23, 2006. This is the sixth year of the White House Tee Ball Initiative.In attendance at the game were General Peter Pace, Chairman of the Joint Chiefs of Staff, who served as the Commissioner of the game, Tim Brant from ABC Sports and WJLA-TV acting as the play-by-play announcer, and seven-year old Zane Ellingwood, who founded “America’s Littlest Heroes” last year in his hometown of Cumberland, Maryland.

In his opening remarks, Bush welcomed parents and grandparents to a “historic ballpark.” Pitcher Mike O’Connor from the Washington Nationals was at the game as well.