As reported by several outlets , the Trump administration dismissed members of the National Science Board (NSB), which is tasked with establishing policies for the National Science Foundation. It's not clear how many members have been dismissed. According to screenshots shared with The Washington Post, board members received a message that their position was "terminated, effective immediately. The NSB establishes policies for the National Science Foundation (NSF), the independent US agency responsible for apportioning about 25 percent of federal support towards research conducted by the country's colleges and universities. The foundation has existed for over 75 years and has contributed to the development of MRIs and cellphones, among other breakthroughs. Up to 25 active members can head the NSB, however, the current board only has 22 members; the NSF's former director, Sethuraman Panchanathan, abruptly resigned last year . In response, Congresswoman Zoe Lofgren called the latest decision a "real bozo the clown move" in a statement. "This is the latest stupid move made by a president who continues to harm science and American innovation," Lofgren, who also serves as the Ranking Member of the House's Science, Space and Technology Committee, added in the statement. "It unfortunately is no surprise a president who has attacked NSF from day one would seek to destroy the board that helps guide the Foundation." It's unclear if the NSB's next scheduled board meeting for May 5 will take place. When asked about the recent terminations and the next meeting, the NSB referred to the White House for additional details. We've reached out to the Trump administration for confirmation and will update the story when we hear back. This article originally appeared on Engadget at https://www.engadget.com/science/trump-has-terminated-several-members-of-the-independent-national-science-board-170405205.html?src=rss
Within hours of an armed gunman's attempt to enter the White House Correspondents Dinner, attended by top administration officials and hundreds of journalists, President Donald Trump did what he does best: use the assassination attempt to defend his ballroom project. During a White House press conference just hours after he and several cabinet members were […]
Two months following the deadly shooting in Tumbler Ridge, British Columbia, OpenAI's Sam Altman has formally apologized for not informing police of the alarming ChatGPT conversations seen with the suspect's account. Before the incident, OpenAI banned the account belonging to the alleged shooter, Jesse Van Rootselaar, for violating its usage policy due to potential for real-world violence. "I am deeply sorry that we did not alert law enforcement to the account that was banned in June," Altman wrote in the letter. "While I know words can never be enough, I believe an apology is necessary to recognize the harm and irreversible loss your community has suffered." Altman noted in the letter, which was published in full by Tumbler RidgeLines , that he spoke with both Darryl Krakowa, Tumbler Ridge's mayor, and David Eby, the British Columbia premier, and agreed that a "public apology was necessary, but that time was also needed to respect the community as you grieved." Eby, who also highlighted Altman's letter in his post on X , agreed that the "apology is necessary," but added that it was "grossly insufficient for the devastation done to the families of Tumbler Ridge." Moving ahead, Altman reaffirmed in the letter that OpenAI would "find ways to prevent tragedies like this in the future" and work with all levels of government to prevent something like this from happening again. Altman's latest commitment builds on the previous letter from OpenAI's vice president of global policy Ann O’Leary, who said the company would notify authorities if it finds "imminent and credible" threats in ChatGPT conversations. This article originally appeared on Engadget at https://www.engadget.com/ai/openais-sam-altman-apologizes-for-not-reporting-chatgpt-account-of-tumbler-ridge-suspect-to-police-221400813.html?src=rss
