Pádraic Brady has a new post today proposing that what the PHP ecosystem needs is a way to better publish security disclosures in a format that's easy to parse and deal with.

This is a branch off from a separate discussion on the PHP-FIG mailing list about other ways the Framework Interoperability Group can encourage and foster wider interoperability among its member projects (and by extension, the whole PHP community). I'll start by noting two interesting developments in recent months and one long standing best practice.

The two "interesting developments" he mentions are the relatively recently released SensioLabs Security Checker that uses you Composer file to find security issues and the new entry in the latest version of the OWASP Top 10 list for "Using Components with Known Vulnerabilities". The best practice he talks about is more around the timely/responsible disclosure of vulnerabilities and how some kind of decentralized tracking of these issues that puts the responsibility back on the developers of the tool and not on one tracking resource.

In a recent post to PHPMaster.com Kevin Mowry shows you how to use SimplePie, a simple to use programatic feed reader you can use to parse things like RSS feeds.

If you're an avid feed consumer like I am, you might be a bit sad to see Google's recent announcement of Reader reaching end of life. Reader was simple and easy to use, but there's no reason you can't have the same functionality with your own homegrown project. The PHP library SimplePie allows for quick and easy feed consumption and display. Here's how you can get started on your own feed reader.

He helps you get it installed (via Composer) and shows you how to use some of its most basic functionality to parse the New York Times' feed. He also includes examples of getting the information back out of the SimplePie object. There's also some snippets that show how to only get the latest items and how to cache the results.

On the MaltBlue blog Matt Setter has a new tutorial posted about creating RSS feeds quickly and easily with the help of the Zend Framework and context switching.

Ever wanted to know how to take an existing Zend Framework application where you have posts, records, news or anything else stored in a data source and updated regularly, and make it available as a feed for your users that they can subscribe to? Well today, that's what I want to show you. Recently, during the development of the burgeoning PHP cloud development casts site, I had just that situation.

He shows you how to set up some of the routing for the RSS and Atom feeds, pointing them to specific module/controller/action paths for handling. He then creates a "_getFeed()" method that pulls together the needed content and uses the Zend_Feed_Writer_Feed component to create the feed of the correct type. This is then exported, returned and - thanks to a bit more configuration - turned into a correctly-formatted feed.

If you're a regular reader of PHPDeveloper.org, you know that there's a few articles posted here (almost) daily about what's happening in the PHP world. Unfortunately, this only scratches the surface of the quality content that's out there. In an effort to provide more PHP goodness to the community as a whole, PHP Quick Fix has been launched - a service linking to stories that don't make it on PHPDeveloper.org.

All of the stories on PHP Quick Fix (you can also follow it on twitter) are still hand-selected out of the mounds of PHP content that shows every day to ensure the best quality. There's no automatic syndication here - just more good, useful PHP (and related topics) to add to your day.

Additionally, if you're interested to see how it all works (thanks to a GimmeBar backend) check out this post on blog.phpdeveloper.org.

If you're a last.fm user and have been curious about how to get the latest list of your "last played" selections, Philip Norton has just the code you'll need.

The other day I was approached by a friend (Julie Cheung) and asked if I could create some code that would display a list of last played tracks from last.fm. Julie isn't a PHP developer and so the code I gave her had to be easily understandable so that she could edit it herself if needed. The following code is what I came up with.

The code pulls from the defined user's "recenttracks" feed and parses it (via a simplexml_load_string call) into an object that's looped through and outputted. Data that comes back from the feed includes artist anme, name of the track, a URL to more information about it and an image of the album cover. He also includes an updated version that caches the data for three minutes so it's not always relying on the last.fm servers to be there.

Rob Allen has posted a method he's come up with for displaying an RSS feed right in with the rest of the content of your WordPress blog. The key is in the simplicity of the MagpieRSS library.

My wife decided that she wanted to display a list of her latest AudioBoos in the sidebar of her blog. She looked at the AudioBoo JavaScript widget but decided it wasn't subtle enough and so she enlisted me to solve her problem. It turns out that AudioBoo has an RSS feed, so a simple plugin was required. I had a quick look on the extension site, but most are now "widgets" which her theme isn't set up for or didn't provide an unsigned list. Hence, I whipped up a small extension for her.

With the help of Magpie, a simple call to "fetch_rss" was all it took to pull in the AudioBoo RSS feed and a bit of PHP to loop through it and pull out the relevant bits. They're all displayed in a simple list - you can see it in action on her blog (look for the "Audioboo Updates" section).

On Qafoo.com there's a new tool that's been introduced to help you keep track of the current Call for Papers that are currently happening for PHP conferences. The start of the PHP conference season is in full swing, and sometimes it can be hard to keep up. Their Call for Papers Manager can keep that information at your fingertips.

The tool works quite simple: You can add CFPs you know about and which are relevant for the PHP community through a simple form. In order to remember the CFPs, you can configure two kinds of reminders: fFor upcoming CFPs and for ending CFPs. For each of these lists, you can determine when to be reminded, like 2 days before the event occurs. These lists can then be easily integrated into your normal feed reader using an RSS or Atom feed.

You can use the URL requested to get different kinds of reminders delivered to your feed reader too. If you have a conference and your Call for Papers is open or upcoming, add it to the list!

In a new post to his blog today Gonzalo Ayuso talks about video streaming and PHP. Well, okay, not so much using PHP for playing the video, more for the security and streaming around the streaming feeds.

For example we want to show videos only to registered users based on our authentication system. Imagine we're using sessions for validate users. That's means we cannot put the media in a public folder and point our media player to those files. We can obfuscate the file name but it'll remain public. In this small tutorial We're going to see how to implement it with PHP.

Since the video stream he wants to deal with is a live one (and not a single video file that can be read all at once) he shows how to use the output buffering functions in PHP to output small chunks of the data at a time with the correct headers attached.

Brian Swan has a new post to his blog today about consuming protected feeds of OData coming from SQL Azure in a PHP application.

I did write a post a few weeks ago that described how to enable anonymous access to SQL Azure OData feeds (Consuming SQL Azure Data with the OData SDK for PHP), but I had a few things to learn about AppFabric access control before I felt comfortable writing about authenticated access to these feeds.

He starts from the Azure side, creating a sample OData feed and adding permissions to only allow access to a specific (database) user for the feed. You'll use a set of data to connect to the feed - a username, a secret key, an issuer name and the OData endpoint address. Then, using the OData SDK he shows how to generate the needed classes with the automatic tool and use them to connect to the endpoint and retrieve data from the feed. He also includes a little snippet for those that might not want to use the SDK - an example using curl to connect and authorize the session.

In a new post to his blog Cal Evans has posted five twitter accounts that he's used to replace his feed reader for everyday reading:

I have given up on feed readers. I never did like them much to begin with and have found over the past couple of years that twitter does a better job of showing me interesting blog posts than Google Reader ever did. In addition to recommendations from friends however, there are a hand full of accounts that I follow to keep up with what is going on.

Here's his list of the five accounts to follow:

• @phpdeveloper (yup, that's us!)
• @planetphp
• @weierophinney (Matthew Weier O'Phinney)
• @phpc
• @phpcamp