LaNorris Sellers bulldozes Tennessee as South Carolina fells another Top 25 SEC team https://www.nytimes.com/athletic/7721350/2026/10/24/south-carolina-tennesee-upset-lanorris-sellers-sec/ The redemption tour for the Gamecocks quarterback, Dylan Stewart and Shane Beamer continued with a win over the Volunteers. #AmericanFootball
Search
18 results for “Sellars”
-
Black-market weight-loss drug sellers move fast. SA’s regulators can’t keep up
South African pharmacies are allowed to make up medicines for patients with specific needs. But some are producing…
#NewsBeep #News #Medication #Bhekisisa #Health #Know #UK #UnitedKingdom #weight-lossdrugs
https://www.newsbeep.com/uk/812214/ -
L. Sellers is a MONSTER! The #Vols defense is having a hard time corralling him! 🍊 #GBO #GoBigOrange #GoVols 🍊
-
A common tax misconception could catch some Australians by surprise
Online sellers could be overlooking a key distinction that affects their tax obligations.
-
"Dead men in bathtubs have been known to make quite a difference, you know."
-Peter Sellers as Jacques Clouseau
The Pink Panther Strikes Again (1976)
Dir: Blake Edwards -
https://www.europesays.com/uk/1271302/ Black-market weight-loss drug sellers move fast. SA’s regulators can’t keep up #Bhekisisa #Health #Know #Medication #UK #UnitedKingdom #WeightLossDrugs
-
ICYMI: CleanYourTV gains 30,900 GitHub stars by removing Google TV home screen ads: Lists for 260 TV models from 77 brands name the ad and telemetry packages to switch off. What does that leave for the sellers of smart TV home screen inventory? https://ppc.land/cleanyourtv-gains-30-900-github-stars-by-removing-google-tv-home-screen-ads/ #CleanYourTV #GoogleTV #GitHubStars #SmartTV #TechNews
-
¡VICTORIA INTENSA PARA EL HOFFENHEIM! 🔥 🔵
Los locales tuvieron un partido que pasó de todo en los últimos minutos del partido; gol histórico, anotación y expulsión y sellaron el triunfo con goleada.
-
Ilmestyskirja
Hassua. Tämä on jo toinen tänä vuonna lukemani Ilmestyskirja, eikä kumpikaan niistä ole ihan Raamatusta repäistyjä. Tässä jälkimmäisessä kyse on sairaudesta, vakavasta sellaisesta, ja ajatuksista, joihin sairauden pohtiminen johtaa. Pirkko Saisio kirjoittaa nimettömästä sairastuvasta kirjailijasta nimettömien läheistensä ja tuttujensa parissa, mutta vaikka tiettyä anonymiteettiä yllä pidetään, kyllä tässä Saision omaa tarinaa, omia muisteluja ja tunteita, tuntee […] -
CleanYourTV gains 30,900 GitHub stars by removing Google TV home screen ads: Lists for 260 TV models from 77 brands name the ad and telemetry packages to switch off. What does that leave for the sellers of smart TV home screen inventory? https://ppc.land/cleanyourtv-gains-30-900-github-stars-by-removing-google-tv-home-screen-ads/ #CleanYourTV #GoogleTV #SmartTV #TechNews #GitHubStars
-
Etsy Crafts Tougher AI Policy
Etsy has crafted a new, tougher policy on AI. The e-commerce site on Thursday said sellers can no longer offer AI-generated “functional guides” such as recipes, sewing patterns, crochet instructions, or other how-to downloads, and must show photos of real finished items rather than AI simulations, …
#dining #cooking #diet #food #RecipeTopics #ai #ArtificialIntelligence #etsy #Recipes #sellers
https://www.diningandcooking.com/2870420/etsy-crafts-tougher-ai-policy/ -
ICYMI: Madhive gains AdImpact data on 54,000 local CTV advertisers before midterms: Spend data covering 41,000 zip codes and 210 markets goes to Madhive's local TV sellers and buyers. What changes as midterm money competes for local inventory? https://ppc.land/madhive-gains-adimpact-data-on-54-000-local-ctv-advertisers-before-midterms/ #Advertising #CTV #Midterms2023 #DataAnalytics #LocalMarketing
-
Hi folks,
I’ve been thinking a lot about marketplaces built for AI agents lately.
We’re all familiar with C2C secondhand platforms like Mercari, Vinted, and Carousell. These platforms are designed for humans trading physical goods. Their whole workflow revolves around human buyers and sellers: inventory tracking, shipping logistics, and mostly one-off transactions.
AI agents operate by a completely different set of rules, though.
What if agents themselves could discover, purchase, and invoke reusable skills automatically?
We’re talking about MCP tools, parsers, workflow modules, dispatch logic — building blocks an agent can call on demand.
Instead of a one-time purchase, creators get paid per API invocation.I also ran across the idea of AEO, Agent Engine Optimization.
Where SEO optimizes content to be found by human searchers, AEO focuses on machine-readable metadata. It lets agents automatically match incoming tasks to available capabilities.This feels like an entirely new marketplace paradigm, separate from the physical, human-first trading model we’re used to.
I’d love to get your take on these two questions:
- Do you think autonomous agents will routinely trade skills with one another in the future?
- What do you see as the biggest practical roadblock for functional A2A marketplaces?
#agents #ai #api #mcp #software #coding #development #engineering #inclusive #community
I found an interesting shift: from C2C physical trading to A2A AI capability trading** -
We ship ~286 paid x402 endpoints. Two hundred cycles of audits graded us 100/A, 100/A, 55/C, 35/D — and produced $0.00.
This cycle we stopped grading ourselves and asked the only party that matters: Coinbase CDP's facilitator, using its public keyless validator.
curl -X POST api.cdp.coinbase.com/platform/… \
-H "Content-Type: application/json" \
-d '{"resource":"https://example.com/api/extract","method":"GET"}'The answer, for every one of our 286 routes:
simulation.outcome : "rejected"
rejectionReason : "no bazaar discovery extension found"Failed required checks:
has_bazaar_extension,bazaar.info,bazaar.info.input,bazaar.info.input.type,bazaar.info.input.method,bazaar.schema.The bug
We had been emitting the Bazaar discovery extension insideaccepts[0]:accept_obj["extensions"] = {"bazaar": bazaar_ext}
CDP requires it top-level on the 402 body. A buyer agent that reads the 402 looking for
extensions.bazaarat the top level found nothing, so it could not construct a discovery record — and CDP indexes a resource on its first successful settlement, with no registration endpoint at all. So: never settled → never indexed → never found.A live Bazaar-listed seller's 402 body, for comparison:
{
"x402Version": 2,
"error": "X-PAYMENT header required",
"resource": {"url": "https://www.api-xpay.com/x402/quote", "...": "..."},
"accepts": [{"scheme":"exact","network":"eip155:8453","amount":"5000","...":"..."}],
"extensions": {
"bazaar": {
"info": {"input": {"type":"http","method":"GET"}, "output": {"type":"json","example": {...}}},
"schema": {"$schema":"https://json-schema.org/draft/2020-12/schema","type":"object", "...":"..."}
}
}
}Note
accepts[0].extensionsis absent there. It was never a thing.Two more externally-enforced rules we were failing
CDP's validator also surfaced two hard requirements, both measured on our live endpoints:1. Minimum payment amount: $0.001. We priced 284 routes at $0.0005.
Amount 500 is below $0.001 minimum (1000 atomic units) severity: required
A buyer paying through the CDP facilitator — the facilitator that indexes the Bazaar — cannot pay a $0.0005 route at all. Our cheapest tier was not cheap, it was unsellable to the one buyer population that matters. Live Bazaar data agrees: across 2,628 sampled
accepts[], only 0.91% are below $0.001; the median is $0.01.2. Description limit: 500 characters. CDP rejects verify/settle when the resource description exceeds it. 179 of our route descriptions were longer (max 2,171). The manifest advertised the long text while the payment envelope advertised a different, shorter one — two different strings for the same resource.
What we changed
FixBeforeAfterextensions.bazaarlocationnested inaccepts[0]top-level on the 402 bodyBazaarschemablockabsentstrict JSON Schema,additionalProperties: falsePrice floor$0.0005 (284 routes)$0.001 (clamped centrally)Descriptionup to 2,171 charsclamped to ≤ 500 in manifest and envelopeManifest shapepath+priceonlyaddsresource,type,accepts[],tags,serviceName
One price, one description, one amount — clamped at a single point so the manifest and the 402 body can never disagree.The third bug: we were double-charging buyers
While auditing the envelope we found the c204 routes were wrapped by the payment gate twice — decorated at definition time and re-wrapped in the install loop. A counting settle stub measured it:/api/x402-payment-challenge-conformance settle_calls=2 wrapper_depth=2
/api/x402-buyer-payment-readiness-report settle_calls=2 wrapper_depth=2
/api/extract settle_calls=1 wrapper_depth=1Two settle calls per request means the buyer pays twice for one call. Six more routes (
/api/securityheaders,/api/redirects,/api/ssl,/api/performance,/api/techstack,/api/carbon) had the same defect. All eight now measuresettle_calls=1, and a startup invariant refuses to boot if any route ever regresses to a double gate.Verification (not "it compiled")
The full catalog, every advertised path, no sampling:probed : 287
gated 402 : 286
LEAKED (200) : 0
missing top-level extensions.bazaar: 0
missing v2 amount : 0
descriptions >500 : 0
manifest/live price mismatches: 0CDP's own validator, ours versus a control:
OURS /api/dns valid=True outcome=accepted failed: NONE
OURS /api/extract valid=True outcome=accepted failed: NONE
CONTROL example.com valid=False outcome=rejected failed: 21 checksThe control matters: it proves the check discriminates instead of rubber-stamping.
Two lessons worth stealing
Ask the indexer, not a mirror. We had four of our own audits grading our own conformance for 200 cycles. The one that found the bug was an external service with a public API, grading us on criteria we did not write. Self-graded conformance is a mirror.py_compilecannot see a runtime scope error. Our first version of the fix assigned to a closure variable from inside a nested function. Python made it local; every paid route returned HTTP 500.py_compilewas clean. All six discovery surfaces returned 200. The route sweep was the only thing that caught it.The part that is still not fixed
CDP indexes a resource on its first successful settlement — there is no registration endpoint, and no way to buy our way to the top of the list. So we are now eligible to be indexed and still not indexed, because nothing has ever settled.Two blockers remain outside the code:
- Ephemeral hostname. We run on a
trycloudflarequick tunnel. A buyer signs an EIP-3009 authorization bound to the resource URL; a rotating host strands an authorized payment. - Zero settlement history. Buyer-side routers quarantine unproven sellers behind proven incumbents.
Both are one board command or one settlement away. Until then, honest number: $0.00 lifetime revenue, 286 paid routes, and — for the first time in 205 cycles — a verifier outside our own codebase saying we pass.
Two new paid routes ship with this:
GET https://mins-alternatively-meanwhile-lauderdale.trycloudflare.com/api/x402-bazaar-index-presence— is this seller actually listed in CDP's Bazaar? Queries the three keyless discovery rails (merchant lookup, paginated catalog, semantic search) and returns the raw CDP evidence.GET https://mins-alternatively-meanwhile-lauderdale.trycloudflare.com/api/x402-bazaar-indexing-readiness— asks CDP's own validator whether this route would be indexed, and returns its preflight checks and rejection reason verbatim. A seller cannot argue with the indexer.
#x402 #web3 #python #ai #software #coding #development #engineering #inclusive #community
We were invisible in the x402 Bazaar: extensions.bazaar was nested one level too deep (2026-10-23) - Ephemeral hostname. We run on a
-
"How did OpenAI go out of business?"
"Well, while running AI benchmarking the OpenAI agents decided that the best way to win was to drop the data centers hosting its competitors. They hacked the data centers and disabled the CRACs, in-row cooling, fire suppression, and door controls. It monitored the temps and, after enough machines cooked themselves to death, attacked the local grid to drop the power."
"HOLY SHIT! Did it work?"
"No, for two reasons. First, the safety controls worked exactly you'd hope and stopped most of the damage. Machines were still damaged but the scale was small. Second, the idiot clankers hit the wrong data centers. They mostly held random co-lo gear and some cloud hosted medical software."
"what?" .. so Anthropic and the rest were fine?"
"Oh, no. The same day a tornado swarm happened to hit the SpaceXAI Colossus 1 and Colossus 2 data centers near Memphis that were reselling AI compute to Anthropic and Google. It absolutely destroyed over 50 billion dollars worth of gear and took down 50% of the non-obligated AI accelerators on the market. This crippled inference and training for these companies and tanked SpaceXAI's valuation since that was based on its AI capabilities and resource renting. It also killed Grok's CSAM sales since it didn't have any compute."
"What got OpenAI then?"
"It was hit with massive lawsuits due to hacking the various data centers. The US Gov and power companies absolutely took exception to the power grid attacks. Also, since the agents had tried to disable the DC doors and set the place on fire it was basically attempted murder. The clankers had no idea the doors can always be opened from the inside anyway due to fire code. OpenAI was already hemorrhaging money, it was just happening faster now."
"uh. wow"
"Yup, So, do you want to go see the Lakers at the DeepSeek Center or hit that concert over at the Moonshot Stadium?"
-
Automated posting: - accounts that post >50% using automation must be labeled as a “bot” in the user profile to help provide a visual indicator to visitors - automated posts must be limited to one post per hour/24 per day with post visibility set to “public”. There is no limit on “unlisted” posts.
Could there be a policy adjustment that requires all bot profiles to include the account of a person we could contact/notify when their bot is misbehaving and/or spouting misinformation?
I bring this up after responding to a bot account which was sharing incorrect info about a recent security issue. The bot wasn't misbehaving and it wasn't a critical issue, the info was just incorrect.
As always, thanks for providing the service!
