Other improvements for WordPress 3.2 are including a refreshing look within admin area, distraction free writing when one creates new blog post in full screen with WordPress, new default theme, automatic update will be faster whenever the next version comes out (i.e., 3.3 or so), requiring higher/newer backend technology such as PHP 5.2.4 and MySQL 5, and few other minor improvements.

We’ve seen WordPress from a humble beginning to a full blown content management system.  Instead of feeling a slow down in WordPress development process since WordPress is so capable now, we have seen WordPress’s development continues to improve at either constant speed or has sped up — at least that’s how I feel!  Combining with frequent releases of WordPress and easy update process through automatic update/upgrade, I think self-hosted WordPress users have it much easier than any other users from other content management systems.  Even better, if you’re using WordPress.com, you get the feeling of WordPress 3.2 plus less headache from maintaining one’s own servers.

Anyhow, if you’re thinking of creating a blog, I think WordPress 3.2 won’t disappoint you!  Perhaps, you want to take a test on WordPress.com first for getting to know the platform, and then go for gold by hosting your very own WordPress blog on your own server.  Downloading WordPress 3.2 to host on one’s own web server by going to WordPress.org.

Source:  http://wpcandy.com/presents/everything-we-know-about-wordpress-3-2

Blogsy supports WordPress.com and self hosted WordPress and Blogger.com. Besides of supporting those two blog host/platforms’ API, Blogsy is also supporting APIs of YouTube and Picasa and Flickr, allowing it to let you drag and drop images and videos from these services. This is something WordPress app cannot do, but Blogsy manages to make it work. For your information, you do need to first entering third party services’ credentials for Blogsy to communicate with third party services’ API before you can drag and drop contents onto your blog. A perfect example would be drag and drop videos in your YouTube account onto your blog using Blogsy. Talking about embedding videos, you still have to copy embedded code from videos and paste them into Blogsy’s write side. Switching from write side to rich side is easy as swiping a finger of yours across the screen once. You can imagine rich side of Blogsy as WYSIWYG editor, and the write side is HTML editor.

Another very useful feature for Blogsy that WordPress lacks is to save your blog post as draft. Blogsy also has its own web browser so you don’t have to switch in and out between Safari and a blog app. I have to admit that Blogsy’s user interface is pretty, and it does know how to allow users to utilize bigger space in screen real estate when bloggers are typing away with their blogs. Lastly, Blogsy allows you to use three fingers swipe with upward motion to quickly save and publish and update a blog post.

Current Blogsy version has a price tag of $2.99, but they say they will raise the price of the app when the next version comes out. In the end, I think Blogsy is a much better app than the current WordPress app. With Blogsy on your iPad 2, I think you may have a greater joy of blogging on the go.

Update & Correction: In this blog post I had mentioned that WordPress App has no save draft functionality. I was wrong. It does have this functionality, but it only becomes available when you don’t use the update or cancel functionality and quit the writing process of your blog post abruptly without saving your work. This is why it had alluded me from beginning. I have to say I prefer this functionality to be made available out in the open for a blog app, and this is why I think Blogsy app is better than WordPress app (i.e., version 2.7.2) in this aspect, but of course I favor Blogsy over WordPress app for many other reasons too.

Example:  define ( ‘BP_REGISTER_SLUG’, ‘givemeanewacct’ );

With that line inside wp-config.php, the next time someone wants to sign up a new account, they’ll be redirected to yourdomain.tld/givemeanewacct.

This method probably is useless against human spammers, but it will work effectively against bots.  Then again, you have to change the slug frequently to prevent bots from adapting to the new slug.  Luckily, it’s rather painless to change the slug within wp-config.php.

Source:  http://techcrunch.com/2011/03/14/half-a-billion-blog-posts-later-google-to-give-blogger-a-revamp/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+
Techcrunch+%28TechCrunch%29

Upgrading to WordPress 3.1 is a walk in the park.  It’s true only if you are using PHP5 and not PHP4, and you are upgrading directly from WordPress 3.0.5 to WordPress 3.1.  If the things that I just mention are fitting with your very scenario, then you can use the auto upgrade button inside your WordPress installation.  Otherwise, you have to do the manual way!

If you are using WordPress as multi-site, I think you’re going to see a major change to your administration area.  For one example, you need to click on top right corner where it says Network Admin to become super admin (i.e., super user) so you can remove, add, edit, and ban users from your WordPress network.

Also, for all installations, that’s either multi-site or not, WordPress 3.1 will hide the custom fields by default.  To use the custom fields, you need to check a check box inside Screen Options (i.e., to right corner near the Help link) which says Custom Fields.  Have fun playing with WordPress 3.1., and I’m sure there is a lot more to the new features list of WordPress 3.1 — go to WordPress.org for getting the full details of what new features are available for WordPress 3.1.

Source: http://wordpress.org/news/2010/12/3-0-4-update/