What I learned:

A Lancet audit put a number on the problem and it is climbing fast - The moment everyone is citing is Maxim Topaz's Columbia Nursing audit of 2.5 million biomedical papers, published in The Lancet on May 7. It found 4,046 fabricated citations across 2,810 papers, with the rate up more than twelvefold since 2023 - from roughly 1 in 2,828 papers to about 1 in 277 in early 2026, per Retraction Watch. What lands hardest with researchers is Topaz's framing that this is not an academic-hygiene problem but a patient-safety one: "A medical professional or clinical guideline developer has no way of knowing that the evidence they are relying on does not exist," per Columbia Nursing. The detail that 98.4% of affected papers had received no publisher action is the part academics keep flagging as the real scandal.

NeurIPS became the symbol of peer review failing at the top end - Researchers keep returning to the finding that ~53 papers accepted at NeurIPS 2025 (about 1%) carried hallucinated citations that survived 3-5 expert reviewers each, with GPTZero confirming 100 fabricated references, per The Register. The takeaway in the community is brutal: if it sailed through the most prestigious AI conference's review pipeline, ordinary journals have no chance. The "submission tsunami" / "AI slop" language from that coverage has become the shorthand scientists use for why reviewers can no longer catch this by hand.

arXiv's one-year ban is the flashpoint - and academics revolted - The single most-discussed journal-side response is arXiv's May 14 "one-strike" rule banning authors for up to a year if hallucinated citations or leftover chatbot prompt artifacts are found, per @iam_elias1, whose thread ("Then academics lost their minds") pulled 182 likes. Coverage in Nature and TechCrunch confirms the policy, and the backlash got the Futurism "academics in meltdown" treatment - a vocal minority arguing they should be free to use AI to write papers while staying immune from the hallucinations it injects. Integrity experts split the difference, calling the ban "welcome but unenforceable," per Inside Higher Ed.

Publishers are fighting AI with AI, but drawing a hard line on reviewers - On the response side, the concrete move is detection tooling: Springer Nature rolled out the first AI tool to flag suspicious or copied peer reviews (after Geppetto and Snappshot), now tested across 100+ open-access journals and 100,000+ submissions, per Nature. Policy is bifurcating - Wiley and Springer Nature permit conditional reviewer AI use with disclosure, while Elsevier and Cell Press tilt toward prohibition. The near-universal rule now: reviewers must not upload manuscripts into public generative-AI tools while publishers build "safe" in-house ones.

Practitioners on the ground are exhausted and skeptical - The human texture comes from working academics. A 482-upvote, 224-comment thread on r/Professors ("Why is AI being shoved down our throats?") captures the burnout, and the Fortune story circulating among researchers - about Columbia's Maxim Topaz discovering AI hallucinations in his own polished manuscripts - was shared with the warning that this is now "entering the permanent record," per @OwenGregorian. Even practical advice threads reflect the new caution: @AKlN05_ telling people that "real research beats AI scraping" and to trust peer-reviewed journals and university presses as the gold standard.

KEY PATTERNS from the research: 1. The crisis now has hard numbers and a patient-safety angle, not just anecdotes - 1-in-277 biomedical papers and a 12x rise since 2023 - per The Lancet 2. Peer review failing at NeurIPS (100 fabricated citations past 3-5 reviewers each) is the proof-point researchers cite that human review can't catch this anymore - per The Register 3. arXiv's one-year ban is the boldest enforcement move and the most contested - widely seen as "welcome but unenforceable" - per @iam_elias1 4. Publisher strategy is AI-detection-tooling plus a reviewer-side ban on uploading manuscripts to public LLMs - per Nature 5. The deepest fault line is accountability: should authors be liable for hallucinations their AI tools inserted? - per Futurism

What I learned:

OpenCV 5 dropped at CVPR and the framing is "classic CV and AI under one roof," not "AI won" - The first major release since 2018 landed June 6 and trended on Hacker News around June 9, per Phoronix, which called it "a huge release and a major step forward." The headline numbers everyone is repeating: a rewritten DNN engine, ONNX coverage jumping from ~22% to over 80%, and built-in LLM/VLM support, per @lcheylus on X. But the developer takeaway from CNX Software is that the classic detectors stay alongside the neural ones - the era of "OpenCV for classic vision plus something else for AI" is what's ending, not classical CV itself.

The migration is brutal in C++ and a non-event in Python - The release removes the legacy C API entirely, drops Python 2, and requires C++17, per Phoronix. Migration writeups frame it bluntly: some projects get faster and gain modern AI features for free, others won't compile until they're updated. For Python users though, cv2.imread() and cv2.dnn.readNet() still work, and pip install opencv-python>=5.0.0 plus re-running tests is about 90% of the job. The line getting passed around: "Running a VLM from OpenCV directly is not something I expected to see in 2026, but here we are."

Where classical still wins: edge, interpretability, and anything geometric - The recurring answer across the research is that manually designed detectors can match or outperform deep learning on face, vehicle, and traffic-sign detection in both precision and compute cost, per AllPCB. SLAM, structure-from-motion, image stitching, and 3D reconstruction remain classical strongholds because they're math and geometry problems, not big-data problems. The 2026 twist is interpretability becoming a procurement requirement, not just a research talking point - deep learning's decision basis is often unexplainable, and classical pipelines win when you have to justify the output, per Mad Devs.

On Reddit, OpenCV is the plumbing nobody is replacing - The actual r/computervision activity this month is people shipping things built on classical primitives: "Applying computer vision to real life" (189 upvotes) and "I built AeroPuzzle - a real-time hand gesture puzzle game using OpenCV and MediaPipe" (220 upvotes). Even the deep-learning releases like LibreYOLO v1.2.0 (263 upvotes) lean on OpenCV underneath, and r/opencv questions are still about running OpenCV on a Raspberry Pi - the edge use case that deep learning struggles to fit.

The "obsessed with LLMs" framing has a clean answer: OpenCV sits underneath the LLM - Even when the headline model is YOLO, SAM, OCR, or a VLM, OpenCV does the resize, crop, threshold, perspective transform, camera calibration, tracking, and frame extraction first. It doesn't replace deep learning - it's combined with it, and OpenCV 5 leaning into that hybrid (classic CV + DNN + small VLMs in one battle-tested library) is exactly why developers still care. The hybrid pattern even shows up in new tooling on X, like @telekinesis_ai's Cornea library combining "SOTA Vision Foundation Models with robust classical computer vision algorithms."

KEY PATTERNS from the research: 1. Classical CV still wins on geometry (SLAM, SfM, image stitching, 3D reconstruction) and edge/embedded compute where it matches DL on precision at a fraction of the cost - per AllPCB 2. Interpretability moved from research nicety to procurement requirement in 2026, favoring explainable classical pipelines - per Mad Devs 3. OpenCV 5's pitch is consolidation, not reinvention - classic detectors stay, three DNN engines sit behind one unchanged API - per CNX Software 4. The C++17 / legacy-C-API removal is the real migration pain; Python users barely notice - per Phoronix 5. In practice OpenCV is the preprocessing/postprocessing layer beneath YOLO, SAM, OCR, and VLMs - it's combined with deep learning, not displaced by it - per @telekinesis_ai

What I learned:

Cursor Camp is the toy that made everyone get it - Neal Agarwal's Cursor Camp (out April 29) drops you and a crowd of strangers onto an illustrated campsite as bare mouse cursors - no chat, no usernames, no profiles - and people are genuinely moved by it. Aftermath nailed the feeling: "there's a strange comfort in being surrounded by other live cursors," because "you get the sense that there are real people on the other end of each pointer, doing exactly what you're doing." Reviewers keep reaching for Journey and Club Penguin to describe it, per PC Gamer.

The magic word everyone uses is "vibe," not "feature" - the PartyKit Cursor Party team, who ship the open-source script that adds live cursors to any site, put it bluntly: multiplayer cursors "aren't the most sophisticated way to share presence but they are super effective," and once you realize "just behind the glass, there are other people and we can be together - well, that's a vibe." Their own GitHub README answers its own "Why?" with one word: "Vibes." That's the whole pitch, and it works.

Presence without conversation is the actual feature - what people love is the absence of the usual social-media machinery. No followers, no persistence, no performance - just the raw signal that you are not alone on this page. Matt Webb's Interconnected frames it as "every webpage deserves to be a place," and says seeing live cursors makes other websites feel impoverished by comparison. Boing Boing called Cursor Camp a "wholesome no-chat online hangout spot," which captures why it reads as comforting rather than chaotic.

Wordless collaboration is where the warmth comes from - the surprise hook is that people piece out what to do together, silently. In Cursor Camp strangers collaboratively build a fire and make mushroom stew with zero direct communication, per PC Gamer. The PartyKit crew describe the same thing on the open web as "serendipitous back-and-forths" - you wiggle your cursor, a stranger dances back, and that tiny unprompted reciprocity is the payoff.

It's landing as a counter-move to the loneliness internet - the most quietly telling signal in the data is @nicole_ripka writing that "more technology should create intimacy, not just scale," with a kid spotted "playing Cursor Camp at the dinner table." That's the cultural read: these toys feel magical because they reintroduce ambient human presence to a web that mostly optimized it away. On the builder side, presence is also going mainstream as table stakes - @aayushman2703 drew 1,200+ likes pitching a multiplayer site builder "where your whole team co-edits live and visitors see your published page being built."

The infrastructure to make it yourself is right there - this isn't just Neal's magic; it's a copy-pasteable category now. partykit/cursor-party lets you add multiplayer cursors to any site with a single script tag, and liveblocks/liveblocks (4.6K stars) sells the managed "realtime infrastructure for multiplayer apps" version. The barrier to making your own shared-presence toy collapsed, which is why the genre is spreading.

KEY PATTERNS from the research: 1. Presence beats interaction - just seeing live cursors is enough; the magic is "real people behind the glass," per PartyKit 2. Stripping away chat/usernames/profiles is a feature, not a limitation - "wholesome no-chat hangout," per Boing Boing 3. Wordless collaboration (building fires, making stew together silently) is where the warmth lives, per PC Gamer 4. People read it as an antidote to scale-without-intimacy - "technology should create intimacy, not just scale," per @nicole_ripka 5. "Every webpage deserves to be a place" - live cursors make the web feel alive again, per Interconnected 6. The category is now DIY - one script tag via partykit/cursor-party or managed infra via Liveblocks