Resynthesizer, a plug-in for GIMP. The author also has details of the algorithm used published in his thesis paper.

To quote:

"People who do drugs are not *criminals*. They might be *sick*, but I don't think jail is gonna heal 'em. Yep, thank God they caught me. What was I doin' ruinin' my life with that marijuana? I wanna thank Bubba, my rehabilitator back there. I would not want to come out of jail wanting to do less drugs, I would wanna come out mainlining heroin into my fucking eyeball. I don't know the case yet that jail healed anybody. K? K, America? Wake up from you rlaw enforcement fucking fantasy, and shut up. It ain't gonna work, K? It's not gonna work. So let's move on to a plan that *might* work. Isn't that simple? Feels good, too, don't it?"

In sake of not being partially off-topic, my two cents boils down to *safe* integration of medical marijuana into our society. Are the local cops willing and able to legally protect these cultivators if said address(es) are made public? Are the cultivators able to protect themselves legally if necessary? Should a single marijuana plant be grounds for public announcement if said grower is unable to protect themselves from what could potentially be life or death situations?

I do not pretend to know the answers to these questions, nor do I wish to live in a fantasy land that cannabis cultivators are in a fair or safe world today when it is *still* federally illegal to possess such, even though, in my opinion, it is unconstitutional for such to be enacted by the federal government and not on a case by case basis via state level. Let the states decide as it were meant to be in the first place. Either way, we *must not* continue ignoring these issues as we have been and enact policies that show compassion towards fellow human beings.

Drugs nor people are inheritedly safe even when proper moderation and education is exercised. We must accept this but also accept that drugs have been and will continue to be in our society for the foreseeable future to come. The drug policies today are not keeping us safe from drugs whatsoever. Is safety not what matters to us? We cannot stop the universe from turning just as we cannot stop chemical reactions from occuring.

Believe it or not, but sometimes the usage of a drug does indeed outweigh the costs of not doing so for an individual and all others concerned. The federal nor sometimes state governments can decide this for us. We must integrate the decision making process peacably and compassionately; sharing roles between the patients, physicians and pharmacists on a local level.

In fact, OpenDNS does block this very web site at the DNS level, without bothering to ask the end user beforehand. When I go to d0z.me, I get the following message:

This site was blocked by OpenDNS in response to either the Conficker virus, the Microsoft IE zero-day vulnerability, or some equally serious vulnerability.

If you think this shouldn't be blocked, please email us at contact@opendns.com.

I apologize for being a bit pedantic, but: only cold medicines of which containing the drug ephedrine (including its synthetic derivatives, such as pseudo-ephedrine) are scheduled to that contract agreement.

Yes, the ephedrine class of drugs are often times used in the synthesis of (meth)amphetamines. Of course, this law, just like the hundreds of thousands of other similarly retarded laws here, does not help (hurt?) stop those sorts of interests! It doesn't dent the production labs, but simply keeps the "criminals" on their feet all the more -- increasingly cautious & paranoid they become -- which actually is benefiting to those concerned within and wish to stay out of the prisons.

It has, however, made it rather difficult for my mother to obtain sufficient quantities of the drug for her rather bad allergies ... seems as though no other drug works as well for her. As with *all* the laws against drugs here, the prohibition does exactly opposite of its "intentions" -- makes it difficult for legit consumption and merely justifies the brutality of the drug subcultures.

:-)

I'm glad that I am not the only one -- I, too, am having the same described problem as stated above, but only on my main workstation, which its browser version is 3.5.9 whereas version 3.6.3 of Firefox on my other station does not have these issues! Although, even on the newer version of Firefox, I am click

Damn rendering issues ...

Huh? You just defined the very such piece of computer technology otherwise known as a "server". I don't post here often, but this comment just makes my jaw drop unusually low for some reason, so I apologize ahead of time if I sound offensive...

1) A server, as described in a TCP/IP client & server topology, is a computer that is "always on" the internet, or so you very well hope so, especially if it is being used for "business" oriented tasks. Those packets get served to your "clients" whom serve you back, and this process cycles over until satisfied. Does this sound like another real world scenario to you?

2) A server is often updated at least once a week, sometimes more, depending on the sort of update this is. You could even argue such a hardware piece is often the most updated piece of equipment, generally speaking. (Some development systems could certainly be an exception, for instance!)

3) A server, by definition, is tasked with the role of serving, or "hosting" information back to said requesting clients, whom could and often are making all sorts of requests all at the same time (concurrently), hitting up your resources significantly as the volume of concurrency rises. This often taxes the hardware in several different key areas, sometimes very much like a video game (on steroids, even!) especially if you do not have a network topology in which allows better distribution of said serving tasks across.

In summary, have you ever tried keeping one, much less several parallel video surveillance systems up for months upon years at a time, with minimum downtime as any loss of said outage could leave you liable to your real-life business clients? Sometimes you don't have the luxury of redundancy to save your ass. When incoming bandwidth is not your bottleneck, you've gotta keep your disks seeking every bit as fast as they can keep up to, along with fast concurrency capabilities, along with allowing proper time for distributed mass A/V encoding of said daily video surveying operations to occur before considering that a solid "tape" and pushing those off to another system for backup, which mind you, is getting hit by many other requests in parallel to this first example.

Okay, so I did a terrible "summary", especially now as I am continuing onward with this new paragraph, but in other words ... real life servers do not often have it easy in their life! Their CPU, memory and disk I/O are often pushing near or at maximum utilization if you are trying to get every dollar out of your time & money spent. I push my personal workstations plenty hard, but not anywhere close to what some of my servers have gone through on a daily basis!

P.S. My examples given are of only my own personal real life business experiences in the "small time" playing league -- this represents 0.01% of what big name brand servers running many of our web sites we most all depend on every day, free or paid. Yes, my "servers" were indeed a mixture between the real stuff and the commodity desktop class hardware. Whereas I cannot prove this, I've got both win32 and personal *nix workstations that have indeed been alive w/o reset for a year. When your hardware does not fail, satisfied setups and plenty of other systems running to do various testing on, with the right style of administrated setup you can easily scale to the years. ksplice can be used on personal desktops / workstations, too.

You only *simply* have to devote a lifetime to computer science to learn the trade down to a true art.! :-)