An anonymous reader quotes a report from Ars Technica: President Trump yesterday demanded that the Federal Communications Commission punish or rebuke an NBC journalist for saying he has "mixed results" in his election endorsements. In the latest example of how Trump is using the FCC to harass reporters and news organizations that he dislikes, he said Meet the Press host Kristen Welker "will be reported to the FCC for rebuke or punishment" for what he claimed was a "purposeful inaccuracy." "Kristen Welker, the Unpopular 'Hostess' of the once great Meet the Press, now considered Meet the Fake Press, just stated that Donald Trump has 'mixed results' on his Endorsements of Candidates, when the recent WINS of Darline Graham and Mike Mazzei, stand at 100% for the U.S. Senate, and 98% for the U.S. House, recently and over the longterm. How can anyone be allowed to say this, working for freely given Public Airwaves? Results are attached. Because of this purposeful inaccuracy, she will be reported to the FCC for rebuke or punishment," Trump wrote in a Truth Social post. A separate post from Trump yesterday said, "THE FAKE POLLS USED BY OUR CROOKED MEDIA ARE OUT OF CONTROL, AND SOMETHING MUST BE DONE ABOUT IT. FCC TO THE RESCUE! President DJT." Trump also posted a rant on Friday about New York Times journalist Maggie Haberman, calling her "an unattractive person both inside and out" who "should be forced to turn over any and all money that she's made through her fake reporting on me." Trump referred to Haberman throughout his post as "Maggot Haberman." Trump's post about Welker included an image purporting to show he has near-perfect results in his endorsements this year. "The Press is a Disgrace to our Nation, and I hope that Chairman Brendan Carr, and the fine people of his Commission, will take this Threat to our Country very seriously," Trump wrote. Perhaps indicating that he will refer additional journalists for FCC punishment, Trump wrote that Welker "is not the only one. The Radical Left News is going out of their way to harass, demean, and libel anything 'TRUMP.'" The FCC website says the commission "cannot prevent the broadcast of any particular point of view," and that it "generally will not intervene" in complaints about "one-sided news reports" because "it would be inconsistent with the First Amendment to replace the journalistic judgment of licensees with our own." As noted by Ars, FCC Chairman Brendan Carr has "made it clear he takes orders from Trump, abandoning his previous position -- which he held under Democratic presidents -- that the FCC must operate independently of White House interference." Carr could use the commission's regulatory authority over licensed broadcasters to open an investigation into Welker, potentially creating pressure on NBC and its affiliated stations through licensing proceedings or other FCC actions. The most likely vehicle would be the FCC's rarely enforced news distortion policy, which Carr has repeatedly revived to target coverage he considers misleading; historically, however, the policy required an unusually high evidentiary bar and was seldom enforced.

Read more of this story at Slashdot.

California's age-verification bill has passed in its legislature — but with its open-source carve-out intact, reports the blog Linuxiac: Back in May, we reported that California lawmakers amended Assembly Bill 1856 to carve open-source operating systems out of the state's upcoming age verification requirements. Three months later, that exemption survived the legislative process intact, and the bill has cleared both chambers of the California Legislature... sending the measure to Engrossing and Enrolling, the final legislative preparation stage before it can be presented to Governor Gavin Newsom... For operating systems that are covered, AB 1856 builds on California's Digital Age Assurance Act, which is scheduled to take effect on January 1, 2027. Under the current text, when an operating system runs on a device and includes an account setup feature, its provider must offer an interface that asks the account holder for the birth date, age, or both, of the device's primary user during account setup. The operating system must then be capable of providing a digital age signal to covered application stores and application developers through a reasonably consistent real-time API. Instead of exposing a precise birth date, the signal identifies one of four age ranges: under 13, 13 through 15, 16 through 17, or 18 and older... Covered application stores must request the signal from the operating system and make it available to developers.

Read more of this story at Slashdot.