DiltoGeggins

aye aye aye again with the triggering?

A snippet from the article. I removed some content for brevity.

For decades, climate change has proceeded at roughly the expected pace, says David Armstrong McKay, a climate scientist at the University of Exeter, in England. Its impacts, however, are accelerating—sometimes far faster than expected.

For a while, the consequences weren’t easily seen. They certainly are today. The Southwest is sweltering under a heat dome. Vermont saw a deluge of rain, its second 100-year storm in roughly a decade. Early July brought the hottest day globally since records began—a milestone surpassed again the following day. “For a long time, we were within the range of normal. And now we’re really not,” Allegra LeGrande, a physical-research scientist at Columbia University, told me. “And it has happened fast enough that people have a memory of it happening.”

...a growing number of climate scientists now believe we may be careening toward so-called tipping points, where incremental steps along the same trajectory could push Earth’s systems into abrupt or irreversible change—leading to transformations that cannot be stopped even if emissions were suddenly halted. “The Earth may have left a ‘safe’ climate state beyond 1°C global warming,” Armstrong McKay and his co-authors concluded in Science last fall. We don’t really know when or how fast things will fall apart.

Some tipping points will interact, worsening one another’s effects. When melt from Greenland’s glaciers enters the ocean, for example, it alters an important system of currents called the Atlantic Meridional Overturning Circulation. Right now it’s the feeblest it’s been in more than 1,000 years.

A shutdown of that ocean current could dramatically alter phenomena as varied as global weather patterns and crop yields. If the temperature of the sea surface changes, precipitation over the Amazon might too, contributing to its deforestation, which in turn has been linked to snowfall on the Tibetan plateau.

One grim paper that came out last year, titled “Climate End Game,” mapped out some of the potential catastrophes that could follow a “tipping cascade,” and considered the possibility that “a sudden shift in climate could trigger systems failures that unravel societies across the globe.”

Chris Field, the director of the Stanford Woods Institute for the Environment and a contributor to several IPCC reports, warned that “at some point, the impacts of the climate crisis may become so severe that we lose the ability to work together to deliver solutions.”

very pleasing. very very pleasing.

Hopefully I'm not repeating an already known issue.

,,,,,,,,,,,

edit: just to clarify this particular sequence of events. It usually happens when I navigate into a post. And I stay there. And then later, sometimes even after leaving the window, and I come back and try to navigate back to the main page. The navigation is unresponsive. Then when I go to leave the hexbear website, it lets me but only after I "okay" a message that says, "Leave site? Your changes won't be saved".. so somehow the website thinks I am writing a comment even though that is not the case.

,,,,,,,,,,,

edit2: appears that these are the errors I am getting from within the console:

Failed to load resource: net::ERR_CONNECTION_CLOSED 2client.js?v=1:2 Uncaught TypeError: e is not a function at client.js?v=1:2:904615 at Array.forEach () at Object.call (client.js?v=1:2:904584) at C (client.js?v=1:2:909616) at Object.t [as push] (client.js?v=1:2:909921) at Object.Q [as event] (client.js?v=1:2:914009) at ae (client.js?v=1:2:210176) at HTMLDocument. (client.js?v=1:2:209738) client.js?v=1:2 Websocket closed. (anonymous) @ client.js?v=1:2 (anonymous) @ client.js?v=1:2 e.dispatchEvent @ client.js?v=1:2 e.handleEvent @ client.js?v=1:2 handleCloseEvent @ client.js?v=1:2 client.js?v=1:2 WebSocket connection to 'wss://hexbear.net/api/v3/ws' failed: e.tryConnect @ client.js?v=1:2 (anonymous) @ client.js?v=1:2 client.js?v=1:2 Websocket closed. (anonymous) @ client.js?v=1:2 (anonymous) @ client.js?v=1:2 e.dispatchEvent @ client.js?v=1:2 e.handleEvent @ client.js?v=1:2 handleCloseEvent @ client.js?v=1:2 client.js?v=1:2 WebSocket connection to 'wss://hexbear.net/api/v3/ws' failed: e.tryConnect @ client.js?v=1:2 (anonymous) @ client.js?v=1:2 client.js?v=1:2 Websocket closed.

,,,,,,,,,,,

I find that in certain situations, I cause my session with the website to freeze.

I am not certain what leads to this, but I think the cause has something to do with the fact that I've told Hex Bear I want to comment, or make some other edit on the current page. (From what I can ascertain though, I haven't intentionally gone into such an editing mode.)

The workaround is that I navigate away from the Hex Bear website, usually by doing a search for "hex bear". Then, I navigate back into a fresh Hex Bear session. When I do the first step above, I get this message, "Leave Site? Changes you made may not be saved." I click yes and that allows me to find Hex Bear and start my new session.

Just curious if anyone has encountered this? I am one of those end users who gets lost easily and thus causes mayhem to happen on occasion.

Thanks so much, if you want me to provide more detail, just holler...>

edit: it happened on the new megathread just now https://hexbear.net/post/276470 (The Einstein thread) my cursor wasn't focused on the comment field or anything I could tell. When I would go to click on the "hexbear" link at the top of the page there was no response. when I went to the url field and navigated away from the page, there was that message, "Leave Site? Changes you made may not be saved."