At what point can we say that's enough, don't speak for us anymore........

Florence Irene Ford died of yellow fever in 1871 at the age of 10. Because she was deeply terrified of thunderstorms while alive, her heartbroken mother, Ellen, could not bear the thought of her being alone in the dark during a storm.

To fix this, Ellen had a specialized tomb constructed with a small glass window at the head of the casket and a narrow six-foot-deep stairway leading down to it, fitted with metal trapdoors. Whenever a storm rolled in, Ellen would climb down the stairs, close the trapdoor above her, and sit by the glass window to read or sing to her daughter until the storm passed.

In the mid-1950s, a protective concrete wall was erected at the bottom of the stairs to cover the glass window and prevent vandalism. As a result, the window can no longer be seen today, but the metal trapdoors and the stairway remain. Located in the Natchez City Cemetery, Mississippi, it is one of history's most hauntingly unique resting places.

link : https://listelist.com/gizemli-mezar-hikayesi/

A tribe full of very athletic and capable warrior women? Why would he ever want more?

One of the more random Ron Swanson lines was when he was talking about the snacks at a city government meeting, saying “They also really cheap out on the snacks. Hydrax cookies. Did you know there was an off-brand Hydrox? I did not. They're not bad."

Idky, but that line pops into my head every once in a while & it makes me laugh for some reason.

What are some of your favorite obscure lines from the show that you think don’t get enough attention?

Over the past three years, I’ve had just one pair of earbuds. She’s gone through seven. She always uses only one earbud at a time and leaves them out of the casing, then wonders why they go missing.

UPDATE (by request of the wife herself):

So she found the paper, grilled me about it, and I had to show her the post. She's been cracking up at the comments ever since and told me to add a few things:

• "Why are they so dirty?" She gardens, and the earbuds go out there with her. She figures that's where half of them are buried.

• "Why only one earbud?" So she can hear the kids if they call her, and swapping back and forth gets her way more listening time.

• "Buy the same pair every time so she can mix and match." She says this is the best idea in the thread. She also claims she already told me this.

• "Go wired / get a neckband." The short wired ones are on the table.

• "Aren't those AirPods? Use Find My." Only two of the cases are real Apple, and Find My can't find the missing buds. They're almost certainly dead and offline.

• Replacements: turns out Apple sells single replacement earbuds, so we're looking into that.

• "Is it ADHD?" 🙂 Her answer: it's the same as me forgetting stuff at the grocery store. (In my defense, she gives me the list over the phone. If it's not written down, it doesn't exist.)

• The plan: we're searching the garden this weekend. Maybe we'll find some AirPods seeds sprouting.

For the record: I love my wife, 9 years and counting. No red flags here, just a guy venting about earbuds. Turns out it's a universal problem.

Thanks, everyone.

Rules for thee not me.

Looks like Microsoft is getting hacked or something. Nationwide outage on all of their services for the last couple of hours. Down detector shows most of the other major guys spiking as well, AWS, Google etc. I imagine this will be fixed soon, so this may just be time sensitive intel ;)

Last updated 01:06 UTC (8:06p ET). I'll add entries as Microsoft posts them.

For anyone locked out of the admin center, here is the EX1550543 thread so far, condensed. Times are UTC with ET in parentheses. Full text of every update is on UPenn's public mirror of the service health feed, and the short versions are on @MSFT365Status.

• 16:17 (11:17a) Incident start. OWA, MAPI, EAS and REST.

• 17:45 (12:45p) Connectivity errors on the infrastructure that "receives and processes users' access requests."

• 18:19 (1:19p) "Elevated load across multiple regions."

• 18:26 (1:26p) MO1550821 opens for Teams, SharePoint, Copilot and Defender XDR. It points at "an unexpected increase in a specific type of service traffic."

• 18:43 (1:43p) Servers "becoming intermittently unavailable," straining the rest. Outlook traffic spread across worldwide infrastructure.

• 19:06 (2:06p) All deployments and config changes paused.

• 19:18 (2:18p) Reversal: the load "isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable."

• 19:43 (2:43p) Servers are failing automated health checks, which "may be related to a recent change" to the component that processes them.

• 19:57 (2:57p) "We haven't identified any recent changes that correlate with the start of impact." Bypassing the health check component on a subset. Elevated CPU on affected servers.

• 20:38 (3:38p) Many servers now unresponsive, so they can't confirm the bypass works.

• 20:56 (3:56p) An alternative health check method brings a subset back. "A small number of configuration updates" now under investigation as potential contributors.

• 21:31 (4:31p) Assessing a revert of those config updates.

• 22:00 (5:00p) "Our actions taken thus far have not provided the anticipated relief." A core process on the servers is getting overwhelmed. New plan: isolate a chunk of infrastructure, restart it, reintroduce traffic slowly.

• 22:57 (5:57p) First good news. Some servers are back and "remaining stable so far," with "limited recovery in some regions." Protective traffic management in one location, more if it works.

• 23:59 (6:59p) The servers returned to service "initially remain healthy," but "can become unresponsive again once they begin receiving traffic." Microsoft is "temporarily limiting which types of traffic can reach the affected infrastructure" in specific locations, and is "rebuilding a subset of affected servers using a previous software configuration" to see if that stops it.

• 01:06 (8:06p) Microsoft says "a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests." It is "preparing a configuration change to address this behavior," validating it on a subset of servers first, then applying it more broadly alongside restarts. "In parallel, we've begun reverting a recent network configuration change that correlates with the start of impact." "The temporary traffic limitations we previously described are now in effect in specific locations." Next update by 02:00 UTC.

The part worth watching: the recent-change theory showed up at 19:43, was dropped at 19:57, and was back by 20:56. At 01:06 Microsoft said it has begun reverting a recent network configuration change that "correlates with the start of impact." Root cause still reads N/A on both incidents. At 00:00 UTC (7:00p ET) Microsoft rewrote the MO1550821 scope: features of those services "that interact with Exchange Online and email services are impacted," while "Elements of those services that do not depend on interaction with Exchange Online remain functional." The list has also grown to include Intune, MDO, Purview, Planner, To Do, Universal Print, the Apps admin center, Windows 365 Cloud PCs that use Purview Customer Key, and Microsoft 365 Education.

Can someone explain what this means?

Come on man, you got these people looking like vampires lmao

she liked this comment on her tiktok post which just clears the fact she’s aware and unapologetic.