Yes. In China it happens apparently quite often that weather is regionally modified, e.g. in order to have good weather conditions during certain events (like olympics in Beijing). But also in other countries weather modification is applied, for reasons of agriculture, pollution, skiing, etc. Obviously, one wonders on the environmental impact of such an artificial cloud feeding process with silver iodide. I just googled, stumbling upon this report http://www.weathermodification.org/AGI_toxicity.pdf which published the result: no environmentally harmful effects...
and w.r.t. ur question: I mean different weather conditions which we experience locally (like droughts or other extreme weather events) are (often) due to large-scale/global climatic changes. Hence, cloud seeding just describes a local, short-term mitigation of these events.
However, there is a geoengineering proposal (so climate modification) which also suggests to seed clouds above the sea (i.e. increase cloud coverage, e.g. by using seaspray as cloud condesation nuclei), thereby increasing the planetary albedo (Earth reflectance) and reducing the energy reaching the Earth surface. If this idea is promising or not, I couldn't judge upon, but for sure it is worthwhile to take a closer look at.
Well, the topic GPL vs other open-source licenses (e.g., BSD, MIT, etc.) is old as the internet and it has provided material for long and glorious flame wars.
The executive summary is that the GPL license (the one used by Linux) is a license which imposes some restrictions on the way you are allowed to (re)use the code. Specifically, if you re-use or modify GPL code and re-distribute it, you are required to make it available again under the GPL license. It is called "viral" because once you use a bit of GPL code, you are required to make the whole application GPL - so in this sense GPL code replicates like a virus.
On the other side of the spectrum, there are the so-called BSD-like licenses which have more relaxed requirements. Usually, the only obligation they impose is to acknowledge somewhere (e.g., in a README file) that you have used some BSD code and who wrote it (this is called "attribution clause"), but they do not require to re-distribute the whole application under the same license.
GPL critics usually claim that the license is not really "free" because it does not allow you to do whatever you want with the code without restrictions. GPL proponents claim that the requirements imposed by the GPL are necessary to safeguard the freedom of the code, in order to avoid being able to re-use GPL code without giving anything back to the community (which the BSD license allow: early versions of Microsoft Windows, for instance, had the networking code basically copy-pasted from BSD-licensed versions of Unix).
In my opinion (and this point is often brought up in the debates) the division pro/against GPL mirrors somehow the division between anti/pro anarchism. Anarchists claim that the only way to be really free is the absence of laws, while non-anarchist maintain that the only practical way to be free is to have laws (which by definition limit certain freedoms).
So you can see how the topic can quickly become inflammatory :) GPL at the current time is used by aro
whoa, the comment got cut off.
Anyway, I was just saying that at the present time the GPL license is used by around 65% of open source projects, including the Linux kernel, KDE, Samba, GCC, all the GNU utils, etc.
The topic is much deeper than this brief summary, so if you are interested in it, Leopold, we can discuss it at length in another place.
Thanks for the record long comment - am sure that this is longest ever made to an ACT diigo post!
On the topic, I would rather lean for the GPL license (which I also advocated for the Marek viewer programme we put on source forge btw), mainly because I don't trust that open source is by nature delivering a better product and thus will prevail but I still would like to succeed, which I am not sure it would if there were mainly BSD like licenses around. ... but clearly, this is an outsider talking :-)
Well, not going into the discussion about GPL/BSD, the viral license in this particular case in my view simply undermines the "clean and clear" motivations of the initiative authors - why should *they* be credited for using something they have no rights for?
And I don't like viral licences because they prevent using things released under this licence to all those people who want to release their stuff under a different licence, thus limiting the usefulness of the stuff released on that licence :)
BSD is not a perfect license too, it also had major flaws
And I'm not an anarchist, lol
Greenwich could lose its place at the centre of global time if a move to "atomic time" is voted in by the International Telecommunication Union in Geneva in January 2012.
Haha this is really a British article...
Already since 1972 we don't use GMT but UTC, which is based on atomic clocks. However British continue to call it GMT... The question is to drop the leap second in UTC, and France is definitely for this change (for scientific motives of course...;) I don't see how this is connected to winter time however...
And they shouldn't worry Greenwich is still the beginning of the world with 0 degree longitude !
"the end of GMT as an international standard could accelerate the move to keep British Summer Time into the winter, letting us have lighter evenings."
As I understand it, if GMT looses its "prestigious" status, then it would be easier to push through all-year BST in UK.