IndieWebCamp September 5-12, 2014

This is an automatically-generated summary of the IndieWebCamp wiki edits from September 5-12, 2014

Table of Contents

New Pages

Changed Pages

New Pages


Created by on September 10

indie-config is a method of using protocol handlers and postmessage to setup your indie website to both notify the browser that it can handle webactions and then do so.

indie-config was introduced and discussed at IndieWebCampUK 2014



By setting up indie-config on your personal site, you can then click on web action links or buttons on others sites (e.g. "Reply", "Favorite" etc.) and have those actions automatically activate your site's posting interface to.


How to setup indie-config on your personal site:

Create the configuration page

Create a page on your site that only you will need to access. This might be a page such as "config.html". This page should contain the following Javascript:

(function() {
  if (window.parent !== window) {
      // The endpoint you use to write replies
      reply: '{url}'
    }), '*');

Replace the URL above with the URL to your own posting interface.

Register the web action protocol

On your home page, find somewhere to add this code to be displayed only to you when you are signed in to your own site.

window.navigator.registerProtocolHandler('web+action', '', 'Aaron Parecki');

Note that you will want to replace the URLs ( and my name ('Aaron Parecki') with your own information. You should replace the URL with the page you made in the previous step. The text you add as the third parameter will be shown in the browser prompt, so it makes sense to use your name or possibly the name of your site's software.

Turn it on

Now when you visit your home page, you will see a prompt asking whether your site should be allowed to handle "web+action://" links.


Click "Add Application" (or the equivalent for your browser) and your website is now registered in your browser or operating system.


How to load someones indie-config

An example Promise-based indie-config loader:

// Lazy-create and return an indie-config load promise
// The promise will be resolved with a config once the indie-config has been loaded
var loadIndieConfig = function () {

  // Create the Promise to return
  var loadPromise = new Promise(function (resolve) {

    // Parse the incoming messages
    var parseIndieConfig = function (message) {

      // Check if the message comes from the indieConfigFrame we added (or from some other frame)
      if (message.source !== indieConfigFrame.contentWindow) {

      var indieConfig;

      // Try to parse the config, it can be malformed
      try {
        indieConfig = JSON.parse(;
      } catch (e) {}

      // We're done – remove the frame and event listener
      window.removeEventListener('message', parseIndieConfig);
      indieConfigFrame = undefined;

      // And resolve the promise with the loaded indie-config

    // Listen for messages from the added iframe and parse those messages
    window.addEventListener('message', parseIndieConfig);

    // Create a hidden iframe pointing to something using the web+action: protocol
    var indieConfigFrame = document.createElement('iframe');
    indieConfigFrame.src = 'web+action:load';
    document.getElementsByTagName('body')[0].appendChild(indieConfigFrame); = 'none';

  // Ensure that subsequent invocations return the same promise
  loadIndieConfig = function () {
    return loadPromise;

  return loadPromise;


Ok to registerProtocol handler every time

Q: Is it ok to run that register protocol thing every time I load my home page?

A: Yes it is ok. If you run the registerProtocolHandler() on the same page that's already registered nothing will happen – it will know that everything is registered as it should.

Using custom handler for replies instead of configuration

Q: Why does the custom handler send back configuration information instead of just handling replies directly? (i.e., web+action://permalink would be handled by with

A: This does not provide a fallback if there is no handler registered. There would be a <a href="web+action://permalink">Reply</a> link on the page that would go nowhere


Q: Couldn't you use isProtocolHandlerRegistered to check if a handler is registered, and only use the custom protocol if it is?

A: That function doesn't exist! And it would be a potential privacy leak, e.g., allowing sites to see which apps you have installed on your phone by checking facebook:, twitter:, etc..

See Also


Created by on September 7

  • Sun, September 7 stub with need to copy
  • Sun, September 7 Removed stub status, added tantek’s notes from IRC, linked to kevin’s notes
  • Tue, September 9 headers for intro demos, hack day demos, add IRC link to start with
  • Fri, September 12 /* Hack Day Demos */ write up Hack Day demos from my IRC notes and memory.
  • Fri, September 12 shorten headlines for narrower TOC


Start Demos

Demos from the 2014/UK/Introduction.

Transcribed from IRC Logs.

See also: Kevin’s IWC UK Selfdogfooding Demos Notes

Tantek Çelik

  • I just demonstrated /https Level 2 support on my site
  • also showed that relmeauth.php is currently broken so I need help with that
  • demonstrated signing in with @t - using Twitter for sign-in to my own site
  • showed that the session cookie that is set is sent on Encrypted Connections Only

Jeremy Keith

  • noted he got webmentions working last year
  • since then he got notes posting working on his site
  • including POSSEing to Twitter
  • when he's logged into his own site he goes to, it has a textarea at the top because he's logged in
  • he posts a note there, which automatically POSSEs to Twitter
  • then using Bridgy, anyone who @-replies, or likes etc. shows up on his post original
  • also he has a "Choose File" button below his textarea — he can choose a picture which posts it to his own site
  • storing photos on his own site, will see how hosting fees go. He stores various forms of the image
  • uses srcset to serve small.jpg medium.jpg or large.jpg in the version of the image/photo post on his home page
  • POSSEs the photo to Twitter, also to Flickr
  • still hasn't moved his archives from Flickr to his own site, but nevermind the history, from now on, he hasn't given Flickr anything new — all the photos on Flickr since he implemented this are copies
  • narrows the window, shows responsive design on his, e.g. for a phone display
  • wanted to POSSE to Instagram but no API to post there — there is ownyourgram, which does a PESOS
  • Jeremy may try to get another instances of his updated software running, e.g. on his wife Jessica's site

Tom Morris

  • posts notes on there, primarily text based — occassionally photos and such
  • added recently: articles section:
  • uses Mozilla Persona to sign-in, using Rails+Omniauth. Persona was the only thing that didn't need an API Key, because he's not starting an app, he's signing into a website!
  • when Tom is logged in it just shows his posting interface at the top of his home page with title, text content, check boxes for POSSE to Facebook and Twitter
  • also has a full posting interface with tags, lat, long, location label, License popup
  • feature he's added recently
  • using for map tiles, which they also serve over https
  • each place he can associate with different things, has an edit link, lat long and an OpenStreetMap reference — clicking on that goes to the OpenStreetMap object for that place
  • also has a Add New Venue UI
  • would like to post photos on there at some point because still currently using Flickr, and Wikimedia commons, also wants to work on image resizing

Sam Machin

  • rather than posting things, working on owning his own communications — last year showed WebRTC to make a call
  • the idea is that we can replace all forms of phones with URLs
  • you call me by going to my page
  • your contacts become your bookmarks
  • goes to (front end code is running on github)
  • a lot of backend infrastructure you have to do to get working, so he's doing that as a separate open source setup, and separate static HTML+CSS to do the call stuff
  • "Voicemail is shit. Everyone hates it." -sammachin

Nat Welch

AKA icco

  • had the inverse problem — a bunch of sites that did webmentions and such
  • got rid of his entire hosting system
  • started version 2.0 on the train ride over here
  • old sites: (long form, markdown), (for people to tweet at him, site about when he was sad about thing) scraped pinboard links
  • next version is /natnatnat, as of four hours ago

Pelle Wessman

  • at last year's IndieWebCamp, got tired of hosting his own server
  • everytime he wanted to do something it was hard because he had to update Linux, so he's switched to github pages for everything
  • last year's IWC UK, worked on server for embedding webmentions on static pages, uses Jekyll on github pages
  • add a form at the bottom of each post like Jeremy for people to send their webmentions. It's embedded with JS, which pulls down the webmentions and displays them inline
  • the other service is a Heroku app —
  • you just sign in with github, add a basic rel=webmention link (it gives you the <link> code to copy / paste to your posts and the <script> to embed)
  • in addition wrote a tool to test webmentions, including XSS tests — "webmention-testpinger" also included in his webmention endpoint
  • it runs everytime automatically with every deployment and runs the tests to make sure they all pass
  • his herokuapp uses Glenn's microformats2js parser to retrieve the actual content of mentions

Glenn Jones

  • last year showed that he writes the articles on his blog are in HTML in a folder which syncs automatically to his server
  • but these days mostly uses his phone for writing notes, taking pictures, checkins. Went to build a completely new system:, built in Node.js
  • goes to, shows a Post UI with textarea built using ContentEditable (it's one of the worst pieces of the standard to work with) which automatically links URLs, @-names, hashtags
  • optional photo, checkin, reply; public/private lock toggle
  • clicking the reply option shows a "in-reply-to" URL field
  • added UI to "Push to" (POSSE) to other sites, e.g. Twitter — UI to *set up* POSSE, which is then automatic
  • everything in the system, if you put /json at the end, gives the JSON microformats for it, always just generated by parsing the HTML of the page
  • shows a "store at" UI for archiving/backing up his transmat posts as static files on his local laptop — all this HTML has the microformats markup of the original and a special manifest with offline CSS file
  • over the last year has been building it up experimentally
  • shows how bridgy is connected to his permalinks too, showing favorites and replies
  • "Reclaim your Tweets": you upload a Twitter zip file archive
  • Loads all your old tweets into Transmat
  • Glenn has imported all his old tweets to his own sites, including interactions with each tweet like favorites, retweets, and replies (not included in the archive)
  • as he goes through the tweets, he imports the account information for everyone he's interacted with to — goal is to eventually do autocomplete with that info while typing
  • has started adding places too:
  • can edit a place with a geofence, lat long radius
  • has a near.html page for figuring out which of *his* Places are nere where he is now

Shane Hudson

  • last time he was here was trying to use WordPress using webmention
  • gave up and wrote his own CMS, and gave up again and started to use Craft (
  • has not pushed it live yet ( still uses WordPress), craft version is at, has webmentions and fragmentions etc
  • last night built a geolocation thing (plugin?) for his Craft CMS — it automatically finds his geo
  • provides UI to enter heading, body, tags, mentioned URLs
  • has got webmentions working — somebody wrote a plugin for sending, so he wrote a plugin for receiving them
  • in order to switch to Craft, needs to move interactions on his WordPress posts to his Craft CMS

Andrew Marks

  • has a Known install setup, exploring IndieWeb stuff
  • has a soundcloud page - he makes music, also has a film blog on WordPress
  • quickly shows Known, demos posting photo
  • shows location checkin — quickly locates 68 Middle street

Tim Retout

  • Debian developer has discovered IndieWeb 2 weeks ago
  • shows his home page — backend in Node, has posts
  • using - set it up on his website the other weekend
  • shows that he has A+ SSL

Rosa Fox

  • Just noticed that my CSS doesn't work over https... should fix that!
  • has been working as web developer for 7 months!
  • static site, blog is linked to WordPress (
  • with rails has built a basic outline and deployed to Heroku, will be working on that this weekend

Barnaby Walters

  • now demoing
  • fed up with looking at 20 different sites, wanted to build a reader, didn't want to have to visit twitter to read people's stuff
  • first got distracted and built open source yahoo pipes called "intertubes" (It's Yahoo! Pipes but without the sunsetting feature), then got back to his use-case
  • built Shrewdness - essentially a Tweetdeck clone
  • you can subscribe to a bunch of URLs, e.g. twitter-style firehose feed of everyone he follows on twitter
  • it only parses microformats2, doesn't touch the twitter API at all, still gets twitter info via a twitter to microformats2 proxy converter
  • second column is his mentions, all webmentions to his site show up there
  • third column is search (using elastic search on the backend)
  • can't figure out what it means by relevant, so just uses ordered by date
  • demonstrates multiple searches, creating a new search column
  • barnabywalters site supports micropub — it's a way of having your website having an API that client apps can post to. With this you can use other people's client software to post to your site
  • this enables "Reply" buttons in shrewdness
  • connected to his site, posted a reply from within shrewdness and shows that the reply has been posted on
  • subscribed to over 60 feeds in shrewdness, all based on microformats2 — no need to support RSS or Atom

Al Power

  • loves playing with CMSs, classic tinkerer, also photographer
  • trying out kirby and perch

Joschi Kuphal, @jkphl

  • has implemented webmentions receiving on his site
  • posting articles now, would like to post photos, notes etc.
  • Using Typo3, popular open source CMS in central Europe
  • would like to put some of these functionality into Typo3 extensions
  • wrote an Indieweb plugin for Typo3

Calum Ryan @calum_ryan

  • has another site — shows based on Modux(sp?)

Hack Day Demos

Demos from the Hack Day!

Transcribed from

See also: Kevin’s IndieWebCamp UK Demos 2014-09-07 notes.

Glenn Jones

Glenn built improvements to transmat. (IRC notes).

He built a map view that shows the venues nearest to his current location (via GeoLocation API).

He also found an open source HTML5 JS open source pedometer and repurposed it into transmat so that when running on his Android as a web app, it can detect when he's walking, and only do GPS lookups when he's walking, so it saves battery.

Now he has an HTML5 JS app that can auto-checkin for him while he's walking.

Barnaby and Pelle

Barnaby and Pelle built cross-site reply webactions that work purely via their websites - no browser extension needed! (first time this has been done; IRC notes).

Barnaby has setup registerProtocolHandler on Taproot to register a handler for the "web+indie:" protocol when he loads a particular page on his website so that his website is registered to handle web actions via the <indie-action> tag.

Barnaby demonstrates loading the page that calls registerProtocolHandler. The browser asks to confirm that he wants to handle "web+indie" URLs.

Then Baranby goes to Pelle's website home page where he has a list of posts that he's written, with <indie-action> tags next each with "Reply", "Like", and "Tip" webactions.

Pelle's site also has a web component (open sourced on github) to handle his <indie-action> tags, which creates an iframe that uses that same protocol handler using a Promise, which connects the iframe to calling the handler that Taproot registered.

Thus without anything installed in the browser, barnabywalters can go to voxpelli_'s site, click the Reply button that was there which automatically goes to barnabywalters Taproot UI to post a reply!

Barnaby Walters

Barnaby also built a map-view aggregator that shows icons for people at the locations embedded in their recent posts. (IRC notes)

This is a demo URL for now, but Barnaby plans to include this map view as another column type in shrewdness, so you can have a map view of recent posts from people you're following.


Grant got a fancy new domain and setup transmat on it - which makes it the second installation of transmat! (IRC notes).

And also built a contact page:

It has links and text for various methods:

but no icons yet.

Grant has implemented a people focused communication UI on his site!

Jeremy Keith

adactio https

Jeremy Keith has gotten https working on! (IRC notes).

Jeremy has achieved https Level 4. All URLs redirect to https. However subdomains (e.g. are still http.

adactio webactions

Jeremy's also implemented the new <indie-action> tag for webactions around his existing Tweet action links, both on his post permalinks, and on his posts in-stream (e.g. on his home page or when paginated).

Shane Hudson

Shane went from no SSL and no comments yesterday to https level 5! He also imported the contents of all his old comments from his WordPress blog to his Craft install (the CMS he's dogfooding, contributing plugins to, selfdogfooding). (IRC notes).

He was able to get SSL setup on his site with an A rating, and forward secrecy, and is thus https level 5.

Shane also wrote a script to do the import of comments from WordPress to Craft. It's "a bit crude, dealing with XML to CSV a few times".

Nat Welch

Nat Welch (AKA icco on IRC) got his blog running (his own software) in Go hosted on AppEngine with SSL, achieving https level 4! (IRC notes).

AppEngine does SSL for free if you're ok with SNI.

So now Nat has SSL Labs rating A- on! And also automatic redirect works from http to https. Thus he has also achieved https Level 4!

Right now he's using AppEngine default auth, using his Google account. Eventually he wants to use indieauth to auth into his site.

Tim Retout

Tim got running on his site and added support to it for POSSEing to Twitter. (IRC notes)

His goal is to add all the indieweb feature support too like webmentions, microformats etc. He has to run off to catch a train.

He is also too humble, as he helped numerous people in person at the camp get on SSL, https level 4 or 5 at that. A round of applause for Tim![1]

Tom Morris


Tom shows his current site His CSS is now "less sucky" and made his site more responsive on mobile / small display etc. (IRC notes)

mf2py as a service

Tom also got the Python microformats2 parser (mf2py) running as a service that you can submit your URLs to and get back pretty-printed JSON.

tommorris https

Tom got his main site up to https Level 4 with an A- rating, but has not yet done so with * (e.g.

During the next demo, Tom got his SSL Labs rating from A- to A with some help from Aral. And during the demo after that took his rating up to A+ thanks to the post:

Kevin Beynon

Kevin got IndieAuth login to his own site working! (IRC notes)

Kevin started by showing us his site home page using a tablet. We projected it by holding up to the Talky HD camera.

He pointed out that there is no admin link on the home page then went to his "secret" URL at /admin/ which has an IndieAuth login screen. He entered his own URL, and chose to RelMeAuth authenticate using Twitter which redirected to it and back and came back with the message "Log-in Successful".

Kevin went to his home page again, and showed that it now has visible links to "admin" and "log out". Next he plans to bring his post creating and editing interface into his home page front end, so that he can do inline editing and post notes from his home page.

Joschi Kuphal

Joschi got his site's https support to SSL rating A+, fixed his webmention implementation, and implemented webactions on permalinks. (IRC notes)

jkphl https A+

Joschi noted that his site was running with SSL before but had some flaws. He worked on it and improved his site's rating from F to A+.

jkphl webmentions fixed

He also fixed some flaws with his webmention implementation thanks to feedback from Ryan Barrett online.

jkphl permalinks webactions

Third, Joschi implemented webactions on permalinks, in particular he added <indie-action> markup around his default Twitter, G+, Facebook "share" links. He then demonstrated his site working with Barnaby Walters's Web Action Hero Toolkit browser extension.

Chris Asteriou

Chris is fairly new to the IndieWeb and started with going through IndieMark, adding h-entry and h-card markup, and a notes section to his site.(IRC notes)

digitalbliss microformats

Chris showed, noted that he added h-entry on his page with entries. He clicked the "Play" link at top to show this. And then he marked up the info at bottom of his home page with h-card.

digitalbliss notes

Chris added a notes section and used the verification tools on to check it and verify that he reached IndieMark Level 2.


Tantek switched his permalink webactions from <action> tags to <indie-action> tags and researched the UX of webactions on posts in a stream (e.g. a home page).

tantek indie-action

Based on the webactions discussion session in the first day with Tantek, Jeremy, and Pelle, they concluded that the <indie-action> tag was more appropriate than the <action> tag.

Tantek initially publicly proposed the <action> tag for consideration in a session on Web Actions at Open Source Bridge 2012, and then later implemented them at last year's IndieWebcampUK 2013 which were then demonstrated working with Barnaby Walters's browser extension.

Changing from <action> to <indie-action> at a minimum better fits with the web component model. Jeremy Keith pointed out that an <indie-action> tag in particular would be a good example of a web component, worthy as a case-study for web components.

Tantek updated his permalink webactions to use <indie-action> tags and Barnaby updated his browser extension to support them as well.

in-stream webactions

Tantek analyzed the UI of various silos, in particular Instagram and Twitter.

Instagram has a very minimal simple webaction UI, with just "Like", "Comment", and "..." (more) buttons, the first two with both icon and text labels, which makes sense since their primary content is large (relative to the UI) images/video (visual media). Instagram's webactions are identical on photos viewed on their own screen, and when in a stream of media. Deliberately designed consistency.

Twitter on the other hand is horribly inconsistent between different views of tweets, and even different streams, sometimes their webactions are:

  • on the right with text labels
  • on the left with no text labels

Their trend seems to be icon only, likely because the text label distracts from the tweet text content around it, especially in a stream of tweets that are primarily (nearly all) just text.

Tantek walked through comparisons of Twitter's different webactions button icon/text usage/placements with Aral, who came to the same conclusions from the data.

It may be ok to use both icon and text labels on note/post permalink pages, as there is more distinction between the (single) content area, and the footer of webactions.

However, the conclusions is that in-stream webactions should use just icons (clear ones at that) when among posts that are primarily, mostly, or perhaps even often just text.

Next Tantek is working on implementing icon-only webactions on his home page posts stream. He made some progress but realized it will require him to rework some storage code first.

Aral Balkan

Aral upgraded his site's https support to SSL rating A+ and https Level 5, and his how-to blog post about it! (IRC notes)

Aral already supported https on his site beforehand. On IndieWebCampUK hack day he added support for forward secrecy, which raised its SSL rating from A- to A+ and thus he achieved https Level 5!

Apparently it took him only 2 lines of code to implement that change on nginx, and noted that it's a bit harder on Apache.

After his demo, Aral also updated his blog post about SSL setup with nginx with what he learned and how to get to SSL rating A+.

Rosa Emerald

Rosa created a UI on her site for CRUD posting of projects. (IRC notes)

Rosa wanted to make her own CMS with support for posting images and tags. She demonstrated her local dev install of her new CMS with:

  • a UI for creating a new project
  • CRUD posting interface for projects
  • using Postgres to store data

Aaron Parecki

Aaron participated remotely, added support for posting bookmarks to his site, and added bookmarks posting via micropub to his Quill app! (IRC notes)

Aaron has been publishing bookmarks to another place for a long time in a [[WordPress] install at and he wanted to integrate them into his main site

Once Aaron got the bookmark post type implemented in his publishing software p3k and deployed to his site, he did a mass import from the WordPress XML export.

That was the last thing aaronpk was using WordPress for, so he's no longer using WordPress to publish any of his own content.

Now all of Aaron's bookmarks are at all marked up with microformats. Each bookmark is an h-entry, and embedded inside is an h-cite of the bookmark itself.

This also means you can comment, bookmark, and like his bookmarks themselves!

During later demos, Aaron also updated his Quill app with a bookmark posting interface, as well as a bookmarklet so you can quickly open the Quill UI to make a bookmark.

Kevin Marks

Kevin built a feed coverter that takes legacy RSS/Atom feeds and produces modern readable and usable h-entry page, including such niceties as inline playable audio elements in converted podcasts. (IRC notes)

Kevin noticed that people are building h-feed readers, so he built a tool that takes legacy RSS Atom feeds and unmunges them and produces nice clean h-entry feeds.

The converter is at is a URL he bought ages ago, and set it up on Google AppEngine.

E.g. if you put in into it, it generates a nice readable HTML page with h-entry, which you can then subscribe to in an indie reader like Barnaby's shrewdness.

Kevin demonstrated using unmung to convert a podcast feed into an h-feed with embedded playable HTML5 <audio> elements, providing an actual useful interface, much better than the original feed.

Kevin made the point that no one wants to parse RSS or Atom any more. Now by parsing the microformats JSON representation, you can get any existing RSS or Atom etc.

You can now subscribe to iTunes podcasts etc. in your indieweb reader!

Robin Taylor

Robin added support for https (including forward secrecy, getting an SSL "A" rating) to his site and automatic redirects from http to https, achieving https Level 5! (IRC notes)

UK Homebrew Website Clubs

As we were wrapping up, Tom Morris asked openly if anyone would be interested in coming to a Homebrew Website Club in London. Jeremy Keith similarly asked the group for interest in a Homebrew Website Club Brighton.

Both had quite a bit of interest, so we can expect to start seeing more Homebrew Website Club meetups in more locations!


The people I met at @indiewebcamp are the A-Team of the Internet. Give them some tape and an oxy-acetalyne torch and they'll fix the web.


Created by on September 7

SPDY is a protocol similar to HTTP with some optimizations to reduce latency and is the basis of HTTP/2.

The design of SPDY requires SSL, which is a barrier to entry, enforcing it as a secure protocol. It also has compression (gzip or DEFLATE) by default so that it is always fast. These two design principles are very opinionated, unlike HTTP which can (and often is) be used in inefficient and insecure ways.


IndieWeb Examples

Community members that have deployed SPDY support on their primary personal website.

David Shanske


SPDYCheck can check a website for support.

Impact on best practices

Once SPDY or HTTP/2 is in all modern browsers, best practices may no longer be accurate due to the way the protocol has built-in minification and concatenation. Until then, we should probably still be minifying and concatenating so that browsers that aren't supported will still be quick.

See Also


Created by on September 6

The opening IndieWebCamp 2014 UK session.

IndieWebCamp leaders will lead you through:

  1. Announce: Welcome to the 3rd annual IndieWebCampUK!
  2. Show Squarespace parody video
  3. Tell brief history:
  4. Show home page and principles
  5. Note explicit decision to focus on
    • personal site "scratch your own itch" doers, doing, selfdogfooding, demoing
  6. Overview of IndieWebCamp Two Days:
    • day 1: intro/demos, lunch, brainstorming sessions, dinner
    • day 2: day two hack sessions, lunch, hack sessions, demos
  7. Demos of what works on your site today - note: must be a demo on your primary personal website (NOT: a secondary site, demo deployment, other corp/school/org site, random github library - this is a challenge to get your stuff working on your public personal site - if you won't put it on yours, why should anyone else on theirs?)
  8. Explanation of today (brainstorming sessions) vs tomorrow (hack sessions)
  9. Intro to how Barcamp sessions are scheduled: write THREE THINGS on a notecard:
    1. session name,
    2. your name,
    3. session #hashtag - used for tagging and
  10. Session scheduling!
  11. Camp leaders call *start your sesssions* at start time



See Also


Created by on September 7

Unmung is a service that turns legacy feeds into h-feeds.


To use unmung, go to and enter the URL of an Atom or RSS feed, for example Daring Fireball

You get an h-feed rendition of the feed.

This means you can subscribe to legacy feeds using shrewdness, eg like this

hacked for IndieWebUK 2014 by Kevin Marks

code on github

Created by on September 7

  • Sun, September 7 Created page with "==About Me== ⚒ UX Designer for [ Wikimedia Foundation] + [ Wikipedia]. Made [ How Wrong You Are]..."
  • Sun, September 7 /* About Me */

About Me

⚒ UX Designer for Wikimedia Foundation + Wikipedia.

Made How Wrong You Are.



Created by on September 9

  • Tue, September 9 Created page with "{{stub}} '''<dfn>[ DigitalOcean]</dfn>''' is a [[web hosting]] provider targeted towards developers and offers low cost cloud servers in data centers acr..."
  • Tue, September 9 tell about who is using digitalocean and their irc channel

DigitalOcean is a web hosting provider targeted towards developers and offers low cost cloud servers in data centers across the world.


DigitalOcean has an IRC channel on freenode; #digitalocean

IndieWeb community members using DigitalOcean

See Also

Created by on September 7

  • Sun, September 7 Created page with "is [ Joschi Kuphal]"

is Joschi Kuphal


Created by on September 6

주요 원칙

🗽 인디 웹을 구성하는 데 있어 주요한 원칙들입니다...

  • 여러분의 데이터를 직접 소유하세요.
  • 🔍사람에게 먼저 눈에 보이고 그다음 컴퓨터입니다. (참고. DRY)
  • 💪친구들이 아닌 여러분 자신을 위한 도구를 만드세요. Metcalfe 법칙을 위배하긴 어렵습니다: 인디 웹에 참여하면, 모든 친구를 설득시킬 수 없습니다. 그러나, 여러분 자신의 필요를 충족하는 것을 만든다면, 참여하지 않은 사람에게도 호환될 것입니다. (참고. POSSE) 여러분 자신을 위한 도구를 만드는 시간이나 노력은 다른 이들이 아직 참여하지 않았기에 멋진 시간이 될 것입니다.
  • 😋개밥먹기를 해야 합니다. Whatever you build should be for yourself. If you aren't depending on it, why should anybody else? We call that selfdogfooding. More importantly, build the indieweb around your needs. If you design tools for some hypothetical user, they may not actually exist; if you build tools for yourself, you actually do exist. selfdogfooding is also a form of "proof of work" to help focus on productive interactions.
  • 📓Document your stuff. You've built a place to speak your mind, use it to document your processes, ideas, designs and code. At least document it for your future self.
  • 💞Open source your stuff! You don't have to, of course, but if you like the existence of the indie web, making your code open source means other people can get on the indie web quicker and easier.
  • 📐UX and design is more important than protocols. We focus on UX first, and then as we figure that out we build/develop/subset the absolutely simplest most minimal protocols sufficient to support that UX, and nothing more.
  • 🌐Build platform agnostic platforms. The more your code is modular and composed of pieces you can swap out, the less dependent you are on a particular device, UI, templating language, API, backend language, storage model, database, platform. The more your code is modular, the greater the chance that at least some of it can and will be re-used, improved, which you can then reincorporate.
  • 🗿Build for the long web. If human society is are able to preserve ancient papyrus, Victorian photographs and dinosaur bones, we should be able to build web technology that doesn't require us to destroy everything we've done every few years in the name of progress.
  • 🎉Have fun. Remember that GeoCities page you built back in the mid-90s? The one with the Java applets, garish green background and seventeen animated GIFs? It may have been ugly, badly coded and sucky, but it was fun, damnit. Keep the web weird and interesting.


🌈 With IndieWebCamp we've specifically chosen to encourage and embrace a diversity of approaches & implementations.

This background makes the IndieWeb stronger and more resilient than any one (often monoculture) approach.

One of the key things we recognize with IndieWebCamp is that no one project is likely to be the answer.

We're much more likely to advance the state of the art by encouraging everyone to build what works for them, and then figure out how to interoperate between different coding/implementation approaches. This is what makes IndieWebCamp different (more inclusive) than all other such "open source" efforts out there.

📑Multiple implementation efforts help to simultaneously explore different parts of the indieweb problem space as we're all choosing to focus on building the particular aspects of what's important in an indie web site for ourselves. Additionally, multiple approaches to the same problems in essence A/B(/C/D/...) test different approaches simultaneously, each of which can then learn from and evolve in response to the others.

This parallel diversity both produces better indie web solutions faster, and allows for the incorporation of new approaches to address new problems, adapting as the needs of an indie web site change over time.



  • There seems to be an unwritten principle of focusing on UX that I've encountered multiple times while participating in the indieweb community. A recent example where it was cited is this. Should we make it explicit? (see also [1]) 18:54, 7 July 2013 (PDT)
    • Added explicit principle above about UX/design. - Tantek 13:40, 24 August 2013 (PDT)


This article was quoted nearly verbatim in WIRED:

See Also


Created by on September 6

google_announcement.png 웹 사이트 폐쇄란 서비스가 종료되어 더 이상 콘텐츠 영구 링크가 제공되지 않아 웹 상에서 연결이 중단되고 찾을 수 없는 상태가 되는 것입니다. 웹 사이트 폐쇄의 문제는 여러분의 콘텐츠와 정체성을 웹 상에서 지키기 위한 중요한 이유입니다.

콘텐츠 호스틍 웹 사이트가 문을 닫은 역사를 보면 수백만 혹은 수십억개의 퍼머링크가 웹 상에 삭제되었고, 이들 사이트에는 많은 일반 사용자의 글과 콘텐츠가 올려져 있었습니다. 웹 사이트 뿐만 아니라 모바일 앱에서도 사용자 데이터가 없어지는데, 게임이 종료되어도 사용자의 등급, 활동 기록이 사라지며, 지메일이 종료된다면 공개 링크 정보가 아니더라도 사용자 메일 정보가 없어집니다.

큰 기업일 수록 서비스를 종료하는 사례가 많으며 사용자들의 데이터를 삭제하는 빈도가 높으며 Andy Baio의 사례에서 보듯이 만들고, 성장하고, 인수되고, 각성하고, 관심이 떨어지고 문을 닫게 됩니다.


종료 예정 사이트

웹 사이트가 종료되는 예정 목록 및 현황을 보실 수 있습니다:

사이트 종료가 예정 혹은 공지 되었다면, 아래의 방법대로 확인을 부탁드립니다.

  • 종료가 확인 되었다면, 연도별로 중단 완료로 이동해 주세요.
  • 종료일자가 지나도 아직 제공중이면, 중단 예정으로 이동해 주세요.
  • [site-deaths|해외 사이트 종료 현황]을 꼭 보시기 바랍니다.




더 바세히 보기


Created by on September 6

"여러분은 뭔가 알기 때문에 여기와 있습니다. 설명하기는 어렵더라도 느끼고 계시는 거죠. 아마 인생을 살아가면서 계속 느꼈을 거에요. 세상 (웹)이 잘못 돌아가고 있다는 것을..." — Morpheus, The Matrix

이유야 어떻던간에 여러분은 온라인 상에 콘텐츠, 정체성 및 자신을 투영시키고 있습니다. 그렇지만, 아무때나 문을 닫는 스타트업 기업이나 아주 거대 서비스 사일로의 입장에서는 별로 안전하지 않습니다. 우리는 우리 손으로 우리 데이터를 지켜야 합니다.


왜 인디 웹인가

왜 자기 웹 사이트가 있어야 하는가

더 나은 사용자 경험

  • 더 나은 UI/UX. 예) Twitter보다 더 나은 네비게이션 및 간단한 인용 인터페이스를 만들 수 있음 [1].


  • 맞춤형 시각 디자인: 모든 사람이 TwitterYouTube 같은 디자인을 좋아하지 않습니다. "아니야, 이거 보다는 내가 원하는 건 이거야"라고 말할 수 있는 것이 중요하고 그래픽 스타일 선호에 따른 혁신의 자유가 있는 것이 매우 중요합니다.
  • The freedom to decide what content and what types of content to publish. Set your own rules and your own limits. Erik 21:53, 3 July 2013 (PDT)
    • Longer notes. Host notes on your own site that are longer (perhaps even just slightly) than the 140 character Twitter limitation . Tantek 16:58, 27 February 2013 (PST)

권한 위임

  • Richer content embedding. Auto-embed images, video, and any other rich content you want from your own notes, instead of waiting for Twitter to implement it. E.g. compare original and tweet copy. Tantek 16:58, 27 February 2013 (PST)
  • APIs only expose some aspects of your data: having your data under your control allows you to add new functionality to that data, adding new methods of discovery and connection based on the specific shape of that content.

저자 중심

  • Link destinations see you / your site as a referrer and credit you with sending traffic. Some silos (Twitter, Facebook, YouTube) wrap all links published in posts with their own link-redirectors (,, thus making the link destination think they're getting traffic from the silo in general, rather than from you and your profile. Links on your own site, however, notify destinations through the HTTP REFERER (sic) that your site (and thus you) are sending them traffic directly. Tantek 15:09, 13 March 2013 (PDT)
  • Amazon affiliate links work. As part of their link-wrapping strategy, silos (e.g. Twitter, Facebook) may strip affiliate information from Amazon links, and/or only link to the where an Amazon link redirects to, and/or add their own silo-specific Amazon affiliate code to all the Amazon links in your posts! When you publish Amazon affiliate links in posts on your own site, the links work as expected. Tantek 15:09, 13 March 2013 (PDT)

보다 견고함

문제 해피

콘텐츠 분실

낮은 신뢰성

정체성 분실

사이트 분실


콘텐츠 도둑

  • Your art has been sold without your permission (or notification!) to a 3rd party who then profited from it, e.g. deviantART selling your work.
  • You aren't happy that silo owners could use your work without compensation. (Instagram's terms of service change in January 2013 will allow them to use your work for "in connection with paid or sponsored content or promotions, without any compensation to you" - see [9]).
  • Your content was taken and its ownership errantly transferred to a big content copyright holder / media company. (YouTube video upload, 2012)

콘텐츠 및 정체성 어뷰징

  • You dislike your identity being used to advertise stuff you never consented to advertise. Facebook again.
  • You dislike seeing your content on silos surrounded by ads. Facebook puts adds in the sidebar next to anything you post. Other silos do so similarly.

Personalisation/filter bubble

  • Facebook attempts to target you specifically with content you enjoy and thus creates filter bubbles. Over-personalisation of content by social media silos means you are often left unexposed to material you would find interesting or informative but which the algorithm has decided isn't for you.
  • In 2012, Facebook conducted a study where they "manipulated the emotional content" of user's news feeds in order to see how people would react if they changed the ratio of positive to negative stories in feeds. This study was done without the consent of the users and a member of Facebook's data science team apologised after the study was published and then criticised. Personalisation apparently now also includes personalisation for the purpose of psychological experimentation.

Negative community

  • You aren't happy with the community or perceived community that comes baked in with the silo-based tools you use to publish. Perhaps you want to share photos of things you like without people making assumptions regarding your gender or race or social class (see danah boyd's The Not-So-Hidden Politics of Class Online).

Why Indie Web Camp?

  • You're here because you know this and you want to design and build a web presence where you're in control.
  • Maybe you bought your own domain for vanity reasons but now want to put it to good use.

We, the organizers of IndieWebCamp want that as well, and have started building it for ourselves.

Join us and together we can grow the IndieWeb.

(More motivational examples/citations linked from: "Itches & Scratches: sharecropping and site death" - 2010-199 Federated Social Web Summit talk by Tantek)

Why Indie Web Camp community?

  • Because building the IndieWeb is a continuous process. The IndieWebCamp event is inspiring, but we need to carry on doing so for more than a few days a year when we meet in real life.
  • Because we can support one another and share the best way to do things.
  • As we discover new ways to do things, we can document the crap out of them.
  • Because some of you live out in the middle of nowhere. You are welcome to join in too!

see also


Created by on September 7

  • Sun, September 7 Created page with "[ Ello] is microblogging silo similar to Twitter or Tumblr for posting short status updates and pictures. Ello offer threaded commenting and a minimalist "designy"..."

Ello is microblogging silo similar to Twitter or Tumblr for posting short status updates and pictures. Ello offer threaded commenting and a minimalist "designy" feel to it with some unusual (but nice) UX animations & interface ideas. As of Sep. 2014 Ello is currently in invite only.


Ello is a simple, beautiful, and ad-free social network created by a small group of artists and designers. We originally built Ello as a private social network. Over time, so many people wanted to join Ello that we built a public version of Ello for everyone to use. About


Created by on September 7

Jeremy Keith

Created by on September 7



Created by on September 10

Tom Morris


Created by on September 10

  • Wed, September 10 etherpad dump from

IndieWebCampUK 2014

2014-09-07 webactions hack session

switching from <action> to <indie-action> per web components convention.

some updates to

Twitter is inconsistent about in-stream webaction UI. semi-consistent:

  • left aligned - underneath the text (datetime is on same line as author icon name at top)
  • grey icons only - no text label (some views have counts of faves, retweets)
  • favorite, retweet, repost

So will likely imitate that.

2-3 specific webactions at most any more, use a (...) "more" menu/popup for more choices, e.g.:

  • email post
  • embed post
  • mute author
  • block or report author

2014-09-06 in-stream web actions

buttons like: Like - Repost - Reply

under each post - on a permalink e.g. - in stream e.g.

Tantek demos the fallback webaction to like -> favorite on Twitter e.g. on

Barnaby demos how it works for him with the Webaction Hero Toolkit Browser Add-on with a Reply button.

on , because the <action> tag uses the "inline" attribute, it puts in an iframe for barnaby to write a comment.

part of the reason to add webactions to posts inline is that silos are doing and have taught users to do it.

Silo Examples:

  • Twitter - appears to be moving to showing tweet actions left-aligned underneath each tweet
  • Facebook - Like/Comment

see also wiki pages

Facebook has a read it later / save feature as well:

Appears that silos have been converging on putting actions on the left side, underneath a post. Twitter, Instagram, Facebook

Another possibility: Options: Twitter: Favorite, Retweet, Reply Facebook: _________

See Also

Created by user:danlyke on September 11

Hello World user:danlyke

Created by user:danlyke on September 11

  • Thu, September 11 user:danlyke Created page with "Home page at"

Home page at


Created by on September 10

  • Wed, September 10 etherpad dump from

Glenn jones talking about transmat

it powers (not the articles section yet but everything else) "Our Mac App stores all your content in HTML. This format is both readable offline and has true longevity. The HTML contains a full copy of all your data and can be used as a backup" nice!

will likely use the wordpress model. hosted service and open source version

core event and plugin structure.. Node events i presume?

would be easy to add an ftp plugin

webmentions arrive at glen and then are forwarded to transmat to be handled. still in prototype mode, but will be supported on all transmat sites.

talking about all the different little parts of transmat that are available at (the microformat parser is top notch in node!) - autolinker - markdown processor - microformats parser - webmention endpoint/forwarding/processing

"its like elastic search with a UI/UX for independent publishing"


Created by on September 10

  • Wed, September 10 etherpad dump from

Security IndieWebCamp UK 2014

  • Let’s at least not get embarrassingly hacked
  • For HTTPS: need a cert signed by a commonly-trusted authority
    • StartSSL are free
    • Globalsign will give out free wildcard certs to open source projects
  • Which certificate?
    • Basic SSL cert will cover bare domain and www. (tom: because who wants to type www all the time)
    • Generate at least 2048 bit key
    • Don’t get a SHA1 cert, it’s being phased — get a SHA2


  • you generate a key (.key file) — this never leaves your server
  • you generate a certificate signing request (.csr)
  • you send the CSR to the authority (NOT the .key)
  • you get a certificate (either .crt or .pem) which is signed by the authority

Jeremy: this stuff isn’t easy, esp. for people who’ve just learnt HTML+CSS — why isn’t there a GUI where you can press a button and it’s done? Tim: With StartSSL there’s no need to use the CLI, you can do it all in the browser [ed: how? need docs!]

First: get HTTPS working Then, make sure all that effort wasn’t wasted:

  • redirect HTTP -> HTTPS
    • some web application frameworks give you hooks to ensure URLs are protected
  • add HSTS header
  • make sure your cookies are secure (only served over HTTPS) and HTTP-only (XSS attacks can’t access them via JS)
  • avoid mixed content warning

Intermediate certificates: when a root authority gives someone else the ability to sign, and they sign you, you need to provide both your cert and any intermediate certs, concatenated in the same file [in what order?]

Created by on September 12

twitter @jboy irc yobj github jboynyc


Created by on September 10

  • Wed, September 10 etherpad dump from

Location IndieWebCamp UK 2014

Glenn: wants to be able to do last-checkin discovery for people, enabling maps of where people were last seen.

Barnaby: could be implemented easily using latest h-entry with location on homepage + location algorithm

adactio’s been storing his location on blog posts for two years, not sure what to do with it.

Tom Morris: thinking of storing location automatically, making location checkbox toggle public display rather than collection.

Glenn: if we’re all posting reasonable checkins we can start to build aggregation tools enabling foursquare-like use cases

Tom: handling OSM data is tricky because there’s so much of it and you want it all to hand at once to get useful results.

Tom: fireagle used to have location accuracy as an oauth option — you could even choose to share country-level data only, which still has legitimate uses.

Glenn: we’ve all been publishing location data assuming that it’s accurate, but that’s not the case, which starts to really matter once you consume the data. The HTML5 geo API gives us accuracy in metres, we need to publish this in microformats.

Possibility of using h-feed + h-entry + location + rel next/prev to crawl feeds and build up a history of people’s location.


Created by on September 10

  • Wed, September 10 etherpad dump from

2014-09-06 Indie Communications one of several IndieWebCampUK 2014 sessions!

14:45-16:20 Some background posts on indie communications

CIP - can redirect home phone to mobile, etc

telephony - not changed much since 1876! Mechanical phone exchange numbers, dialling, switching

comms - hangouts, skyper, viber, whatsapp, facetime,

whatsapp - uses phone number...

forget phone number - use URL and build it on the web!!

Closed ecosystem... can only facetime if have facetime account... can only skype with skype account

Social identity - this is how you contact me

Web RTC - protocol can carry anything

peer to peer goes between two browsers

data channels audio/video real time

Real time text

Google hangouts uses web rtc but it is still closed

Moving real time session data between people

Mozilla - still need account on the system

voice codec if sending voice... streaming

Phono: Calling in interface - browser to browser

Ben Roberts thatmustbeme/contact

You could choose the way that you want to be contacted, stops you getting called in the middle of the night

Twitter dm, Skype, IRC relies of buddy list... approving that person Lot of comms we do if we don't know that person... restaurant

Phone numbers - some people closely guard them, hard to stop people contacting you if they do have your number. Web can gate who contacts you.

Could give services URL.

Web RTC on front end CIP on backend


Stun box... allows machines to discover own ip address

Turn - more restrictive NAT

Many aspects to doing end-to-end indie communications

WebRTC is just plumbing.

Scenario: 1. pick up a computer with a browser that supports WebRTC 2. go to my site 3. start a call to me

Using IndieAuth -> domain - > intersection of contact preferences

  • A signs into B's website with IndieAuth
  • B's website shows more methods of contact (easy)
  • B's website checks A's website for a rel=contact to a e.g. "/contact.html" page
  • B's website parses the h-card from that page and checks all the "url" properties
  • B's website does an intersection of the schemes of those URL properties and those on B's site
  • B shows methods of contact that *both* B and A have.
    • optionally it can show other methods of contact that A does not have, but just greys them out, so that A knows they could go install/setup those.

Contextual enhancements for the contacter, e.g. show contextual information on contacts page or even home page like:

  • time where the person is (via automatic checking of Foursquare to imply timezone)
  • at the movies - do not contact (again via Foursquare)



Previous session


2014-03-07 Personal Site Focussed Mobile Comms UX (and payment)

  1. indiecomms


  • Tantek Çelik (



  • grid of communication apps on mobile device - high cognitive load - how do I communicate with this person?
  • open

comm app - you have a new message! BETTER GO CHECK IT!

  • Start with people - click to open a window to compose a message to them
  • UI design on indiewebcamp wiki - in public domain. If you can implement it first, great!
  • iOS - Face icon, several comm methods in subfolders next to it
  • List of communication methods would change depending on whether tantek is asleep, or depending onthe timezone
  • Potential issue: Everyone who implements a list of contact methods on their site will do it differently, so there won't be a standard at-a-glance way to identify this. But everybody wants to be able to choose how to present it on their site.
  • Possible solution is different reader interfaces that can parse the raw microformats data
  • If we get the markup right, we can create an awesome stylesheet that everyone can share so people who are not good at CSS can use it and make it look nice
  • It has to look better and have a better experience than the native grid of comm apps on the mobile device (otherwise it just looks like "some crappy web thing")
  • Discussion: preference of contact method; Travis wonders why not just have one interface to send to preferred?
  • Good problem to have; at least the person has the ability to specify their communication preference in order. Silos have taken a stab at this, but example of Windows people-centric client-only UI getting this wrong - sorted by your pref of comms, not your friend
  • Does this mean all contact methods are public? No, can choose to publish only certain channels publicly (like AIM), and if you IndieAuth in, then new channels appear. Maybe grey them out instead of hiding them so people know there are more things that will show up if they log in.
  • much discussion about specifics, webrtc
  • u-impp - rfc4770 - only supports 8 methods?
  • IRC URI: irc://myserver/kilroy,isnick?msg=are%20you%20here%3F


Need to convert it (part or whole) to JS, probably with

  • TODO: find URI schemes for all the apps (sms:, etc)
  • snarfed: many of these are posted, offers to find them
  • irc://,isnick
    • Colloquy doesn't support ",isnick" and thus creates a channel "tantek" instead
      • Need to file a bug against Colloquy
    • Snak doesn't support this, tries to join #tantek and #isnick


Created by on September 10

  • Wed, September 10 etherpad dump from



Discussion at comparing different ways to use and/or build CMSes.

Roll your own?

  • Hard!
  • Requires maintenance
  • often happens because current tools don't do what you want
  • Customization
  • Learn stuff?
  • Ops Overhead

From group, six people had rolled their own, a few ruby and PHP, mentions of C#, Node, Python and Go.

Data Storage

  • Databases
    • Each system uses their own format
    • You have to write Exporter / Importer
    • "Bro, do you even backup?"
  • HTML
    • Much harder to lose / corrupt
    • Viewable in the browser

Off the shelf

  • Lock in?
  • Easy mode
  • Tested
  • possibly crufty


Ones that people at talk had used:

  • Django CMS (Python)
  • Drupal (PHP)
  • Wordpress (PHP)
  • Kirby (PHP)
  • MUDX (PHP)
  • Expression Engine (PHP)
  • Craft (PHP)
  • TYPO3 (PHP)
  • Ghost (Node)
  • Jekyll (Ruby)
  • Hoisted (PHP)
  • Perch (PHP)
  • Docpad (PHP)


  • Known


Created by on September 10

  • Wed, September 10 etherpad dump from

Indiewebcamp UK 2014

  1. indieconfig

Problem: I’m at a post and want to reply to it, how can I do that in-context rather than copy/pasting URLs and such nonsense.

Existing solution: webactions, working demo cross-browser extension. Problems: no-one wants (or should have to) install+configure a browser extension

Pelle built a proof-of-concept (during the demos!) using iframes and registerProtocolHandler to do the same thing without using a browser extension.

We should be able to tell sites we’re browsing how to present us with a dialog

T: perhaps this could work like geolocation/getUserMedia — there’s an async JS API allowing sites to request location data, pending user approval. What if we had that for identity/discovery of your personal website?

The proof-of-concept adds a custom well-known protocol using navigator.registerProtocolHandler(), eg. web+indieconfig, that's pointing to the users own site. Other pages then include an iframe using that well-known protocol, which then resolves to the users own page. The code in that iframe sends a JSON encoded message to its parent window by using window.parent.postMessage() and the parent receive that message, checks that it was sent from the iframe, parses it and uses the data in it to eg. figure out the "reply" URL to use as a fallback in a webactions reply.

Additional things possible in the proof-of-concept is to eg. add a whitelist-check within the iframe using something like confirm(), localStorage and document.refeerer to check if the refeerer is allowed to know about your indie configuration or not.

See Also

Changed Pages


15 edits by,,


11 edits by,,,,
  • Sun, September 7 /* Wrap tweet or share */ Update action to indie-action
  • Sun, September 7 /* Wrap favorite reply retweet */ Update action to indie-action
  • Sun, September 7 /* IndieWeb Examples */ Updating action to indie-action
  • Sun, September 7 /* Tantek */ updated my site to use <indie-action> instead of <action>
  • Sun, September 7 /* Wrap tweet or share */ Link to custom elements spec
  • Sun, September 7 /* IndieWeb Examples */ Added my indie-action implementation
  • Sun, September 7 /* Tantek */ noted I *currently* use <indie-action> tags, and merely historically used <action> from 2013-09-08 to 2014-09-06
  • Sun, September 7 /* Wrap tweet or share */ Add link to custom element name definition / Submit to @adactio's will
  • Sun, September 7 revert span id, was there for past references. note date since for Pelle, sort
  • Wed, September 10 /* IndieWeb Examples */ add adactio
  • Wed, September 10 /* Web Action Browser Support */ added greasemonkey script


8 edits by,,

IRC People

8 edits by,,,, user:danlyke,


6 edits by,,


6 edits by,,,

Main Page

5 edits by,


5 edits by,
  • Sun, September 7 /* Creating Objects */ add example of creating a bookmark post
  • Sun, September 7 /* New Bookmark */ oops forgot to actually add the bookmark url
  • Sun, September 7 /* New Bookmark */ add bookmark name
  • Tue, September 9 /* Adding a Syndication URL */ registering my preference for parameter name 'url' instead of 'u'
  • Wed, September 10 change to url=X instead of u=X and remove fuzzy language

2014/UK/Guest List

5 edits by,,,,


3 edits by,,
  • Sun, September 7 /* 3rd party tracking exploits */
  • Wed, September 10 /* Implementations */ Add Tools section with Firefox Addon from eliemichel!
  • Wed, September 10 /* Issues */ add issue about multiple comments when h-feed is sent as the source page


3 edits by


3 edits by,
  • Wed, September 10 /* FAQ */ indieauth for more than 1 domain
  • Wed, September 10 /* What if I have more than one domain */
  • Thu, September 11 TOC should go before the FAQ, so you don't have to scroll through all the FAQ to get to a quick list of the questions


2 edits by,

2 edits by


2 edits by,


2 edits by

Getting Started

2 edits by
  • Fri, September 12 /* Bonus: get your own personal short domain name */ shorten heading
  • Fri, September 12 /* Publish (on your) Own Site, Syndicate Elsewhere */ POSSE


2 edits by


2 edits by


2 edits by
  • Sat, September 6 /* 2013 */ Added new entry about darQroom death
  • Sat, September 6 /* 2013 */


2 edits by


2 edits by
  • Mon, September 8 /* Flat files */ changed "vast majority" to "many", many counter-examples (Known, Bundle, Publify, Homesteading)
  • Tue, September 9 /* Databases */ update -> Known


2 edits by


1 edits by
  • Sun, September 7 /* SSL Setup */ Added a link to my notes on setting up SSL on nginx/Digital Ocean w. NameCheap EssentialSSL


1 edits by


1 edits by


1 edits by


1 edits by


1 edits by

Main Page-ko

1 edits by


1 edits by


1 edits by
  • Sat, September 6 change from redirect to a summary of NYC, including past organizers


1 edits by


1 edits by

Amazon S3

1 edits by
  • Sun, September 7 /* Add local file rsync / copy to S3 using Fuse S3 to avoid command line clients use */


1 edits by


1 edits by


1 edits by


1 edits by
  • Fri, September 12 nice big useful link at the top so people don't waste much time with OpenID


1 edits by

videos about the indieweb

1 edits by


1 edits by

How to set up web sign-in on your own domain

1 edits by


1 edits by


1 edits by


1 edits by
  • Tue, September 9 /* FAQ */ added some q's that are frequently a'ed by me! cc: tantek,aaronpk


1 edits by


1 edits by
  • Fri, September 12 hCard->h-card, OpenID->IndieAuth, and other minor updates, get started, move forward

1 edits by