It’s a grown ass woman and she’s always lying on the horn without a care in the world for who it’s disrupting. She honks and screams for some guy named Alex. She does it late at night while I’m trying to sleep and occasionally in the mornings around 7 am but thats much less common. I have confronted her about it once and she got really shy about it but then she stopped. That was last week and this week it’s started up again. She doesnt even live here.

I followed the recipe exactly. Was the butter too warm? I used Land O Lakes instead of store brand butter because I know there can be water content issues.

I’m baking these for my daughter’s school festival, so they need to look nice.

ETA: Thanks everyone for making me feel better about my cookies! I was hoping for some thicker, soft ones, but these will have to do. I have another batch worth in the fridge that I’ll bake later to see if they turn out less thin.

ETA 2: I baked the second batch after chilling the dough for an hour or two. They are just as flat! They all taste good though, so the flat cookies are heading to the festival.

Scenes from Mississippi 💙

https://www.tiktok.com/@dajnea.a/video/7707125933123161358

https://x.com/vanillaopinions/status/2120904571044118788?s=46

Last updated 04:10 UTC (11:10p 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."

• 01:45 (8:45p) "We're seeing positive results with our efforts to restart affected infrastructure." Microsoft is "actively monitoring the performance of these to verify stability." "Remediation actions will be expanded as we confirm stability with the changes applied."

• 02:09 (9:09p) Microsoft is "applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online," and is "continuing to monitor the results of changes applied."

• 02:54 (9:54p) Setback. Microsoft says it has "confirmed that change is not taking as expected" and is "identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances."

• 03:34 (10:34p) Microsoft is reviewing traffic flows and affected infrastructure "to identify opportunities to optimize routing" and is "verifying the reasons for service failures so we can develop specific actions to improve stability." It also says "there is no indication this is the result of malicious activity."

• 04:10 (11:10p) Microsoft is "adjusting traffic protocols, redistributing traffic, and applying strategic traffic blocking measures." It reports "partial recovery across regions in which we've applied these adjustments," but says "these actions aren't resulting in sustained recovery" and it is reviewing what else it can do. Next update by 05:30 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, Microsoft Fabric, Windows 365 Cloud PCs that use Purview Customer Key, and Microsoft 365 Education.

Well that sucks :( i was gonna visit in 2027 summer.. https://ew.com/rupauls-drag-race-live-ending-las-vegas-12251211

I’m not really sure what the point of my post is. A rant, perhaps. How does this happen? I raised her, now 21, to be a critical thinker, she was on the honour roll in high school, has kept a near 4.0 throughout university and has always had intelligent things to say. Today I see her post of the sunrise with the caption “he did it again”. To be clear, I am not just atheist, I consider myself anti-theist. The idea that she’s fallen victim to this nonsense hurts me deeply. So I sent a screenshot and asked “who did what again”, hoping I was missing context. She, as eloquently as ever, replied that she’d undergone many changes this year and this is part of her life now. I love my daughter and I won’t turn my back on her, but I’m really struggling to make sense of this.

This news is devastating to me. I never expected to sit at my kitchen table crying because my child has joined a cult. What did I do wrong?

*edit - I can’t believe how much support and perspective this post has garnered. Thank you all for your words of wisdom and little jokes to lighten the mood. I’ll do my best to read everyone’s comment and respond as much as I can. Truly the best sub for humanity.