[wp-hackers] Plugin update & security / privacy

[Jared Bangs]

I think a large part of the objection to changing it at this point may not
necessarily be the nature of the issue itself (or lack of clarity /
understanding) but rather the timeliness of the complaint.

Regarding the transmission of the URL, it's certainly up for debate whether
the PR value of not sending it outweighs the potential future benefits of
including it.

It probably does (IMHO) even assuming, as I think most of us do, that it
would never be used for "evil" purposes. :)

However, this particular thread was just too late in the game to consider
for this release. 2.3 had been in bug-fix-only mode for quite a while.
There's already a trac ticket (#5066) for this, so hopefully we can just
discuss that in a calm and rational manner (for a future release) going
forward.

Hey, the good thing is that we have an update mechanism in place to change
it quickly later on if that's deemed appropriate. :)

- Jared

On 9/25/07, Moritz 'morty' Struebe <morty at gmx.net> wrote:
>
> Mark Shields wrote:
> > This e-mail thread found it's way onto slashdot, by the way.  As usual,
> > there's a lot of spin.
> > http://yro.slashdot.org/article.pl?sid=07/09/25/1632246
> >
>
> Yea, and unfortunately it seems that I failed say what I wanted to.
> Everyone is talking about this being part of the update information
> system, which it isn't. It only for statistics. And nobody seems to get
> the difference between transmitting URL and plugin data separately to
> transmitting them together.
> Seems like having a gray position isn't very popular. Or maybe it's just
> too complicated that to things are not that dangerous by them selves as
> they are linked to each other. :-/
>
> Cheers Morty
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>