Hm. The covenant of Noah is about two paragraphs before this part (King James Version) which is used for various justifications of slavery and discrimination against all sorts of people because they are said to bear the Curse of Ham. If folks wanted to use the Bible to justify anything ISIS says is justified by God's words in the Koran, they could easily do so.
18 And the sons of Noah, that went forth of the ark, were Shem, and Ham, and Japheth: and Ham is the father of Canaan.
19 These are the three sons of Noah: and of them was the whole earth overspread.
20 And Noah began to be an husbandman, and he planted a vineyard:
21 And he drank of the wine, and was drunken; and he was uncovered within his tent.
22 And Ham, the father of Canaan, saw the nakedness of his father, and told his two brethren without.
23 And Shem and Japheth took a garment, and laid it upon both their shoulders, and went backward, and covered the nakedness of their father; and their faces were backward, and they saw not their father's nakedness.
24 And Noah awoke from his wine, and knew what his younger son had done unto him.
25 And he said, Cursed be Canaan; a servant of servants shall he be unto his brethren.
26 And he said, Blessed be the Lord God of Shem; and Canaan shall be his servant.
27 God shall enlarge Japheth, and he shall dwell in the tents of Shem; and Canaan shall be his servant.
Careful what you wish for. With the current generation, you might end up with iWar instead.
I like to get these scammers on the line for as long as possible, but without wasting my time. So far, what I've seen to work well was "Oh, my computer just crashed, I need to reboot" and "Now windows is applying updates". This means they'll wait without me having to think of stuff to tell them. Any other effective tricks?
Get rid of your dictator and adopt a representative democracy and it will be over. Indeed, nobody could have thought it would go on this long.
In my opinion the peer-review should be changed to a double-blind system: the reviewer should not see name and affiliation of the authors, and judge the work as it would grade an undergrad paper (i.e. harshly). Like this I believe the signal-to-noise ratio in journals would increase, and only good papers would get published.
Please no! The problem with this approach (and it's already happening) is that what will get published is boring papers that bring tiny improvements over the state of the art. They'll get accepted because the reviewers will find nothing wrong with the paper, not because there's much good in there. On the other hand, the really new and interesting stuff will inevitably be less rigorous and probably more controversial, so it's going to be rejected.
Personally, I'd rather have 5% great papers among 95% of crap, than 100% papers that are neither great, nor crap, but just uninteresting. Reviews need to move towards positive rating (how many thing are interesting), away from negative ratings (how many issues you find in the paper). But it's not happening any time soon and it's one of the reasons I've mostly stopped reviewing (too often overruled by the associate editor to be worth my time).
PaleMoon is just Firefox 24 ESR. You're still using Firefox, someone just s/Firefox/PaleMoon/g 'd it.
Thanks for the reports of stale gasoline - I'm convinced. Tonight I'll head out & recycle my old gas. The problem isn't getting things together; it's keeping it all up to date & ready. Your comments hit me in the right place: be prepared.
I'm associated with a ham radio emergency group; the rule is that the station's equipment must be immediately ready for action. In an emergency, you don't have the luxury of stringing a cable, or figuring out which power supply can work with which rig. If the transceivers aren't wired up, tested, and set to go, they might as well be underwater. Same's true for on-the-air skills. You gotta check into the 2-meter net at least every month, or you'll get rusty and screw up when things get hot.
And so it is with earthquake readiness. It's not enough to put away a survival stash and let it molder. Gotta keep things fresh - gotta keep my skills sharp.
ps to ksmithderm
Background: I live on North Oakland, next to Berkeley, in the Rockridge section. Urban, detached 2 bedroom house about 100 years old.
We bolted down our house, fully reinforced the stemwalls, and installed shearwalls. For our little 2-bedroom bungalow in Oakland, this set us back around $20,000. Earthquake insurance seemed outrageous (around $2,500/year, with very limited benefits). Along with the earthquake retrofit, we set aside a few cases of food & twenty 5-gallon jugs of water. A 2Kw Honda generator. Radio, flashlights, FRS walkie-talkies, etc. Small amount of medical stuff.
Yes, I have onsite and offsite backups (that's easy); the real problem would be connectivity after a quake. There's probably a hundred telephone poles between my house and the central office.
Some challenges: Keeping food & water fresh is a problem - cans get rusty as water condenses on cold surfaces. Some camping food goes bad. MRI rations taste, well, horrible. We should replace water & food annually, and generally forget to. (We discovered diapers in our earthquake stash, left over from when our college kids were infants)
Storing gasoline for the generator is a problem. I'm told that gasoline gets stale after a few months (is this true, or an urban legend?). It's a pain to lug a 3 gallon gas can around, and it's not something I want under my house. (I store it in a shed, where it's out of sight & out of mind - so I rarely refresh it. Is there a small, 5 or 10 gallon under-ground gasoline storage tank?). I should start and exercise the generator every month; it's more like every two years or so. Our experience in the 1989 quake was that gas stations can't pump after an earthquake (no power).
Our neighborhood's quake group (the Oakland - Rockridge Shakers) meets every summer, and the earthquake drills have been quite useful - we've had several fun practice sessions, where we hunt for human dummies hidden around the neighborhood, search for downed wires, and practice using walkie-talkies. Afterwards, it's a block party, and we compare notes while sharing lunch.
My home business, Acme Klein Bottles, lost two glass Klein bottles in last night's quake. Both fell off a shelf and shattered on the floor. Good lesson: keep my glassware stored down low, with holders to prevent boxes from shifting. Since most of my glass Klein bottles are stored under our house; a major local temblor that destroyed the house would also wipe out the business.
It's been in Nightly for a while. I'm posting using it. The only thing that doesn't work well for me is...Gmail.
There's also full sandboxing support, but you need a compile time flag for it.
You don't have to. The browser is fully open source. That's why they're actually comparing vs Chromium, not Chrome. But Chromium is missing quite a few features compared to Chrome like H264 support.
PaleMoon is just a rebranded Firefox 24 ESR.
Palemoon is just Firefox 24 ESR, which is coincidentally what the Tor Browser Bundle used to be based on.
"The Chrome Security team has been a source of innovation in the browser security space. Tor Browser Bundle is based on Firefox and thus inherits progress made by Mozilla automatically. While improvements in Chrome may not be appropriate for Firefox, they could be integrated in Tor Browser Bundle. In a best case scenario, members of the Chrome Security team may be allowed to work with the Tor Project on these changes."
Basically it's saying: Chrome is also doing good stuff, combine it with the stuff you get from Mozilla for a better result.