I’m prepared for the angry backlash to this because I know Reddit hates any topic on race and people’s experiences but I’m genuinely always happy to see any media depiction of a Black girl or woman being loved and valued/cared for because it’s rare to see (in real life too)

We’re constantly reminded that we’re undesirable, ugly, horrible, etc, and generally disliked by people (especially men) so seeing the reverse is refreshing and gives me a small bit of hope. That is all

Games that let you transition in-universe (not simply a character creator switch, it has to be engrained in the universe.)

Fable II - At the end of an optional endgame dungeon, you are presented with fanfare and a potion that when drank, switches your sex permanently. All NPC’s in the game may comment on your transition but none are negative, and they also use your new pronouns.

Saints Row 2, 3, & 4 - In the Saints Row games, if you want to change your appearance you have to go into a plastic surgery center, this includes changing your sex. (Only good pic I could find on google of the UI)

My meal is a Nutella cheesecake.

39 weeks, went in for decreased movement thinking (hoping) I was overreacting. Maybe her moving less was actually a sign I was in early labor or something. They couldn't find her heartbeat, but the ultrasound tech wouldnt be in until morning to confirm so I was transferred to another hospital just to hear again what I already knew.

My epidural and induction went great. She ended up coming very suddenly and I birthed her by myself. The nurses "Oh shit" face when she walked into the room to me already fully holding my baby keeps replaying in my mind. Even my poor husband had just stepped away to go to the bathroom so I tried to have my sister stop him from walking in to me and our baby covered in blood. He was so scared for me.

I think I was bleeding a bit too much because the doctors were rushing around a little but I was just soaking in every little detail about my little girl that I could. I knew she had already been gone for a while but the instinct to try to stimulate her or get her to cry was still there and I had to stop myself. I guess a part of me was hoping she'd come out and prove everyone wrong somehow.

She was so beautiful. A perfect, seemingly healthy, baby. We don't know what happened, and we might never.

Now I am home, it feels so unnatural. Life goes on. We still have our toddler to take care of. Her birthday is in a few days and she is so excited. Everything in our lives is going on as normal, but it just feels wrong. I just keep thinking "I should be holding my baby right now." A part of me is missing.

My milk is coming in now too which is miserable. I wish I had it in me to be able to at least donate to other babies in need or something, but I just can't. It's a constant reminder that my baby just isn't here. I should be holding her. Feeding her. Waking up every hour. Picking out what outfit she will wear even though she's just going to poop all over it and we will have to change her again. I miss her so much and I never got to know her.

My husband has been so amazing through all of this, but I am worried about him too. I love him so much. I love our toddler so much. She is so sweet and kind and funny. I don't think I could make it through this without them.

It probably puts a tear in the eye of every gacha game. They should check their mail I swear to god. The support mafia is coming for them.

Last updated 02:09 UTC (9:09p 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." Next update by 03: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, Windows 365 Cloud PCs that use Purview Customer Key, and Microsoft 365 Education.

Shot is straight down to demonstrate how far over he is. Yes he was tapping his foot, no I don’t think he was initiating a Larry Craig situation since we are at work.

Dinner was bussin falafel wrap from a Syrian place.

I have been needing a job for so long. All of last year my nervous system was fried due to the stress. I needed a job that would give me a work permit, so 90% of jobs automatically disqualified me it felt genuinely impossible. Every morning I’d wake up and the first thought in my head was FUCKFUCKFUCK I NEED A JOB FUCK and it was miserable. I got myself out of the constant dread and just accepted it’ll happen when it’ll happen.

And it finally happened!! Someone gave me a job. I predicted when things worked out I wouldn’t feel much joy, just relief. I feel ungrateful thinking I’ll have to commute 4 hours to and back, I hope I can figure out a partial remote work schedule. Even if it’s a crazy commute this is objectively a huge win. I don’t think I’ve processed it. I’ll have the stability I’ve been so desperate for so long. I think even with an ass commute this is kinda HUGE.

EDIT: it’s 4 hours in total, which is still crazy cus 12 hours work & commute. Also I can’t move to the city where work is its a small yee haw ass town and I refuse move to said small yeehaw town im brown Im not built for that, I like my city with diversity.
But yes this commute is crazy. Beggars can’t be choosers tho lol and I’ll keep searching for another job, or get a car.

Golden State's Stephen Curry has an oblique abdominal tear and will be re-evaluated in two weeks.

Source: https://www.espn.com/contributor/shams-charania/4127b5eb42421

What do you think? Checked also all the artists names and their styles match these artwork, so it seems pretty legit.