IndieWebCamp November 14-21, 2014

This is an automatically-generated summary of the IndieWebCamp wiki edits from November 14-21, 2014

Table of Contents

New Pages

Changed Pages

New Pages


Created by on November 15

We'll schedule the sessions on the day of the camp! See Schedule for an overall outline of the timeslots. Feel free to brainstorm ideas of sessions you'd like to talk about, or you'd like someone else to talk about.

See: 2014 Online Schedule



Add your session ideas for things you want lead a discussion about. Be sure to add your name.


Proposed by: thedod

Discussion of security concerns in Indieweb. This would include Indieauth, Tor, Vouch, etc.


Proposed by: Ben Roberts

messaging refers to one user sending another user a message (memo, letter, etc.). There are numerous technologies for such personal messaging.

  • Discussions of private messaging and a possible extension to Indieauth to reduce concurrent calls
  • Discussion of a private real time chat. The conclusion of many was that this may be better done by interfacing with existing protocols over a using the private messaging discussed above.
  • Suggestion for microformat markup for selective portions of a post to indicate the intent of the author in regards to what can be shared/reposted, to be expanded under private posts


Proposed by: Aaron Parecki

Micropub is an open API standard that is used to create posts on one's own domain using third-party clients. Discussion of CRUD implementation and other considerations.


Proposed by: David Shanske

Discussion of comments-presentation, reply-context as a matter of designs. Oembed as a tool for presentation.

Session Title

Proposed by: ___



If you are interested in a topic but do not feel like you can lead the discussion, add it here.


Requested by: thedod Facilitator: Tantek Çelik

Discuss while learning the art of wiki page editing with Tantek Çelik.

Wrote up notes and advice during IndieWebCamp Online: wikifying

Session Topic

Requested by: ___


Previous Years


Created by on November 20

Webvatar is a service that provides direct URLs for <img> tags when you have the domain, or website address, of the user.

Thus, by using <img src=""> you can shorten your need for servers and microformats2 parsing and still get people's pictures.

Currently, Webvatar supports microformats2 and microdata, has probably a lot of stupid bugs and falls back at an image with the domain name written in it for people whose images it cannot find (or an image generated by, if you pass the URL with ?alt=robohash or, if you don't like robohash, if you apss the URL with ?alt=hash you get a pretty picture of the SHA256 hash of the target address).

The code running the service is at and accepting criticism, suggestions and pull requests.


See Also


Created by on November 16

wikifying is the practice of putting stuff on the wiki, or something in particular on the wiki. E.g. We need to wikify that (FAQ|concept|jargon|etherpad).



Wikifying both in general, and particular subjects, notes, or documents, helps grow the searchable & discoverable commons of the IndieWebCamp community.

How to

Wikify yourself

Like many things in IndieWebCamp, start by editing your own page, in this case, your own "User:" page.

Your "User:" page is linked from the bottom of footer links, first link on the third row, with the name of your domain that you used to login to the wiki (just before "My talk").

Click on it and edit your User: page.

If you're not sure what to put on your User: page, start simple. Name, URL, h-card, e.g.

<span class="h-card">[ Your Name]</span>

Next, add an itches section where you capture what you want to work on for your own site. E.g.

== Itches ==
* Add a more extensive [[h-card]]
* Figure out a [[URL design]] for my posts
* Start posting [[notes]] manually at [[permalinks]]
* Try checking my site in
* Check out [[IndieMark]] for additional ideas of things to add to my site

When you start collecting lots of itches, you may want to start prioritizing them, especially by what you're currently working on. Start a "Working on" section for that:

== Working On ==
* the next thing I'm working on
* the next next thing I'm working on
* ... etc.

Lastly, check out others' User: pages, especially folks that have been doing this a while, to see what else you could add to yours and work on.

Incremental Wikifying

There's lots of incremental wikifying to help with.

  • fixing typos
  • adding IndieWeb Examples - if you find a page for a technology you support on your site, or a project you use on your site, add yourself to the "IndieWeb Examples" for that page
  • add issues and questions (for FAQs)
  • collect questions/answers from IRC and add them to the appropriate wiki page

New pages

There's lots of new page creation you can help with. Create new wiki pages for:

  • etherpads of notes from IndieWebCamp sessions after they're finished, to archive the session notes somewhere more findable / linkable
  • definitions of any new terms or jargon that people use in IRC
  • new projects you start using on your personal website; be sure to include your site in the IndieWeb Examples section on the page.

Related Articles

The above is very much specific to what is good wikifying for IndieWebCamp in particular.

Here are related articles on good writing, structure, and wikifying in general:

See Also


Created by on November 21

Twister is a "fully decentralized P2P microblogging platform built from free software implementations of Bitcoin and BitTorrent protocols"[1].

Twister has a desktop client which can also serve as a localhost webserver you browse to and get a Twitter-like experience.

The main focus of the project is censorship-resistance [allegedly. No citation given on purpose. Read the source :p]. There's no way to delete anything. Your typos will live forever.

See Also


Created by on November 21

  • Fri, November 21 Created page with "{{stub}} [] is a new network of independent hosters who offer CMS Software as a Service."
  • Fri, November 21 link back to web_hosting
  • Fri, November 21 dfn, see also

IndieHosters is a new network of independent hosters who offer CMS Software as a Service.

See Also


Created by on November 16

notes from the micropub session: has an implementation of delete and update now:

  • adds two OAuth scopes (edit and delete)
  • undelete would fall under delete scope

Currently other actions besides create are specified by an "action" field

  • action=delete
  • action=edit
  • action=undelete
  • action=syndicate

currently ben has no way to remove a title (no current difference between handling a field empty vs a field not present)

after deleting a post, ben's logged-in view shows the post with "deleted"

silo examples of removing partial content:

  • composing a tweet, attaching a photo, removing the photo before posting
  • removing facebook preview from the post
  • google+ removing a circle that a post is shared with

Different kinds of

  • updating: changing existing values
  • updating: deleting existing values (removing tags, removing location)
  • updating: adding new values (adding tags, or adding location)
  • delete: whole post
  • undelete: whole post

how to handle add/remove from fields that have multiple values? (tags, syndication targets)

a micropub request to syndicate - not just an edit, since it's not idempotent

  • action=syndicate?

how to create/edit ACL for a post in micropub?

querying micropub endpoint for the list of syndication targets

go to Quill, Quill prompts you to click a checkbox to say "use this as my default post interface"

other things to query for:

  • list of categories you might want to add to a post, maybe for an autocomplete interface
  • list of people you want to tag - (once someone implements people tagging of course

session facilitating

Created by on November 17

  • Mon, November 17 Created page with "<dfn>Session facilitating</dfn> refers to facilitating a brainstorming session at an IndieWebCamp event. Session facilitators are responsible for setting the discussion topic/goa..."
  • Mon, November 17 added See Also section

Session facilitating refers to facilitating a brainstorming session at an IndieWebCamp event. Session facilitators are responsible for setting the discussion topic/goal and keeping the conversation on track. The facilitator should also make sure they or someone else is taking notes (often in an Etherpad).

Suggest a topic

Choose something you want to discuss in a brainstorming session. It can be a discussion, an extended demo, a help or intro session, etc.

Discussions can be broad and open-ended or more specific and targeted. Decide what kind of session you want to have and choose your topic accordingly — if you want to talk about font colors and sizes, "design" is probably too broad a topic.

There might be a tendency to worry that if you choose something too narrow, there will not be enough to talk about, but that's usually not the case! (In fact it can be the opposite). 45 minutes goes by quickly when you are analyzing examples or digging into the details of implementation.

Session Goals

Consider whether your session can produce some documentation, research, working example, actionable todo list, or other artifact. This can help focus the session and can give people ideas of things to work on on the second day.

Tantek suggests useful documentation falls on a spectrum (ordered roughly from good to excellent).

  • have multiple people participate
  • producing some notes in IRC -> etherpad -> wiki
  • documenting existing examples (textually)
  • document them with screenshots
  • documenting existing UI flows (beyond just one screenshot)
  • coming up with (better) indie web user flows
    • a textual descriptions / lists of steps
    • mockups (drawings, sketches)
    • HTML+CSS samples
    • working examples

If you take notes on a whiteboard, make sure to take a photo of the end result for later reference.

See Also


Created by on November 19

LOCKSS is an acronym for Lots Of Copies Keeps Stuff Safe, a mnemonic for the technique of keeping and encouraging many copies of things as a way of improving their longevity.

See Also


Created by on November 15

  • Sat, November 15 Created page with "{{stub}} <dfn>Onboarding</dfn> refers to the first experience a user has when installing, configuring, and first logging into an application. A great onboarding process walks the..."
  • Sat, November 15 /* IndieAuth Chicken or Egg */

Onboarding refers to the first experience a user has when installing, configuring, and first logging into an application. A great onboarding process walks the user through all the required steps (e.g. configuring the database or file system location, setting the base URL of the site, etc.), helps spot

IndieWeb Examples

  • Known
    • On first installing Known, the user is directed to a setup page that checks for required PHP dependencies, helps them configure a database connection and creates database tables if necessary, and guides them through configuring the appearance of the site.
    • Once installed and running, a friendly robot named "Aleph" offers to help with more advanced usage and topics (add screenshot)
  • OwnYourGram and Quill are micropub clients that double as guides to setting up micropub on your IndieWeb site. New users walk through the process of setting up authorization, token, and micropub endpoints, with thorough documentation and tests with helpful feedback along the way.
  • Bridgy. Once users have given Bridgy read access to their social media account, it attempts to detect potential configuration problems (e.g., no webmention endpoint) and give the user a bright yellow heads up.


IndieAuth Chicken or Egg

Personal website software that uses IndieAuth for user logins (e.g. Red Wind) faces a potential "chicken or the egg" problem.

  • To set the site URL, add an h-card, configure rel=me's for social media profiles, etc. the user must log in as an administrator.
  • To log in as an administrator via IndieAuth, the user needs an personal website with rel=me's that link to their social media profiles.

Just to test and develop locally requires the user have an IndieAuth-capable website.

Some ideas:

  • All configuration via text files or environment variables.
  • Provide alternative password based login.
    • Only in development mode?
  • Do not require a login at all until the site is configured and IndieAuth is successful.


Created by on November 21

  • Fri, November 21 Created page with "An <dfn>IndieHoster</dfn> is a member of the [[IndieHosters]] network."

An IndieHoster is a member of the IndieHosters network.


Created by on November 17

Eye-Fi is a brand of SD card that contains a built-in Wi-Fi radio which can be used to quickly transfer images from a digital camera to a computer or mobile device (iOS/Android).

It'd be pretty neat to be able to post photos to your own site (and possibly also POSSE them out to photo silos like Flickr and Instagram) from a mobile device using EyeFi.

Users playing with it

  • tommorris: my use case is this - back on 2014-03-29, I posted this - I would have liked to have taken it with my decent camera (X-Pro1), then posted it to my own site from my phone, with the photo hosted on my own (sub)domain. irc log


Created by on November 14

Date Description Payer Payee Amount
2014-10-11 Saturday Breakfast Sponsors Whole Foods $39.72

one click migration

Created by on November 21

If you remember the desktop era, before the web2.0, and so before the web app era, it was quite easy to migrate from applications to applications. If you take the example of an ODT document, you can read/edit it from different software (OpenOffice, LibreOffice, Microsoft Office, Zarafa..). And you can read/edit them from different platform also like linux, windows, android.. So at this time, migrating your data was not really a problem. You put them in a drive, put this drive in a new device, and you just need a software to read/edit it, and that's it.

When the web transformed into applications, it introduced a great bug! Suddenly your data were tied with your application far from your control. Unhosted web app is trying to solve this by decoupling data and application on the web. But in the mean time, we need to work on hosted web app.

There is also an other issue related to web application. The format is always tied to this web application. So usually, to transfer your data between related applications, you need some kind of conversions. As an example, you have wordpress providing importers for other blogging applications like tumblr.

And applications like wordpress provide an exporter/importer, but it never works fully, and even when you are migrating from wordpress to wordpress, you always need to manually tweak it. Plus this exported file doesn't contain your domain name nor your SSL certificate.

So in the particular case of the Indie App Store, the first implementation will probably provide wordpress and known. It would be important that people will be able to migrate their data (from known for instance) between implementations of such a store, but also between web hosting providers.

Even thought unhosted web applications are coming and wordpress is already offering importer/exporter tool, it would be a greater good for the user of such a store to have access to a one click migration feature.

Then to make this feature available to the Indie App Store, we need to define what Migration Format is for web applications.


Created by on November 16

Page to Be Created later

Migration Format

Created by on November 21

You can find IndieHosters's format documentation on their GitHub repository.


Created by on November 20

Indieweb Taxonomy

Created by on November 20

  • Thu, November 20 Created page with "''The '<dfn>[ Indieweb Taxonomy] Plugin</dfn>''' is a [[WordPress]] plugin that adds response support to WordPress. It creates a tax..."

The 'Indieweb Taxonomy Plugin' is a WordPress plugin that adds response support to WordPress.

It creates a taxonomy called Kind, which consists of types Reply, Repost, RSVP, Like, Favorite, and Bookmark. It then adds post metadata boxes to the WordPress post editor for a URL, a title, and content/citation. This allows a post to act as a response to another post, quote, etc.

The post uses the Webmention Plugin to send webmentions to any URL it is responding to.

Related Plugins

See Also


Created by on November 20


See Also


Created by on November 19

PAAS (Platform As A Service) is a hosting environment typically for a web applications written in scripting languages (python, ruby, node) and usually offers simplified setup and maintenance tools compared to a VPS. They usually cost money and are powered by service specific platforms although many offer limited gratis tiers.


  • [Heroku]
  • [Google App Engine]
  • [App Fog]
  • ...


Created by on November 21

Intentionally left blank.


Created by on November 19

  • Wed, November 19 Created page with "{{ stub }} <dfn>LXC</dfn> stands for [ Linux Container], provides lightwheight isolated, environments linux for software stacks like LAMP and is the co..."

LXC stands for Linux Container, provides lightwheight+isolated linux environments for software stacks like LAMP and is the core technology behind docker.

Retrieved from ""


Created by on November 19

The Wormhole is a coffee shop in Chicago, and possible HWC venue.

Changed Pages


14 edits by,,


11 edits by,


9 edits by,,


6 edits by
  • Wed, November 19 /* Itches */ geo-taged notes
  • Wed, November 19 /* Geo-tagged Notes */ reduce implementation to apparent minimum, note possible improvements
  • Wed, November 19 /* Geo-tagged Notes */ cite motivation
  • Thu, November 20 /* Working On */ one-off person-area-tag reply to aaronpk's photo post, to person-area-tag benwerd, as part of pushing forward building blocks for SWAT0
  • Thu, November 20 /* one-off person-area-tag reply to photo */ steps.
  • Fri, November 21 /* Itches */ Expiring Content


5 edits by,

web hosting

4 edits by,
  • Thu, November 20 /* Custom domain silos */ content hosting service
  • Fri, November 21 Add IndieHosters as an option
  • Fri, November 21 /* Personal Clouds */ change "Personal Cloud / Indie Hosting" to "Personal Cloud / Home Hosting", to avoid confusion with the new section I just added
  • Fri, November 21 merge 'using an Indie Hoster' section into 'CMS SaaS' section


4 edits by,


4 edits by,

4 edits by

2014/Online/Guest List

4 edits by,,


4 edits by,,
  • Mon, November 17 expand dfn to be more specific
  • Mon, November 17 /* Why */ Added "Lightweight Pull Request" Idea
  • Mon, November 17 /* Silo Examples */ add example of a github diff URL and clarify pull requests are a collection of commits
  • Mon, November 17 pull request / patch is a *collection* of edits


3 edits by


3 edits by

3 edits by
  • Fri, November 14 /* Nginx Configuration */ update cipher list to support IE 8 / XP as per ssllabs
  • Fri, November 14 /* Nginx Configuration */ fix my broken wiki markup
  • Fri, November 14 /* Host Specific Configuration */ spdy: announce support and compress headers

private posts

3 edits by,


3 edits by,


2 edits by,


2 edits by,

2 edits by


2 edits by

Semantic Linkbacks

2 edits by


2 edits by


2 edits by


2 edits by


2 edits by


2 edits by


2 edits by


1 edits by

1 edits by


1 edits by


1 edits by


1 edits by


1 edits by

Main Page

1 edits by


1 edits by

start a page

1 edits by


1 edits by


1 edits by


1 edits by


1 edits by


1 edits by


1 edits by


1 edits by


1 edits by


1 edits by

1 edits by


1 edits by


1 edits by


1 edits by


1 edits by
  • Wed, November 19 collection explicit chosen, changes, feeds difference


1 edits by


1 edits by
  • Wed, November 19 /* See also */ Added links to diversity reports for Google, Facebook, Apple, and Microsoft

1 edits by
  • Wed, November 19 /* working on */ capture some wikifying I need to do


1 edits by

feed reader

1 edits by
  • Wed, November 19 dump Other Aggregators to leave for someone else to cleanup, someone thought these were interesting to list on business-models so keeping the list despite the fact that none of them actually make money for charging for aggregation


1 edits by


1 edits by