For security reasons, the UI to enable oEmbed’s discovery ability was removed from WordPress today. It’d be too easy for a novice to accidentally embed some bad HTML into their blog if they posted the URL to a malicious website.
I am in the early stages on recoding my Viper’s Video Quicktags plugin from scratch and in the process I will be replacing JW Player with a free and open-source alternative. JW Player is really great, but sadly it’s released under a non-commercial license which just won’t do.
So please, if you know of any good Flash players that will do FLV, MP4, etc. please leave a comment with a link!
Here’s my list so far of players to compare and pick between: (I’ll update this list with suggestions)
Flowplayer (currently leaning towards this one, it seems really badass)
I’ve released a new version of my SyntaxHighlighter Evolved plugin. It’s not a recode of the plugin, however it is a major overhaul of the plugin. It features an update to the highlighting package (with new languages and parameters) and other various things. Here’s the full changelog:
Major overhaul, mainly to extend flexibility so that this plugin could be used on WordPress.com without actual code modification (only actions/filters are used instead to modify it).
Updated SyntaxHighlighter package to v2.1.364. Highlights of the changelog include:
ColdFusion brush (aliases: coldfusion, cf)
Erlang brush (aliases: erl, erlang)
Objective-C brush (aliases: objc, obj-c)
padlinenumbers parameter. Set it to false for no line number padding, true for automatic padding, or an integer (number) for forced padding.
rb alias for Ruby
Commenters can now use this plugin to post code.
Plugin’s shortcodes now work inside of the text widget again. Requires WordPress 2.9+ though.
Overhaul of the TinyMCE plugin that assists in keeping your code sound when switching editor views. Thanks to Andrew Ozz!
This plugin’s stylesheets are now dynamically loaded. If they aren’t needed, they aren’t loaded.
Lots of sanitization of shortcode attributes. Invalid keys/values are no longer used.
Chinese translation thanks to Hinker Liu. Will need updating for v2.3.0.
New filter to control what shortcodes are registered. Used by WordPress.com to trim down the number of them.
Saving of user’s settings is now done using register_setting() instead of manually handing $_POST. Yay!
By default, a post meta is used to mark posts as being encoded using the 2.x encoding format. This is bad for a site like WordPress.com. You can use the new syntaxhighlighter_pre_getcodeformat filter to return 1 or 2 (based on say post_modified). See SyntaxHighlighter:get_code_format() for more details. Don’t forget to remove_action( 'save_post', array(&$SyntaxHighlighter, 'mark_as_encoded'), 10, 2 ); to stop the post meta from being added.
New syntaxhighlighter_precode filter to modify raw code before it’s highlighted.
New syntaxhighlighter_democode filter to modify example code on the settings page.
I’ve recoded my Regenerate Thumbnails plugin. It’s now powered by AJAX and should work better on shared hosting environments as it’s pretty much impossible now to make it run out of processing time as each resize is done from it’s own page call. It also features a fancy progress bar (I love you jQuery UI!).
SyntaxHighlighter, now known as SyntaxHighlighter Evolved (to better differentiate against the various plugin forks out there), has been recoded from scratch and is now at v2.0.0! It features an all new version of the highlighter and so much more.
My decently popular WordPress Admin Bar has been forked into the core of WPMU. Changes/improvements made to my standard plugin will likely be ported over, but I’m not going to bother with porting over any WPMU-specific code back to my plugin since it’s in the WPMU core now.
Best of all for me, this means I can hand off the baton for the WPMU-specific code I had been dreading writing (bar showing up on all blogs, etc.). I haven’t fiddled around with WPMU code too much, so to be frank I wasn’t the best person for the job. With it being a part of the WPMU core, it can now more easily be contributed to by the contributors to WPMU.
The bad news is now even more people will be seeing and using my plugin which means I need to stop slacking and make the improvements I’ve been meaning to do. D’oh.
UPDATE: This post no longer applies (or works) as YouTube now has built-in HD support for embeds.
Wired is reporting that YouTube now has a 720p-ish (reports vary on what resolution it truely is, but it’s sure good) video playback support. Even more important, the audio is stereo instead of mono (you can really hear the improved quality).
YouTube’s default video resolution is utter crap (not sure what the resolution is) and the existing higher quality video was 480×360. This new video resolution is 2-3 times as good as the previous “high quality” resolution.
To prove it, here’s some sample videos. The difference is more apparent if you click the fullscreen button, especially if you have a large monitor. Make sure to also have your speakers or headphones on to notice the improved audio quality.
YouTube Default (Low Quality)
YouTube’s Previous High Quality
YouTube’s New HD Quality
I have added support to my Video Quicktags plugin but note that if a video does not have the HD quality version available (99% or more don’t), it will drop back to the lowest quality format. As a result, I don’t recommend making the HD format your default on your blog. Instead, set the quality to 22 like this: