SoylentNews is people
SoylentNews
Climate Central reports
[...] A massive iceberg roughly 225 square miles in size--or in more familiar terms, 10 times the size of Manhattan--broke off [from the Pine Island Glacier] in July 2015. Scientists subsequently spotted cracks in the glacier on a November 2016 flyover. And in January, another iceberg cleaved off the glacier.
Satellite imagery captured the most recent calving event, which Ohio State glaciologist Ian Howat said " is the equivalent of an 'aftershock'" following the July 2015 event. The iceberg was roughly "only" the size of Manhattan, underscoring just how dramatic the other breakups have been.
[...] The ocean under Pine Island Glacier's ice shelf has warmed about 1°F since the 1990s. That's causing the ice shelf to melt and pushing the grounding line--the point where the ice begins to float--back toward land, creating further instability.
[...] The glaciers [such as the Pine Island Glacier] and ice shelves [such as the Larsen C ice shelf, which is on a death watch] help hold back a massive ice sheet on land. Their failure would send that ice to the ocean, pushing sea levels up to 13 feet higher than they are today.
[...] Cutting carbon pollution presents the only path forward to stave off the worst impacts of a melting Antarctic.
(Score: 0) by Anonymous Coward on Sunday February 19 2017, @08:46PM
Often the #content fragment will hide things like a title bar
I block a great deal of junk in my browser.
If I have ever linked to a page that does what you described, I regret that.
I make an effort to avoid such situations.
When I come across a page that does ridiculous nonsense with their presentation, I try to find another page with similar content and link to that instead.
That said, it doesn't sound like you are actually talking about the browser's title bar but rather the headline within the page.
On some occasions, I've chosen a #FragmentIdentifier that is a bit farther down the page, where the actual content starts.
In that case, the #FragmentIdentifier helps to -avoid- such page-construction nonsense.
Again, this is in consideration of our users who depend on a screenreader; a lowest-common-denominator thing.
evaluate if the source is credible
I'd like to hear from anyone here whose browser does not allow him/her to hover over the hyperlink and see the URL.
You are hand-waving.
crap links
You are hand-waving.
If you are not willing to click the link and see what results, and evaluate that, what good is it having you on staff?
since [the time] you tossed in a link [...] to a Google [cache] version of a page
I had done it prior to that and that passed without a ripple.
You are hand-waving again.
I ALWAYS include a link to the (orig) page.
Again, if you're not willing to click the link and evaluate that, what use are you to the site?
we see a lot of links in submissions that [...] have the trackers still embedded in them
I challenge you to point to even 1 of those from me.
I make an effort to remove that junk.
[URLs] pulled direct from the address bar
I rail against that myself.
(The cold weather viking bikers link the other day got a rebuke from me for its form.)
I'm similarly rebuking you right now regarding your ability to evaluate what is useful in a URL and what is not.
sources [...] very far left (as yours tend to be) or very far to the right (as The Mighty Buzzards tend to be)
I've said before that I wouldn't give you a plugged nickel for a person or a story without a point of view.
I consider the types associated with that to be intellectually lazy.
If you can't defend your belief system when it is challenged, what you have hasn't been arrived at through an actual thought process; it's just prejudice.
I've also mentioned that those types of stories tend to get the most activity here, so clearly there is a hankering for them.
article from bufferapp.com
...which is about tracking junk that I have already said I make a point of removing.
It has nothing to do with the topic at hand.
Additionally, that page's construction is an example of something for which I might include a #FragmentIdentifier.
1) The content doesn't begin at the very top of the page (HTML-only presentation).
1a) Accessibility guidelines also state that if you don't put your content at the very top of the page, the very first thing on your page should be a Jump To Content link.
Not done there.
2) There's interstitial junk between the headline and the start of the text body (though I've seen much worse).
Compounding the badness of the page construction, is the fact that there is no #FragmentIdentifier just before the headline.
The first useful #FragmentIdentifier is #article_wrapper. [bufferapp.com]
Use of Accessibility features on the page is a ham-fisted, slap-dash effort.
As such, even using the #FragmentIdentifier that is available is a less-than-ideal situation.
I shall now go cry in the corner, for I have been called a nitwit by some guy on the internet.
...and well you should. 8-)
-- OriginalOwner_ [soylentnews.org]
(Some guy on the internet)