| 开发者 | frenemydev |
|---|---|
| 更新时间 | 2026年7月18日 08:29 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
https://your-site.com/?frenemy=check in a private window; your Frenemy wizard flips to Connected within a minute.No. Classification and reporting run on PHP's shutdown hook, after your page has been sent (and on most hosts, after the connection to the visitor is already closed). The classify step itself is local — no network calls in the request path, ever.
Not in this version — Frenemy for WordPress is deliberately observe-only, and there is no enforcement code in the plugin. See first, then decide: your dashboard shows exactly who visits and what they claim to be.
Page caches and static files are served before WordPress (and therefore Frenemy) runs. Frenemy sees every request that reaches WordPress itself: cache misses, searches, POSTs, logins, REST and XML-RPC traffic — which is where bot activity concentrates. We state this honestly rather than estimate numbers we can't measure.
Per PHP-reaching request: the classification, method and path, status, duration, and the visitor IP (processed transiently on our side — hashed with a rotating salt, raw value never stored). The user-agent string is transmitted only for unrecognized bot-like requests, never for humans. Presumed-human traffic is sampled at a low rate; exact totals are kept via counters, not tracking. No cookies are set, no fingerprinting is done, and no visitor profile is built. See https://frenemy.dev/privacy.
Three ways, strongest first: define FRENEMY_DISABLED as true in wp-config.php (host-level), deactivate the plugin, or use the "Pause observation" toggle in Settings → Frenemy. Uninstalling removes every option the plugin created.
Not yet — single-site installs only in this version.