IndieWeb friendly refers to online services interoperating well with the indieweb by supporting open formats, protocols, and IndieWeb building-blocks as well as enabling users to transition to their own indieweb sites.
- 1 Why
- 2 How
- 3 Friendly Services
- 4 In Progress
- 5 Brainstorming
- 6 Previously
- 7 See Also
If you're making a content hosting service (e.g. for blogging, photo posting, etc.), by being indieweb friendly, you can reduce the fear of lock-in, and encourage more folks to freely experiment.
By interoperating with existing indieweb formats and protocols, you instantly help your users interact with an existing live, vibrant, and friendly community.
Some developers have been able to more rapidly been able to build platforms and services and allow their users more flexibility and choice by relying on IndieWeb building-blocks. For example, by supporting the W3C recommended Micropub specification, platforms don't need to immediately design and build user interfaces for posting content as there are a variety of (both web and mobile) clients that can handle this on their behalf. Many of these are also open source to decrease the time for modifying and adapting them to other use cases.
To be indieweb friendly and interoperate with indieweb sites, start with doing the following:
Basic support for indieweb formats and protocols
- Provide a way for users to enter a personal website/blog, and then automatically link to it from their profile page with rel=me. If your site supports OAuth, this is key to becoming an RelMeAuth provider for Web sign-in.
- Markup users' feeds and post permalink pages with the h-entry microformat including a nested h-card for the authorship information. This permits others to easily provide rich reply-contexts when replying to posts on your site.
- Markup users' profile pages with h-card
- Let the user automatically syndicate in posts (marked up using h-entry) from their personal site
Be a good POSSE destination
- Support WebSub notifications for receiving posts from their personal site
- Link permalinks back to users' original posts from syndicated copies on your service
- Use rel-canonical on links from syndicated copies on your service to original posts.
- Send webmentions to users' original posts from comments on their POSSE copies.
Support distributed interactions
- Support receiving webmentions + h-entry parsing to accept decentralized comments on posts.
- If your service supports subscription/following/friending/anything showing an aggregated timeline/feed/stream, allow users to subscribe to other people’s personal site feeds marked up with h-feed and/or h-entry
- Let users link a domain name to their profile and content, treat that domain as canonical (e.g. like Tumblr and GitHub do)
- Provide a way for users to export all their user data (posts, comments, tags, likes/faves), and interactions on that data.
- Provide HTTP redirects if users want to change their domain name, or switch from a subdomain on your service to their own domain name
- Asks for your personal website on sign up and grabs rel="me" links to build your user profile
- Huffduffer user profile is marked up with rel="me"
- microformats2 support for podcast feeds, including h-feed (actually hfeed) and h-entry
- https://huffduffer.com/add?page= ostensibly scrapes microformats data from the source page to fill in the title, permalink, and description.
Withknown, running hosted versions of Known, was designed from the start to be IndieWeb friendly and supports a huge amount of IndieWeb building blocks including WebSub, Webmention, Micropub, and IndieAuth. While existing accounts on the service are still supported, the company is not accepting new customers or accounts at this time.
(need specifics on all the above)
Sites or tools that have in-progress (pending) work to make them more IndieWeb Friendly
There was a pull request to improve Pandoc templates to generate h-entry but no record of it exists in the repository or in The Internet Archive.
Ideally, someone building a service who wants the service to be IndieWeb-friendly should be able to come to this page and have a clear path of how to do so. In addition to a clear guide with examples of things like adding h-entry to posts, h-card to authors, etc, we should also provide links to tools that can validate or test the markup.
Sites that had some IndieWeb friendliness but appear to have been shut down or experienced site-death.
- App.net supported several indieweb building blocks, outlined in Dalton’s response to Brennan Novak part 2.