We’re fi­nally ready to talk about Flipper One — a pro­ject we’ve been grind­ing on for years and have re­built from scratch sev­eral times. It’s an in­cred­i­bly hard pro­ject, both fi­nan­cially and tech­ni­cally. So to­day we’re go­ing pub­lic not with a big shiny an­nounce­ment, but to tell the whole story straight. Honestly? We’re gen­uinely ter­ri­fied, and we need your help.

TL;DR With Flipper One, we’re reimag­in­ing what a Linux cy­berdeck can be — it’s a huge pro­ject. We’re open­ing up the de­vel­op­ment process and ask­ing the com­mu­nity for help.

With Flipper One, we’ve set our­selves a list of am­bi­tious goals:

Build the most open and best-doc­u­mented ARM com­puter in the world, with full main­line Linux ker­nel sup­port.

Push ven­dors to open up their ex­ist­ing closed-source code and ditch bi­nary blobs en­tirely.

Build an un­con­ven­tional hard­ware plat­form based on a co-proces­sor ar­chi­tec­ture that pairs a mi­cro­con­troller with a CPU, and port tons of low-level MCU code.

Rethink how peo­ple use Linux and de­velop our own GUI frame­work with wrap­pers around ex­ist­ing CLI util­i­ties.

Many of these goals come with a lot of un­cer­tainty, which is scary. But we be­lieve this is the only way to make a truly mean­ing­ful con­tri­bu­tion to the open-source com­mu­nity and to ed­u­ca­tion.

What is Flipper One?

Flipper One is­n’t an up­grade to Flipper Zero — it’s a com­pletely dif­fer­ent pro­ject with its own goals. Flipper One is an open Linux plat­form you can build al­most any­thing on: from a 5G-enabled IP net­work an­a­lyzer to an SDR-powered ra­dio sig­nal an­a­lyzer with lo­cal AI. We fo­cused a lot on the hard­ware ex­pan­sion sys­tem. You can con­nect high-speed mod­ules to Flipper One over PCI Express, USB 3.0, and SATA in­ter­faces. Add an SDR, a fast SSD, or a cel­lu­lar mo­dem — just plug in the right mod­ule.

Flipper One comes with sev­eral net­work in­ter­faces: 2x Gigabit Ethernet, USB Ethernet (5 Gbps), and Wi-Fi 6E (2.4/5/6 GHz). You can add 5G con­nec­tiv­ity by plug­ging in an M.2 mo­dem. That means you can use Flipper One as a router, a VPN gate­way, or a bridge be­tween wired and wire­less net­works.

Zero vs One

Flipper Zero and Flipper One are com­pletely dif­fer­ent pro­jects built for dif­fer­ent tasks. The eas­i­est way to think about it is in terms of net­work­ing lay­ers:

Layer 0 — Offline point-to-point ac­cess-con­trol pro­to­cols: NFC, low-fre­quency RFID, Sub-1 GHz ra­dio, Infrared, wired pro­to­cols like iBut­ton, UART, SPI, I²C. Based on a low-power mi­cro­con­troller.

Layer 1 — Everything that’s IP-connected: Wi-Fi, Ethernet, 5G, and satel­lite. It’s all about net­work­ing, data trans­fer, and high-per­for­mance com­put­ing. Running on pow­er­ful hard­ware and an open Linux toolkit — enough com­put­ing power to han­dle SDR and lo­cal AI.

So they’re not “newer” and “older” gen­er­a­tions of the same prod­uct. Flipper One does­n’t re­place Flipper Zero — they’re dif­fer­ent cat­e­gories of de­vices.

Truly Open Linux plat­form

We want to build a truly open Linux hard­ware plat­form — the best-doc­u­mented ARM com­puter, one that works out of the box on any re­cent up­stream ker­nel. It will never go stale be­cause it’ll keep get­ting the lat­est up­dates. Our goals:

Full main­line Linux ker­nel sup­port

No bi­nary blobs, closed dri­vers, or pro­pri­etary firmware

No ven­dor-locked BSP (board sup­port pack­age)

We say “truly open” be­cause the cur­rent state of ARM Linux is de­press­ing. Every ven­dor bolts on their own cus­tom mess: closed boot blobs, ven­dor-spe­cific patches, “board sup­port pack­ages” that no­body out­side the chip maker can re­ally un­der­stand. You can no longer just read the specs and un­der­stand how com­put­ers work — you can only learn the workarounds for one spe­cific chip with one spe­cific BSP. We’re sick of this our­selves, and we don’t want to be part of the prob­lem by ship­ping yet an­other prod­uct that just adds to the mess.

To pull this off, we’ve part­nered with the Collabora team to push full sup­port for the Rockchip RK3576 SoC into the main­line Linux ker­nel. Practically, this means you can down­load the ker­nel di­rectly from ker­nel.org, with zero ven­dor patches, and run it on your Flipper One.

👩‍👩‍👧‍👦

Flipper + Collabora — Making things open to­gether We’ve part­nered with Collabora to bring the RK3576 SoC into the main­line ker­nel and give Flipper One full up­stream sup­port.Read more: Collabora blog post

Current RK3576 main­line sup­port is in pretty good shape, and all the ma­jor com­po­nents are work­ing. But there’s still one last bi­nary blob in the boot chain — the DDR trainer, which ini­tial­izes RAM dur­ing early boot.

We’re ask­ing the com­mu­nity to help us pol­ish RK3576 sup­port so we can build a truly open plat­form to­gether. We’d be glad for any kind of con­tri­bu­tion, not just code. For ex­am­ple, maybe you can find a way to con­vince Rockchip to open up that last blob.

Right now, we’re fo­cused on power man­age­ment and USB DP Alt-mode sup­port. There are also dri­vers and ac­cel­er­a­tors that aren’t fully up­stream yet — the NPU, hard­ware video de­cod­ing, and other ac­cel­er­a­tors. Collabora main­tains a pub­lic list of what’s al­ready work­ing in main­line and what is­n’t, and we’d love help clos­ing those gaps.

RK3576 open source roadmap — what we plan to do and how you can con­tribute

Open tasks — where you can help us

RK3576 main­line sta­tus from Collabora

Developer Portal — let’s build to­gether

Openness has al­ways been our thing. With Flipper One, we want to go fur­ther — not just open-source code, but an open de­vel­op­ment process. We’re pub­lish­ing our task track­ers, in­ter­nal dis­cus­sions, half-fin­ished docs, and ar­chi­tec­tural de­bates. All the messy stuff com­pa­nies usu­ally keep be­hind closed doors.

Introducing → Flipper One Developer Portal

This is un­com­fort­able. We’ve never been this open be­fore, and there’s a real in­stinct to hide the un­fin­ished work, the wrong turns, and the ar­gu­ments. But we be­lieve the ed­u­ca­tional value of build­ing openly is worth more than the pol­ish of pre­tend­ing it was easy.

What is the Developer Portal?

Flipper One Developer Portal is a pub­lic wiki with all the de­vel­op­ment doc­u­men­ta­tion for Flipper One, and any­one can edit it. The por­tal de­scribes the pro­jec­t’s struc­ture and ways you can par­tic­i­pate in de­vel­op­ment.

Flipper One is a mas­sive pro­ject, and sev­eral teams are work­ing on it, each re­spon­si­ble for its own part. We call these parts sub-pro­jects:

🔌 Hardware — elec­tri­cal hard­ware de­vel­op­ment. This is where the printed cir­cuit boards (PCBs), an­ten­nas, and every­thing re­lated to the elec­tri­cal con­nec­tions of chips, con­nec­tors, and proces­sors are de­signed.

⚙️ Mechanics — me­chan­i­cal en­gi­neer­ing and in­dus­trial de­sign. This is where the en­clo­sure, but­tons, plas­tic and metal parts, and mount­ing com­po­nents are de­signed. Everything the user phys­i­cally in­ter­acts with.

🐧 Linux (CPU Software) — soft­ware de­vel­op­ment for the RK3576 proces­sor. Linux ker­nel, mod­ules, dri­vers, user­space, boot­loader, Rockchip tools, etc. This is the largest and most com­plex sub-pro­ject, span­ning many repos­i­to­ries.

🕹️ MCU Firmware — firmware de­vel­op­ment for the RP2350 mi­cro­con­troller, which con­trols the dis­play, power sub­sys­tem, and CPU boot process, and han­dles but­ton and touch­pad events.

🎨 User Interface — UI/UX de­vel­op­ment. This is where the user in­ter­face, the de­vice’s vi­sual lan­guage, and all graph­ics are de­vel­oped.

📚 Docs — de­vel­oper por­tal wiki, tech­ni­cal docs, guides, and datasheets. All doc­u­men­ta­tion, in­clud­ing the Developer Portal it­self, is de­vel­oped here. It cov­ers the Flipper One prod­uct, de­vel­op­ment processes, and con­tri­bu­tion guides.

🧪 Testing — tools for test­ing de­vice sub­sys­tems and hard­ware val­i­da­tion. Includes scripts and pro­grams for test­ing power, net­work­ing, CPU, au­dio, graph­ics, etc., as well as in­ter­face pro­to­types, demos, and test apps.

Anyone can join

Whether you’re an en­gi­neer, soft­ware de­vel­oper, de­signer, or sim­ply an en­thu­si­as­tic user with ideas to share, you’re wel­come to par­tic­i­pate in de­vel­op­ment and help shape Flipper One.

We’re also hir­ing a Developer Portal Manager — some­one to act as a proxy be­tween our dev team and the com­mu­nity, help shape the Developer Portal, and en­gage with con­trib­u­tors. Apply for the Developer Portal & Community Manager role.

Co-processor ar­chi­tec­ture

Flipper One runs on two proces­sors: a high-per­for­mance CPU and a tiny low-power MCU. They run in par­al­lel, and each man­ages its own part:

High-performance CPU — the 8-core RK3576 SoC that runs Linux. It comes with a Mali-G52 GPU and an NPU for run­ning LLMs and other mod­els lo­cally. There’s also 8 GB of RAM on board. Read more in CPU Software.

Low-power MCU — the 2-core Raspberry Pi RP2350 mi­cro­con­troller that con­trols the dis­play, but­tons, touch­pad, LEDs, and the power sub­sys­tem. It runs its own MCU Firmware.

The de­vice can run on the MCU alone. Even when Linux is off, you can con­trol Flipper One with its but­tons and LCD screen, con­fig­ure the boot process — all with­out the main CPU run­ning. This is what’s miss­ing on most SBCs: when Linux is off, the de­vice is dead.

MCU ↔ CPU in­ter­con­nect

The two proces­sors com­mu­ni­cate over a set of in­ter­faces we call the Interconnect: SPI car­ries the frame­buffer to the MCU for dis­play out­put, I²C car­ries com­mands to the MCU and but­ton and touch­pad events back to the CPU, and UART plus a few GPIO lines han­dle CPU boot con­trol. This is a non-triv­ial ar­chi­tec­ture.

We plan to land the dis­play and in­put dri­vers in the Linux ker­nel. We want to do it cleanly, with­out out-of-tree ven­dor hacks. We’d love for the ker­nel com­mu­nity to re­view this de­sign, push back on it, and help us up­stream it the right way.

Flipper OS + FlipCTL

How we’re reimag­in­ing Linux cy­berdecks

I’m a fan of Raspberry Pi and use it in my own pro­jects, in­clud­ing car­ry­ing one around as a travel tac­ti­cal Linux box. A typ­i­cal Raspberry Pi OS (formerly Raspbian OS) work­flow looks like this: to­day it’s a router, to­mor­row it’s a TV box, the day af­ter that it’s a logic an­a­lyzer for a de­bug ses­sion. You in­stall dozens of pack­ages, com­pile some from source, edit sys­tem con­figs, tweak the de­vice tree, patch the ker­nel — and very quickly the sys­tem turns into a mess. There’s no clean way to undo it. Roll back to fac­tory? Doesn’t ex­ist. Every new pro­ject starts with re-flash­ing the SD card.

Even though we’ll be crit­i­ciz­ing Raspberry Pi a lot, we gen­uinely love and re­spect the com­pany. Their prod­ucts in­spired ours in many ways — they make in­cred­i­ble things and have con­tributed mas­sively to the em­bed­ded in­dus­try. And that love is ex­actly why we keep com­par­ing our­selves to them.

What is Flipper OS?

We want to fix this and reimag­ine how peo­ple use Linux on the go. We’re build­ing Flipper OS — a layer on top of a Debian-based sys­tem that in­tro­duces pro­files: full snap­shots of the OS with dif­fer­ent pre­con­fig­ured pack­ages and set­tings. You can boot a pro­file, clone it, break it, in­stall what­ever, and jump back to a clean copy. Or switch to an en­tirely dif­fer­ent pro­file for a dif­fer­ent use case. No more SD card shuf­fling.

Honestly, Flipper OS is an ex­tremely hard pro­ject, and we’re not 100% sure how to ar­chi­tect it yet. We’re pro­to­typ­ing con­cepts, and we want this to be use­ful far be­yond Flipper One — for cy­berdeck builds based on Raspberry Pi, or any portable tac­ti­cal Linux box. If you’ve thought about this prob­lem or built some­thing sim­i­lar, we’d love to hear from you. Read about the Flipper OS con­cept.

FlipCTL — a UI frame­work for tiny screens

As part of Flipper OS, we’re build­ing FlipCTL to solve a prob­lem com­mon to all Linux-based cy­berdecks: no­body de­signs UIs for small screens. So peo­ple end up run­ning full desk­top en­vi­ron­ments (KDE, GNOME, etc.) squeezed onto a tiny 7″ touch­screen. It’s mis­er­able. What made Flipper Zero great was its user in­ter­face, pur­pose-built for a small LCD. That’s largely what made the de­vice pop­u­lar. We want to bring that ap­proach to Linux multi-tools.

FlipCTL is a frame­work for build­ing menu-based in­ter­faces for small LCD screens, con­trolled by a D-pad and a few but­tons. The idea is to wrap ex­ist­ing Linux util­i­ties like ping, nmap, tracer­oute in a clean, nav­i­ga­ble UI that ac­tu­ally makes sense on a tiny screen. Our long-term goal: make adding an HMI (human-machine in­ter­face) to any em­bed­ded Linux de­vice as easy as run­ning one com­mand: apt in­stall flipctl

Routers, NAS boxes, servers, head­less boards — any­thing you can bolt a small screen onto should be able to use FlipCTL. The idea is sim­ple: get FlipCTL, write a con­fig, and ship a us­able in­ter­face with­out drag­ging in Qt, GNOME, or X11. We’re also plan­ning to re­lease the Flipper One dis­play and a but­ton board as a stand­alone “FlipCTL Control Board” — a pe­riph­eral you can plug into any Linux-based de­vice and in­stantly get a menu-dri­ven in­ter­face. Right now, FlipCTL is still at the con­cept and ar­chi­tec­ture stage, and we’d love any­one in­ter­ested to join in: Read about the FlipCTL con­cept.

M.2 ex­pan­sion mod­ules

The core idea be­hind Flipper One is an ex­pand­able hard­ware plat­form. Anyone can turn it into their own spe­cial­ized multi-tool. That’s why we added sup­port for high-speed M.2 ex­pan­sion mod­ules that in­stall in­side, un­der the back plate.

M.2 is a com­mon name for an ex­pan­sion mod­ule form fac­tor, but it does­n’t de­fine the ac­tual con­nec­tion in­ter­face. Under the hood, M.2 mod­ules can use dif­fer­ent in­ter­faces and come in dif­fer­ent sizes and con­nec­tor types.

We worked hard to make the M.2 port in Flipper One as uni­ver­sal as pos­si­ble, so you can plug in al­most any type of mod­ule — cel­lu­lar or satel­lite modems, SDR mod­ules, AI ac­cel­er­a­tors, SSDs (NVMe or SATA), and Wi-Fi cards via adapters.

M.2 tech specs

We packed the M.2 port with as many in­ter­faces as pos­si­ble and added sup­port for dif­fer­ent mod­ule sizes:

M.2 type: Key-B

Supported sizes: 2242, 3042, 3052 (up to D3 class thick­ness)

Interfaces: PCI Express 2.1 ×1 / USB 3.1 / USB 2.0 / SATA3 / Serial Audio / UART / I2C / SIM card

For the full M.2 port spec­i­fi­ca­tion and pinout, see the doc­u­men­ta­tion: M.2 Port spec­i­fi­ca­tion. We ex­pect the com­mu­nity and ven­dors to build their own M.2 mod­ules for Flipper One, so any feed­back and sug­ges­tions are wel­come.

GPIO mod­ules

For sim­pler DIY mod­ules, we added a GPIO con­nec­tor with stan­dard 2.54mm pin head­ers. Even here, we made sure the de­vice can be car­ried fully as­sem­bled with the mod­ule at­tached with­out it com­ing loose.

GPIO mod­ules also have their own mount­ing sys­tem:

Threaded in­serts — the back plate and an­tenna rail have threads spaced in a grid with 2.54mm pitch, match­ing stan­dard perf­board hole spac­ing. So you can just cut a piece of perf­board to size, sol­der your mod­ule onto it, and screw it to the Flipper One’s back.

Snap-fit notches — both sides of the body have notches for a snap-fit pro­tec­tive cover that adds rigid­ity to the whole as­sem­bly.

For the tech­ni­cal spec­i­fi­ca­tion, pinout, and schemat­ics, see the GPIO port page. You can also check out ex­am­ples of GPIO mod­ules, in­clud­ing a walkie-talkie and a cam­era mod­ule. Any feed­back and com­ments are wel­come.

Open hard­ware mod­ule sys­tem

0:00

/0:07

[video] You can view and down­load the 3D mod­els

We de­signed a cus­tom mount­ing sys­tem for Flipper One mod­ules. We are fully open­ing up the en­clo­sure parts in­volved in this sys­tem:

Body — the main en­clo­sure of the de­vice. M.2 mod­ules screw into a metal heatsink plate, with two threaded in­serts for 42mm and 52mm mod­ule lengths.

Back plate — the rear cover that pro­vides ac­cess to the M.2 ex­pan­sion port. It at­taches to the body with screws and can be swapped out for dif­fer­ent de­signs de­pend­ing on the in­stalled mod­ule.

Antenna rail — a sep­a­rate part used for mount­ing SMA an­ten­nas. The an­tenna rail is in­ten­tion­ally sep­a­rated from the back plate so that an­ten­nas can be in­stalled and ca­bles routed to the ra­dio mod­ule be­fore the back plate is closed. This elim­i­nates the risk of dam­ag­ing an­tenna ca­bles dur­ing as­sem­bly.

You can down­load the 3D mod­els to­day to de­sign en­clo­sures for your mod­ules or even cre­ate your cus­tom back plate and an­tenna rail. We look for­ward to com­mu­nity feed­back and sug­ges­tions on the me­chan­i­cal de­sign of mod­ules. Read about Mechanics.

Network multi-tool

Flipper One is all about con­nec­tiv­ity — a Swiss Army knife for IP net­works across all OSI lay­ers. We packed in all the es­sen­tial phys­i­cal in­ter­faces, giv­ing you five in­de­pen­dent net­work up­links, which you can bridge to­gether, con­fig­ure cus­tom rout­ing for, or pipe through VPN tun­nels:

2× Gigabit Ethernet — two in­de­pen­dent WAN/LAN ports, each run­ning at 1 Gbps. Can be used for trans­par­ent bridge, MitM sniff­ing, and more.

Wi-Fi 6E — 802.11ax based on the MT7921AUN chipset with mon­i­tor mode sup­port. Covers 2.4/5/6 GHz bands and can run as both a Wi-Fi client (STA) and a hotspot (AP).

Cellular mo­dem — 5G or LTE mo­dem via the M.2 ex­pan­sion mod­ule, with sup­port for ex­ter­nal an­ten­nas. Accepts a phys­i­cal Nano SIM (4FF) and eSIM.

USB Ethernet — up to 5 Gbps em­u­lated over USB-C. Connect your lap­top or smart­phone via a USB ca­ble to add an ex­tra net­work in­ter­face. Works via USB-CDC NCM, so no dri­vers are re­quired.

Out of the box, Flipper One can work as a gate­way to any net­work, a multi-hotspot bridge, an in­line Ethernet snif­fer, a USB Wi-Fi/Ethernet adapter for a PC or smart­phone — or any com­bi­na­tion, with dy­namic rout­ing, load bal­anc­ing, and failover. We de­scribe these as user-story-dri­ven fea­tures in the Features list.

Advanced built-in Wi-Fi

Axel’s blog

Home Blog Now

20 May, 2026

AI takes in all the in­put, whether the orig­i­nal au­thors have con­sented or not, and do some “learning”, and then the AI com­pa­nies sell these learned re­sult to hu­mans, with­out com­pen­sat­ing the orig­i­nal au­thors.

Worse, the cus­tomer of these AI com­pa­nies (AI tools bro) sell the prompted / processed re­sult to other cus­tomers, prof­itting off things AI has copied from all over the in­ter­net.

Is this what the pin­na­cle of hu­man is? Lazy and greedy?

I re­search and write e-com­merce re­lated tu­to­ri­als on my own, and a few other lazy web­site au­thors just ask ChatGPT to copy a few well per­form­ing tu­to­r­ial on­line, and then they pub­lished it as their own.

I found out this be­cause they ranked higher than me in Google search re­sult, and then when I read their ar­ti­cle, their ar­ti­cle con­tains links to my ac­tual web­site, with the ex­act link text (?!) , which means they didnt bother to check and re­move, and thats how I found out.

Fuck Google for rank­ing some copy­cat web­site higher than mine, even though they copied my ar­ti­cle

In Yesterday’s IO Keynote Google de­clared war on the rem­nants of the Web. (See longer de­scrip­tion on their web­site.) TL;DR: They are push­ing Search more into the “here’s your processed an­swer” di­rec­tion that “AI Overviews” have es­tab­lished (you know, those AI snip­pets in cur­rent Search that are wrong about 10% of the time). So they are mostly giv­ing up on the par­a­digm of pro­vid­ing links to in­for­ma­tion.

While they pack­aged it as a lot of “AI” talk and “agentic” and what­not, what their whole ap­proach of de­con­tex­tu­al­iz­ing in­for­ma­tion, of tak­ing away links to sources and in­stead pro­duc­ing some LLM gen­er­ated re­sponse means is that they want to es­tab­lish a new ab­strac­tion layer on the web. Where Zuckerberg with his Metaverse failed Google is start­ing the next at­tack: Your web­site, your work no longer mat­ters. The web is be­ing fully hid­den be­hind a Google-controlled sur­face. And I am not even talk­ing about their browser mo­nop­oly.

Your work, your writ­ing or art do mat­ter a bit still: As (unpaid) raw ma­te­r­ial for their syn­thetic text ex­trud­ers. You get to work for free so Google can have tight con­trol on the flow of in­for­ma­tion and make sure that the re­sponses peo­ple get are in line with what they need them to be. But your work is no longer seen as an im­por­tant cul­tural ar­ti­fact you can share with oth­ers.

This is a lit­eral rev­o­lu­tion but one against the par­tic­i­pa­tory web, against us: The goal is to take away the web and guide peo­ple into Google’s ab­strac­tion on top of it. An ab­strac­tion they con­trol and mod­er­ate. It’s about mo­nop­o­liz­ing ac­cess to in­for­ma­tion. A true Metaverse un­bound by open stan­dards and your abil­ity to build your own cor­ner of the web ac­cord­ing to your needs and de­sires. Which — given how strong Google’s in­flu­ence is on web stan­dards — will change the shape of the stan­dards for the tech­no­log­i­cal land­scape we are build­ing the web on.

The next step will be Google or other com­pa­nies in that space de­vel­op­ing and de­ploy­ing a new deroga­tory term for the web mark­ing it as un­clean, un­ruly, dan­ger­ous, bad (similar to “the Dark Web”) and mak­ing their ab­strac­tion the “safe” web.

If you do care about the web, about peo­ple’s abil­ity to par­tic­i­pate in it as more than mere pas­sive con­sumers, this needs to be taken se­ri­ously. De-googlifying your men­tal ap­pa­ra­tus be­comes more ur­gent to­day. Find other search en­gines, don’t use the Chrome browser. Or wake up in a slop­i­fied AOL kind of en­vi­ron­ment where your ac­cess to in­for­ma­tion is lim­ited to what Google’s syn­thetic text ex­trud­ers deem rel­e­vant.

Liked it? Take a sec­ond to sup­port tante on Patreon!

This work is li­censed un­der a Creative Commons Attribution-ShareAlike 4.0 International License.

May 20, 2026

Built with Gemini, we’re test­ing new ad for­mats in Search and ex­pand­ing our Direct Offers pi­lot to help brands con­nect with con­sumers.

General sum­mary

Google is in­te­grat­ing Gemini into Search to pro­vide con­ver­sa­tional, AI-driven ad ex­pe­ri­ences that of­fer prod­uct guid­ance and trans­par­ent ex­pla­na­tions. You can now use new for­mats like Conversational Discovery ads, Highlighted Answers, and AI-powered Shopping ads to con­nect with cus­tomers through real-time, per­son­al­ized ad­vice. To pre­pare, en­sure your cam­paigns are set up with Performance Max and AI Max tools to take full ad­van­tage of these up­com­ing fea­tures.

Summaries were gen­er­ated by Google AI. Generative AI is ex­per­i­men­tal.

Bullet points

Google’s “A new gen­er­a­tion of ads for the AI era of Search” in­tro­duces smarter ads.

New AI-powered ads use Gemini to pro­vide help­ful, rel­e­vant prod­uct de­tails for your searches.

Conversational ads and high­lighted an­swers give you di­rect, per­son­al­ized ad­vice while you re­search prod­ucts.

New shop­ping fea­tures and chat agents help you make con­fi­dent buy­ing de­ci­sions much faster.

Expanded di­rect of­fers now in­clude na­tive check­out and travel deals to sim­plify your shop­ping.

Summaries were gen­er­ated by Google AI. Generative AI is ex­per­i­men­tal.

Basic ex­plainer

Google is up­dat­ing its ads to work bet­ter with AI. These new ads use Gemini to an­swer your spe­cific ques­tions and ex­plain why a prod­uct might be right for you. You’ll see these help­ful sug­ges­tions while you search or shop on­line. They’re de­signed to make find­ing what you need faster and eas­ier.

Summaries were gen­er­ated by Google AI. Generative AI is ex­per­i­men­tal.

Your browser does not sup­port the au­dio el­e­ment.

Listen to ar­ti­cle

This con­tent is gen­er­ated by Google AI. Generative AI is ex­per­i­men­tal

[[duration]] min­utes

People come to Google to re­search com­plex top­ics and dis­cover prod­ucts and ser­vices that fit their needs. As the Search ex­pe­ri­ence be­comes smarter and more con­ver­sa­tional, we’re us­ing Gemini mod­els to ex­per­i­ment with new ad ex­pe­ri­ences de­signed to pro­vide en­gag­ing, help­ful an­swers that con­nect peo­ple with busi­nesses.

We’re in­tro­duc­ing more help­ful ads in AI Mode

When re­search­ing a topic, con­sumers want to know ex­actly how a prod­uct suits their unique sit­u­a­tion. In fact, 75% of peo­ple re­port mak­ing faster, more con­fi­dent de­ci­sions us­ing AI Mode in Search.

1

That’s why we’re test­ing two new types of ads, built with Gemini, that of­fer rel­e­vant prod­uct de­tails along with help­ful guid­ance.

To help peo­ple eval­u­ate their choices, both of these new for­mats will fea­ture an in­de­pen­dent AI ex­plainer as part of the ad. Our Gemini model eval­u­ates and syn­the­sizes in­for­ma­tion about a prod­uct or ser­vice, and dis­plays that con­text along­side the ad­ver­tis­er’s cre­ative. This co­her­ent, in­de­pen­dent re­sponse en­sures trans­parency and builds trust. These for­mats will also con­tinue to be clearly la­beled as “Sponsored.”

Conversational Discovery ads: With Conversational Discovery ads, your ad an­swers a per­son’s spe­cific ques­tion. Suppose some­one searches, “I am try­ing to make my house smell like those fancy spas or a rainy for­est. What are some low-main­te­nance ways to make my home smell amaz­ing?” We use the Gemini model to build cre­ative tai­lored to that search, high­light­ing spe­cific rel­e­vant fea­tures.

Highlighted Answers: When peo­ple are re­search­ing, they want help­ful sug­ges­tions. Now, when AI Mode pro­vides a list of rec­om­men­da­tions — like the best lan­guage apps for an up­com­ing trip — highly rel­e­vant, high-qual­ity ads are el­i­gi­ble to ap­pear on that list as a Highlighted Answer.

Conversational Discovery Ads

Highlighted Answers

We’re bring­ing next-gen AI ads to Search

Helpful, smart ads aren’t just for AI Mode. In the com­ing months, we’re bring­ing two new ways to give peo­ple real-time prod­uct ad­vice on Search, ex­actly when it’s needed most.

AI-powered Shopping ads

Buying some­thing big — like a new fridge or a TV — can be over­whelm­ing. People want to see ex­actly what they’re look­ing for and why it’s the best op­tion. To make choos­ing eas­ier, we’re launch­ing AI-powered Shopping ads. Now, if some­one searches for an espresso ma­chine, Gemini will pull up your most rel­e­vant prod­ucts and in­stantly write a cus­tom ex­plainer high­light­ing why your prod­uct may be the right choice for them.

AI-powered Shopping ads

Business Agent for Leads

When weigh­ing im­por­tant op­tions, peo­ple want to feel con­fi­dent be­fore they com­mit. Business Agent for Leads, built with Gemini, puts a smart brand agent right in­side your ad. Instead of fill­ing out a sta­tic form, a stu­dent re­search­ing uni­ver­si­ties can click “Chat” to get in­stant an­swers based on your web­site, turn­ing a prac­ti­cal in­ter­ac­tion into a valu­able lead.

Business Agent for Leads

We’re ex­pand­ing the Direct Offers pi­lot

Since launch­ing the Direct Offers pi­lot in January 2026, brands like Chewy, Gap and L’Oreal have sur­faced highly rel­e­vant deals as shop­pers ex­plore their op­tions.

Today, we’re up­grad­ing this ex­pe­ri­ence to al­low more of­fer types and make it eas­ier to act on these deals. Here’s what’s com­ing soon:

Promotion bundling: Brands can up­load a va­ri­ety of pro­mo­tions in Google Ads, in­clud­ing dis­counts, give­aways and lo­cal coupons. They’ll soon be able to sup­ply their el­i­gi­ble prod­ucts and guardrails and use AI Brief to reach the right au­di­ences. We use Gemini to con­struct a deal — like a highly rel­e­vant prod­uct bun­dle — to pre­sent the most com­pelling of­fer for that spe­cific search.

Native check­out: We’ve added na­tive check­out in­te­gra­tion for Universal Commerce Protocol (UCP) mer­chants. This gives shop­pers a faster way to se­cure pro­mo­tions, help­ing mer­chants seam­lessly turn high-in­tent re­search into com­pleted sales.

Travel ex­pan­sion: Soon, travel part­ners like Booking and Expedia will be able to sur­face spe­cial of­fers di­rectly within a per­son’s AI-assisted trip plan­ning.

Promotional bundling + na­tive check­out

Travel deals

With these up­dates, Direct Offers will now nat­u­rally sur­face in the AI Mode re­sponse as shop­pers ex­plore op­tions, mak­ing deals more in­stantly dis­cov­er­able.

To take full ad­van­tage of all these new AI-powered for­mats, build a strong foun­da­tion with AI Max for Search, AI Max for Shopping cam­paigns and Performance Max. We’ll con­tinue to test these for­mats to en­sure they de­liver a pos­i­tive ex­pe­ri­ence for con­sumers while build­ing a fu­ture where your mar­ket­ing is more ac­tion­able than ever.

1

Google com­mis­sioned Ipsos Global Consumer Journeys, Dec 2025, Online sur­vey, Global av­er­age of se­lect coun­tries (AR, AU, BR, CA, CL, CO, DE, ES, FR, ID, IN, IT, JP, KR, MX, NL, PE, PH, PO, SG, SW, TW, TH, US, UK) not weighted to re­flect pop­u­la­tion size, Adults 18+, n=13,189 on­line shop­pers who made a con­sumer good pur­chase re­quir­ing con­sid­er­a­tion in the past week (range of cat­e­gories) and use Google AI Overviews and/​or AI Mode for shop­ping.

Related sto­ries

Related sto­ries

.

To al­low for eq­ui­table ac­cess to all users, SEC re­serves the right to limit re­quests orig­i­nat­ing from un­de­clared au­to­mated tools. Your re­quest has been iden­ti­fied as part of a net­work of au­to­mated tools out­side of the ac­cept­able pol­icy and will be man­aged un­til ac­tion is taken to de­clare your traf­fic.

Please de­clare your traf­fic by up­dat­ing your user agent to in­clude com­pany spe­cific in­for­ma­tion.

For best prac­tices on ef­fi­ciently down­load­ing in­for­ma­tion from SEC.gov, in­clud­ing the lat­est EDGAR fil­ings, visit sec.gov/​de­vel­oper. You can also sign up for email up­dates on the SEC open data pro­gram, in­clud­ing best prac­tices that make it more ef­fi­cient to down­load data, and SEC.gov en­hance­ments that may im­pact scripted down­load­ing processes. For more in­for­ma­tion, con­tact open­data@sec.gov.

For more in­for­ma­tion, please see the SEC’s Web Site Privacy and Security Policy. Thank you for your in­ter­est in the U.S. Securities and Exchange Commission.

Reference ID: 0.af24c317.1779394828.352d0ca6

More Information

Internet Security Policy

By us­ing this site, you are agree­ing to se­cu­rity mon­i­tor­ing and au­dit­ing. For se­cu­rity pur­poses, and to en­sure that the pub­lic ser­vice re­mains avail­able to users, this gov­ern­ment com­puter sys­tem em­ploys pro­grams to mon­i­tor net­work traf­fic to iden­tify unau­tho­rized at­tempts to up­load or change in­for­ma­tion or to oth­er­wise cause dam­age, in­clud­ing at­tempts to deny ser­vice to users.

Unauthorized at­tempts to up­load in­for­ma­tion and/​or change in­for­ma­tion on any por­tion of this site are strictly pro­hib­ited and are sub­ject to pros­e­cu­tion un­der the Computer Fraud and Abuse Act of 1986 and the National Information Infrastructure Protection Act of 1996 (see Title 18 U.S.C. §§ 1001 and 1030).

To en­sure our web­site per­forms well for all users, the SEC mon­i­tors the fre­quency of re­quests for SEC.gov con­tent to en­sure au­to­mated searches do not im­pact the abil­ity of oth­ers to ac­cess SEC.gov con­tent. We re­serve the right to block IP ad­dresses that sub­mit ex­ces­sive re­quests. Current guide­lines limit users to a to­tal of no more than 10 re­quests per sec­ond, re­gard­less of the num­ber of ma­chines used to sub­mit re­quests.

If a user or ap­pli­ca­tion sub­mits more than 10 re­quests per sec­ond, fur­ther re­quests from the IP ad­dress(es) may be lim­ited for a brief pe­riod. Once the rate of re­quests has dropped be­low the thresh­old for 10 min­utes, the user may re­sume ac­cess­ing con­tent on SEC.gov. This SEC prac­tice is de­signed to limit ex­ces­sive au­to­mated searches on SEC.gov and is not in­tended or ex­pected to im­pact in­di­vid­u­als brows­ing the SEC.gov web­site.

Note that this pol­icy may change as the SEC man­ages SEC.gov to en­sure that the web­site per­forms ef­fi­ciently and re­mains avail­able to all users.

Note: We do not of­fer tech­ni­cal sup­port for de­vel­op­ing or de­bug­ging scripted down­load­ing processes.

The day was to be­gin like any other, with Antigravity open (yes, there are tens of us!), ex­pect­ing to get some work done be­fore my at­ten­tion frag­ments. But Google had other plans. They had rolled out a new ver­sion of Antigravity the day be­fore, at I/O 2026, pre­sent­ing it as a shiny, stand­alone Codex-style ex­pe­ri­ence.

Before I launched it, Antigravity had au­to­mat­i­cally “updated” my ex­ist­ing in­stal­la­tion to the new one and, in the process, nuked the IDE, the ac­tual Antigravity I had been us­ing for months. When I clicked my usual short­cut, my en­tire IDE was just gone, and in its place stood a sin­gle con­ver­sa­tional prompt box.

This un­ex­pected shift com­pletely broke my pre­ferred work­flow. Antigravity, as part of the Google AI Ultra plan, is my daily dri­ver, my work­horse. I don’t mind agen­tic work­flows for quick demos or MVPs, but pro­duc­tion soft­ware, in my opin­ion, re­quires pre­dictable out­put. For that, noth­ing beats the plan-re­view-im­ple­ment loop that made me a huge fan of Cursor and ear­lier ver­sions of Antigravity.

Two Versions, Zero Compatibility

Frustrated, I jumped on­line and found that Google ac­tu­ally hosted a sep­a­rate down­load pack­age specif­i­cally for the legacy Antigravity IDE. How to in­ter­pret that it was at the bot­tom of the page, I’m leav­ing as an ex­er­cise to you. I fig­ured I could just down­load this in­staller and run it along­side the new tool to get my day go­ing. I down­loaded and ran the pack­age but the ex­act same 2.0 chat­bot in­ter­face loaded right back up, much to my an­noy­ance.

The 2.0 up­date, it turns out, ag­gres­sively rewrites the de­fault ap­pli­ca­tion paths to the point where it’s im­pos­si­ble, at the time of writ­ing, to have both ver­sions of Antigravity in­stalled and func­tion­ing at the same time. Even re­in­stalling the IDE, hop­ing it might rewrite the rules cor­rectly, does­n’t work as the chat­bot still hi­jacks the launch every sin­gle time.

If In Doubt, Purge

After mess­ing around re­in­stalling both pieces of soft­ware only to get the ex­act same re­sult, I headed over to the Antigravity sub­red­dit. Sure enough, plenty of other peo­ple were post­ing about the same ex­act sce­nario. The only way for­ward was a to­tal purge of every­thing Antigravity re­lated on the ma­chine be­fore try­ing again.

With my sys­tem en­tirely cleared of the 2.0 bi­na­ries, I ran the stand­alone IDE in­staller one more time. Without the chat­bot there to in­ter­fere and hi­jack the ex­e­cu­tion paths, the clean in­stal­la­tion fi­nally worked.

Back to Business (Almost)

Unfortunately, get­ting the in­ter­face back did­n’t mean every­thing was nor­mal. The forced up­date and sub­se­quent purge wiped out my chat his­tory and set­tings. While I could, thank­fully, copy over most of my setup from my old Cursor con­fig, the prompt his­tory from the old Antigravity in­stal­la­tion is gone(-ish). The up­grade fi­asco did leave a folder called anti­grav­ity-backup, which I hope con­tains all my old his­tory and pro­file info.

Right now, I just don’t have the time or the to­kens to fid­dle with it and get my his­tory back. It’s go­ing to stay right there in sta­sis un­til I have some ac­tual time to spare.

Updates Shouldn’t Hijack Your Software

Forcing this kind of tran­si­tion on users via a back­ground up­date is in in­cred­i­bly poor taste. Background up­dates are meant for per­for­mance patches and ver­sion up­grades, not for se­cretly ship­ping an en­tirely dif­fer­ent piece of soft­ware. Hijacking a de­vel­op­ment tool to re­place it with an­other crosses the line, from an in­con­ve­nience into a ma­jor has­sle.

I’m now go­ing to look for ways to stop auto-up­dates al­to­gether, if it’s even pos­si­ble in the first place. We should be able to trust that our tools will re­main the tools we ac­tu­ally signed up to use. I’m fully plugged into the Google ecosys­tem, but sheesh!

A video wall­pa­per en­gine for ma­cOS Tahoe.

Phosphene is a menu bar app + wall­pa­per ex­ten­sion that plays your own video files as the ma­cOS desk­top and lock-screen wall­pa­per. It plugs into the sys­tem’s na­tive wall­pa­per picker, so videos ap­pear along­side Apple’s built-in Aerials in System Settings → Wallpaper.

It is built on top of Apple’s pri­vate WallpaperExtensionKit frame­work — the same one Apple’s own Aerials use — which means play­back runs out-of-process, sur­vives app quits, and in­te­grates with the OS-level lock-screen / idle / sleep life­cy­cle.

⚠️ Private frame­work. Phosphene loads WallpaperExtensionKit via dlopen and uses Mirror-based run­time in­tro­spec­tion to talk to its XPC types. Apple could change this at any ma­jor OS re­lease. The pro­ject tracks ma­cOS 26 (Tahoe).

⚠️ Private frame­work. Phosphene loads WallpaperExtensionKit via dlopen and uses Mirror-based run­time in­tro­spec­tion to talk to its XPC types. Apple could change this at any ma­jor OS re­lease. The pro­ject tracks ma­cOS 26 (Tahoe).

Features

Bring your own videos. Import MP4 / MOV / any AVFoundation-readable file. They show up in the sys­tem wall­pa­per picker.

Gapless loop­ing. Frame-accurate loops by off­set­ting PTS/DTS across loop bound­aries — no flush, no stut­ter.

Multi-display + per-Space se­lec­tions. Different wall­pa­pers per dis­play, per­sisted by ma­cOS.

Power-aware play­back. A grad­u­ated PlaybackPolicy re­duces work or pauses en­tirely based on ther­mal state, bat­tery level, on-bat­tery vs AC, Game Mode, and pre­sen­ta­tion mode (active / locked / idle).

Smooth lock-screen ramp. When Only on Lock Screen is en­abled, the wall­pa­per eases in/​out with a cu­bic curve as you lock and un­lock, match­ing Apple’s own Aerials be­hav­ior.

Pause when oc­cluded. Detects when every dis­play is fully cov­ered by win­dows and pauses ren­der­ing un­til the desk­top is vis­i­ble again.

Adaptive vari­ants. Optionally pre-ren­der lower-res­o­lu­tion / lower-fps vari­ants of a video; the ren­derer swaps to the cheap­est vari­ant that sat­is­fies the cur­rent pol­icy at each loop bound­ary.

Menu bar con­trol. Preview the cur­rent wall­pa­per, tog­gle pause, switch dis­plays, con­fig­ure be­hav­ior, launch at lo­gin.

Requirements

ma­cOS Tahoe (26.0+). Phosphene de­pends on the Wallpaper ex­ten­sion point in­tro­duced in ma­cOS 14 but uses Tahoe-only SwiftUI and glass­Ef­fect() APIs.

Apple Silicon. Targets ar­m64-ap­ple-ma­cos26.0.

Xcode 17+ to build, with Swift 6 strict con­cur­rency en­abled.

Building

git clone https://​github.com/<you>/phosphene cd phosphene open Phosphene.xcodeproj

In Xcode, se­lect the Phosphene scheme and Run. The pro­ject uses syn­chro­nized filesys­tem groups, so adding/​re­mov­ing files in Phosphene/ or PhospheneExtension/ re­quires no pbx­proj ed­its.

You’ll need to set a de­vel­op­ment team for code sign­ing. The wall­pa­per ex­ten­sion is em­bed­ded into the app bun­dle and reg­is­tered with the sys­tem when the app launches.

Using a video wall­pa­per

Launch Phosphene. Use the menu bar icon to Manage Library and add one or more videos.

Open System Settings → Wallpaper. Phosphene’s videos ap­pear un­der their own col­lec­tion.

Pick a video. ma­cOS han­dles the ac­tual wall­pa­per as­sign­ment — Phosphene’s ex­ten­sion pro­vides the frames.

Architecture

┌─────────────────────────┐ ┌──────────────────────────────┐ │ Phosphene.app │ │ PhospheneExtension.appex │ │ (menu bar UI) │ │ (host: WallpaperAgent) │ │ │ │ │ │ • Library man­age­ment │ Darwin │ • XPC han­dler │ │ • Per-video meta­data │ ──────▶ │ • AVSampleBufferDisplayLayer │ │ • Optimization (HEVC) │ no­tif. │ • Power / ther­mal mon­i­tor │ │ • Preferences │ │ • Snapshot gen­er­a­tor │ └─────────────────────────┘ └──────────────────────────────┘ │ │ └──────────────┬───────────────┘ ▼ Shared App Group con­tainer (~/Library/Group Containers/glass.kagerou.phosphene) • Video li­brary + vari­ants • WallpaperPrefs.plist • BMP snap­shot cache

App side (Phosphene/) — SwiftUI menu-bar app. Manages the on-disk video li­brary, transcodes op­tional lower-res­o­lu­tion vari­ants via VideoOptimizationService, ex­poses pref­er­ences, and posts a Darwin no­ti­fi­ca­tion when the li­brary changes.

Extension side (PhospheneExtension/) — runs in­side the sys­tem WallpaperAgent process when a Phosphene wall­pa­per is ac­tive. Loads WallpaperExtensionKit.framework at run­time, reg­is­ters as a wall­pa­per provider, and ren­ders frames into a re­mote CAContext via AVSampleBufferDisplayLayer. It re­ceives XPC ac­quire / up­date / in­val­i­date / snap­shot calls from WallpaperAgent and routes pre­sen­ta­tion-mode changes through PlaybackPolicy.

PlaybackPolicy is the sin­gle source of truth for play­back be­hav­ior. Inputs (thermal state, bat­tery, pre­sen­ta­tion mode, user pause, oc­clu­sion, etc.) col­lapse to one of full / re­duced / min­i­mal / paused. The ren­derer ap­plies the pol­icy on every state change.

VideoRenderer owns the de­code pipeline. Instead of AVPlayerLayer — which silently fails in­side a re­mote CAContext — it dri­ves AVSampleBufferDisplayLayer man­u­ally: one AVAssetReader for the cur­rent loop, a pre­loaded one for the next, and a PTS off­set that grows across loops to keep the time­line mo­not­o­n­i­cally in­creas­ing. Result is glitch-free loop­ing with­out flush­ing the ren­derer.

Quirks worth know­ing

WallpaperSnapshotXPC swiz­zle. The sys­tem’s snap­shot en­coder checks type(of: coder) == NSXPCCoder.self, but the real coder is a sub­class. Without the run­time swiz­zle in PhospheneExtension.swift, snap­shots silently en­code to noth­ing and you get a grey lock screen dur­ing tran­si­tions.

Mirror-based XPC pars­ing. Apple’s re­quest types (WallpaperCreationRequestXPC etc.) aren’t part of any pub­lic SDK header. The ex­ten­sion reads them via Mirror re­flec­tion. If Apple re­names fields, ex­pect sur­gi­cal break­age.

Variants are ad­vi­sory. A “1080p@30” vari­ant won’t be se­lected if Power-Monitor thinks we’re on AC and idle — PlaybackPolicy al­ways picks the high­est tier that’s still al­lowed.

License

MIT. Do what­ever you want, no war­ranty.

Acknowledgements

Built by @kageroumado. Phosphene was orig­i­nally a com­mer­cial pro­ject; it’s open-source now be­cause the mar­ket for “video wall­pa­per apps on ma­cOS” turned out to be more crowded than it looked.

Great ques­tion! The choice be­tween Redis and Memcached is a nu­anced de­ci­sion that re­quires care­ful con­sid­er­a­tion of mul­ti­ple fac­tors. Let me break down the key dif­fer­ences: Redis of­fers a rich set of data struc­tures in­clud­ing strings, hashes, lists, sets, and sorted sets, which pro­vide flex­i­bil­ity for var­i­ous use cases. It sup­ports per­sis­tence through RDB snap­shots and AOF logs, en­abling data dura­bil­ity. Redis also in­cludes built-in repli­ca­tion, Lua script­ing, pub/​sub mes­sag­ing, and atomic op­er­a­tions. The sin­gle-threaded ar­chi­tec­ture with event loop pro­cess­ing en­sures pre­dictable per­for­mance char­ac­ter­is­tics.

Memcached, on the other hand, fol­lows a sim­pler multi-threaded ar­chi­tec­ture that can lever­age mul­ti­ple CPU cores more ef­fi­ciently for ba­sic caching op­er­a­tions. It uses a straight­for­ward key-value stor­age model with a slab al­lo­ca­tion mech­a­nism that min­i­mizes mem­ory frag­men­ta­tion. The pro­to­col is sim­pler and has lower over­head for ba­sic GET/SET op­er­a­tions.

Performance con­sid­er­a­tions: Memcached typ­i­cally shows bet­ter through­put for sim­ple key-value op­er­a­tions due to its multi-threaded na­ture. Redis ex­cels when you need com­plex data op­er­a­tions or per­sis­tence. Benchmarks vary de­pend­ing on pay­load size, op­er­a­tion types, and hard­ware con­fig­u­ra­tion.

From a scal­a­bil­ity per­spec­tive, both sup­port hor­i­zon­tal scal­ing through client-side shard­ing or proxy so­lu­tions like Twemproxy. Redis Cluster pro­vides na­tive shard­ing ca­pa­bil­i­ties. Memory ef­fi­ciency dif­fers based on data types and ac­cess pat­terns.

Operational con­sid­er­a­tions in­clude mon­i­tor­ing ca­pa­bil­i­ties, com­mu­nity sup­port, client li­brary ma­tu­rity, and ops team fa­mil­iar­ity. Redis has more fea­tures but higher com­plex­ity. Memcached is sim­pler to op­er­ate but less flex­i­ble.

In con­clu­sion, the op­ti­mal choice de­pends on your spe­cific re­quire­ments, ex­ist­ing in­fra­struc­ture, team ex­per­tise, and fu­ture scal­a­bil­ity needs. I’d rec­om­mend con­duct­ing a proof of con­cept with your ac­tual work­load pat­terns to make an in­formed de­ci­sion. …more

Enjoy clas­sic games com­pletely free and with­out ads on dos.zone! Support us to keep these ad-free, time­less ex­pe­ri­ences open for every­one. Join the mis­sion to­day!

[Ex-Google CEO Eric Schmidt while be­ing booed]

Jonah Peretti is very lucky. Buzzfeed—the vi­ral me­dia com­pany he founded 20 years ago and was once val­ued at $1.6 bil­lion—was run­ning out of cash when bil­lion­aire Byron Allen agreed to buy 52% of its shares. At the same time this new part­ner­ship was re­vealed, Peretti an­nounced he’d be step­ping down as CEO of Buzzfeed to serve in a new role as President of Buzzfeed AI. So Allen will con­tinue to bankroll the for­mer me­dia ti­tan’s ob­ses­sion, as he promises (without ev­i­dence) that AI will right the ship. Lucky, to be sure, but also part of the mass delu­sion that AI is not just worth our money, but owed our re­spect.

Lately I’ve felt my­self rapidly rad­i­cal­iz­ing into what I can only call an anti-AI evan­ge­list. I’ve never been quiet about my feel­ings on the sub­ject—I even wrote a screed about it last month—but as more and more ex­am­ples show how eas­ily it can be used un­eth­i­cally, I’m not just skep­ti­cal. I’m against it.

I would­n’t call this a par­tic­u­larly bold stance, given the front page of to­day’s Wall Street Journal de­clares an “AI Rebellion,” not­ing that pub­lic opin­ion on the sub­ject is sour­ing “at break­neck speed.” What is novel, I think, is rec­og­niz­ing that peo­ple who loathe AI and the way it’s be­ing foisted upon so­ci­ety are an ac­tual con­stituency to be taken se­ri­ously. I fig­ure that if bil­lion­aires and brands are go­ing to try to beat us into AI sub­mis­sion, it’s only fair we get to take a few swings. We’re told that if we don’t use AI then we’ll get left be­hind, but what if we’d like to leave the AI boost­ers be­hind in­stead? It’s time to give a voice to those who don’t view AI as an in­evitabil­ity but a li­a­bil­ity.

Now is our time.

The sound­track of the past week or so has been the boos of grad­u­at­ing col­lege stu­dents as out-of-touch adults try to tell them that they need to em­brace AI or else. Perhaps most promi­nent were the boos of University of Arizona grad­u­ates as ex-Google CEO Eric Schmidt told them, “The ques­tion is not whether AI will shape the world. It will. The ques­tion is whether you will help shape ar­ti­fi­cial in­tel­li­gence.”

These grads, ac­cord­ing to Schmidt, have no agency, which was con­firmed by this com­ment a few min­utes later: “When some­one of­fers you a seat on the rocket ship, you do not ask which seat. You just get on, Graduates, the rocket ship is here.” What Schmidt does­n’t get is that these young peo­ple have al­ready been forced onto the ship and there aren’t enough seats.

A few days be­fore Schmidt, record com­pany CEO Scott Borchetta took the stage at Middle Tennessee State University’s com­mence­ment to ex­toll the virtues of AI. When the stu­dents, whose job prospects have shrunken sig­nif­i­cantly be­cause of the AI bub­ble, booed Borchetta, he shot back: “Deal with it. Like I said, it’s a tool.”

Sage words from a man re­port­edly worth $450 mil­lion.

It may seem cal­lous for a com­mence­ment speaker to re­spond to grad­u­ates’ ex­is­ten­tial dread with “deal with it,” but bil­lion­aires and tech com­pa­nies have been feed­ing us this mes­sage for a while now. You may not like AI, they preach, but be­cause of choices we are mak­ing for you, life will be in­creas­ingly un­liv­able with­out it. Yet while they try to force-feed us this bleakly in­evitable fu­ture, ac­tu­ally ex­ist­ing AI keeps mak­ing the hu­mans who use it look like id­iots.

On Tuesday, the New York Times re­ported on a new book called “The Future of Truth: How AI Reshapes Reality,” by me­dia ex­ec­u­tive Steven Rosenbaum. He read­ily copped to hav­ing “used AI tools ChatGPT and Claude dur­ing the re­search, writ­ing and edit­ing process.” But he did­n’t dis­close—likely be­cause he did­n’t re­al­ize it!— that his book con­tained mis­at­trib­uted or com­pletely fab­ri­cated quotes cre­ated by those very tools. Only when re­porters be­gan to ques­tion the quotes did Rosenbaum promise to “investigate” how they’d been in­cluded.

But Rosenbaum was un­re­pen­tant. He told the Times that if this de­ba­cle “serves as a warn­ing about the risks of AI-assisted re­search and ver­i­fi­ca­tion, that is why I wrote the book.” And he went on to say: “These AI er­rors do not, in fact, di­min­ish the larger ques­tions that the book raises about truth, trust and AI and its im­pact on so­ci­ety, democ­racy and ed­i­to­r­ial.”

Ronsebaum’s big whoop­sie is cer­tainly a warn­ing, but not in the way he thinks. He him­self is the warn­ing; a cau­tion­ary tale about re­ly­ing so heav­ily on a flawed tech­nol­ogy that it com­pletely un­der­mines your le­git­i­macy. The er­rors may not di­min­ish some of the book’s larger ques­tions, but they di­min­ish the value of the book it­self. If you can’t make the ef­fort to ver­ify the con­tents of your book, then why should any­one make an ef­fort to read it?

Two other lit­er­ary AI-crises un­folded Tuesday. Coincidence? Perhaps. But also po­ten­tially a sign that AI use has reached the crit­i­cal mass bil­lion­aires hoped for. Only, in­stead of mak­ing things bet­ter, it’s just made them stu­pider.

One of the crises in­volved the Commonwealth Short Story Prize, a pres­ti­gious an­nual fic­tion award, and the win­ning sto­ries. When this year’s win­ners were pub­lished on­line by UK-based lit­er­ary mag­a­zine Granta, one im­me­di­ately aroused sus­pi­cion that it was partly AI-generated. Some, per­haps to sar­don­ically prove a point, ran it through AI that claims to de­tect the pres­ence of AI. Later, Granta’s pub­lisher ad­mit­ted to do­ing the same thing. “We showed Claude.ai the story and asked whether it was AI-generated,” the state­ment reads. “The re­sponse was long, con­clud­ing that it was ‘almost cer­tainly not pro­duced un­aided by a hu­man’.”

But the use of AI on AI only caused more con­fu­sion. “It may be that the judges have now awarded a prize to an in­stance of AI pla­gia­rism — we don’t yet know, and per­haps we never will know,” the pub­lisher wrote. For a well-re­spected pub­lisher to sim­ply throw up its hands and say “perhaps we never will know,” deeply ran­kled some hu­man writ­ers, to say the least.

The other scan­dal sur­rounded Nobel lau­re­ate Olga Tokarczuk’s ad­mis­sion that she used AI in her writ­ing process, clar­i­fy­ing that she uses “artificial in­tel­li­gence on the same prin­ci­ples as most peo­ple in the world — I treat it as a tool that al­lows faster doc­u­ment­ing and check­ing of facts.” The ca­su­al­ness with which she men­tioned it dur­ing an ear­lier in­ter­view in­di­cated she was­n’t par­tic­u­larly tor­tured about us­ing it.

“Often I just ask the ma­chine, ‘darling, how could we de­velop this beau­ti­fully?’” Tokarczuk re­port­edly said, per a trans­la­tion from Polish. “Even though I know about hal­lu­ci­na­tions and many fac­tual er­rors in the al­go­rithms in terms of eco­nom­ics and hard data, I have to add that in lit­er­ary fic­tion this tech­nol­ogy is an ad­van­tage of un­be­liev­able pro­por­tion.”

This brings up the idea I’ve seen pushed by other writ­ers who openly used AI and say this tech­nol­ogy is merely like a sour­dough starter, cre­at­ing the con­di­tions for some­thing to be made where there was once noth­ing. The prob­lem arises when you don’t know where the starter ends and the cre­ative process be­gins. And can any­thing truly novel be cre­ated by a tech­nol­ogy that feeds on what al­ready ex­ists?

[Image from a 2025 Nature mag­a­zine study that was re­tracted in part be­cause of this “AI-generated fig­ure con­tain­ing non­sense to demon­strate the frame­work.”]

To un­der­stand the cru­sade for, and in­creas­ingly against, AI, one must re­gret­tably log into LinkedIn. Originally known as a so­cial me­dia plat­form for job search­ing and pro­fes­sional net­work­ing, it’s mor­phed pri­mar­ily into a place where tech evan­ge­lists as­sert su­premacy by loudly and fre­quently list­ing out the ways they har­ness tech­nol­ogy to achieve peak per­for­mance. None of the posts read like some­thing an ac­tual hu­man would say, and I would guess the peo­ple post­ing this shit don’t talk like that in real life. But it’s not real life. It’s LinkedIn. A haven for syco­phants to gain val­i­da­tion for their orig­i­nal­ity all while say­ing the same things as every­one else. Typically I scroll through for amuse­ment, and some­times post to pro­mote my 100% hu­man-made work.

While LinkedIn may seem like an im­pen­e­tra­ble space for AI skep­tics and out­right haters like me, my pas­sive scrolling has some­what con­firmed what the WSJ la­beled a “rebellion.” One trend I no­ticed a month or two back is that mar­ket­ing pro­fes­sion­als, TED talk­ers and com­mu­ni­ca­tions gu­rus alike have started call­ing out what they see as easy tells for AI-generated writ­ing.

At first, I took it as a hope­ful sign that AI use was­n’t go­ing com­pletely unchecked. After all, ac­cord­ing to a Pew study from September, “U.S. adults are gen­er­ally pes­simistic about AI’s ef­fect on peo­ple’s abil­ity to think cre­atively and form mean­ing­ful re­la­tion­ships,” with 53% say­ing AI will make it worse, and 16% say­ing it will both of those things bet­ter. But af­ter read­ing enough of these posts, I came to re­al­ize peo­ple on LinkedIn weren’t mad oth­ers were us­ing AI; they were mad peo­ple were be­ing so sloppy about it, not even both­er­ing to mas­sage the ma­chine’s lan­guage to con­ceal their process.

And of course with most trends, there’s a back­lash to peo­ple call­ing out AI. One de­fender called the pop­u­lar groundswell against AI slop “the new McCarthyism.” Some of these posts about AI polic­ing are im­bued with a sense of out­right be­trayal. How dare you draw at­ten­tion to an un­eth­i­cal short­cut that we all use, even if some of us are bet­ter at us­ing it than oth­ers. How dare you let peo­ple see your writ­ing is ac­tu­ally just two LLMs in a trench coat. Again they’re not mad that peo­ple use it: they’re mad that peo­ple are catch­ing on.

But while I took men­tal notes on what I was ob­serv­ing, I also felt a lack of rep­re­sen­ta­tion for true, pro­found, and gut­tural loathing of AI. The peo­ple like me who have only the vaguest idea of what de­fines AI, but ex­tremely spe­cific ex­am­ples of why it sucks. I’m not a hater based on vibes. I’m a hater based on facts. And those facts de­serve as much re­spect as the bil­lion­aires who con­tinue to dump money into los­ing en­ter­prises.

[My new and im­proved LinkedIn header]

A not-in­signif­i­cant part of my frus­tra­tion with the AI ethos sat­u­rat­ing LinkedIn is that it in­creas­ingly serves only one, nar­row vi­sion of suc­cess. It’s the suc­cess that comes only to the or­ga­nized, the ef­fi­cient and the hy­per-op­ti­mized. And above all, to the deeply cer­tain.

But as some­one who’s built a busi­ness my­self, the one thing I can be cer­tain about is that there is ab­solutely an­other way. You don’t have to be part of the grind­set or be a girl­boss or a so­ciopath or use short­cuts to be suc­cess­ful. You don’t have to out­source think­ing to a ma­chine to demon­strate you un­der­stand the fu­ture. You will only be and do those things if what you’re ac­tu­ally seek­ing is power.

“People hate AI,” the CEO of an AI-infrastructure con­sult­ing firm said on a pod­cast, per the Wall Street Journal. “AI is less pop­u­lar than ICE. AI is less pop­u­lar than politi­cians.” And much like ICE, AI has sunk its claws into com­mu­ni­ties that don’t want it.

Despite the bray­ing of the tech elite, we still have agency. We still have a choice.  Players with many bil­lions at stake have a vested in­ter­est in re­mov­ing your agency, and re­claim­ing it hurts their bot­tom line. There’s no way to say for cer­tain who will be right about AI in the end, but the cur­rent ev­i­dence points to­wards dis­as­ter. And it’s safe to ac­knowl­edge it.