![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)

As a follow-up to
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
NBC Nightly News featured a new scientific report suggesting significant changes in sea levels will impact the United States much sooner than thought. The report entitled Surging Seas
finds the odds of “century” or worse floods occurring by 2030 are on track to double or more, over widespread areas of the U.S. These increases threaten an enormous amount of damage. Across the country, nearly 5 million people live in 2.6 million homes at less than 4 feet above high tide — a level lower than the century flood line for most locations analyzed. And compounding this risk, scientists expect roughly 2 to 7 more feet of sea level rise this century. [see graphic below]
![]() |
![]() |
The report has been made available online, and Climate Central has designed a super elegant and user friendly interactive map to see what impact sea level changes will have on your own community. The map draws its information from a peer reviewed study. And it uses the National Elevation Dataset, a product of the U.S. Geological Survey.

The effects of a five foot sea rise on my home town of Hampton, Virginia. The solid blue line indicates the current shoreline, gray shows the areas affected by rising sea levels with the interior blue line the new coast line. The "city" of Poquoson would be completely wiped out. This portion of Virginia is called "Tidewater" and it would be affected the most because of the low laying tidal flats and swampy areas. On a personal note, two weeks ago, my insurance agency dropped home coverage due to my proximity to living near a flood zone in Brooklyn. The letter cited increased risks from hurricanes and other issues associated with climate change (i.e. rising sea levels).
Here what happens to Staten Island, Brooklyn, and Queens (5 foot rise):

This is the full feature from NBC Nightly News (you *MAY* have to refresh your browser page to reload the embedded video correctly ;)
(no subject)
Date: 17/3/12 02:35 (UTC)Where you could argue "shut up" is not a big deal, so likewise could I argue "you jerk" is along those same lines.
Noone likes being told to shut up and no one likes being called a jerk. Where's the difference?
and honestly -- do you believe the "intent" of his sentiment was any less direct than mine? I dont know why you believe that, but I guess that would be your perrogative.
(no subject)
Date: 17/3/12 05:06 (UTC)I'm sorry if "shut up" was rude. Next time I'll just tell you to close your mouth or hush.
(no subject)
Date: 17/3/12 07:06 (UTC)have more of an objection to not having *both* of us being spoken to -- rather than what was said in this case
But anyways...onward and upward...
(no subject)
Date: 17/3/12 09:03 (UTC)If you believe calling people jerk is just fine, that would be your prerogative. But the moment they come complaining, I would have to do something about it. So I would err at the side of caution in such situations.
(no subject)
Date: 17/3/12 09:20 (UTC)If you had to "do something about it" and you honestly believe that only I would be at fault in such an exchange -- I posit either the rules or their intent/interpretation would be flawed.
If we want to believe that rudeness is A-OK, but a named response is bad... then that seems problematic of much more than just *me*
So I err on the side of caution, but not to the point where I'm afraid to take it up at the appropriate time to whomever is involved and argue it.
I believe what is being described here to be one-sided enough that I would be willing to argue it, even if I lost.
Hopefully we wont find ourselves there.
(no subject)
Date: 17/3/12 09:32 (UTC)That said, I do share your hope. It wasn't such a big deal as it may sound.
(no subject)
Date: 17/3/12 09:36 (UTC)and when "shut up" = "dont be silly" then I would agree with your point. Except, they're not, so I'm not really following you there.
It wasnt a big deal except you keep calling just me out -- and you're downplaying the rudeness of his comment -- which also is something I keep asking WHY you feel it's not a "big deal"?
(no subject)
Date: 17/3/12 09:40 (UTC)I answered your latter question in the neighboring comment.
I think you are taking this too personally. I see a slur - I react. I cannot give a much more complex explanation for that, frankly.
(no subject)
Date: 17/3/12 09:26 (UTC)Why is telling me to "shut up" just fine and dandy again?
You acknowledge there are subjective elements to the discussion here, and that "name calling" is bad. But WHY is name-calling bad?
Usually it's because it's "rude".
So why again am *I* the only one who was spoken to? If you're going to be in a position of having to "do something about it" -- exactly why should I be understanding of the guy who says "Shut up" not even being looked at??
I'm honestly curious as to how the dispensement of fairness has been determined.
(no subject)
Date: 17/3/12 09:29 (UTC)But again *I* am the one with the warning?
Nice...
(no subject)
Date: 17/3/12 09:34 (UTC)(no subject)
Date: 17/3/12 09:42 (UTC)Honestly -- this is something that takes interpretation?
Sure I could have responded differently. But the point I keep making that I feel you're ignoring is there were *ALSO* different ways he could have **initiated** a response to me in the first place.
(no subject)
Date: 17/3/12 09:44 (UTC)(no subject)
Date: 17/3/12 09:49 (UTC)I wouldnt have told you to, nor would I say such a thing and be surprised
if someone said *hey!* over the comment.
I appreciate your feedback but I hope you see my objection as well. Thanx again