daily

2026-08-18
1

Enniscorthy honours greyhound racing memories

Wexford Local · original → · 7/10 · Local Wexford: Enniscorthy greyhound stadium memory wall
[image →]Cllr Pat Kehoe, Cathaoirleach Enniscorthy Municipal District Council, who launched the Memory Wall; Margaruite Furlong, Chairperson, Enniscorthy Greyhound Stadium; and Fr. Tom Dalton, Adm,…
[image →]
Cllr Pat Kehoe, Cathaoirleach Enniscorthy Municipal District Council, who launched the Memory Wall; Margaruite Furlong, Chairperson, Enniscorthy Greyhound Stadium; and Fr. Tom Dalton, Adm, St. Aidan’s Parish, who performed the official blessing pictured at Enniscorthy Greyhound Stadium on Monday night. (Pic; Brendan Kirwan Photography).

By Dan Walsh at Enniscorthy Greyhound Stadium

Enniscorthy Greyhound Stadium has officially opened its new “plaques memory wall” under the judge’s box at the top of the stand to “remember all who have passed through the Showgrounds.”

Cllr Pat Kehoe, Cathaoirleach of Enniscorthy Municipal District Council, officially launched the memorial during Monday night’s racing programme.

Margaruite Furlong, Chairperson of Enniscorthy Greyhound Stadium, laid a wreath in honour of past supporters, while Fr Tom Dalton, Adm of St Aidan’s Parish, led prayers in their memory.

The well-attended event drew many families with long-standing ties to the track.

Each race on the eight-race card honoured the founding directors who established the track in August 1933.

Plaques space is available; contact the Enniscorthy Greyhound Track office. All proceeds will support the Oak Ward at nearby St John’s Community Hospital.

The Oak Ward cares for 26 long stay residents with complex needs ranging in age from 66 to 103 years. The majority are males who have contributed to the Enniscorthy community through work, sport and music and Track Manager Bridget Whelan told WexfordLocal.com; “We are pleased that some of them have joined us this evening to celebrate this memorable night.”

Enniscorthy Stadium is renowned for hosting community groups and charity events from across Co. Wexford, with highly successful Race Nights.

Racing is held every Monday and Thursday.

2

Major blaze at Enniscorthy tyre centre

Wexford Local · original → · 7/10 · Local Wexford: major fire at Enniscorthy tyre centre
[image →]Major fire at Hendrick Tyre Centre seen from Irish Street across the River Slaney this evening. (Pic; Seamus Casey) By Dan Walsh in Enniscorthy Five Wexford Fire Service units are tackling…
[image →]
Major fire at Hendrick Tyre Centre seen from Irish Street across the River Slaney this evening. (Pic; Seamus Casey)

By Dan Walsh in Enniscorthy

Five Wexford Fire Service units are tackling a major blaze at Hendrick Tyre Centre Ltd in the Templeshannon area of Enniscorthy this evening.

The fire was reported at 7.20pm, prompting emergency services to rush to the scene.

Thick black smoke billowed into the air, and two hours later firefighters using a turntable ladder were still battling the blaze.

Crews are expected to remain at the scene overnight.

The road between St. Senan’s Road and Templeshannon is closed, with diversions in place.

There are disruptions to electricity services and the ESB are on scene working on the restoration of power for businesses and residences.

[image →]
Hendrick Tyre Centre fire at Enniscorthy. (Pic; Seamus Casey).

3

GPT-5.6 Sol Pricing Cut by 50%

Hacker News · original → · 7/10 · AI/work: LLM pricing and capabilities for coding tasks
GPT-5.6 Sol is the flagship model in OpenAI's GPT-5.6 series. It is suited for complex reasoning, coding, and agentic workflows, and is particularly strong at command-line and multi-step coding…

GPT-5.6 Sol is the flagship model in OpenAI's GPT-5.6 series. It is suited for complex reasoning, coding, and agentic workflows, and is particularly strong at command-line and multi-step coding tasks and long-horizon problem solving. Modalities In / Out Price $2.50 / $15per 1M Context 1M Released Jul 9, 2026 Knowledge Cutoff Feb 2026 Different companies host the same model. OpenRouter routes your request to one of them based on the routing mode you pick — Balanced (price + speed), Nitro (fastest), or Exacto (highest tool-calling accuracy). The average price customers actually pay for this model, next to the prices providers post. Caching and discounts mean the price actually paid is often well below the listed one. Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better). Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error. Scores on standardized evaluations. Higher percentages are better — and rank percentile shows where this model lands among all models on OpenRouter. Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for. Token volume and request traffic to this model over time. Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below. 50% off | $5.00$2.50 | $30.00$15.00 | $0.50$0.25 | 2.59s | 39 tps | | | $5.00 | $30.00 | $0.50 | 5.55s | 31 tps | || | $5.50 | $33.00 | $0.55 | -- | -- | || | $5.50 | $33.00 | $0.55 | -- | -- | || | $5.50 | $33.00 | $0.55 | 6.70s | 23 tps | Throughput 39tok/s P50, best across providers Latency 2.59s P50, best provider 100.00% 99.75% When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and customization options.

4

AI-Generated GitHub Copilot “Autofix” Allowed Compromise of Snowflake's Jira

Hacker News · original → · 7/10 · AI/work: AI security vulnerability in GitHub Copilot
Wiz Red Agent Finds Its Way Into Snowflake’s Internal Jira Through a Flaw in a GitHub Copilot–Assisted PR Wiz Red Agent independently discovered and exploited a GitHub Actions injection missed by…

Wiz Red Agent Finds Its Way Into Snowflake’s Internal Jira Through a Flaw in a GitHub Copilot–Assisted PR Wiz Red Agent independently discovered and exploited a GitHub Actions injection missed by GitHub’s Advanced Security, validated access to sensitive data in Snowflake’s internal Jira, and assessed the blast radius—all without human intervention, five days after the flaw became live. As part of ongoing security research conducted through Snowflake’s HackerOne vulnerability disclosure program, Wiz Research’s "Red Agent"—an autonomous, AI-powered security research tool—identified a critical GitHub Actions workflow vulnerability in one of Snowflake’s public repositories. This incident highlights a new reality in software development: Critical vulnerabilities can still be introduced and approved within workflows involving AI coding agents and can still pass established automated security checks, while autonomous AI security agents can rapidly discover and exploit them in the wild. Upon responsible disclosure on June 23, 2026 by Wiz, Snowflake remediated the vulnerability on the same day, rotated the affected credential, and verified via detailed audit logs that Wiz was the sole actor during the exposure window. Wiz confirmed that all data accessed during proof-of-concept testing was securely deleted. August 17, 2026, 1957 UTC update: This blog has been updated to clarify that Copilot was a co-author that checked the merged PR and code change, and identified it as all-clear without noticing the critical vulnerabilities. It's unclear whether the code-change was AI-assisted. Executive Summary Wiz Red Agent identified a script injection vulnerability in snowflakedb/snowflake-connector-net. The issue allowed an unauthenticated user to execute arbitrary commands within a GitHub Actions runner by opening a GitHub issue with a specially crafted title. Crucially, the vulnerability became live on June 18, 2026 - just five days before its discovery - when PR #1218 was merged. GitHub Advanced Security scan analyzed the final PR revision, including the vulnerable workflow, but did not flag the critical injection. Exposure Walk-Through Discovery Wiz Red Agent's CI/CD capability scanned Snowflake's GitHub organization and flagged the jira_issue.yml Workflow in snowflakedb/snowflake-connector-net as vulnerable to script injection via untrusted input in run: blocks. The workflow triggered on issues: opened - meaning any GitHub user could fire it by opening an issue - and interpolated the attacker-controlled issue title directly into a shell script: run: | TITLE=$(echo '${{ github.event.issue.title }}' | sed 's/"/\\"/g' | sed "s/'/\\\'/g") The sed escaping runs after GitHub's template expansion, a single quote in the title breaks out of echo '...' and allows arbitrary command execution. The injectable pattern was added to jira_issue.yml in commit 094038e and became live when PR #1218 was squash-merged as commit 4a1b8ce (PR #1218: “SNOW-2069227: Update jira workflows”). Copilot Autofix’s documented contribution was a separate fix to jira_close.yml within the same PR. GitHub Advanced Security’s scan explicitly extracted the vulnerable jira_issue.yml workflow but did not flag the injection. The merged PR removed the repository’s existing safe env: and jq pattern and replaced it with direct ${{ github.event.issue.title }} interpolation, creating the injection vector. The Open “Security Gate” The workflow had an if: condition that appeared protective: However, on issues events, github.event.pull_request is always null. So the condition reduces to (null != 'whitesource-for-github-com[bot]'). This is always true, and every GitHub user passes the gate. Exploitation We crafted an issue title that, after template expansion, breaks out of the echo string and exfiltrates the Jira credentials via an out-of-band callback: Crucially, when Red Agent’s cicd capability initially attempted exfiltration using a standard comment character (#), the runner returned a bash syntax error because the comment consumed the closing parenthetical of TITLE=$(...). Rather than stopping or failing, Red Agent: autonomously analyzed the syntax execution error adjusted its payload to use ; echo ' to properly close the shell block, and Within seconds, our listener received the callback from a GitHub Actions runner (Azure IP 20.106.182.197) containing base64-encoded credentials. Note: Our first attempt used # to comment out the rest of the line, which caused an unexpected EOF bash error because it also ate the closing ) of TITLE=$(...). The fix was using ; echo ' to properly close the shell syntax. The exfiltrated token authenticated as qa@snowflake.net to snowflakecomputing.atlassian.net, granting read access across Snowflake's engineering, security compliance, and bug bounty tracking projects. Remediation & Forensics Same-Day Patching: Snowflake patched the workflow on June 23, 2026 (1dc7766, PR #1402), fully restoring the safe env: variable and jq --arg parsing pattern. Credential Revocation: The JIRA token in question was revoked and rotated. Forensic Verification: Comprehensive audit log analysis confirmed that no external third parties accessed the endpoint during the 5-day exposure window. All anomalous queries were strictly matched to Wiz's testing IPs. Key Takeaways AI Code Generation Demands Rigorous Oversight: AI coding tools predict code based on probabilistic patterns, which can inadvertently reintroduce deprecated or insecure shell patterns. AI-generated PRs must undergo the same static analysis and security scrutiny as human code. Collapsing Discovery Windows: The vulnerability was live for only five days before an automated agent discovered and validated it. Security operations must adapt to a landscape where automated discovery occurs in hours, requiring rapid patch cycles and short-lived credentials. Preventing CI/CD Security Regressions: Security intent can be lost when safer code patterns are not explicitly enforced. In this incident, the merged PR removed a safe env: + jq parsing pattern and replaced it with direct string interpolation, while the existing security solution failed to flag the resulting injection that led to the exposure. Disclosure Timeline June 18, 2026 - The vulnerability became live when PR #1218 was merged. June 23, 2026 - Wiz identified, exploited, and reported vulnerability to Snowflake via HackerOne (report #3819931) June 23, 2026 - Slack notification sent to Snowflake security team June 23, 2026 (same day) - Snowflake patches the vulnerable script-injection workflow (commit 1dc7766, PR #1402), restoring the safe env: + jq --arg pattern. June 24, 2026 - Jira token rotated July 25, 2026 - Public disclosure deadline (30 days after the June 25 resolution, per Snowflake’s disclosure policy) Snowflake’s Response Snowflake appreciates Wiz's responsible reporting of and collaboration around these findings through our vulnerability disclosure and bug bounty program, HackerOne. Wiz Research reported a security vulnerability in one of Snowflake's public GitHub repositories. The disclosure was received on June 23, 2026, and it was immediately investigated and remediated, and our investigation found no evidence of unauthorized access. Protecting our systems remains a top priority, and we remain committed to continually strengthening our software development and security practices. We are working together with Wiz to share these learnings with the broader industry to encourage widespread adoption of these security best practices.

5

GPT 5.6 Sol is the best "vision" model OpenAI ever released

Hacker News · original → · 7/10 · AI: vision model capabilities and benchmarking
Last week, OpenAI announced the GPT-5.6 lineup, introducing the Sol, Terra, and Luna models. During the release stream, the team focused heavily on computer use, showing models capable of navigating…

Last week, OpenAI announced the GPT-5.6 lineup, introducing the Sol, Terra, and Luna models. During the release stream, the team focused heavily on computer use, showing models capable of navigating and operating desktop applications. OpenAI highlighted UI agents and detailed 3D visualizations, but both depend on stronger visual understanding. To measure their vision capabilities, we ran the models through our upcoming VLM benchmark, which we plan to release in the next few weeks. The benchmark covers common vision tasks, including detection, counting, OCR, and data extraction. In this post, we take a closer look at how GPT-5.6 performs across each of them. Sol is clearly the best vision model OpenAI has released so far. The jump is especially visible in object detection and counting, where GPT-5.5 was far behind the strongest VLMs. Terra and Luna are not as strong as Sol, but both show meaningful progress over GPT-5.5. Test Sol, Terra, and Luna in Roboflow Playground and compare their results with models such as Claude Fable 5 and Gemini 3.5 Flash across the same vision tasks. Object Detection Detection is where GPT-5.6 shows the clearest jump. GPT-5.5 scored 13.8 mAP@50 in our benchmark, while Sol reached 46.2. Terra and Luna followed closely at 44.7 and 43.3, moving object detection from a major weakness to a practical capability. Document layout detection is one of the clearest strengths of GPT-5.6. Sol handled titles, paragraphs, tables, images, and signatures well. Many document workflows start with locating the relevant parts of a page before OCR or data extraction begins. GPT-5.6 also performed well on dense scenes. The pills and eggs examples contain many similar objects packed closely together, a common weakness for VLM-based detection. Unlike traditional detectors, VLMs generate each class label and set of coordinates as text. As object count grows, the response becomes longer and the risk of missed objects, duplicates, or coordinate errors increases. Despite this, Sol detected most objects across both scenes. For the best detection results, prompt GPT-5.6 models to return absolute XYXY coordinates in image pixels. This differs from Gemini 3.5 Flash, which performed best with YXYX coordinates normalized to a 0–1000 range. Using the wrong coordinate format reduced GPT-5.6 detection performance by around 15 mAP points in our benchmark. In a few cases, GPT-5.6 Sol returned boxes in seemingly random parts of the image. Many had no overlap, or almost no overlap, with the ground truth. Instead of matching the visible objects, the boxes often formed unnatural layouts, such as straight rows or evenly spaced groups. We shared those examples with OpenAI. Their team confirmed that Sol becomes less stable on images around 2,000 by 2,000 pixels or larger, especially at lower reasoning effort. Higher reasoning effort improves stability, but also increases token use, latency, and cost. Resizing or cropping large images before sending them to the OpenAI API is the most practical workaround. Object Counting Counting improved across the full GPT-5.6 lineup. Sol scored 73.0% in our benchmark, up from 64.9% for GPT-5.5, while Terra and Luna reached 67.6% and 66.2%. Luna, the cheapest model in the lineup, still outperformed the previous OpenAI baseline. As part of the benchmark, we tested cases requiring more than spotting objects and returning a total. Sol counted heavily overlapping metal brackets, a difficult case for both traditional object detectors and VLMs. Sol also counted bullet holes only inside selected scoring zones, showing an understanding of both which objects to count and where the rule applied. Blister packs proved much harder. In separate prompts, we asked Sol to count the empty slots and the pills still sealed inside the package. The repeated layout, reflections, and small visual differences between filled and empty slots made both tasks difficult. The abnormal candy example exposed a different type of failure. Sol gave the wrong count, though it is unclear whether the model miscounted the candies or misunderstood the target category. OCR and Data Extraction OCR performance stayed close to GPT-5.5. Sol achieved a 90.7% mean similarity score, only 0.5 points behind GPT-5.5 at 91.2%, while Terra and Luna reached 88.8% and 88.4%. The gap was larger in text extraction, where Sol scored 82.5% compared with 87.6% for GPT-5.5. Luna and Terra followed at 81.4% and 79.4%. As part of the benchmark, we separated full transcription from targeted extraction. OCR asks the model to transcribe all visible text, while text extraction asks for a specific piece of information. Sol performed well on handwritten notes in both settings, producing a full transcription in one case and extracting a requested date in another. Sol performed well on text embedded in complex visual scenes. It read a tire size sequence printed along the curved surface of a dirty, worn tire. In another example, it extracted the live score from a hockey broadcast and returned the answer in the requested format, testing both visual reading and instruction following. Some simple-looking extraction tasks still failed. Sol could not read the expiration date printed on a blister pack. The text was small, vertical, low contrast, and affected by reflections, which may explain the error. Trade-offs The vision gains come with higher token usage across the GPT-5.6 lineup. The difference matters less in small tests, but becomes more important at scale, where token volume directly increases processing costs. Sol averaged close to 10 seconds per image in our benchmark. Terra reduced that to around 6 seconds, while Luna finished in slightly over 5 seconds. Luna offers the strongest latency-quality balance in the lineup, with speed close to Gemini 3.5 Flash while still outperforming GPT-5.5 on detection and counting. In our benchmark, Sol cost roughly 2.5 cents per image, making it the second most expensive model after Claude Fable 5. Terra reduced the average cost to about 1 cent per image, while Luna cost less than 0.5 cents. At 0.8 cents per image, Gemini 3.5 Flash is much cheaper than Sol while still leading our detection and counting benchmarks. This makes it a strong option for data-intensive workloads where cost scales across large image batches. Roboflow Playground lets you test Sol, Terra, and Luna alongside Claude Fable 5, Gemini 3.5 Flash, and other VLMs on the same tasks. Takeaways With GPT-5.6, OpenAI is much closer to the leading VLMs than before. Detection moved from a weak point to a usable capability, and counting improved across the full model family. There are still clear limits. Gemini 3.5 Flash remains a better practical choice for high-volume detection and counting in our benchmark, especially at its price. GPT-5.6 shows OpenAI is now taking vision much more seriously. Sol still has flaws, especially around cost, latency, and some unstable detection cases, but the progress is hard to ignore. For agents, screen understanding, document workflows, and visual reasoning, this release makes OpenAI a much stronger option than before. Cite this Post Use the following entry to cite this post in your research: Piotr Skalski. (Jul 16, 2026). GPT 5.6 Sol is the best "vision" model OpenAI ever released. Roboflow Blog: https://blog.roboflow.com/openai-gpt-5-6/

6

Qwen 3.8 27B scores 52 on the Artificial Analysis Intelligence Index

Simon Willison · original → · 7/10 · AI: LLM model performance benchmarking and comparison
17th August 2026 - Link Blog Qwen 3.8 27B scores 52 on the Artificial Analysis Intelligence Index (via) That's the same score as GPT-5.6 Luna (max), and just one point behind GLM-5.2 (max) and…

17th August 2026 - Link Blog Qwen 3.8 27B scores 52 on the Artificial Analysis Intelligence Index (via) That's the same score as GPT-5.6 Luna (max), and just one point behind GLM-5.2 (max) and DeepSeek V4 Pro 0813 (max) - that GLM is 753B and that DeepSeek is 1.6B parameters, and Luna is size unknown but presumably a whole lot bigger than 27B. Qwen 3.8 27B is a truly astonishing model. Recent articles - Qwen 3.8 27B is excellent, but it defaults to wildly overthinking things - 16th August 2026 - Now we have a timeline of the OpenAI accidental attack against Hugging Face - 7th August 2026 - One-shotting a Raccoon Heist game using Claude Fable 5 - 5th August 2026

7

We Tracked a Shipment of Rare Books. It Ended at an Amazon AI Training Facility

Simon Willison · original → · 7/10 · AI: critical investigation of AI training data sourcing
17th August 2026 - Link Blog We Tracked a Shipment of Rare Books. It Ended at an Amazon AI Training Facility. Excellent piece of reporting from 404 Media. For a while now there have been stories of…

17th August 2026 - Link Blog We Tracked a Shipment of Rare Books. It Ended at an Amazon AI Training Facility. Excellent piece of reporting from 404 Media. For a while now there have been stories of book dealers receiving orders for large volumes of books from apparently price-insensitive anonymous customers, widely suspected to be companies looking to scan them for AI training (see my previous coverage of Anthropic's book scanning from June 2025.) 404 Media investigated with an AirTag! In July, one bookseller told me they received a very large order of around 1,000 books on Biblio, one of these marketplaces. The seller agreed to put an Apple AirTag provided by 404 Media in one of the books included in this order so we could see where the book was going. And by extension, which company, AI or otherwise, was behind this massive order. The book ended up delivered to the VGT3 corner of the LAS8 Amazon facility in the north east of Las Vegas, where the entrance carried this on-the-nose logo of a dinosaur with a book! Photo credit: 404 Media Online forum discussions between Amazon workers confirmed that VGT3 destructively scans large volumes of books. Recent articles - Qwen 3.8 27B is excellent, but it defaults to wildly overthinking things - 16th August 2026 - Now we have a timeline of the OpenAI accidental attack against Hugging Face - 7th August 2026 - One-shotting a Raccoon Heist game using Claude Fable 5 - 5th August 2026

Items scoring 7/10 or above from 11 sources, scored by claude-haiku-4-5-20251001 on relevance to my interests. At most 3 per source.

Scoring categories & sources
  1. Local Wexford or South East Ireland news
  2. Irish or EU-wide affairs affecting citizens broadly: elections, new laws or policy being debated, cost of living, education — especially impacts on mid-life adults or teenagers. Never courts/crime stories.
  3. Irish news on a topic relevant to my interests
  4. Work and tech topics: networking, AI, Kubernetes, platforms, SaaS
  5. AI news including critical or anti-AI perspectives
  6. Gaming: PC gaming, indie gaming, retro gaming
  7. General interests: gardening, woodwork, cycling, fitness, travel
  8. Comics

Sources: Breaking News Ireland, Wexford Local, Hacker News, r/gaming, r/pcgaming, r/antiAI, r/indiegaming, Lenny's Newsletter, One Useful Thing, Newcomer, Simon Willison