built-in notification NOT a panacea, and telling users it is is a disservice. matt’s plugin directory is very “friends-only”. ALL plugin and theme authors should manage their own update notifications. ALL users should check on their own for updates, rather than relying on att’s highly political idea of what themes and plugins are worthy of having security notifications.

Adam, forgive my ignorance man but this is the first time I have ever heard of this… very intriguing and disturbing at the same time. Perhaps BlogSec should get involved, I know of some people offering some great alternative plugin repository’s if needs be.

Its things like this that cause open source groups to branch.

[…] at BlogSecurity points to a site listing known 2.3 compatible plugins.  A few of the ones that I use […]

Just for reference, there’s privacy and security issues with what 2.3 is doing.

drmike, I forwarded your link to Sarah.. seems like quite alot of political mumbo jumbo going on with this new release.

That Storage issue can become a real Problem as the article itself mentions…I personally would like something which is central! The plugin hoster does not need to host the actual plugins but rather links to them like WP Plugins DB does(but wp plugins db misses stuff).

@ Adam: It’s quite time consuming keeping track of your own plugins. Some trustworthy website which manages the plugins (but doesn’t host them) would be good. Independent projects need to come together. Take from WP-Plugins-DB(the managed db), WP-Plugins.org(the Developer accounts, general styling) and WP’s Developer area itself(Statistics function).. all great on their own but imagine them together! Maybe wp-plugins-db will move in the right direction, WP-Plugins seems a bit dead…