- 53
- Sphinn It!
Posted By: nowsourcing 106 days ago
Topic Type: News Story (Jump to http://nowsourcing.com)
Category: Blogging
8 Comments
8 Comments
Save the date for:
SMX Local & Mobile - San Francisco, CA (July 24-25) See the agenda, and register now!
SMX Sao Paolo - Brazil - (Aug. 7-8)
SMX China - September 23 & 24, 2008
SMX Stockholm - September 23 & 24, 2008
SMX East - NYC - (Oct. 6-8) Registration is now open.
SMX London - November 4 & 5, 2008
Comments
Or, you could just remove your version # from your theme. :)
meta tag..
change to this
meta name="generator" content="WordPress 2.5"
g2g
I'm not down with letting Technorati control my blogs. There are a lot of problems with WordPress 2.5 that need to be fixed. Forcing people to upgrade isn't ok.
What sorts of problems are we talking about with 2.5? I just emailed Technorati to see if this story is indeed true so I guess I will let everyone know when I hear something but webgeek what are the problems with 2.5?
For Technorati to get specific about the WP exploits suggests Technorati's business plan is in trouble (it can't handle the spam links). Awareness campaigns are fine, but strong-arming like this has to be resisted.
If technorati actually drops 85-90% of the blogs published on WP, will Technorati be relevant?
I never knew technorati was relevant as it has zero impact for me, yawn.
@johnandrews: I agree 100%! I don't like strongarming tactics like this at all. Exactly...their relevance is in question.
@ HarryWatson00: Every time a major version of a new program/app/operating system is released, there ARE bugs, and it takes time to fix them, so it's rarely wise to upgrade right away. Some examples include a LOT of themes and plugins that have been broken by WordPress 2.5. I dug deeper into it and some key hooks in the code are broken. (I develop plugins so I have to stay on top of it.) This could cause a lot of problems for business owners with custom themes that could be broken by upgrading, along with other problems. It may cause costly downtime for businesses...that's not a joke.
Also, just because WP 2.5 is new doesn't mean it's more secure - it's just that the security flaws haven't been discovered yet. There could be a whole slew of new security flaws waiting to be exposed.
I realize my opinion here may be unpopular, but I feel strongly about this, and it needs to be said. Don't be lemmings, people - say NO to this.
Anyone interested can read my response here: http://sphinn.com/story.php?id=40009