title: "WiGLE and what a crowdsourced Wi-Fi map exposes about home routers" date: 2026/08/25 tags: [wigle, wardriving, wifi, geolocation, privacy, bssid, alpr]

🌐 last30days v3.3.2 · synced 2026-08-25

What I learned:

The interesting thing about WiGLE in the last 30 days is that almost none of the energy is about Wi-Fi - the database now holds over 1.73 billion unique networks and about 23 billion location observations, and the wardriving community spent August pointing that collection apparatus at surveillance cameras instead of routers. The pipeline is explicit: wardrive data uploaded to WiGLE feeds automatically into Flock Finder's next daily scan, which maps Flock Safety ALPR cameras. A hobby built on logging other people's access points became infrastructure for logging the people doing the logging.

The clearest single signal in the window is a vendor counter-adapting in public - @dafr0g_ posted on 9 August, at 397 likes, that "Flock are changing their hardware ids to prevent from being detected. Multiple cameras i knew existed slowly stopped being detected by ouispy. We can expect a rotating set of hwids from them." Detection works by matching OUI prefixes - the manufacturer-assigned first half of a MAC address - and the community target list carried 31 active Flock prefixes as of a 2026-07-16 revision. Rotating hardware IDs is the countermove, and it works, because passive detection can only recognize what it already has on a list. The proposed fix in that same post is telling: put a physical button on the wardriving rig so the operator can log a manual "data anomaly" at a GPS coordinate when the software misses. Human eyes as the fallback sensor.

The hardware floor collapsed this year and that is what actually changed participation - the practitioner content is almost entirely about ESP32-C5 dual-band boards clipped to a Flipper Zero. PINGEQUA's August guides describe the old path as "a parts order: a GPS module to wire in, a microSD card to format, and a flashing toolchain to fight before you've logged a single access point," against $30-40 adapters and a $99 five-function board now. ESP32 Marauder supports direct WiGLE upload from firmware. @463n7_57 is the representative voice, posting a Cerberus rig at 439 likes and describing the motive plainly: "For guys like me it's a bit of a competition to see who can collect the most." The #wdgwars hashtag is the same thing formalized.

The opt-out is weaker than most people who quote it realize - appending _nomap to your SSID is the standard advice, and Google and Apple both honor it. But Microsoft wants _optout instead, so covering both means naming your network something like 1234_optout_nomap, and the whole scheme is voluntary courtesy dating back to 2011 EU pressure over Street View. Crucially it is an instruction to commercial positioning providers, not a property right - the crowdsourced databases built by volunteers are a separate question, and a suffix nobody is contractually bound to respect is a request, not a removal.

The project itself is quiet while the community is loud - the official @wiglenet account states it is no longer monitored, a WiGLE submission to Hacker News on 24 August drew 6 points, and the Android client sits at 953 stars. Meanwhile the r/privacy layer is saturated with Flock stories - cameras now assisting with traffic tickets, and someone in a Darth Vader costume addressing San Diego's City Council with "the emperor is a fan of Flock, and we must continue utilizing Flock technologies so that we can follow and surveil the rebel scum." The database is 25 years old and effectively unattended; the thing built on top of it is where the argument is.

KEY PATTERNS from the research: 1. The collection layer and the use layer have fully decoupled - WiGLE is a neutral upload target, and Flock Finder / DeFlock are the applications that give a 2026 wardrive its political meaning 2. Detection-by-OUI is structurally losable - a vendor can rotate hardware IDs faster than a volunteer list updates, per @dafr0g_ 3. Gamification, not privacy activism, is what keeps the raw collection running - competition and #wdgwars show up far more than any stated cause, per @463n7_57 4. The legal line practitioners actually repeat is passive-versus-connect - logging SSIDs, BSSIDs and GPS is broadly legal, connecting or cracking is not, per PINGEQUA 5. Flock is litigating the map rather than the mapping - a trademark cease-and-desist to DeFlock's creator, rejected by the EFF on First Amendment grounds, which concedes the underlying observation is lawful

title: "Where independent search engines get their index after the Bing API shutdown" date: 2026/08/25 tags: [search-engine, index, bing-api, marginalia, brave, mojeek, antitrust]

🌐 last30days v3.3.2 · synced 2026-08-25

What I learned:

The set of search engines that actually own an index is far smaller than the set that markets itself as an alternative - the corpus keeps making the same distinction and most alternative-search roundups blur it. SearchEngines.Net draws the line explicitly: use Brave or Mojeek when you specifically want an independent index, choose DuckDuckGo, Startpage, Ecosia or Qwant when privacy or mission matters more than crawler independence, and SearXNG "doesn't crawl the web itself" at all - it queries 100+ other engines and merges. Kagi is openly hybrid: Google, Bing, Mojeek, Brave, Marginalia, plus its own indexing component. Marginalia's index is a supplier to a commercial search product, which is a more interesting fact about it than anything on its own homepage.

Marginalia is the best-documented independent crawler and one of the smallest - it runs its own crawler identified as search.marginalia.nu in both user-agent and robots.txt token, from a published static IP range, on an eight-to-ten-week refresh cycle, with no Google or Bing feed anywhere in the pipeline. The size is where you have to be careful: the project FAQ says roughly 300 million documents occupying about a terabyte as of 2024 and describes itself as outdated, and the current about-page says only "hundreds of millions." No dated 2025 or 2026 figure has been published, so any precise current number circulating is unsourced. For scale, Mojeek hit 9 billion pages in 2025 and Brave reports 30 billion with 100M+ daily updates. Marginalia is roughly two orders of magnitude below the small commercial independents, and that is the point rather than a failing.

The clearest statement of what Marginalia is for came from a competitor's README - mwmbl, an open-source non-profit search engine, positions itself by contrast: "Marginalia Search is fantastic, but our goals are different: we aim to be a replacement for commercial search engines whereas Marginalia aims to provide a different type of search." The same README dismisses YaCy's peer-to-peer index as spiritually closest but too slow to fetch results. Those two sentences map the whole non-commercial index space better than any listicle in the window.

The economics of owning an index inverted in the last year, and the Bing shutdown is why - Microsoft retired the Bing Search APIs on 11 August 2025, which removed the cheap tier that let anyone put a search box on a product without crawling. The 2026 replacement guides rank the survivors and almost all of them are resellers or SERP scrapers - SerpAPI for Bing SERP parsing, DataForSEO at $0.60 per thousand - with Brave the one entry described as "an independent 30B-page index outside the Google/Microsoft duopoly." Then the agent market arrived with real money behind it: Brave launched an LLM Context API built for agent consumption, and Parallel raised $100M to build out its own web-scale index. Crawling the web yourself went from a hobbyist's principled loss to venture-backed infrastructure in about twelve months. A new entrant on Reddit pitches itself on exactly that axis: "built on our own independent, continuously crawled index - not a Google or Bing reseller, and not a scraper hitting sites on demand."

The legal route to an index is real, ordered, and still delivering nothing - Judge Mehta's September 2025 remedy requires Google to share its web search index and click-and-query data with Qualified Competitors and to offer capped syndication licences. But Google is appealing, the DOJ cross-appealed by a 3 February 2026 deadline seeking the divestitures Mehta refused, and appellate argument is projected for late 2026 or early 2027. The Economic Liberties amicus calls the ruling "the barest data-sharing and syndication remedies in its arsenal," noting it left the default payments intact while Google grounds its GenAI products in the same search index. SerpAPI filed its own brief. Nobody has received index access.

What people actually reach for these engines to do is find the old web, not replace Google - the one high-engagement video in the window, at 128,920 views, frames it as recovering what ranking buried: "Somewhere out there is a website some guy built in 2004 about the history of lighthouse lenses, and it is genuinely wonderful, and you will never ever find it on Google," and on Marginalia specifically, "search something on Marginalia and you don't get 10 companies trying to sell you the answer." @cyb_detective lists the working set the same way - Marginalia, Wiby, Million Short, Search My Site, Mwmbl, Mojeek - under "6 search engines that find the internet that Google forgot." Meanwhile the ambient Google complaints on Hacker News are about the product decaying rather than about alternatives: the time filter breaking, the classic Search button disappearing from an AI-first homepage, CAPTCHAs on search.

KEY PATTERNS from the research: 1. Owning a crawler and owning a brand are different things, and only Brave, Mojeek, Marginalia, Mwmbl and a handful of others clear the first bar, per SearchEngines.Net 2. Index scale spans two orders of magnitude among "independents" - roughly 300M documents for Marginalia against 9B for Mojeek and 30B for Brave 3. The Bing API retirement on 11 August 2025 is the event that made independent crawling commercially rational, by deleting the cheap alternative 4. Agent demand, not consumer search, is what is funding new indexes now - Parallel at $100M and Brave's LLM Context API 5. The court-ordered path to Google's index is stuck in appeals until late 2026 at the earliest, so it is not a 2026 option for anyone building today 6. Marginalia explicitly is not trying to replace Google, per mwmbl's own README drawing the distinction

title: "Why AI-driven NPCs still have not shipped in real games" date: 2026/08/25 tags: [ai, npc, gaming, nvidia-ace, local-inference, mods, regulation]

🌐 last30days v3.3.2 · synced 2026-08-25

What I learned:

The platform layer quietly got its most serious release yet and almost nobody in the gaming communities reacted - NVIDIA shipped the ACE Game Agent SDK in beta at Unreal Fest 2026: open source, a lightweight C/C++ agentic framework for native in-game integration, with Unreal Engine 5 plugins for speech recognition, a small language model, and text-to-speech. Three APIs - Agent for chat history and multi-step reasoning, Chat for direct inference control, RAG for grounding answers in a developer-built game knowledge base. The number that matters is the floor: it runs entirely on local RTX hardware with no cloud, on GPUs with as little as 8GB of VRAM, including an RTX 3060. Cloud latency and per-token cost were the two structural objections to generative NPCs, and this removes both by moving the model onto the card the player already owns.

The shipped titles are real but the interesting thing is which AI feature survived - inZOI lets players activate Smart Zoi, turning city NPCs into characters that observe their environment and make decisions rather than cycling pre-programmed schedules. But a July patch summary from @inZOIDailyNews lists both directions at once: "Smart Zoi improvements coming" alongside "AI building feature discontinued." A shipped title kept the generative character and cut the generative asset tool. That is a real verdict from contact with players, and it points the same way as everything else in this window. Elsewhere KRAFTON's PUBG Ally runs Mistral-Nemo-Minitron-8B-128k-instruct on the player's own GPU, trained on PUBG terminology and map locations, in English, Korean and Chinese - and TechRadar's hands-on headline was "but I'm not impressed so far."

One person's Skyrim companion outdrew every corporate AI-NPC announcement in the window - the single strongest community signal in the corpus is a Hacker News thread at 367 points and 73 comments on 23 August, titled "I built a low-latency AI companion that plays Skyrim with me." Not a demo reel, not an SDK launch. An individual solving the latency problem well enough that a companion can act alongside a player rather than talk at them. The gap between that reception and the silence around ACE's actual release is the most honest measure in this research of where the interest lives.

The loudest gaming conversation this month is about AI replacing workers, not AI playing characters, and conflating the two misreads the room badly - the biggest thread in the entire corpus, at 5,028 upvotes on r/pcgaming, reports that Saber Interactive replaced a lead writer with ChatGPT midway through development: "All the passenger voices were AI too. Either they changed direction at some point or they're not disclosing it on Steam." Then 1,556 upvotes for anti-AI clauses now being commonplace in game dev contracts with a lawyer noting copyright law "wants humans making art," and 319 for Vapor World pulling AI-generated cutscenes after player backlash. Not one of these is about NPCs. The anger attaches to undisclosed substitution of labour, which is a different object entirely from a companion that helps you loot.

The split inside the developer community runs along professional lines, and a top comment named it before the argument even started - r/gamedev's official AI-use policy thread pulled 1,176 upvotes and 1,625 comments. The second-highest comment, at 571 upvotes, predicted the shape of the response: "Hobby devs / non-programmers will be outraged by this and will not be able to fathom what could lead to such a stance. Professional game devs or SWEs will find this a pretty normal" position. The top comment at 648 upvotes went straight at disclosure instead: "OP currently works at a company developing a plugin for Unity AI integration which he decided to not disclose for some odd reason." Disclosure, again, rather than the technology. The same instinct shows up in r/skyrimmods at 687 upvotes for a mod author who "won't tag it as AI-assisted and is hiding comments calling him out."

The regulatory problem is the memory, which is exactly the feature that makes a companion worth having - as of July 2026 twelve US states have enacted AI-chatbot legislation aimed at Replika and Character.AI-style products, but the Harvard Journal of Sports and Entertainment Law argues the statutory definitions arguably capture generative NPCs too: a character that remembers your choices, responds to free-form dialogue, shows anthropomorphic features and holds a persistent relationship across dozens of hours satisfies elements of some companion statutes. Suggested mitigations to stay inside the video-game exclusion are topic guardrails, adversarial testing, and tying NPC dialogue tightly to gameplay. A Japanese-language post in the corpus put it more directly: AI NPCs are no longer just in-game staging, and the more they remember and attach to you, the less separable character design becomes from legal and safety design.

KEY PATTERNS from the research: 1. On-device inference is what unblocked this - an 8GB VRAM floor and an RTX 3060 baseline removes the cloud latency and per-query cost objections in one move 2. Every shipped implementation uses a small model, not a frontier one - Mistral-Nemo-Minitron-8B for PUBG Ally, Qwen3-8B supported in ACE 3. Player backlash is precisely targeted at undisclosed labour replacement, not at generative characters, per r/pcgaming 4. Disclosure is the actual demand across every angry thread in the window, in both r/gamedev and r/skyrimmods 5. Enthusiasm concentrates on individual builders rather than platform releases - one person's Skyrim companion outdrew the whole ACE launch 6. Persistent memory is simultaneously the product feature and the regulatory exposure, per the Harvard JSEL analysis