making bbPress (and WordPress) work better!

Why does ANY information need to be sent to the WP servers?

With the 2.3 fiasco over sending a list of all plugins being used and blog url to the WP servers, I can’t understand why they didn’t do this more intelligently?

If there was a mini-downloadable database of all the current version numbers, a blog would NOT have to send ANY information at all.

It’s a far better technique too, where the server only has to do the work once to compile the mini-database and the client-side does all the work comparing version numbers.

Then the DB is assigned a version number (build #) to itself and you only download the new DB when it’s a major build number change.

Completely passive technique and no “privacy” violations of any kind.

IMHO, easier to code too.

5 responses

  1. Because then Matt would have to admit that he made a mistake and that won’t happen. When they had folks up in arms about removing feed stats, they didn’t even admit it then. They just turned off comments on that post and had the forum volunteers take the abuse. Matt didn’t admit that they were broken but there was a lot of evidence that they were. (On my own blog, I went from an average of 8 to well over 200 when I moved back to my own server.)

    September 26, 2007 at 12:34 pm

  2. There’s a link in the comment there to the post about removing feedstats. Doesn’t show up unless you hover. Feel free to edit my comment to show that as a seperate link.

    September 26, 2007 at 12:35 pm

  3. fiasco? Although that does relieve some “privacy” concerns that sounds like an awkward experience and I don’t buy that it is a more technically sound approach — that file is going to grow and grow, why have thousands of entries when you have only ten plugins. I do like your creative problem solving though!

    December 6, 2007 at 6:14 pm

  4. Pingback: buy text links

  5. Actually, the technique would allow the list to be updated via a “diff” (or patch) instead of re-downloading the entire list. Google uses this technique for it’s “safe browsing” program, where the chrome browser (or firefox plugin) downloads the most recent list of malware sites as a patch, instead of sending the current url to Google.

    September 26, 2008 at 3:24 pm

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s