Why not upgrade? was (Re: [wp-hackers] Maintenance release,
first gate of "is the issue major?")
computerguru at neosmart.net
Thu Oct 5 19:27:14 GMT 2006
Yeah, it's very simple.
You *don't* send a ping.
You do *all* the checks locally. It's what I do with my programs and scripts, and it works great.
Just have the local WP install grab a text file off the automattic server that contains the latest version (for instance grab version.php from the repo), and *locally* compare the version in that file to the version installed.
That simple. No one ever knows what version _you_ are running, and the only information being exchanged is what version is the latest that exists.
I think that addresses the privacy concerns?
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
> bounces at lists.automattic.com] On Behalf Of Craig
> Sent: Thursday, October 05, 2006 10:24 PM
> To: wp-hackers at lists.automattic.com
> Subject: Re: Why not upgrade? was (Re: [wp-hackers] Maintenance
> release, first gate of "is the issue major?")
> I like the idea of giving people a notice/warning/heads-up about a new
> release, especially one that is done for security purposes. However, if
> put something into the core that sends a ping to the WP Mother Ship
> what version is running, and then the Mother Ship sends that
> instructions to inform the user, then people will howl about privacy.
> In order to do this in a way that minimizes such claims, you really
> have something in the Install routine that clearly illustrates an opt-
> choice to be notified of updates and what information may be
> transferred and
> how one's privacy is assured.
> Given that I am code-clueless, there may be a way to accomplish this
> raising the ire of privacy advocates, in which case you can simply
> ignore my
> comments. :^)
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers