IndieWebCamp October 24-31, 2014

This is an automatically-generated summary of the IndieWebCamp wiki edits from October 24-31, 2014

Table of Contents

New Pages

Changed Pages

New Pages


Created by on October 31


IndieWebCampOnline 2014

Join us for the very first IndieWebCamp Online - one of many IndieWebCamps.

Join us digitally for two days (?) of a BarCamp-style gathering of web creators building and sharing open web technologies to empower users to own their own identities & content, and advance the state of the indie web!

The IndieWeb movement is a global community that is building an open set of principles and methods that empower people to take back ownership of identity and data instead of relying on 3rd party websites.

At IndieWebCamp you’ll learn about ways to empower yourself to own your data, create and publish content on your own site, and only optionally syndicate to third-party silos. Along the way you’ll get a solid grounding in the history and future of Microformats, domain ownership, IndieAuth, WebMention and more!


  • Guest List - click and add yourself (and optionally an apprentice)


Currently I am looking for a co-organizer to help work out details of the event. - Ben Roberts



A traditional IndieWebCamp is two days. But, being as the group does not have to gather in the same physical location, this opens the door to ask if the frequency of IndieWebCamps could be increased if there were also one-day events. Would not suggest an IWC be less than a full day event.


An IndieWebCamp consists of BarCamp style discussions and a Hack Day. Are there variations of this or alternate formats?

For example, a Hack Day where we break up into groups of people who want to work on implementing the same/similar features...


Having an online event means one has to factor in the timezones of the various attendees. Common timezones of physical IWCs have been European/UK, Pacific, and Eastern times.

One option is to adopt a time that works for the majority of participants, which requires some advance notice, and possibly may alter attendance.

An alternate one is to split the day into smaller pieces to accommodate.


Previous IWCs have used However, this is a group chat tool, and not necessarily tuned for a presentation format. It may be more ideal to use Hangouts On Air. Hangouts limits the number of Hangout participants while allowing for live streaming for observers.

Would suggest a 'dry run' in advance, so that the coordinators can assist others in getting things working.

See Also

2015 DCProvidenceSFNYCPortland/NYC/BerlinUKCambridge
2014 SFNYCPortland/NYC/BerlinUKCambridgeOnline
2013 PortlandUKHollywood
2012 PortlandUK
2011 Portland


Created by on October 30

Docs go here.


Created by on October 28

  • Tue, October 28 Created page with "{{stub}} '''<dfn>[ SSLv3]</dfn>''' is an older version of TLS and is now considered insecure and should not be used. === S..."
  • Tue, October 28 /* See Also */
  • Tue, October 28 /* See Also */

SSLv3 is an older version of TLS and is now considered insecure and should not be used.

See Also


Created by on October 27

  • Mon, October 27 Created page with "[ coisas] is a multipurpose CMS that runs in the browser and deploys the static HTML it generates to GitHub Pages. It forces you to organize your..."
  • Mon, October 27 added screenshot.

coisas is a multipurpose CMS that runs in the browser and deploys the static HTML it generates to GitHub Pages.

It forces you to organize your content into a hierarchy of pages, each of which may have markdown or HTML text and any number of children. So you start with one page, at the root address, and add children from it.

All the pages are generated from the same HTML template, so they all feature a global title and description, a navigation bar indicating where in the website that page is located, and a list of children of that page.

Coisas does not come with any CSS, so the generated website at the first time you do it is very crude, what is good, so you can style it easily with a minimum of global CSS rules, and also style any page individually, as each page is rendered with its path passed as classes to its HTML.

Coisas is nowadays powering (code) and (code).

To try it yourself, go to this template, fork it, rename it and you're ready to go.




Created by on October 25

MediaWiki is open source server wiki-project written in PHP that is used by Wikipedia and

MediaWiki uses MySQL for primary storage.


IndieWebCamp Customizations

IndieWeb Examples

Tom Morris

Tom Morris uses MediaWiki on his personal site wiki at:

Other Independent Examples

Friend of GWG

David Shanske has setup MediaWiki for a friend as a private thing and maintains it for them.

See Also about the IndieWeb

Created by on October 30

  • Thu, October 30 testing what the page looks like using templates for listing articles
  • Thu, October 30 single author property

This is a work in progress.

📡 Welcome to news about the IndieWeb where recent notable articles about the IndieWeb are cited and linked to keep you up to date.

Want a weekly digest that covers the state of indie web? Something that can end up in your inbox?

Want to watch a talk about the IndieWeb?

Check out the news page for links to more sources of IndieWeb news.

Articles about the IndieWeb (in chronological order)




Created by on October 26

An algorithm is a series of steps used to to automatically perform some computation and/or other operations to come up with a result.


Examples of algorithms on

See Also


Created by on October 25

David Shanske


Created by on October 28

  • Tue, October 28 Created page with "[ scrapboard] is a [[CouchApp]] that replicates the functionality of the late [[Orkut#Scrapbook]], allowing people to post and receive scraps ..."

scrapboard is a CouchApp that replicates the functionality of the late Orkut#Scrapbook, allowing people to post and receive scraps in a decentralized way, with each person being responsible for hosting their own scrapboard instance.

scrapboard can be easily hosted in a CouchDB instance and accessed there directly (as in fiatjaf's scrapboard), or it can be embedded as an iframe into a personal webpage (as in fiatjaf's web page).

Although scrapboard works better if the person sending the scrap also has one scrapboard of their own (so them can claim the authenticity of their scraps), scrapboard is not an island, it works with anonymous scraps, named or unnamed, and will surely work with webmentions if the senders decide to allow CORS on their websites.


As spam in the Scrapbooks was the main cause of degradation of Orkut#See_Also, scrapboard takes some measures to counteract it:

  • It is a indie thing, so it will not be easy for a spammer to find available scrapbooks and spam them as it was with Orkut, a silo in which every click or randomly typed address would take you to a new personal profile;
  • It limits the number of scraps allowed to 1 every 100 seconds;
  • It requires a hashcash token to be submitted with every scrap sent;
  • It requires the person sending the scrap to go through a cumbersome process that first fetches a token data (changed every 100 seconds) with which to calculate the hashcash token, and only then to submit the token, so it mitigates automated spammers.

Moreover, I don't have any experience or knowledge about spamming, so this is mostly a guess and I'm open to suggestions. You can drop me a line at [1].--fiatjaf 18:16, 27 October 2014 (PDT)


Created by on October 29

  • Wed, October 29 Created page with "'''Homebrew Website Club (HWC) Lisbon meetup 29 Oct 2014''' present: Pierre, Jose, Mirjam, Michiel. Michiel asks how we can get more people interested in this meetup, and how (..."

Homebrew Website Club (HWC) Lisbon meetup 29 Oct 2014

present: Pierre, Jose, Mirjam, Michiel.

Michiel asks how we can get more people interested in this meetup, and how (if at all) HWC can make sense in Lisbon.

We discuss the size of other Lisbon tech meetups - most are around 10 people (php, crypto party, bitcoin), but the javascript meetup is significantly bigger (around 30 people). We agree to come back to this point once everybody is on the same page about what IndieWeb is, and what the aim and topic of HWC is.

The network effect made monoculture Federated Social Web efforts (Diaspora is mentioned as an example) of limited usefulness, therefore POSSE is better if your friends are (still) on facebook.

Jose defends email as the best way to communicate, but the problem is people now check their Facebook inbox more often and are less on mailing list (e.g. even to promote this meetup, you would have to post it on Facebook).

We consider the possibility of running e.g. a VOIP/telephony server at home, but mention that it's a lot of hassle to maintain one.

Pierre mentions an automated mail responder he once linked to Facebook messages, that would ask people to continue the conversation outside of Facebook, but somehow Facebook did not relay these replies to the Facebook message sender. is mentioned and discussed.

Jose presents his personal website, - he basically uses it as a humans-only business card (gmail address displayed in a GIF image). His PGP key and a png image of a link to his Facebook account is also on there. It's hosted on Google Sites, with Google Analytics on there.

Jose remarks that Google is more trustable than smaller hosting providers - he doesn't want to put his website on a hosting platform whose business model he does not understand, and who may not be there in 5 years.

Jose also shows a blogspot site which he uses mainly to display an embedded widget of his account, and a blog about seismology which he runs and which is updated automatically through Yahoo pipes.

We talk about Yahoo Pipes, IFTTT, and Twitter closing down rss support.

Pierre tells Jose about "web sign-in" (IndieAuth), but Jose questions the utility of it. Mirjam asks why a big website like for instance EuropCar would allow customers to log in with IndieAuth. Jose questions what percentage of people would meddle with their html to set up IndieAuth.

Pierre defends that activating IndieAuth is easier if you use e.g. a WordPress plugin.

We talk a bit more about how the personal site (e.g., the identity provider (e.g. Twitter), and the relying party (e.g. work together in IndieAuth.

In response to Jose's concerns about html being hard to edit, Michiel mentions the new IndieHosters project as an effort that could help IndieAuth reach a broader install base.

Jose mentions that blogs are anti-chronological, and shares a tip for WordPress users - it has a 'book' option, which makes it chronological.

We look at Mirjam's site,, which uses scanned-in hand drawings to achieve layout effects which would be a lot harder to achieve in pure html. Mirjam asks how she can set up POSSE, to share the feed of her website to Facebook, and reach a bigger audience with news updates. Even though the site has a static content design, it has a rss feed, which could be POSSEd to Facebook.

We discuss the difference between privacy concerns and identity ownership concerns.

We discuss click-twice Like buttons which avoid tracking (like the one on

We mention

Mirjam wants some posts to appear in her feed but not on the main page.

We discuss if signing up for more web 2.0 silos (like for instance leads to more tracking and privacy invasion, or whether it actually democratizes things if you give your data to lots and lots of advertising companies instead of to just a few.

We discuss how to be safe as an activist - best option: don't use technology at all! :)

Unfortunately we don't have any time left to do any actual work on anyone's website (also, only two out of four participants had their laptop with them).

Where can we take this meetup from here?

  • we could share tips and tricks
 * help with implementing own website
 * options to avoid commercial silos
 * general tips for how to use free and open technology
 * exchange knowledge about how for instance cookies work
  • what would make you happy that you didn't miss next meetup?
 * if we learn useful tips about using the internet in a safe/good way
 * announcing beforehand what the topic will be could help with this. But that goes a bit against the spontaneous nature and barcamp-ness.
  • Jose mentions that maybe encryption is the only real way to be free
  • Mirjam mentions that this is not just about keeping activists safe, but also about just limiting the power of silos on all internet citizens
  • We discuss how to differentiate HWC meetups from more generic Internet Freedom meetups. We could do a meetup about basic hygiene for internet users (e.g. prismbreak, ToS;DR). Discussion about why it is important.

We should ask people from the Internet Freedom group why they didn't feel attracted to attend HWC the first two times.

Created by on October 27

Benjamin Terry


A Network Administrator at Carson Health, Benjamin Terry has taken an interest in the Indie Web.

His site / domain is


Created by on October 30

  • Thu, October 30 stub - since I linked to it on IRC, call to action for organizers

One of several IndieWebCamp events in 2015.

This page is for planning the main annual IndieWebCamp, likely in multiple locations like Portland, NYC, Berlin.

If you'd like to help out, join IRC, and add your name below!


  • Tantek Çelik - can help co-organize in SF, Portland, or New York.
  • ...

See Also

Changed Pages

Indie Box

3 edits by

3 edits by
  • Sat, October 25 /* working on */ contribute to Upcoming from an IndieWeb perspective
  • Sun, October 26 /* working on */ wiki and blog IndieWebCamp 2014 Cambridge demos
  • Thu, October 30 /* working on */ document using dated permalinks for recovering, longevity

2 edits by


2 edits by
  • Tue, October 28 /* POSSE */ Added link to some code for autofilling content share boxes with what is typed in content - for status updates.
  • Tue, October 28 /* POSSE */


2 edits by,


2 edits by


2 edits by
  • Wed, October 29 /* MailRoute */
  • Wed, October 29 /* MailRoute */ removed because it is covered further down already, didn't see that at first.


1 edits by

Two-factor authentication

1 edits by


1 edits by


1 edits by


1 edits by


1 edits by
  • Sat, October 25 update dfn to include some history, status, and new "Return of Upcoming" section with recent references


1 edits by


1 edits by


1 edits by

how to edit this wiki

1 edits by


1 edits by


1 edits by


1 edits by

1 edits by
  • Fri, October 31 /* Nginx Configuration */ drop sslv3 due to poodle, tune cipher list some


1 edits by

1 edits by


1 edits by


1 edits by


1 edits by
  • Tue, October 28 /* Criticism */ Added update on Github DMCA process


1 edits by


1 edits by
  • Mon, October 27 /* Inferring post kinds from properties */ p-invitee -> invitation


1 edits by

Posts about the IndieWeb

1 edits by
  • Thu, October 30 link to this-week-in-the-indieweb so it's more discoverable


1 edits by