I used to work down the street from this place. They have several practice poles that the students learn to climb. As I understand it, the pole broke and landed atop the student, so it wasn't just the fall that killed him.
(The article is tagged "subscriber only", but it let me see it anyway.)
We watched a couple of hungry polar bears 🐻❄️ attempt to have walrus for dinner. Both were unsuccessful. We also saw a number of bears attacking at once, and they were able to isolate some walrus pups and elderly or sickly walruses. The whole group feasted.
The narrator said that this was unusual, as polar bears are not just antisocial, they actively dislike one another.
To be honest, in that part of #SoCal, I'd probably directly contact the University of California's Riverside campus with that question. That would cut through all the #SEO manipulation of search results and get information straight from someone who knows what they're talking about.
One might say that my relationship with various methods of receiving bills and receipts is "complicated".
And that's not counting the ones where you have to log into their site every month to download an encrypted file and copy the individual file's passcode. Nobody has time to securely store a file-by-file passcode. Either give it to me unencrypted or use a single passcode that applies to every file.
(This topic came to mind because of @clacke's discussion of storing his receipts in #DeltaChat (which AFAIK is just a chat-like interface atop e-mail ... so I guess all that would also be available in his inbox).
After a while, $EMPLOYER stopped requiring receipts to be faxed and allowed us to upload .pdf and .tiff documents ... so paper became a special case and even more burdensome.
And of course, I've used the submit receipts and delete local copies method because even dealing with electronic receipts across personal and employer computers is too much hassle.
Now, however, every company wants to do electronic receipts and "pull" type billing (where they hit your card or bank account periodically without any action on your part, and if they make an error, you have to depend upon them agreeing and sending excess funds back ... while any related overdraft or overlimit fees would remain your responsibility). They also all want you to submit an e-mail address and a cell phone number so they can spam you with unneeded and unwanted notifications.
This happened just as I no longer had access to a receipt scanner (or any other scanner ... I've long used the "tape receipts to a sheet of paper" method and a regular scanner), so going fully back to paper hasn't been a viable option either.
That was shared by a girl in my class named Cynthia. She seemed to be almost twice my height and more than twice my weight. The next year I changed schools and I don't think I ever saw her again. But she used to share lots of funny things (which often seemed to be sourced from MAD).
I'm in the market for a GS instance to move my presence there. Also for a Friendica instance that isn't Libranet.de (intolerably buggy, and since I've hosted ~F instances in the past, I know it wasn't anywhere near this bad in the past).
While I'm at it, I'd like to set up new secondary accounts on a couple of Misskey instances.
In all cases, I desire an easy ToS and less power-mad administrator ... but not so easy or hands-off that racists and a$$holes congregate there.
I'd run a (similarly small and closed-registration) Friendica instance, and used its built-in RSS functionality, but TT-RSS was just so much better for me.
At the time, it even had a mobile client.
I originally dropped it because the main developer stopped doing releases and recommended that people run it from git. To me, that was like being in perpetual beta, and I didn't want to do that.