Title: climatesaver's Replies | WordPress.org

---

# climatesaver

  [  ](https://wordpress.org/support/users/climatesaver/)

 *   [Profile](https://wordpress.org/support/users/climatesaver/)
 *   [Topics Started](https://wordpress.org/support/users/climatesaver/topics/)
 *   [Replies Created](https://wordpress.org/support/users/climatesaver/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/climatesaver/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/climatesaver/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/climatesaver/engagements/)
 *   [Favorites](https://wordpress.org/support/users/climatesaver/favorites/)

 Search replies:

## Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Armour - Honeypot Anti Spam] Blocks reply from the Fediverse with Activitypub plugin](https://wordpress.org/support/topic/blocks-reply-from-the-fediverse-with-activitypub-plugin/)
 *  Thread Starter [climatesaver](https://wordpress.org/support/users/climatesaver/)
 * (@climatesaver)
 * [10 months, 2 weeks ago](https://wordpress.org/support/topic/blocks-reply-from-the-fediverse-with-activitypub-plugin/#post-18574682)
 * Replying to a blog post from Mastodon, triggers a POST request executed by the
   Mastodon server to/wp-json/activitypub/1.0/actors/1/inbox . The POST request 
   contains some JSON format defined in the ActivityPub protocol. Examples are here
   [https://www.w3.org/wiki/ActivityPub/Primer/Replies](https://www.w3.org/wiki/ActivityPub/Primer/Replies)
 * With WP Armour installed, WordPress replies with a HTTP 500 error. Without WP
   Armour, this POST requests triggers a HTTP 202 and the reply is added to the 
   blog post in WordPress.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Honeypot Toolkit] Breaks wp-cli](https://wordpress.org/support/topic/breaks-wp-cli-3/)
 *  Thread Starter [climatesaver](https://wordpress.org/support/users/climatesaver/)
 * (@climatesaver)
 * [1 year ago](https://wordpress.org/support/topic/breaks-wp-cli-3/#post-18469830)
 * Yes, adding 127.0.0.1 to the allowlist fixes this. Should not the plugin do this
   automatically then?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Statistics – Simple, privacy-friendly Google Analytics alternative] Needs way to prevent minutely hits on /wp-json/wp-statistics/v2/online](https://wordpress.org/support/topic/needs-way-to-prevent-minutely-hits-on-wp-json-wp-statistics-v2-online/)
 *  Thread Starter [climatesaver](https://wordpress.org/support/users/climatesaver/)
 * (@climatesaver)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/needs-way-to-prevent-minutely-hits-on-wp-json-wp-statistics-v2-online/#post-17905876)
 * Thanks. To give you an idea of the impact of this issue: 2,5 days ago I disabled
   wp-statistics completely on my site and flushed all WordPress caches. Now 2,5
   days later, I’m still getting 20 hits (404 not found) per minute on `/wp-json/
   wp-statistics/v2/online` . This site has about 350 visits per day, according 
   to awstats so it’s not really a very busy site. You might want to reconsider 
   the defaults regarding to this option.

Viewing 3 replies - 1 through 3 (of 3 total)