WW Disable browse-happy archived
WordPress plugin to disable queries to BrowseHappy API (e.g., for privacy reasons)
by Volodymyr Kolesnykov · github.com/sjinks/wp-disable-browse-happy · website
★ 1stars
31composer installs
2forks
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/sjinks/wp-disable-browse-happy/archive/refs/heads/master.zipAlso on Packagist as wildwolf/wp-disable-browse-happy:
composer require wildwolf/wp-disable-browse-happyFrom the readme
wp-disable-browse-happy
WordPress plugin to disable queries to BrowseHappy API (for example, for privacy reasons).
When you go to the Admin Dashboard of your WordPress site, WP checks
whether your browser is up-to-date, and displays a notice if it is not
(i.e., "You are using an insecure browser!" or "Your browser is out of date!").
This is probably not a bad thing, but:
1. It could be annoying for Linux users (they may have a browser with all
security patches backported yet its version will not be the latest)
2. wpcheckbrowserversion() function, which implements the check, does that
with a call to http://api.wordpress.org/core/browse-happy/1.1/ (or https://
if the SSL support is enabled):
You can see that this code sends your user agent string, WordPress version, and
the URL and IP address (implicitly) of the blog. Strictly speaking, it is enough
to send only the user agent to check whether the browser is up-to-date, the rest
of the information is not necessary.
WordPess plugin guidelines say that
"In the interest of protecting user privacy, plugins may not contact external servers
without the explicit consent of the user".
I think that the same should apply to the WP Core i