{"id":9717378,"date":"2017-11-24T07:30:23","date_gmt":"2017-11-24T07:30:23","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/does-what-is-says-but\/"},"modified":"2017-11-24T07:30:23","modified_gmt":"2017-11-24T07:30:23","slug":"does-what-is-says-but","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/does-what-is-says-but\/","title":{"rendered":"Does what is says, but&#8230;"},"content":{"rendered":"<p>This is a great added feature to Limit Login Attempts, which solves the problem of entire, trusted ip addresses getting blocked, just because someone messed up logging in.<\/p>\n<p>However, there&#8217;s quite a lot of self-promoting on the admin page of the plugin. This in itself is not that big a deal, but Chrome warns on the page that: &#8220;This page is trying to load scripts from unauthenticated sources&#8221;. Chrome blocks the scripts but this is still something that should not happen.<\/p>\n<p>I&#8217;m not against promoting on the page, but maybe it could be done in a way that doesn&#8217;t actively poll the developer&#8217;s servers before the user initiates an action.<\/p>\n","protected":false},"template":"","class_list":["post-9717378","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/9717378","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/9717378\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=9717378"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}