The article frames the ejections as a direct attack by publishers protecting their reprint revenue stream, noting that in several cases the ejected scientists were the actual authors of the papers being distributed. It positions this as the logical endpoint of a publishing model where researchers do unpaid work, sign away copyright, and then get blocked from sharing their own results.
Draws an analogy to a developer being ejected from a JavaScript conference for handing out MIT-licensed code they wrote themselves. Argues this isn't a copyright skirmish but a direct hit on publisher reprint revenue — papers licensed back to pharma and CME providers for $50 to six figures per bulk order.
Several ejected scientists posted on Bluesky and Mastodon describing the encounter, with at least one explicitly calling for the ADA to clarify whether it invited the enforcement or merely allowed it to happen. Their position is that the conference organizer cannot remain silent while attendees are physically removed for sharing peer-reviewed science.
Submitted the Ars Technica story to Hacker News where it drew 165 points and 82 comments — a strong signal that the developer community sees the incident as emblematic of the wider dysfunction in scholarly publishing, where conglomerates like Elsevier, Springer Nature, and Wiley extract rent from work they didn't fund or produce.
At the American Diabetes Association's 2026 Scientific Sessions, security escorted multiple researchers off the conference floor for handing out reprints of peer-reviewed journal articles. According to Ars Technica's reporting, the papers in question were not leaked drafts, not pre-prints scraped from somewhere, and not anyone else's intellectual property. In several cases, they were reprints of papers the ejected scientists had personally authored.
The enforcement wasn't initiated by the ADA's program committee. It was driven by publishers — the same houses that license those reprints back to pharmaceutical companies and CME providers for anywhere from $50 to several hundred dollars per copy, with bulk orders running into six figures. Handing out a free PDF at a conference booth isn't a copyright skirmish; it's a direct hit on a revenue line item that publishers fight to protect.
The affected researchers were, predictably, not amused. Several have posted on Bluesky and Mastodon describing the encounter, and at least one has called for the ADA to publicly clarify whether the conference invited the enforcement or merely tolerated it. As of this writing, the ADA has not issued a substantive response.
For anyone who has worked in software for the last two decades, the absurdity here is hard to overstate. Imagine being ejected from a JavaScript conference for handing out USB sticks containing the source code to a library you wrote and published under MIT. That's the rough equivalent of what happened in Orlando. The author of the work, distributing the work, to people who would benefit from reading it, was treated as the threat.
The academic publishing model has been broken for decades, and the diagnosis is well-rehearsed: researchers do the work, peer-review the work, edit the journals — usually for free — and then sign away copyright to a handful of conglomerates (Elsevier, Springer Nature, Wiley) who charge their own institutions thousands per year for access. Reprint sales are a smaller but extraordinarily high-margin tributary of that river. When a Pfizer rep wants a thousand copies of a favorable diabetes trial to put in physicians' hands, they don't ask the authors. They buy them, at retail, from the publisher.
The dev world ran this exact experiment and chose the opposite outcome. When proprietary source code dominated in the 1980s, the GNU Project, BSD, and eventually Linux made the case that the substrate of software — like the substrate of science — works better when reading and redistribution are free. arXiv launched in 1991 and now hosts 2.4 million pre-prints. GitHub passed 100 million developers. The biomedical sciences have bioRxiv and medRxiv but no equivalent cultural norm: tenure committees still weigh impact factor, NIH still funds work that ends up paywalled, and a startup founder reading the latest GLP-1 trial still hits a $39.95 paywall.
What makes the Orlando ejections rhyme with software politics is the asymmetry of enforcement. The same publishers who can deploy security guards against authors at a conference have no realistic mechanism against Sci-Hub, which has mirrored most of their catalog for a decade and serves it from servers nobody can subpoena. Like DRM enforcement against legitimate buyers while pirates roam free, the only people who feel the friction are the ones playing by the rules.
For developers building in health-tech, devtools that touch academic data, or any product that ingests scientific literature, the takeaway is concrete: don't assume access. The licensing terms on a paper's PDF are not the licensing terms on the underlying research findings, and the publishers' definition of fair use is much narrower than the one you'd find in a software license. Products like Elicit, Consensus, and Semantic Scholar exist in a permanent gray zone precisely because the source material's licensing is hostile to derivative work. If you're shipping an LLM-backed tool that summarizes literature, run a license audit before you scale.
For anyone with an academic affiliation contributing to open source on the side, this is also a reminder of what makes the software side livable: the existence of permissive licenses (MIT, Apache 2.0, BSD) that explicitly grant the right to redistribute. The reason you can hand someone a USB stick with React on it is not goodwill from Meta. It's a license file in the repo root. Science has no equivalent default. Every paper is copyright-all-rights-reserved unless the author specifically published under Creative Commons or paid an article processing charge — often $3,000 to $5,000 — for the privilege.
The practical action item for engineers who care about this: when you publish a technical paper, push for Creative Commons. When you contribute to open-source projects that touch scientific computing — JAX, PyTorch, scikit-learn — remember that the same researchers who write the underlying papers often can't legally share them with the developers implementing their ideas. That gap matters.
The Orlando ejections are not a turning point — they're a data point in a fight that's been grinding for thirty years. But the timing is interesting: NIH's revised public access policy took full effect in 2025, requiring federally funded research to be freely available on publication with no embargo, and Plan S in Europe has been tightening its grip on subscription journals. The reprint business is a back door the publishers are trying to keep open while the front door is being legislated shut. Expect more friction, more performative enforcement, and more researchers concluding that the only durable answer is to bypass the legacy publishers entirely — the same conclusion the software industry reached when it stopped paying Borland for compilers and started shipping GCC.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.