[wp-trac] Re: [WordPress Trac] #8927: allow turning off 'calling home' even _before_ install

WordPress Trac wp-trac at lists.automattic.com
Tue Feb 24 06:24:55 GMT 2009

#8927: allow turning off 'calling home' even _before_ install
 Reporter:  jidanni                               |        Owner:  jacobsantos
     Type:  enhancement                           |       Status:  closed     
 Priority:  lowest                                |    Milestone:  2.8        
Component:  HTTP                                  |      Version:  2.7        
 Severity:  trivial                               |   Resolution:  fixed      
 Keywords:  dev-feedback has-patch needs-testing  |  

Comment(by DD32):

 >  that would be good for 'Block many, but let through a few', but I'm
 afraid you need one further variable for those who wish to 'Block a few,
 but let through many'.

 That isn't a common use-case, Its a bit more common for boxes to be on
 lans and have NO external access, or only access to certain servers.

 Its extremely rare for someone wanting to (on a software level) block
 access to a select few hostnames.. In those cases, Its better off
 implemented at the network level.

 I do not think !WordPress as a whole needs to support 'Block few, Allow
 many' It benefits the end user little, 'Block many, Allow few' on the
 other hand, Is a functionality which has been needed for enterprise-level
 installs for awhile now.

 While i agree it wouldnt take much to add it in, I just.. Question the
 actual need for it, The only reason i see people using it would be to
 block api.wordpress.org and the plannet feed.. Both of which is a stupid
 thing to do, They're much better off attacking it at a higher level than
 the HTTP request stage.

 > But wait, my "gold standard test" is: starting from a vanilla install,
 all the way even including browsing the dashboard (currently (2.7.1) booby
 trapped to download RSS even before you can reach for "screen options"),
 can I avoid one single download?

 Thats a separate issue really, That once you turn it off, The RSS result
 stays around in the cache. I highly suspect that this will be fixed in 2.8
 with the RSS remodeling and widget(dashboard included) modifications. The
 fact that it downloads the feed once should be ignored, If You don't want
 !WordPress to make any external connections, you'll have defined the
 constant during the setup, Blacklisting will not help in that instance.

Ticket URL: <http://core.trac.wordpress.org/ticket/8927#comment:19>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list