• |

    Republicans Run Washington, but Democrats Get the Blame

    ByJustin Jest

    Right-wing TV’s grievance script wants the keys and the victim’s alibi: “DEMS ARE RIGGING IT,” “ACTBLUE IS THE THREAT,” and Republicans need more seats. Beside those claims, the meme’s labels put Republicans in control of the White House, the U.S. House, the Senate, and the Supreme Court. Those labels are the premise of the argument, not a ledger of who held what when. The contradiction is the point: power gets presented as both possession and persecution.

    Here’s the newsroom-raccoon audit: if you’re holding the keys, you can’t file a break-in report and insist the cure is another key ring. Voters deserve a distinction between accountability and grievance dressed up as a request for still more power. When blame is the product, every setback becomes an ad—and nobody has to explain what they did with the keys.

  • |

    Ticketmaster’s FTC Lawsuit Survives the First Court Test—But Fans Haven’t Won Yet

    ByAmanda Lynn

    A ticket purchase can feel like courtroom drama: you enter your details, wait for the page to load, and wonder what the next screen will reveal. In the federal case against Live Nation and Ticketmaster, the drama has advanced—but only to the next legal scene. On September 28, a judge denied the companies’ motion to dismiss a consumer-protection lawsuit brought by the Federal Trade Commission and seven states. The case can proceed. That is not the same as saying the FTC has proved its case.

    What the FTC and states allege

    The FTC and states allege that Live Nation and Ticketmaster misled consumers about ticket prices and purchase limits. They also allege that the companies facilitated the resale of tickets by brokers who had obtained more tickets than artists’ limits allowed. Those are allegations in the lawsuit, not findings of fact. The distinction matters: a court deciding that a case may continue has not decided that every claim in it is true.

    A motion to dismiss is an early court test, not the finale where the underlying dispute is resolved. Denying it means the lawsuit is not being thrown out at this stage; it does not turn the allegations into established facts. The court order expressly leaves the truth of the accusations undecided. The case now continues, with its claims still to be resolved.

    A court hurdle, not a fan refund

    The September 28 order denied the defendants’ request to dismiss the case at this stage. In practical terms, that means the dispute keeps moving through court rather than ending on that motion. The FTC’s case timeline lists the order and describes the case as pending; Bloomberg Law also reported on the ruling. Neither the order nor the ruling itself hands fans refunds, changes a ticketing screen, or settles how tickets will be sold.

    That gap is easy to miss because “lawsuit survives” sounds like a victory headline—and, legally, it is a meaningful step for the claims to proceed. But the ticket buyer’s immediate reality is more modest: this ruling did not decide whether the alleged conduct happened. There is no court-ordered fix for fans in this decision. The legal process has cleared one obstacle; it has not reached a conclusion about the underlying claims.

    The encore is still unwritten

    For fans, the useful takeaway is to separate legal momentum from practical relief. The lawsuit is moving forward, and its allegations put ticket pricing, purchase limits, and resale under scrutiny. But the case remains unresolved. This order does not tell ticket buyers that the allegations have been proved, and it does not announce a new consumer protection at checkout. A court hurdle is not the same thing as a change to the buying experience.

    Until the claims are decided or the parties otherwise resolve the dispute, the order remains a procedural step—not proof of misconduct and not a remedy for fans. The song matters; so does the invoice. For now, the invoice is still waiting outside the courtroom while the case gets through its opening act.

  • |

    Apple and Epic Are Still Fighting Over the App Store Fee Math

    ByLee Keybum

    An October 9 joint status report in the Apple-Epic dispute records a disagreement over Apple’s production of documents concerning proposed commissions on purchases made through external links. 9to5Mac reported on the filing October 12. The report captures the parties’ competing accounts; it is not a decision on the fees or a finding about which account of the document search is correct.

    Two accounts of the document search

    Epic says Apple’s document production is inadequate and asks the court to set a November 1 deadline for production. That is Epic’s request, not a deadline the court has ordered. Apple disputes Epic’s characterization. According to Apple’s account, it agreed to broaden its searches and expects to make a substantial production later. The filing does not establish either party’s description as the definitive account, and it does not provide a specific later completion date.

    The parties do agree on one procedural point: Epic’s 60-day response period has not yet begun. That does not mean the commission dispute has been resolved or that the court has accepted either side’s position on the documents. It means the report describes an ongoing process, with the timing of the response period still ahead. The filing is a progress update, not a ruling wearing a tiny judge’s robe.

    Why the paperwork reaches users

    Records about how a platform sets fees can help clarify the rules developers must navigate when they offer ways to buy outside an app store. Those rules may affect which options developers choose to offer and, in turn, which choices users see. That is a reason the underlying documents matter. It is not proof that developers will pass a particular fee on to customers, or that prices will change.

    The immediate question in this report is narrower than the larger fight over app distribution and payments: what documents Apple will produce about the proposed external-link commissions, and when. Developers have an interest in understanding the terms of doing business on a major platform. Users have an interest in knowing what purchase routes are available and what rules shape them. Neither point tells us what the documents will show; the filing itself does not answer that.

    For now, the useful takeaway is modest. Epic wants a November 1 production deadline. Apple disputes Epic’s account, says it agreed to broaden its searches, and expects substantial production later. The parties say Epic’s 60-day response clock has not started. The proposed commissions remain undecided in this update, as does the dispute over the paperwork. The corporate maze is still open, now with two sets of annotations and no final map.

  • |

    When a Hurricane Map Makes Things Up

    ByHolden McGroin

    A bad weather map and a real weather threat arrived in the same conversation: one part legitimate danger, one part visual confusion, and a group chat trying to decide whether the corkboard needs more string.

    The graphic was retracted

    AFP reported that Tampa-based Fox 13 meteorologist Paul Dellegatto briefly shared an inaccurate graphic described as AI-generated, then deleted it and acknowledged inaccuracies. That is the sequence the reporting supports: a weather communicator shared a faulty visual, removed it, and recognized that it was wrong. AFP’s account does not establish that the graphic caused specific harm or widespread panic, so there is no need to inflate the story into a disaster of its own.

    Even a short-lived map can complicate a fast-moving weather conversation. Maps borrow authority from tidy colors, sharp lines, and the general air of having passed a meeting. A viewer may not know whether an image is an official forecast, a repost, or an illustration that has wandered away from its facts. The graphic looked like it belonged in the briefing; that is exactly why accuracy matters.

    The threat was real—and geographically limited

    The faulty image should not be confused with the underlying hazard. The National Weather Service Storm Prediction Center’s outlook described a severe-weather setup with possible tornado risk associated with Isaias. The National Hurricane Center’s discussion also noted tornado potential and placed the greatest risk east of the storm’s center, particularly from the Florida Panhandle into southern Georgia. That was a specific forecast area, not a claim that all of Florida—or the entire storm track—faced equal risk.

    The distinction matters because misinformation can work in both directions. A misleading graphic can make a real threat harder to understand; finding a bad graphic can then tempt people to dismiss the threat itself. Neither reaction helps. The image’s accuracy and the official forecast’s assessment are separate questions. In this case, AFP reported inaccuracies in the graphic, while official forecast products described a real, geographically focused tornado risk.

    Check the forecast, not the vibes

    For anyone caught in the next weather group chat, the practical move is unglamorous: go directly to National Weather Service or National Hurricane Center forecast products and compare the location and hazard there. A polished visual is not a substitute for an official outlook, and an inaccurate visual is not proof that the weather danger was invented. Follow the thread, but check the knot.

    There is no need to pretend a correction instantly clears up confusion. The useful lesson is narrower: when an authoritative-looking image conflicts with official forecast information, verify the forecast itself before sharing the image or dismissing the risk. Weather already has enough plot twists without the panic boutique adding props.

  • |

    Freedom 250’s public bill—and the private donations still outside the ledger

    ByPhil McCracken

    Freedom 250’s newly released budget estimate puts key event costs at $128.5 million and anticipated federal funding at $114.2 million. The narrow question in the paperwork is how the private money reportedly raised for the effort is reflected. The estimate does not appear to show how those donations were allocated to the events. That is a transparency gap worth tracking—not evidence, by itself, that anyone mishandled funds.

    What the records show

    On October 8, the watchdog group Public Employees for Environmental Responsibility (PEER) released records it obtained through a public-records request. The budget estimate lists $128.5 million in projected costs and $114.2 million in anticipated federal funding. The record packet also includes a procurement-waiver request and a National Park Service cooperative agreement, pieces of the federal arrangement behind the events. They help explain the public side of the financing; they are not a final, all-in accounting.

    An estimate is a planning document, not a paid invoice. PEER has raised questions about the contracting and taxpayer-funding arrangements, but those questions should not be upgraded into findings the documents do not establish. A waiver request is not, on its own, proof of improper contracting. Bureaucratic paperwork can be alarming without becoming a verdict. The money trail deserves scrutiny; it also deserves accurate labels.

    The private-money question

    The Washington Sun reported that earlier disclosures showed more than $50 million in private funds had been raised for Freedom 250. The outlet said the released estimate did not appear to assign those donations to the events. From this estimate alone, readers cannot see how the reported private funds fit alongside anticipated federal funding and projected costs. It does not show that donations are missing, diverted, or unlawfully handled. A ledger with an unanswered column is an unanswered question—not a crime scene.

    The Washington Sun reported that the administration disputed or qualified treating the estimate as final, and that costs were still being reconciled. So the $128.5 million figure should not be presented as the final cost, and the current documents should not be mistaken for a complete accounting. Reconciliation is part of settling expenses; it is also why the final version matters. Until the accounts are brought together, the estimate does not show how the private and federal funding streams relate.

    What a final accounting should clarify

    A clear final accounting would show total costs, funding sources, and how private donations were allocated, while distinguishing commitments from money actually spent. That would let taxpayers and donors follow the basic trail: what came in, what went out, and which expenses each source covered. For now, the released records offer meaningful figures and a limited view of the arrangement. The right conclusion is neither “nothing to see” nor “case closed.” It is simpler: publish the reconciled accounting, then let the numbers do their job.

  • |

    The Reflecting Pool Case Is Over. The Paper Trail Is Not.

    ByHugh Jass

    David Hearn’s Reflecting Pool case was dismissed with prejudice on October 1. On October 6, his lawyers asked the Justice and Interior departments’ inspectors general to review how the investigation and prosecution were handled. The criminal case is closed; the paperwork has been invited to remain in the building.

    The Associated Press reported that prosecutors dropped the case after information indicated flawed contractor installation caused the damage, rather than Hearn. That reported explanation matters: it shifts attention from the person accused to the work done on the pool. It does not, by itself, establish that investigators acted improperly. A case can end after evidence changes without every unanswered question becoming proof of misconduct.

    What the lawyers want reviewed

    Hearn’s attorneys asked the two watchdog offices to examine the investigation and prosecution. Their request raises concerns about how the case was handled, but those concerns remain allegations, not findings. That distinction is less dramatic than a courtroom reveal, but it is the load-bearing beam in any account of what happened. A letter asking for scrutiny is not an inspector general report, and it does not show that either office has opened an investigation.

    The dismissal with prejudice is a procedural ending to Hearn’s case. It is not, on its own, an official explanation of every decision made along the way, nor does it resolve the lawyers’ allegations. Their request asks for scrutiny of how the case was handled; the reporting available on October 6 did not establish what either inspector general would do next.

    A request is not a verdict

    That boundary is where accountability starts, not where it ends. Inspectors general may review institutional conduct, but receiving a letter does not turn its claims into proven facts. The public deserves clarity about how government decisions are made, especially when a case ends after information points elsewhere. It also deserves careful language while the record is incomplete.

    For now, the reported sequence is stark enough: the case was dismissed, prosecutors had information pointing to faulty installation, and Hearn’s lawyers asked federal watchdogs to review the handling. The request puts questions on the administrative record. Whether the watchdogs take them up—and what any review might conclude—remains unresolved. The filing cabinet has cleared its throat. It has not yet delivered a verdict.

  • |

    The Public Helped Take AI’s Early Risk. It Deserves a Dividend.

    ByLee Keybum

    When public grants, labs, universities, or taxpayer-funded research help shoulder AI’s early risk, it’s odd to treat the upside as an investors-only boarding pass. I read the terms: innovation deserves a reward, but the public shouldn’t be the silent partner that helped build the runway and got left at the gate.

    An American dividend is a proposal, not an existing policy or settled funding plan. Still, if the public helped pay for takeoff, it deserves more than a thank-you and an in-flight safety card while private investors get the view from first class. Big Tech can call that innovation; ordinary people might ask who picked up the tab—and why they weren’t invited to share the return.

  • |

    Images Reported as AI-Generated Fueled Raye–Michael B. Jordan Dating Rumors

    ByHolden McGroin

    One outing, several different stories

    After a reported Six Flags outing involving Raye and Michael B. Jordan, online speculation supplied a romance plot. But a reported outing and a relationship claim are separate things. The corkboard can connect those dots; the highlighter labeled “maybe calm down” is there for a reason.

    In an ExtraTV interview published September 27, Raye addressed the dating speculation by describing herself and Jordan as friends who liked roller coasters. That is her public response. It does not confirm the relationship rumor, and the reported outing does not turn every story attached to it into a fact.

    Then came the visual evidence department, which appears to have been staffed by an algorithm wearing a trench coat. Vanity Fair reported on October 2 that images appearing to be AI-generated circulated online and portrayed the pair as a couple. One image purported to show them together at the VMAs. Vanity Fair reported that Jordan did not attend the event, making that image a useful reminder that a picture can look like documentation while depicting something that did not happen.

    When a picture gets mistaken for proof

    Images offer a shortcut to belief: we see a scene, and our brains start filling in the caption. But visual polish is not provenance. An image alone does not establish where it came from, whether it depicts a real event, or whether the people pictured endorse the story attached to it. Here, Vanity Fair described the images as appearing AI-generated. That is the publication’s account of their appearance, not independent confirmation of how each image was made.

    The rumor machinery works best when distinctions get flattened. “They were reportedly at an amusement park,” “Raye said they are friends,” and “an image purported to show them at an event Jordan did not attend, according to Vanity Fair” are separate statements. Turn them into one romance storyline and it becomes easier to share—and easier to mistake speculation for evidence. The people pictured get assigned a plot; the accounts and feeds circulating it may get another round of attention. Follow the thread, sure. Check the knot, too.

    The modest takeaway is to pause before treating a viral image as a receipt. Ask who reported it, what the people involved actually said, and whether the pictured event checks out. A reported outing can remain just that. It does not need a relationship attached, and an image that appears fabricated does not become true because it arrived in high definition.

  • |

    The White House Press Ban Is Still on a Temporary Court Clock

    ByHugh Jass

    The White House press-access dispute is still running on a temporary court clock. After an October 8 hearing, U.S. District Judge Timothy Kelly extended an order preserving access for CNN, MS NOW and POLITICO through October 13. Their request for a preliminary injunction remains pending. The immediate paperwork keeps the door open; it does not settle who gets to control the doorway while the lawsuit continues.

    The Associated Press reported that Kelly intended to rule on the request by Tuesday, possibly sooner. That is a reported intention, not a guaranteed court deadline or a ruling already delivered. JURIST likewise reported the temporary extension through October 13. For now, the case sits in that peculiar administrative waiting room where everyone has a calendar and nobody has the final answer.

    A bridge, not a verdict

    The distinction matters. The temporary order provides short-term protection while the judge considers whether to issue a preliminary injunction—longer-lasting relief that could govern access while the litigation proceeds. Neither the October 8 hearing nor the extension decides the underlying dispute. The court has not, through this interim step, made a final ruling on the parties’ claims. The filing cabinet has cleared its throat; it has not yet read its conclusions into the record.

    The earlier order, available through a court-document repository, restored the outlets’ press credentials. The current question is whether the court should preserve access under a preliminary injunction rather than only through a short-term order. The outlets have made arguments in their filings about the administration’s actions; those are claims by the parties, not findings by the judge. Keeping that distinction intact is less glamorous than declaring a winner, but it is how the public avoids confusing allegations with a court’s decision.

    Why the interim matters

    White House access rules affect which reporters can observe, ask questions and produce coverage of government activity. That makes the dispute bigger than the credential status of three newsrooms. When access is contested, the public interest includes knowing what rules are being applied, who is applying them and whether the process is being reviewed by a court. Temporary protections can preserve reporting access while that review happens; they cannot substitute for a final resolution.

    So the useful takeaway is modest, and modesty is often the document’s most reliable witness: CNN, MS NOW and POLITICO have temporary access protections through October 13, and their request for a preliminary injunction is still awaiting a decision. The judge’s reported timeline points toward Tuesday, but the court has not yet delivered that next step. Until it does, the case remains between the short-term order and the longer question of what access rules should govern during the lawsuit.

    Sources

  • |

    SSA’s Five-Day Workweek Plan Meets a Union Grievance

    ByMike Rotch

    At the counter, a calendar is not a service result

    You are holding your folder and trying to get help with Social Security. The agency announces a more uniform workweek. That may look tidy on a management chart, but it is not proof that the line will move faster, a call will be answered sooner, or a complicated question will be resolved. A five-day week is a schedule. Service is what happens to the person who needs help.

    SSA’s case for the change

    Federal News Network reports that the Social Security Administration plans to end alternative work schedules, including 4/10 and 5/4/9 arrangements, and move employees to standard five-day workweeks beginning November 16, 2026. SSA’s stated rationale is that staff should be available throughout the week to serve the public. That is a public-service goal. But stating the goal does not establish what customers will experience after the change.

    For someone seeking help, the useful question is not whether a schedule looks consistent from headquarters. It is whether the right help is available when it is needed. Those are not interchangeable measures, and a calendar cannot certify its own success.

    The union says the contract matters

    According to Federal News Network, the American Federation of Government Employees says the move repudiates contract provisions and has filed a national grievance. The 2019 SSA-AFGE collective bargaining agreement provides context for the dispute. It does not, by itself, settle the legal question, and this column cannot declare the change lawful or unlawful from the kitchen table.

    So there are competing positions: SSA says having staff available throughout the week serves the public; AFGE says the change conflicts with negotiated terms. A grievance is a challenge, not a final ruling. Neither side’s position establishes the eventual effect on people seeking help.

    Uniformity is not evidence

    The reporting does not establish what the change will do to wait times, access, staffing levels, or service quality. A more consistent calendar may sound like a fix, but sounding like a fix is not the same as delivering one. Changing schedules does not, on its own, tell us whether customers will get help sooner or whether their questions will be handled more effectively. Paperwork already has enough authority in people’s lives without pretending a new calendar is a customer-service result.

    Judge it by what people experience

    The November 16 start date gives the policy a clear marker, not a verdict on its effects. For the person waiting for an answer, the test is practical: is help available when it is needed, and does the service meet the need? The sources document an announced change, SSA’s rationale, and AFGE’s objection. They do not yet answer that customer-facing question. Washington can standardize a workweek in a memo. The public still needs to see what happens at the other end of the counter.

End of content

End of content