Identify crawlers from the shared generated registry (#86) - #94
Merged
Merged
Conversation
The plugin kept its own table of 54 known bots with its own categories; the dashboard, the edge sensor and the Node SDK use the registry generated from WebDecoy/app. A crawler could be named one thing here and another in the report about it, and the crawler policy vocabulary (#995) had no PHP reader. sdk/src/registry/agents.generated.php is the shared table (schema 2, 182 agents, each with its policy behavior) and AgentRegistry is its only reader. GoodBotList keeps its public API and maps registry categories to the plugin's coarser ones: search and AI-search crawlers are search engines; training crawlers, AI agents and AI assistants are AI crawlers; fetchers are social; scanners, scraping frameworks, headless browsers and HTTP clients are not good bots and score as before. Source-address verification is keyed by registry id. The seven crawlers only this plugin listed are now in the registry (WebDecoy/app#1275); the two W3C validators are dropped. tests/AgentRegistryTest.php replays the shared parity vectors and pins the schema, the mapping and every previously listed crawler. CI now runs the SDK tests.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adopts the crawler registry generated from WebDecoy/app (
sdk/src/registry/agents.generated.php, schema 2, 182 agents with their policy behavior) as the one crawler table.AgentRegistryis its only reader;GoodBotListkeeps its API and maps registry categories to the plugin's.Mapping (registry → plugin): search_crawler, ai_search_crawler → search_engine; training_crawler, ai_agent, ai_assistant → ai_crawler; fetcher → social; monitoring, seo_crawler, feed_reader, archiver → themselves. Security scanners, scraping frameworks, headless browsers and HTTP clients are not good bots and score exactly as before.
Intentional behaviour changes (in the changelog): 128 more crawlers are recognised; with Block AI crawlers on, AI agents/assistants and the newly recognised AI crawlers are refused too; the two W3C validators are no longer listed (they were never allowed).
Drift guards:
tests/AgentRegistryTest.phpreplays the shared parity vectors, pins the schema, the mapping, the applebot/applebot-extended ordering and every crawler the old table named. A new CI job runs the SDK tests on PHP 7.4.Depends on WebDecoy/app#1275 (behavior in the PHP export, seven plugin-only agents added to the registry); the artifact here was generated from that branch.
Closes #86.