[–] [S] 2 points 1 week ago

The Phoenix Symphony is suspending its season because management says it has run out of operating cash—not because the musicians went on strike. The initial trigger, according to the board, was years of operating deficits combined with a failure to raise an expected $7 million in donations, creating a risk that it could not meet payroll. The dispute is over how management handled that crisis and whether shutting down was necessary. phoenixnewtimes

What happened first

The shutdown came during negotiations over the musicians’ contract, which expires Oct. 31:

  • Sept. 30: Management proposed deep salary cuts, according to musician representative Sarah Pasker.
  • Oct. 6: The musicians countered with concessions amounting to just under half the proposed cuts, Pasker said.
  • Oct. 15: The board voted unanimously to suspend the season.
  • Oct. 20: Musicians arrived expecting another bargaining session but instead learned the season would be suspended. The public announcement came that day. phoenixnewtimes

The announced plan is to stop performances after Nov. 1 and lay off all 66 full-time musicians effective Nov. 2. So, as of today, this is an announced indefinite suspension—not an established permanent dissolution of the orchestra. kjzz

What the original dispute was about

Initially, it was a financial and contract dispute: how much musicians’ compensation should be reduced in response to the symphony’s financial problems. It then became a dispute over transparency and the decision to shut down. Musicians say they knew finances were strained and had offered concessions, but were not told during negotiations that layoffs were being considered. They are demanding financial records and a plan to restore performances. phoenixnewtimes

That distinction matters: the available reporting does not establish that a musicians’ refusal to accept cuts caused the shutdown. Management cites a cash shortage; musicians challenge the process and want the books opened. phoenixnewtimes

The $6.5 million donation controversy came afterward

The large donation now in the news was a subsequent escalation, not the original cause.

A court approved a $6.5 million gift from Glenn and May Tansley’s trust on Oct. 14—one day before the board voted to suspend the season. After the public announcement, the trustee asked the court to reverse approval, alleging that the symphony had failed to disclose its financial condition and impending suspension. Those are allegations, not established findings. byucougarswire.usatoday

The symphony says the gift’s terms require a permanent memorial fund, so its principal could not simply be spent on payroll or operating deficits. It also says it has not received the money. Thus, the existence of that gift does not necessarily contradict the claim that it lacked usable operating cash. azfamily

  • source
  • [–] 1 point 1 week ago

    this site is confusing. i hit the little arrow by the file to download the .torrent file. it downloads the entire model from HF in 3 seconds and blows through a gigabyte of my phones data. wtf.
    luckily that outcome was not too horrible. and i actually got a good GGUF.

  • source
  • [–] 1 point 2 weeks ago* (last edited 1 week ago) (3 children)

    iroh-share is not decentralized filesharing.
    iroh seems like a stack. like https://libp2p.io/docs/
    eventually they may have a tool that does decentralized filesharing.
    and if i was going to dev my own solution from scratch, iroh would be my pick.
    but i'm lazy so i use ipfs(kubo) . it works
    update: i now see that iroh has https://github.com/n0-computer/iroh-share
    however it does not share partial pieces like bittorent and ipfs .
    in many cases, that might actually be more efficient (like an ordinary download).
    and from my understanding: it supports multiple providers as the source. ( so it is decentralized ).
    i think there are advantages and drawbacks.

  • source
  • [–] [S] 1 point 3 weeks ago

    https://www.phoenix.gov/newsroom/public-transit-news/service-changes-begin-oct--26.html

    Beginning Monday, Oct. 26, riders will see transit service changes across the Valley, including expanded weekday RAPID service, the launch of the PHXLink microtransit pilot in Phoenix and schedule adjustments to several Valley Metro routes.

    Phoenix Public Transit will launch PHXLink

    Additional routes with schedule adjustments include:

    1, 3, 10, 12, 13, 17, 19, 35, 43, 45, 61, 75, 80, 81, 83, 90, 96, 108, 122, 136, 138, 140, 154, 156, 184, 186, 514, 521, 522, 531, 533, 535, 542, 562, 563, 571 , 573, South Mountain West RAPID, SR 51 RAPID, and Valley Metro Rail B Line .

  • source
  • [–] [S] 1 point 1 month ago*

    "The National Weather Service’s 1991–2020 Phoenix climate thresholds show the progression clearly: the average last occurrence of 100°F is October 5, 99°F is October 8, 98°F is October 11, 97°F is October 13, 95°F is October 18, and 90°F is October 30. That makes about October 18 onward the point when the odds shift noticeably away from mid-90s-plus heat, although individual years can stay hot much later."
    i'm guessing that lower daytime temps(avg or peak) will translate into lower nightly lows. (unless we have already hit some kind of max for heat islan absence nightime cooling)

  • source
  • [–] 1 point 1 month ago

    summary from date-10/7

    ## Irkutsk laboratory death and public-health response
    
    A young female employee of the Irkutsk Anti-Plague Research Institute in Siberia died after being hospitalized with severe pneumonia, prompting concerns that she may have been exposed to a dangerous pathogen during laboratory work. Early reports said she had told colleagues that she accidentally broke a test tube containing live bacteria while collecting samples, although Russian authorities later said their inspections had found no confirmed laboratory accident involving pathogenic microorganisms.
    
    The death triggered an extensive precautionary response. Regional health authorities identified and medically monitored roughly 200 contacts, while some hospital units reportedly limited admissions. A nearby aluminum plant also instructed employees to wear masks amid uncertainty and conflicting reports. Artem Fominikh, director of the Irkutsk Aluminum Plant, urged calm and said that unverified information was circulating.
    
    The Irkutsk Anti-Plague Research Institute—formally the Irkutsk Antiplague Research Institute of Siberia and the Far East—was established in the 1930s to combat plague and later broadened its work to other high-consequence infectious diseases. It plays a public-health role in disease surveillance, laboratory diagnosis, prevention, and research across Siberia and Russia’s Far East, including regions where plague can occur naturally among wild animals and their fleas.
    
    At the center of the concern was the possibility of **pneumonic plague**, a severe lung infection caused by the bacterium *Yersinia pestis*. Russian officials did not initially confirm the cause of death, saying laboratory and tissue testing was still underway. The head of neighboring Buryatia, Alexei Tsydenov, said the worker may have died from plague, while also stressing that there was no recognized plague outbreak in his region.
    
    ## Official assessment and containment measures
    
    Russian health authorities, including Rospotrebnadzor, said they implemented a full set of preventive measures: identifying contacts, conducting medical observation, testing people who had been exposed, and monitoring the local epidemiological situation. Officials reported that no dangerous infectious pathogens had been detected among the contacts. Later updates indicated that monitoring had been completed for all identified contacts, with no confirmed secondary cases.
    
    According to the reported Russian findings:
    
    - Some contacts tested positive for common respiratory infections, including COVID-19 and rhinovirus
    - No evidence emerged that a dangerous pathogen had spread from the deceased worker to close contacts
    - Inspections reportedly found no confirmed incident involving pathogenic microorganisms at the institute
    - Testing of the deceased reportedly did not identify microorganisms associated with her professional work, though the full diagnostic picture was initially still being clarified
    - Authorities said the regional sanitary and epidemiological situation was stable and under control
    
    The World Health Organization said it was aware of reports of a laboratory worker in Irkutsk Oblast dying from severe pneumonia on October 2, 2026. WHO stated that the cause of death had not yet been officially confirmed and that testing was underway. It noted that all known contacts had been identified and monitored, with no symptoms reported among them at that stage. WHO’s initial risk assessment characterized the threat as moderate to low for the immediate Irkutsk area, low for Russia overall, and very low for the broader WHO European Region. 
    
    WHO also said it was communicating with Russian authorities under Articles 9 and 10 of the International Health Regulations (2005). That process involves verifying the event, reviewing laboratory findings, understanding why contact tracing was undertaken, and assessing whether the incident could have international public-health implications. 
    
    The European Centre for Disease Prevention and Control likewise reported no known secondary cases and no evidence of sustained person-to-person transmission, while emphasizing that its assessment rested on limited available information. 
    
    ## Why pneumonic plague caused concern
    
    Plague remains rare, but it is taken seriously because of its severity and because its pneumonic form can be transmitted through infectious respiratory droplets during close contact. It is also one of the pathogens long discussed in biodefense planning because it could, in principle, be deliberately aerosolized.
    
    There are three principal clinical forms of plague:
    
    | Form | Main route or feature | Key concern |
    |---|---|---|
    | Bubonic plague | Usually follows the bite of an infected flea | Fever and painful swollen lymph nodes, known as buboes |
    | Septicemic plague | Bloodstream infection | Can progress rapidly to shock and organ failure |
    | Pneumonic plague | Infection of the lungs | Can spread between people through close-range respiratory droplets |
    
    Pneumonic plague is the least common but most dangerous form. It can arise when someone inhales infectious *Y. pestis* particles, or when untreated bubonic or septicemic plague spreads to the lungs. A person with pneumonic plague may infect close contacts through droplets expelled while coughing. However, ordinary spread requires close and usually sustained exposure; the bacterium is not generally thought to behave like a highly airborne virus that remains broadly suspended throughout indoor spaces for long periods.
    
    That distinction matters. A single suspected case—especially one isolated in a medical setting—does not automatically signal a wider outbreak. Rapid identification, isolation, contact tracing, monitoring, and preventive antibiotics for eligible close contacts can sharply reduce the risk of onward transmission.
    
    ## Laboratory safety and transparency
    
    The case drew particular attention because it involved a worker at a laboratory studying high-risk pathogens. Laboratory-acquired infections are uncommon but possible wherever dangerous microbes are handled. They can result from accidents such as sharps injuries, broken containers, aerosol-generating procedures, failures in protective equipment, or breakdowns in routine biosafety practices.
    
    Experts quoted in reporting emphasized that a suspected occupational exposure to plague would normally lead to an immediate risk assessment and, where appropriate, prompt post-exposure antibiotic prophylaxis. The public does not yet have a complete account of the worker’s medical timeline, the material she may have handled, whether an exposure occurred, or what preventive treatment she received. Those questions are important, but they cannot be answered reliably until Russian authorities release final laboratory and investigative results.
    
    The episode also illustrates why transparency is central to public confidence. When officials rapidly communicate what is known, what is uncertain, what testing has been done, and whether transmission has occurred, they reduce rumors and help neighboring countries calibrate precautions appropriately. U.S. officials, including President Donald Trump and Secretary of State Marco Rubio, called for greater information-sharing, while Russian officials said control measures were in place and the situation was stable.
    
    Several neighboring countries increased preparedness measures. Uzbekistan said it had raised readiness for highly infectious diseases, and Kyrgyzstan announced enhanced quarantine controls at border crossings. Such measures reflect caution rather than proof that international spread occurred.
    
    ## Treatment and prevention
    
    Plague is treatable with antibiotics, but timing is critical. Untreated pneumonic and septicemic plague can be rapidly fatal, whereas early treatment can substantially improve outcomes. Management may include antibiotics, respiratory and circulatory support for severe illness, isolation of pneumonic cases, and preventive antibiotics for people with significant close exposure.
    
    Key public-health measures include:
    
    - Immediate clinical assessment of anyone with compatible symptoms and relevant exposure
    - Isolation and appropriate infection-control precautions for suspected pneumonic plague
    - Prompt laboratory testing through qualified public-health systems
    - Identification and monitoring of close contacts
    - Preventive antibiotics when public-health authorities determine exposure risk warrants them
    - Clear, evidence-based communication to prevent both complacency and panic
    
    For the public, the available information did not support a conclusion that a plague outbreak was occurring in Irkutsk or that there was sustained person-to-person spread. The reported absence of secondary cases, completion of contact monitoring, and lack of dangerous-pathogen findings among contacts were reassuring signs. At the same time, the death of a laboratory worker handling—or potentially handling—dangerous pathogens underscored the continuing importance of rigorous biosafety, biosecurity, transparent investigations, and rapid international notification when a potentially serious infectious event occurs.
    
  • source
  • [–] 1 point 1 month ago* (last edited 1 month ago)
    [–] 1 point 1 month ago

    title: "Sinema’s ex-lover had 'large' knife, threatened to 'take her down' before arrest at Cheesecake Factory: police" url: "https://www.fox10phoenix.com/news/sinemas-ex-lover-had-large-knife-threatened-take-her-down-before-arrest-cheesecake-factory-police" author: "Elias Weiss"


    Kyrsten Sinema's ex-bodyguard, beau re-arrested

    Kyrsten Sinema's ex-bodyguard Matthew Ammel was arrested again in Phoenix after violating pretrial release.

    The former bodyguard and ex-boyfriend of one-time Arizona Sen. Kyrsten Sinema was arrested again on Sept. 30 after authorities say he violated his pretrial release by dropping off a "large, military-style knife" at a gun store — and threatening to kill judges and police officers.

    What we know:

    Prosecutors with the Maricopa County Attorney's Office filed an emergency motion on Wednesday requesting a judge increase the bond for 39-year-old Matthew Ammel to $100,000 cash-only. The filing comes less than two weeks after Ammel's initial arrest for allegedly causing nearly $200,000 in damage to Sinema's Cave Creek home, when he was given supervised release.

    Now, state attorneys are warning that the U.S. Army veteran poses an escalating danger to the public and to Sinema after threatening to "take her down."

    Matthew Ammel appears in court, center, following his re-arrest for violating pretrial release conditions in a felony domestic violence case involving former Arizona Sen. Kyrsten Sinema, right.

    According to court records, Pretrial Services was alerted by North Carolina authorities on Tuesday that Ammel was actively trying to acquire guns and tactical gear while making threats against a judge. Later that afternoon, Ammel's court-ordered GPS tracker placed him at a firearm retailer in north Phoenix, where a sheriff's detective learned Ammel had left a large "hunting-style" knife to be engraved.

    State prosecutors said in court documents that police have serious safety concerns due to Ammel's "erratic" behavior, "highly skilled" military training and efforts to have "military friends" help him assemble a rifle. Court filings say Ammel prepared for violence by discussing funeral arrangements and making threats against the lives of sitting judges, lawyers and police personnel.

    The arrest:

    Detectives with the Arizona State Gang Task Force helped lure Ammel out of his hotel room on 24th Street and Camelback Road and asked him to walk across the street to The Cheesecake Factory parking lot, where he was taken into custody on Sept. 29 at 9:45 p.m.

    Ex-bodyguard accused of trashing former Arizona Senator's home

    The former bodyguard to ex-Arizona Senator Kyrsten Sinema is facing a felony charge after deputies say he caused over $200,000 in damage at her Cave Creek home. FOX 10's Jacob Luthi reports.

    Dig deeper:

    Prosecutors now say Ammel also broke a court protective order shortly after his initial release by getting an acquaintance to reach out to Sinema on his behalf. On top of his Arizona charges, Ammel was already serving unsupervised probation for a prior felony case in North Carolina.

    The backstory:

    The original criminal charge stems from an Aug. 30 incident where deputies say Ammel entered Sinema’s home while she was away, demanding she post a video to X. When Sinema refused, Ammel allegedly destroyed 22 paintings valued at over $123,000 by throwing them into her backyard pool and shattered expensive alcohol bottles and mirrors throughout the house.

    Ammel was initially taken into custody on Sept. 17 after he was discharged from a mental health facility; he was charged with felony aggravated criminal damage domestic violence. The criminal cases follow Sinema’s court filing acknowledging an affair with Ammel in response to an "alienation of affection" lawsuit brought against her in North Carolina by Ammel's wife.

    What's next:

    A judge set a $25,000 bond following the knife incident. Ammel will be arraigned on Oct. 7, with a pretrial conference scheduled for Jan. 20, 2027.

    Map of where a state task force nabbed Sinema's ex a second time:

    The Source: Information in this report was gathered from Maricopa County Superior Court records, the Arizona Department of Public Safety, and North Carolina civil and criminal court records.

  • source
  • view more: next ›