{"id":3416,"date":"2008-08-03T03:30:36","date_gmt":"2008-08-03T03:30:36","guid":{"rendered":"https:\/\/wordpress.org\/plugins-wp\/pingfm-custom-url-status-updates\/"},"modified":"2010-08-12T18:42:13","modified_gmt":"2010-08-12T18:42:13","slug":"pingfm-custom-url-status-updates","status":"publish","type":"plugin","link":"https:\/\/pcd.wordpress.org\/plugins\/pingfm-custom-url-status-updates\/","author":354105,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_crdt_document":"","version":"2.0.1","stable_tag":"2.0.1","tested":"3.0.5","requires":"3.0","requires_php":"","requires_plugins":"","header_name":"Ping.fm","header_author":"Matt Jacob","header_description":"","assets_banners_color":"","last_updated":"2010-08-12 18:42:13","external_support_url":"","external_repository_url":"","donate_link":"https:\/\/www.paypal.com\/cgi-bin\/webscr?cmd=_s-xclick&hosted_button_id=NYC67XZ9JJKLN","header_plugin_uri":"http:\/\/mattjacob.com\/pingfm-wordpress-plugin","header_author_uri":"http:\/\/mattjacob.com","rating":0,"author_block_rating":0,"active_installs":10,"downloads":21376,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":[],"upgrade_notice":{"2.0.0":"<p>This version brings the awesome sauce and slathers it all over your WordPress\nblog. No more janky DB tables, an admin interface for managing pings, local\nimage hosting, better performance, minor bug fixes... What are you waiting\nfor?!<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.9.1","0.9.2","0.9.3","0.9.4","0.9.5","0.9.6","1.0.0","1.0.1","1.1.0","1.2.0","1.2.1","1.3.0","1.3.1","1.3.2","1.3.3","2.0.0","2.0.1"],"block_files":[],"assets_screenshots":{"screenshot-5.png":{"filename":"screenshot-5.png","revision":"1566852","resolution":"5","location":"plugin"},"screenshot-4.png":{"filename":"screenshot-4.png","revision":"1566852","resolution":"4","location":"plugin"},"screenshot-2.png":{"filename":"screenshot-2.png","revision":"1566852","resolution":"2","location":"plugin"},"screenshot-3.png":{"filename":"screenshot-3.png","revision":"1566852","resolution":"3","location":"plugin"},"screenshot-1.png":{"filename":"screenshot-1.png","revision":"1566852","resolution":"1","location":"plugin"}},"screenshots":{"1":"A nicely-designed settings page stands at the ready to accept your input.","2":"Everything is clearly laid out and explained.","3":"More detailed help is only a tab click away at all times.","4":"The illustrious status widget. You feed it status updates, it feeds widgety\ngoodness to all your blog's readers.","5":"A full-blown admin page to manage all your status updates and micro-blogs."},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[16954,20751,49041,409,49042],"plugin_category":[],"plugin_contributors":[87034],"plugin_business_model":[],"class_list":["post-3416","plugin","type-plugin","status-publish","hentry","plugin_tags-custom-url","plugin_tags-ping-fm","plugin_tags-pingfm","plugin_tags-status","plugin_tags-wp-pingfm","plugin_contributors-mjacob","plugin_committers-mjacob"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/pingfm-custom-url-status-updates.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/pingfm-custom-url-status-updates\/trunk\/screenshot-1.png?rev=1566852","caption":"A nicely-designed settings page stands at the ready to accept your input."},{"src":"https:\/\/ps.w.org\/pingfm-custom-url-status-updates\/trunk\/screenshot-2.png?rev=1566852","caption":"Everything is clearly laid out and explained."},{"src":"https:\/\/ps.w.org\/pingfm-custom-url-status-updates\/trunk\/screenshot-3.png?rev=1566852","caption":"More detailed help is only a tab click away at all times."},{"src":"https:\/\/ps.w.org\/pingfm-custom-url-status-updates\/trunk\/screenshot-4.png?rev=1566852","caption":"The illustrious status widget. You feed it status updates, it feeds widgety\ngoodness to all your blog's readers."},{"src":"https:\/\/ps.w.org\/pingfm-custom-url-status-updates\/trunk\/screenshot-5.png?rev=1566852","caption":"A full-blown admin page to manage all your status updates and micro-blogs."}],"raw_content":"<!--section=description-->\n<p>Great for having a personal archive of content sent through Ping.fm, displaying\nstatus updates in your sidebar, or starting a mobile photo blog. While there's\nplenty of room for customizing the plugin, sane defaults ensure that 90% of\npeople can get up and running quickly. Keep reading for a full list of features\nbelow...<\/p>\n\n<h4>Minimum System Requirements<\/h4>\n\n<p>This plugin has required PHP 5 for quite a while, but the increased\nrequirements below are in line with the new standard coming in WordPress 3.2.\nOther version of PHP\/MySQL might work just fine, but I personally use even\nlater versions of both for development and testing. The minimums listed below\nare just that---minimums. My advice is to use the latest stable versions you\ncan get your hands on.<\/p>\n\n<ul>\n<li>WordPress 3.0<\/li>\n<li>PHP 5.2.0<\/li>\n<li>MySQL 5.0.15<\/li>\n<\/ul>\n\n<h4>A Quick Note About Donations<\/h4>\n\n<p>Starting with version 2.0.0 of this plugin, I added a PayPal donation link to\nthe information box in the upper-right corner of the page. Let me be clear: I'm\n<strong>not<\/strong> soliciting donations, there is no charge for this plugin, and you are\n<strong>not<\/strong> obligated to give me any money for any reason. However, people have\nasked me if they could donate, and I wanted to facilitate that if you feel so\ninclined.<\/p>\n\n<p>I've spent countless hours developing and supporting this plugin, but it's\nmostly a labor of love. I first created the plugin to meet my own needs, and\nit's kind of taken off from there. If you feel that the plugin has been useful\nto you in some way, I'd be honored to take your money and spend it on gadgets\nand firearm accessories.<\/p>\n\n<h4>Ye Olde Features Liste<\/h4>\n\n<ul>\n<li><p>Works with Ping.fm's Custom URL feature to collect blog entries, micro-blog\nentries, and status updates and post them to your blog.<\/p><\/li>\n<li><p>Photos posted through Ping.fm can be downloaded to your own blog and\ndisplayed as part of a normal post. It's a super-easy way to set up an\nawesome self-hosted mobile photo blog.<\/p><\/li>\n<li><p>Status updates and micro-blogs can be administered through a native\nWordPress management screen while blogs are, well... normal blog entries!\nEvery feature of this plugin is tightly integrated with WordPress to\nprovide a native look and feel.<\/p><\/li>\n<li><p>A beautiful settings page with predefined smart defaults and contextual\nhelp when you need it.<\/p><\/li>\n<li><p>Status updates are posted to the sidebar and displayed with a widget. A\nstandard template tag is also provided for those of you who are\nanti-widget.<\/p><\/li>\n<li><p>The sidebar widget is customizable with the number of status updates to\nshow and an optional string to prepend all updates with (e.g. you might use\nyour first name if all your status updates begin with a verb like mine do:\nMatt is...). Sensible CSS and examples are provided for you to customize\nthe look and feel of your widget.<\/p><\/li>\n<li><p>Provides an RSS feed and permalinks for your pings so that you can share\nthem with the rest of the world.<\/p><\/li>\n<li><p>Blog entries and micro-blog entries can have certain metadata applied to\nthem automatically. You can set the author, category, tags, and post status\n(published or draft) for all incoming pings.<\/p><\/li>\n<li><p>All the cool features of Ping.fm: post to your self-hosted WordPress blog\nusing SMS, IM, email, desktop gadgets, mobile apps, etc.<\/p><\/li>\n<\/ul>\n\n<h3>Template Tag Usage<\/h3>\n\n<p>void <strong>wp&#095;pingfm&#095;status<\/strong> ( [ int <code>$limit<\/code> [, string <code>$prefix<\/code> [, bool <code>$permalink<\/code> ]]] )<\/p>\n\n<p>Displays status updates in an unordered list (<code>&lt;ul&gt;<\/code>). All parameters are\noptional.<\/p>\n\n<h4>Parameters<\/h4>\n\n<p><em>limit<\/em><\/p>\n\n<blockquote>\n  <p>The number of status updates to show. Default value is 10. Depending on your\n  needs and the location on the page, a value between 5 and 15 is usually pretty\n  reasonable.<\/p>\n<\/blockquote>\n\n<p><em>prefix<\/em><\/p>\n\n<blockquote>\n  <p>Some text to display before every status update. Default value is nothing.\n  This can be useful if all of your status updates begin with a verb. For\n  example, you might post \"going to the store\" from Ping.fm. If your prefix is\n  \"Matt is\", the final output will be \"Matt is going to the store\". Neat, huh?<\/p>\n<\/blockquote>\n\n<p><em>permalink<\/em><\/p>\n\n<blockquote>\n  <p>Whether to show timestamps as permalinks, a la Twitter. The archive page is\n  editable via the <code>tmpl-single.php<\/code> template file.<\/p>\n<\/blockquote>\n\n<h4>Example<\/h4>\n\n<p>If you're using the Twenty Ten theme that ships with WordPress 3.0, you might\nput the following into your <code>sidebar.php<\/code> file:<\/p>\n\n<pre><code>&lt;li id=\"pingfm\" class=\"widget-container\"&gt;\n    &lt;h3 class=\"widget-title\"&gt;Status Updates&lt;\/h3&gt;\n    &lt;?php wp_pingfm_status(); ?&gt;\n&lt;\/li&gt;\n<\/code><\/pre>\n\n<p>mixed <strong>wp&#095;pingfm&#095;latest<\/strong> ( void )<\/p>\n\n<p>Retrieves the single most recent ping (status update) from the database.<\/p>\n\n<h4>Return Values<\/h4>\n\n<p>A <code>stdClass<\/code> object representing the latest ping, if it exists. Otherwise,\nfalse. The object will contain the properties listed below. For more\ninformation, dig through the source of the WordPress <code>get_posts()<\/code> function.<\/p>\n\n<pre><code>ID\npost_author\npost_date\npost_date_gmt\npost_content\npost_title\npost_excerpt\npost_status\ncomment_status\nping_status\npost_password\npost_name\nto_ping\npinged\npost_modified\npost_modified_gmt\npost_content_filtered\npost_parent\nguid\nmenu_order\npost_type\npost_mime_type\ncomment_count\nfilter\n<\/code><\/pre>\n\n<!--section=installation-->\n<ol>\n<li><p>Extract the .zip file you downloaded to a directory under\n    \/wp-content\/plugins\/. The default will be the full name of this plugin\nproject, which is <code>pingfm-custom-url-status-updates<\/code>. Alternatively, you\ncan search for this plugin from the WordPress admin area and install it\nthat way, or just <a href=\"http:\/\/coveredwebservices.com\/wp-plugin-install\/?plugin=pingfm-custom-url-status-updates\">click here<\/a>\nto use Mark Jaquith's plugin installer tool.<\/p><\/li>\n<li><p>Activate the plugin through the 'Plugins' menu in WordPress.<\/p><\/li>\n<li><p>Go to WordPress Admin &gt; Plugins &gt; <strong>Ping.fm Settings<\/strong> to get your\ncustom URL and then follow the instructions on that page to link up with\nyour Ping.fm account. Essentially, you just want to copy and paste the\ngiven URL into your Ping.fm Custom URL settings. Feel free to change any\nother settings on that page (it is <em>your<\/em> blog, after all). If you need to\nspecify a default category for incoming posts, and that category doesn't\nexist yet, go and create it first, and then come back and select it.<\/p><\/li>\n<li><p>Head over to WordPress Admin &gt; Design &gt; <strong>Widgets<\/strong> and add the 'Ping.fm'\nwidget to your sidebar. If you click the 'Edit' link in the activated\nwidget, you'll be able to configure a whole slew of options to your liking.\nIf your theme is non-widgetized, or if you just have a bias against widgets\nfor some reason, you can use the <code>wp_pingfm_status()<\/code> template tag instead.\nMore information about that is on the (Other Notes)[other_notes\/] page.<\/p><\/li>\n<li><p>Post something to your Ping.fm account and let the good times roll! If\nnothing shows up at first, it's probably because you haven't posted anything\nyet. (It seems obvious, but you'd be surprised.) Only updates made <em>after<\/em>\nyou install the plugin will show up, and even then, only after you've told\nPing.fm to post to your custom URL. And, on the Ping.fm side, be sure to\ncheck the appropriate boxes for the kinds of updates you'd like to send to\nyour custom URL. Finally, if you don't think your status updates are\nshowing up, make sure the widget has been added to your sidebar and that\nyou've saved the changes.<\/p><\/li>\n<li><p>For those about to ping, we salute you!<\/p><\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt>Can I change the number of status updates displayed?<\/dt>\n<dd><p>Yes, of course you can! Go to your sidebar widgets and hit the 'Edit' link for\nthe Ping.fm widget. This is all mentioned in the installation instructions, but\nI can see that you're the impatient type that never reads anything. I bet you\ndidn't read the owner's manual for your car, either, huh?<\/p><\/dd>\n<dt>Why am I not seeing any updates in my sidebar?<\/dt>\n<dd><p>Well... have you posted any yet? Only status updates posted to Ping.fm <em>after<\/em>\ninstalling the plugin and <em>after<\/em> configuring the custom URL will show up on\nyour blog. If you're confident you've done everything right, there might be\nsomething else going on. You might have discovered a bug, or an \"undocumented\nfeature\" as we software engineers like to call them. Send me some sugar at\n<a href=\"mailto:m&#x61;&#116;&#x74;&#064;&#x6d;&#097;&#x74;&#116;&#x6a;&#097;&#x63;&#111;&#x62;&#046;&#x63;&#111;&#x6d;\">m&#x61;&#116;&#x74;&#064;&#x6d;&#097;&#x74;&#116;&#x6a;&#097;&#x63;&#111;&#x62;&#046;&#x63;&#111;&#x6d;<\/a> and I'll see what I can do.<\/p><\/dd>\n<dt>Why aren't pings coming through to my site?<\/dt>\n<dd><p>Read the question immediately preceding this one once more. Done? Now go through\nthe checklist below and make sure everything is kosher:<\/p>\n\n<ul>\n<li><p>Is your site blocked off from others using HTTP Basic Authentication or some\nother method? Do you have firewall rules restricting users to a certain IP\nrange?<\/p><\/li>\n<li><p>Are you using any WordPress plugins that limit outside access? I've seen\nproblems related to the Bad Behavior plugin in the past.<\/p><\/li>\n<li><p>Can you hit the \"secret posting URL\" from your browser? You should get an\nerror message, which is a good sign that the plugin is installed and\nworking.<\/p><\/li>\n<li><p>Do you have some boxes checked over at the\n<a href=\"https:\/\/ping.fm\/custom\/\">Custom URL Settings<\/a> page? Next to <em>Use for:<\/em>, you\nneed at least one of those options selected (preferably all three).<\/p><\/li>\n<li><p>Under the main <a href=\"http:\/\/ping.fm\/settings\/\">Ping.fm Service Settings<\/a>, is the\nbox checked next to the <em>Post messages to Custom URL<\/em> option? This is\nimportant.<\/p><\/li>\n<li><p>If you're only posting status updates or micro-blogs from Ping.fm, is the\nwidget activated and placed somewhere?<\/p><\/li>\n<\/ul><\/dd>\n<dt>Can I post blog entries or pages from my Ping.fm account?<\/dt>\n<dd><p>The original answer was a defiant \"get off my lawn, you damn kids!\" That lasted\nfor a whole point release. By popular demand---and thanks in no small part to\nRocco and Vinny, who were sent to convince me---the ability to post blog entries\nhas been available since 0.9.2. Support for creating pages might be added in a\nfuture release. Give the people want they want, right?<\/p><\/dd>\n<dt>Will this plugin work with WordPress.com blogs?<\/dt>\n<dd><p>Definitely not. That would be goofy, because WordPress.com blogs don't allow\nplugins. Plus, Ping.fm already has <a href=\"http:\/\/ping.fm\/blog\/wordpress-bots-you-betcha\/\">support<\/a>\nfor WordPress.com hosted blogs anyway.<\/p><\/dd>\n<dt>Can you add feature X, Y, and Z? And Q? And L?<\/dt>\n<dd><p>I <em>could<\/em> add all kinds of features, but the real question is whether I\n<em>should<\/em>. The intent and operation of this plugin was meant to be simple, but\ngo ahead and pitch your feature idea to me. If it's not too outrageous and I\nthink others would benefit from it, I'll probably add it to a future version of\nthe plugin.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>2.0.1<\/h4>\n\n<ul>\n<li>Fixed edge case where \"<strong>Fatal error<\/strong>: Call to undefined function\nwp_create_category()\" would be triggered if the <code>pingfm_options<\/code> record was\nmanually deleted from the <code>wp_options<\/code> table.<\/li>\n<\/ul>\n\n<h4>2.0.0<\/h4>\n\n<ul>\n<li>Transitioned away from a separate database table holding status updates to\nWordPress's new \"custom post types\" that were introduced in 3.0. This had\nthe added bonus of providing \"real\" single post pages for status updates\nand micro-blogs, and a native WordPress interface for managing it all.<\/li>\n<li>Added true support for images sent from Ping.fm. They're now downloaded\nlocally and given first-class treatment (like any other uploaded media).<\/li>\n<li>Redesigned the entire settings page and rewrote much of the help content.<\/li>\n<li>Rewrote much of the code and split it out into separate classes for\nperformance and organizational reasons.<\/li>\n<li>Fixed timestamp offset bug (again). Hopefully fixed for good this time.<\/li>\n<li>Added robust upgrade functionality designed to be extended to future\nreleases as well as this one.<\/li>\n<\/ul>\n\n<h4>1.3.3<\/h4>\n\n<ul>\n<li>Fixed timezone handling throughout the plugin. Be sure to set a named\ntimezone (the city closest to you) in <em>General Settings<\/em>, or else your\ntimestamps might not be correct.<\/li>\n<li>Fixed invalidly-nested <code>&lt;\/li&gt;<\/code> element in the widget.<\/li>\n<li>Minor code beautification. Very minor.<\/li>\n<\/ul>\n\n<h4>1.3.2<\/h4>\n\n<ul>\n<li>Further tweaking of the way rewrite rules are filtered and flushed. In some\ncases, rewrite rules weren't taking affect immediately after a brand-new\ninstallation of the plugin, but that should be remedied with this release.<\/li>\n<\/ul>\n\n<h4>1.3.1<\/h4>\n\n<ul>\n<li>Tweaked the rewrite rules a little more. There were some edge cases where\nother things would overwrite our rules, but that should be fixed now.<\/li>\n<\/ul>\n\n<h4>1.3.0<\/h4>\n\n<ul>\n<li>Added support for displaying images associated with pings. A corresponding\noption has been added to the settings page.<\/li>\n<li>Added specific check for PHP 4 to prevent code from even being parsed if\nan insufficient version of PHP is found.<\/li>\n<li>Failure for PHP 4 now handled gracefully instead of with a syntax error.<\/li>\n<li>Moved flushing of rewrite rules to only happen on plugin activation and\nnot on every page load. This should have a noticeable positive impact on\nperformance. The only downside is that the plugin will have to be\ndeactivated and reactivated if pretty permalinks are enabled (a worthy\ntrade-off in my opinion).<\/li>\n<li>Cleaned up the code in various places to make it more readable (especially\nwith regard to the error message pseudo-constants).<\/li>\n<\/ul>\n\n<h4>1.2.1<\/h4>\n\n<ul>\n<li>Primarily a documentation release. Lots of stuff in the README was\nclarified, fortified, beautified, and just plain shifted around.<\/li>\n<li>Fixed a small bug related to a new option that was added in 1.2.0. After\nsaving the options twice, the problem would have fixed itself anyway.<\/li>\n<li>Added screenshots for the benefit of the WordPress Plugin Directory.<\/li>\n<li>Moved the changelog off of my site and into the Plugin Directory to give\npeople a more central point of contact.<\/li>\n<\/ul>\n\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>Added option to force all status updates to become actual posts.<\/li>\n<li>Added option in widget to \"permalinkify timestamps\" (archive page is\neditable via <code>tmpl-single.php<\/code>).<\/li>\n<li>Invented new English word: <em>permalinkify<\/em>.<\/li>\n<li>Tried to make the settings page clearer and easier to understand.<\/li>\n<li>Did some code housekeeping.<\/li>\n<li>Added Ping.fm logo to settings page.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Complete code rewrite (PHP 4 procedural to PHP 5 OO) and new way of storing\nsettings in the database.<\/li>\n<li>Did away with external <code>ping.php<\/code> file for receiving updates.<\/li>\n<li>Added native WordPress URL hooks and internal support for <code>mod_rewrite<\/code>.<\/li>\n<li>Added RSS feed containing 20 most recent status updates.<\/li>\n<li>Added archive\/permalink pages for individual pings (mostly in conjunction\nwith RSS feed, but can be used elsewhere as well). Page is templated for\neasy customization.<\/li>\n<li>Provided interface for user-supplied widget styles (CSS).<\/li>\n<li>Widget HTML\/CSS makes more sense. Widget container has an ID of <code>wp-pingfm<\/code>\nand a class of <code>wp-pingfm-widget<\/code>.<\/li>\n<li>Added <code>wp_pingfm_status()<\/code> for people using non-widgetized themes. See\n<em>Other Notes<\/em> section for docs.<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>CSS is now targeting <code>#pingfm<\/code> in a less specific way (because it broke on\nthemes with multiple sidebars).<\/li>\n<li>Fixed random bug only seen in WebKit where a space preceding a status update\nwas considered significant whitespace. (Don't ask me---I don't build it, I\njust code to it.)<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>The first non-beta release!<\/li>\n<li>Modified <code>CREATE TABLE<\/code> for installer after reports of it failing on MySQL\nversions &lt; 4.1.<\/li>\n<li>Added check for widget to determine if database table was created properly.<\/li>\n<li>Tweaked a few textual things here and there.<\/li>\n<\/ul>\n\n<h4>0.9.7<\/h4>\n\n<ul>\n<li>This version was never released publicly and the changes made for it were\nrolled into 1.0.0.<\/li>\n<\/ul>\n\n<h4>0.9.6<\/h4>\n\n<ul>\n<li>Added <a href=\"http:\/\/mattjacob.com\/pingfm-wordpress-plugin\">this page<\/a> as a home\nbase for the plugin on my site.<\/li>\n<li>Made the README more readable (hopefully). The documentation should be\neasier to understand now.<\/li>\n<li>Fixed the <code>mod_rewrite<\/code> example to include the <code>[L]<\/code> flag. The entire line\ndidn't get copied from my conf file the first time around.<\/li>\n<\/ul>\n\n<h4>0.9.5<\/h4>\n\n<ul>\n<li>Minor textual changes and a speed enhancement (eliminated a DB call using\nsome crafty coding).<\/li>\n<\/ul>\n\n<h4>0.9.4<\/h4>\n\n<ul>\n<li>Added widget options to specify colors used in injected style sheet (CSS).<\/li>\n<li>Reorganized, streamlined, and beautified some code.<\/li>\n<\/ul>\n\n<h4>0.9.3<\/h4>\n\n<ul>\n<li>Fortified README with some additional information and a <code>mod_rewrite<\/code>\nexample for shortening the inevitably long URL.<\/li>\n<li>The plugin now auto-detects the directory it's running from. Anything under\n    \/wordpress\/wp-content\/plugins should work reasonably well. If the\nWordPress Plugin Directory wants to create a really long folder structure,\nso be it.<\/li>\n<\/ul>\n\n<h4>0.9.2<\/h4>\n\n<ul>\n<li>Added support for all types of Ping.fm updates. Blog and micro-blog posts\nnow show up as actual entries in WordPress.<\/li>\n<\/ul>\n\n<h4>0.9.1<\/h4>\n\n<ul>\n<li>The initial public release! After being hacked together with loving care\nduring a couple late nights, the code finally sees the light of day. Cue\nangelic choir and bright background light...<\/li>\n<\/ul>","raw_excerpt":"Receives blogs, micro-blogs, and status updates from Ping.fm and posts them to your blog in the best way possible.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/3416","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=3416"}],"author":[{"embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/mjacob"}],"wp:attachment":[{"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=3416"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=3416"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=3416"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=3416"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=3416"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=3416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}