On August 10, 2012, I published a blogpost entitled “A response to Brennan Novak”. In that post, I stated that App.net would support a number of interoperable web technologies.
As the one-year anniversary of my blogpost approaches, I’d like to highlight how App.net supports those technologies.
Line-by-line discussion of what was promised:
- “Activitystrea.ms Atom & JSON feeds, as well as RSS feeds, of public posts for individual users, hashtags, etc.”
Activitystrea.ms support for JSON feeds was just released. This is what the output looks like. Our webfinger API returns a link to the appropriate Activitystream. (In the year that has passed it appears that community support for Atom activity streams has waned).
- “Pubsubhubbub (PuSH) support (as a publisher, initially)”
You can view our PuSH publishing support in action here.
- “Exposing user identities with Webfinger”
Webfinger support was just added. Here is an example of Webfinger in action.
- “Commitment to coordinate between internal and external parties to create and support open-source ‘lightweight’ clients in as many flavors as we can, ala Stripe”
- “Commit to enabling and supporting users in building inbound and outbound syndication to and from App.net”
3rd-party syndication apps such as IFTTT, Buffer, Zapier, Twitterfeed and more have been available and working for quite some time. Additionally, we have built and open sourced the aforementioned first-party syndication tool, PourOver.
I am happy to say that we now have fully supported all of the promised technologies. We have also added a few additional standards that were not mentioned in the original blogpost:
- h-card & h-entry are supported on alpha.app.net
- Support for Media RSS on posts with image annotations, and GeoRSS for posts with geo data.
- Added rel=”me” support in a way that ties into our verification system. This allows things like indieauth to work.
We are looking forward to seeing developer adoption of these technologies.
Also, we believe that the work we have done on PourOver so far will be beneficial on a long-term basis. For example, if a new syndication format is released in the future, PourOver can be modified by us or the community to consume the new format without much difficulty. The fact PourOver is open source, is real-time (because it natively consumes PuSH), and can process a wide variety of inbound formats makes it quite a useful building block for future development.