Nick Fox @Foxaii

“I’m going to donate money to that Tommy Robinson. What did I say, Roy?” “You said, that grifter’s out of gak again.”

PICARD: Data, shields up DATA: Brilliant! Shields can reduce damage we sustain. Not immunity. Not hubris. Just prudence. It's not precaution—it's strategy. [camera shakes] WORF: HULL BREACHES ON NINE DECKS DATA: Here's what happened: you told me to raise shields, and I didn't

The next incredible chapter of this football club is written ❤️ We’ll be in Europe for the first time in our 127-year history next season 🌎 On to Sunday for one final push to find out which competition 💪

I started my career at Bournemouth - they were languishing at the bottom of league one. They didn’t have a real training ground, they had a 3 sided stadium. So many people deserve credit, but the fans who collected money in buckets to save their club are now saving for EUROPE ❤️

An early warning system for WordPress plugin security issues: WP Packages now tracks vendor mass closures publicly RSS feed and APIs also available for mass closures 🔔 wp-packages.org/closures

Looks like we got this almost exactly perfect - including the exact turnout!! Very happy

Find Out Now @FindoutnowUK

2 months ago

Senedd (Welsh Parliament) voting intention: 🟩 Plaid Cymru 35% (+6) 🟦 Reform UK: 28% (+1) 🔵 Conservatives: 11% (-2) 🔴 Labour: 9% (-1) 🟢 Greens: 9% (-2) 🟠 Lib Dems: 6% (-) Implied turnout: 52% Changes from 18-22nd April [Find Out Now, 1-6th May, N=2,001]

7 42 144 44K 15

@Nigel_Farage says the £5m was a "personal gift." The rules say such gifts should be registered if they "could...reasonably be thought by others to be related to membership of the House or to the Member’s parliamentary or political activities.." "Security" is plainly that.

One might expect @ChrisMasonBBC to be able to find the rules on donations - it takes 3 seconds to do so: publications.parliament.uk/pa/cm5803/cmco…

Mr Ethical 🚩 @nw_nicholas

2 months ago

This is unbelievable. Chris Mason reporting on the Farage £5m donation and doesn't mention the rule that new MPs must report all donations in the 12 months prior to being elected. Unbelievable.

483 3K 10K 385K 176

I'd rather drink the water from a tin of tuna than be asked to share a fun fact about myself as an icebreaker during a team building activity at work.

100,000+ stores run this WooCommerce plugin. I doubt any of them know their payments are broken. Any store with $1M ARR could be missing $700k+ in revenue. If you run WooCommerce Subscriptions, check your store. Yesterday, I reported a bug to WooCommerce that silently broke subscription payments after a product switch. Then I got worried: if they missed something this obvious, what else did they get wrong? So I started auditing. Within hours, I had found three more bugs. There were 121 affected subscriptions, and $43,274 in lost revenue. Here's what I found. WooCommerce Subscriptions has an internal flag that controls whether a subscription charges the customer automatically or waits for them to pay manually. When a customer checks out with (for example) Stripe or PayPal, this flag should be set to "automatic." If it isn't, subscription renewals silently stop working: no charge is attempted, no failure email is sent, and the subscription goes on hold until the customer notices and pays manually, or doesn't and churns. Bug 1 (stale cache): After saving subscription dates, the order cache was never cleared. Subsequent saves could serve a stale object with the flag still set to its default: manual. Fixed in subscriptions-core 6.9.0. Bug 2 (broken HPOS backfill): Missing getter/setter methods prevented subscription metadata from being properly synced to postmeta in HPOS when data sync is enabled. Fixed in subscriptions-core 6.5.0. Bug 3 (unnecessary re-fetch): wcs_create_subscription() returned a freshly fetched instance from cache/DB instead of the already-configured object. Any unsaved state, including the corrected flag, was silently discarded. Fixed in subscriptions-core 7.1.0. These three combined accounted for roughly 7% of all subscriptions created at checkout that were silently born broken, despite the customer paying successfully. For 7+ years (we have data from 2017–2024). Automatic payments NEVER fired for these subscriptions. Users never got renewal emails, either. The only way to know they were broken was if the customer noticed they lost access and contacted support, or if the merchant audited their database manually. Bug 4 (switch): When a customer upgrades or downgrades their subscription, the switcher flags the subscription as manual renewal; it only corrects the flag if the payment gateway changes. A customer switching plans while keeping the same gateway (e.g. Stripe to Stripe) cements the flag stuck on manual. I discovered this two days ago, when I found a happy customer in the store overview that I had just helped upgrade, with multiple valid cards on file, put "On Hold" because of a missed payment. For years, I've offered to help WooCommerce improve its code quality and performance. I dry-run code: I find bugs by reading. All four of these bugs are clearly visible in the source without needing to use the software. They could have been caught early. They weren't. The incompetence is immeasurable (well, actually, with the diagnostic queries in my next post, it might be measurable). Our store is small. WooCommerce Subscriptions powers hundreds of thousands of stores. If 7% of subscriptions were silently broken across even a fraction of them, we're looking at potentially millions of dollars in spoiled revenue industry-wide that could have been prevented. Perhaps even billions. None of this was disclosed well or at all. No admin notice. No email. No advisory. The fixes shipped under vague changelog lines like "Make sure we always clear the subscription object from cache after updating dates" and "Ensure proper backfilling of subscription metadata." One fix was labeled "Dev" instead of "Fix." Two don't appear in the GitHub release notes at all. No remediation tool or diagnostic query was provided. Store owners have NO way to know they're affected unless they manually audit their database. The woocommerce-subscriptions-core repo was archived in May 2025 after the code was absorbed into WooCommerce core — making the fix history harder to trace. If you run WooCommerce Subscriptions and used HPOS before mid-2024, check your store. Queries are linked in the tweet below.

Thank you for everything, Andoni ❤️

I know I’m shallow but just how good does that make the rest of the weekend😂 #afcb

🔎 quien — a better WHOIS. Domain lookups with a clean TUI instead of parsing raw 𝚠𝚑𝚘𝚒𝚜 output. DNS records, mail config, SSL certs, HTTP headers, and tech stack detection all in one tool. github.com/retlehs/quien

✨ @​roots/vite-plugin v2.1.0 adds support for theme.json partials You can now split your block styles into `.theme.js` files and co-locate them next to your block templates instead of maintaining one giant theme.json roots.io/roots-vite-plu…

Found the meteorologist responsible for naming Storm Dave.

🎉🎂 We’re 15! 🎂🎉 Happy Birthday to us! 🥳 For 15 years, Pick My Postcode has been giving away free cash to our amazing community, all thanks to YOU! 💙 #PickMyPostcode #BirthdayCelebration #FreeMoney #WinBig #HappyBirthday

Brie Larson was in 1st place in Mario Kart World... until she wasn't.

3 ways WordPress plugins break non-standard installs: - Hardcoded wp-content paths - Direct wp-load.php includes - Assuming WP lives at the root roots.io/wordpress-plug…

New site is: wp-packages.org Already using WP Composer? Your packages will continue to work, but you'll see a warning to migrate The old repo is no longer fetching new updates, so update your config from the one liner in the blog post when you get a chance

roots.io @rootswp

3 months ago

WP Composer is now WP Packages Details: roots.io/wp-composer-is…

1 9 61 12K 10