Trump Delivers Verdict On Pete Hegseth As Dems Demand His Resignation
Amid demands for Secretary of Defense Pete Hegseth’s resignation due to a leaked Signal chat containing information about a military strike in Yemen, President Donald Trump supported Hegseth on Wednesday.
After Hegseth sent administration officials information about the strike in a Signal chat that unintentionally included Jeffrey Goldberg, editor in chief of The Atlantic, who published the full messages on Wednesday morning, the president discussed the controversy.
In the aftermath of the controversy, when a number of Congressional Democrats called for Hegseth to resign, reporters asked Trump if he should think about doing so.
He has nothing to do with this; Hegseth is doing a fantastic job. Hegseth. How is Hegseth involved in this? Trump answered.
The president acknowledged to DailyMail.com that Mike Waltz, his national security advisor in the White House, accepted responsibility for Goldberg’s unintentional inclusion in the Signal chat.
“Mike Waltz” I suppose he claimed responsibility. Nobody else had anything to do with it. When questioned about the probe, Trump remarked, “I guess, I don’t know, I was told it was Mike.”
Trump once more downplayed the controversy surrounding Hegseth’s sharing of classified information that might have jeopardized the operation, focusing instead on the mission’s success.
“The attack was incredibly successful that night, so there was no harm done,” Trump claimed.
The president questioned whether the Signal app was functioning properly and why Democrats were demanding Hegseth’s resignation.
It’s all a witch hunt, you see. Trump stated, “You want to know if Signal works or not. To be honest with you, I don’t know if Signal works. I think that Signal could be defective.”
Although it is not regarded as a secure platform for classified information, the encrypted app that removes messages after they have been received is widely used for communications in Washington, DC.
“You, we, and everyone else use Signal, but we’ll need to determine whether it’s a functioning platform or not.” Trump stated.
Hegseth’s resignation was demanded by Democratic Senators Mark Kelly and Ruben Gallego of Arizona for disclosing information about the operation on the platform.
Kelly wrote on X that the Signal incident was the result of having the most unqualified Secretary of Defense in history.
“We’re fortunate that no service members lost their lives, but Secretary Hegseth must step down for the sake of our nation and our military,” he continued.
“This might have resulted in the deaths of our men and women!” Social media posts were made by Gallego.
He went on. “The Defense Secretary must step down.” It’s embarrassing how inept they are and how they covered it up.
In response, Hegseth blasted The Atlantic on Tuesday for misrepresenting his texts as “war plans” and insisted he did not divulge any classified material during the conversation.
The so-called “war plans,” which were made public by the Atlantic, include: No names. No targets. No places. No units. No paths. No references. No techniques. “No classified information, either,” he added. “Those war plans are really shit.”
On March 15, Hegseth texted a ‘Team Update’ to the Signal group of top Trump administration officials, giving them advance notice of the scheduled military strikes’ times and weaponry.
Hegseth texted, “This is when the first bombs will definitely drop,” revealing the timing of the operations, which involved the use of sea-based Tomahawk missiles and F-18s.
However, Hegseth maintained that he was merely giving a “team update” and that he had not disclosed any “war plans.”
My responsibility is to provide real-time updates to the team. “Everyone is kept informed with general updates in real time,” he said. What I did was that. That’s what I do.
Sen. Marco Rubio also addressed inquiries regarding the incident on Wednesday.
“Clearly, there was a mistake—a significant one—and a journalist was added,” Rubio stated. “I have nothing against reporters, but you shouldn’t be on that thing.”
Rubio referenced the Pentagon’s claim that the text thread contained no classified material.
“The operation and the lives of our servicemen were never in danger due to any of the information on there,” he stated.
"""My husband brought his mistress to our daughter’s wedding—and then asked me to give her my seat beside him.
"""My husband brought his mistress to our daughter’s wedding—and then asked me to give her my seat beside him. For a few seconds, I honestly thought I was looking at the wrong table, because my name card had vanished and Melissa’s was sitting exactly where mine had been on every seating chart. She wore a pale blue silk dress, lifted her champagne as if she belonged there, and avoided my eyes when I stopped beside the chair. David stood up, pointed to an empty seat at the next table, and quietly said, “For tonight, why don’t you sit over there?”
I had spent fourteen months helping our daughter, Emily, plan that wedding, from dress fittings and florist meetings to late-night calls over napkins and seating charts. That morning, while I fastened the pearl buttons on her gown, she made me promise I would enjoy the day and not let anything between her father and me touch it. I meant that promise, because whatever was left of my marriage, I would not make my daughter’s wedding the battlefield where it died. But David had apparently made a different plan, and he expected me to cooperate with it in silence.
When I asked what Melissa was doing there, David’s face showed guilt for only a second before he hid it behind irritation. He acted as though I were creating the problem simply by noticing that his mistress was seated at the family table in the place reserved for the bride’s mother. Then Melissa looked at me and said, “Honey, today really isn’t the day to make Emily uncomfortable.” I almost laughed, because the woman who had been sleeping with my husband for nearly a year was now warning me not to embarrass my own daughter.
I could feel people settling into nearby seats, laughing and talking, unaware that my marriage was being quietly rearranged in front of them. David kept his voice low and told me we should not “do this here,” as if the humiliation belonged to me because I refused to disappear politely. I looked at the empty chair he had chosen for me between a cousin and someone from the groom’s side, and I realized something colder than anger. This was not spontaneous; he had thought about where Melissa would sit, and he had assumed I would move.
For twenty-eight years, I had been the woman who adjusted, explained, forgave, and made excuses when David forgot anniversaries, missed dinners, or put work ahead of family. When he became distant, I learned to expect less instead of asking for more, and somewhere along the way he mistook that patience for permission. Even now, part of me considered taking the other chair, smiling for photographs, swallowing the humiliation, and telling myself it was all for Emily. I actually reached for the chair because protecting my daughter still mattered more to me than winning a public fight.
Then I heard one word behind me: “Mom?” Emily was walking toward us in her wedding dress, still glowing from the ceremony, and at first she looked confused rather than angry. Her eyes moved from me, to the empty chair, to Melissa, then back to the family table where she had personally placed me months ago. David quickly stepped in and announced that he had “rearranged a few things,” as if changing the bride’s seating chart without permission were no more serious than moving a centerpiece.
Emily asked why I was not sitting in my seat, and David casually pointed to the neighboring table and said I would be sitting “right there.” Her smile disappeared, and her eyes dropped to the place card in front of Melissa. I watched my daughter’s expression go completely still as she picked up that card and turned it over in her hand. In that instant, I understood the worst part: Emily had not approved this, and David had brought his mistress into our daughter’s wedding believing he could force everyone to accept what he wanted once it was already done.
What Emily did not know was that six months earlier, I had discovered David’s affair through a message that appeared on his phone while he was in the shower. Melissa had written, “I hate pretending I don’t miss you when she’s around,” followed by another message asking whether Friday was still theirs. When I confronted him, David spent eleven minutes calling me paranoid, insecure, dramatic, suspicious, and unfair before I repeated Melissa’s words exactly. The silence that followed ended our marriage long before either of us ever said the word divorce.
We had kept the details quiet because Emily was planning her wedding, and I refused to turn her happiest season into a crisis about us. David told me he was “confused,” that what he had with Melissa was “more complicated than an affair,” and that he needed time before making decisions. I agreed only that Emily’s wedding came first, so we slept in separate rooms, spoke carefully, and tried to appear functional while our marriage quietly collapsed. I believed David understood that one day required restraint, but he had apparently used that silence to prepare something else.
Three weeks before the wedding, he had casually asked whether Emily had finalized the family table and whether every seat had been assigned. At the time, I thought it was harmless conversation, but standing there with Melissa’s card in my daughter’s hand, I finally understood why he had asked. He had been checking whether there would be room, and when there was not, he simply removed me. Emily looked up at her father and asked, very quietly, “Where is Mom’s place card?”—and for the first time that night, David had no easy answer.
…FULL STORY IN THE COMMENT 👇👇👇"" "
