Thursday, July 15, 2021

On Monday night, governor of the U.S. state of California Gavin Newsom signed a new US$262.6 billion budget bill for the state into law, with US$8.1 billion reserved for US$600 direct stimulus payments to Californians to aid in California’s recovery from the COVID-19 pandemic. The bill for the budget, SB 129, and the bill for the stimulus payments, SB 139, both passed both houses of the California Legislature for this fiscial year.

The payments, dubbed the Golden State Stimulus II, are set to be paid out to eligible California taxpaying residents beginning in September. To be eligible, residents must have filed a state tax return for last year, not be someone’s dependent, and must have earned no more than US$75 thousand in wages last year.

Eligible Californians would get a one-time payment of US$600, and households with dependents would receive an additional US$500. Around two-thirds of Californians are expected to get a stimulus payment, according to the governor’s office. Newsom initially proposed the payments in May to aid the state’s economic recovery, as part of his “California Comeback Plan”.

Californians who already received a stimulus payment earlier in the year are not eligible for this second payment. An additional payment of US$500 is still available for those who claimed dependents on their returns.

The budget also provides for US$5.2 billion in renters’ aid for low-income residents and landlords, which would pay for all rent left unpaid during the COVID-19 crisis, and cover rent for several coming months. Overdue water and utility payments would also be covered by US$2 billion in funding.

An additional US$1.5 billion was for grant money intended for small businesses, with US$120 million in tax credits for businesses willing to relocate to California.

California had a budget surplus of nearly US$76 billion during the COVID-19 pandemic.

In signing SB 129, Newsom line-item vetoed Section 19.55 of the bill concerning US$2.58 billion in appropriations to various funds “on a technical basis”, citing in an explanation appropriations covered under the section were superseded by the budget. In California, a governor may approve a bill passed by the Legislature with specific items related to the budget rejected. The Legislature can override this line-item veto with a two-thirds vote of both the Assembly and the Senate.

Friday, September 25, 2009

Today, after two years of waiting, American iPhone users are finally able to send and receive MMS messages. This long awaited feature has caused Apple and AT&T a great deal of grief from its user base. Originally the grief was directed at Apple for the lack of inclusion on the device, but as time progressed AT&T was faulted for lack of support.

When the iPhone was released in June of 2007, it lacked one feature that was widely available on other devices: MMS or Multimedia Messaging Service. This standard, similar to the all text SMS standard, allows users to send and receive video, audio, and picture files on their mobile phones. MMS was launched in 2002 and by 2007 was a common feature on most new mobile phones. It was not until June 2009, with the release of iPhone OS 3.0, that the devices also had the capability to send and receive these multimedia messages. Unfortunately for American iPhone users, all of whom use AT&T because of an exclusive agreement between the phone company and Apple, AT&T did not allow iPhone users to use this feature; that changed today.

Current iPhone users simply need to update (from iTunes) and reboot their device in order to enable MMS. AT&T was originally concerned about not having the network capacity to handle the data demand of all the MMS messages and in Wikinews’ own testing this seems to be a valid issue. The ability to send and receive MMS messages was functional, but by midday Friday (PST), AT&T’s network was extremely slow, with messages taking in excess of two minutes to send. Tests over AT&T’s 3G network showed upload and download speeds nearly halved what they were just a few days prior.

Tuesday, February 12, 2008

Buffalo, New York —According to radio communications by the Buffalo, New York Fire Department, at approximately 10:15 p.m. EST two water pipes inside the Darwin D. Martin House, a National Historical Landmark, broke causing several rooms to flood.

The breaks were discovered in the gift shop area of the house but quickly began to flood other areas near the shop as firefighters had a difficult time locating the main shut off valves.

At 10:50 p.m., firefighters reported to have shut off “several main valves” stopping the flow of water. The cost of the water damage is not known, but covered several rooms. Recent sub-zero temperatures in the city is said to be the cause of the break. At the time of the call, the temperature was only 10°F with a wind chill of 4°F above zero. On Sunday the temperature was only 3°F with a wind chill of -23°F.

The house, designed by Frank Lloyd Wright, has seen rough times over the years, experiencing problems such as vandalism. The first half of the complex was built in 1903 and finished in 1905. After the pergola, conservatory, and carriage were demolished, restoration and rebuild began in 1992 and is scheduled for completion in 2008 or 2009.

Wednesday, August 31, 2005

A Rhode Island district court has frozen all the US assets of the Palestinian Authority (PA), prompting Palestinian finance minister Salam Fayyad to request the aid of US Secretary of State Condoleezza Rice.

The frozen assets include US holdings in an investment fund worth $1.3 billion, which was used to finance economic development, and $30 million from the Palestinian Monetary Authority.

The ruling was passed upon the PA when they refused to compensate the relatives of a Jewish couple shot dead by members of Hamas in 1996.

US citizen Yaron Ungar and his wife Efrat were killed while returning from a wedding near the West Bank, when their car was shot at repeatedly, killing the couple. Three Hamas militants were jailed as a result.

A lawsuit was filed in 2000 against the Palestinian Authority, the PLO, Hamas, and Yasser Arafat in Rhode Island.

Yasser Arafat hired lawyer and former attorney general Ramsey Clark as his defense. In the case, Clark argued that the PA was a sovereign state, and that it deserved immunity from prosecution accorded to most countries. The court disagreed with this, and in 2004 they ruled that Palestine is not a state, and ordered them to pay the Ungars $116 million. A federal appeals court upheld the verdict in March.

The head of Washington’s PA office, Hasan Abdul Rahman said that his office had been “paralysed” by the verdict.

“It paralyzes the function of the office, and I think that is the intention of the plaintiffs.” he told Associated Press shortly after the decision, and called upon the US administration to intervene.

Thursday, October 29, 2020

The following is the fifth 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 Libertarian Party’s presidential nominee secures ballot access in all 50 U.S. states, the Unity Party of America presidential nominee proposes a novel solution to the issue of “packing” the U.S. Supreme Court, and three candidates give their thoughts on the latest military conflict between Armenia and Azerbaijan.

Wednesday, April 13, 2005The Conservative Party of the United Kingdom, Monday, launched its slimline manifesto for the May 5th general election, a twenty-seven page document entitled The British Dream.

The manifesto focuses on five key areas:

Lower tax and value for money: The party plans to make up to £12 billion of savings annually by reducing beurocracy such as quangos. £8 billion will reduce previous deficit, and £4 billion of tax cuts will be made, especially to what have been called “stealth taxes”. The party promised that funding for education, health, transport and international development would not be cut, and spending on police, defence and pensions would be increased.

Flexible childcare and school discipline: The manifesto promised an increase in maternity pay and more choice of childcare. Under a conservative government more independence over expulsions and admissions would be given to school heads and governors. Special schools for disruptive pupils would be created, and more vocational courses would be created for 14-16 year olds.

Better healthcare and cleaner hospitals: A major feature of the coservative campaign has been hospital sourced infections, and in respose the party have promised to introduce ward matrons charged with keeping hospitals clean, with the authority to close wards with MRSA infections. A Conservative government would contribute funding towards operations in private hospitals. Econimic migrants with HIV or TB would not be allowed to live or work in Britain.

Safer communities and more police: A Conservative government would increase police recruitment by 5,000 a year. The manifesto promised to increase prison terms and increase Britain’s prison capacity by 20,000 places. The party would reverse the Labour government’s decision to relax laws prohibiting Canabis use.

Secure borders and controlled immigration: The manifesto proposes a new border police at Britain’s busiest air and sea ports, with 24 hour surveilance. The party would set a quota on economic migrants and reject asylym-seekers who are not vetted by the UNHCR.

Party leader Michael Howard summed up the manifesto: “If you long for cleaner hospitals, more police, school discipline, controlled immigration, lower taxes and accountability – you can vote for it, on 5 May”, accusing prime-minister Tony Blair, who is campaigning for his third term, of letting the country down.

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)