to-do

Next steps for IndieWebCamp and IndieWeb efforts.

See something here you can help with? Jump in and help with incremental edits!

Questions? Ask in our discussion channels!

Roughly ordered by importance / oldest first.

Update How to Run an IndieWebCamp page/documentation

 * We need an easier/simpler/shorter "how to run an IndieWebCamp" page / documentation https://indieweb.org/IndieWebCamps
 * We need IndieWebCamp in a box prepared to send to new organizers https://indieweb.org/IndieWebCamp_kit
 * Things like "Hello my URL is" stickers, sticky notes for the grid, maybe masking tape. Or at least a list of things to order and have delivered to the venue
 * Questions to ask registrants like: food prefs, childcare needs etc
 * Decrease challenges like all the wiki pages, the nice pages at 2017.indieweb.org/ etc
 * Keeping the choice of which ticketing system to use, for regional prefs. E.g. Tito eventbrite brownpapertickets or even Meetup
 * Possible templates for typical camp pages and planning layout so it doesn't have to be reinvented
 * Add more detailed steps to documentation on what types of information should be gathered via a ticketing system
 * Add some specific tutorials regarding certain ticketing systems such as Tito in regards to best practices like copying an existing event as the beginning for a new event

Improve Getting Started
In progress of updating Getting Started steps to:
 * simplify steps (create subpages if necessary for longer explanations)
 * reduce steps to only those that are required and have direct benefits
 * i.e. are direct steps toward achieving IndieMark levels in various areas.
 * provide an explicit "Why?" quick and easily understandable explanation of the benefits, the motivating reasons for taking this step. What problems are solved? What new capabilities do you get by taking this step.
 * re-order steps in order of ease of implementation / dependency
 * move nice-to-haves, or simpler side options, to other pages.

I've updated Connect and Personal Domain accordingly (including subsuming short domain as a "bonus" subpart of personal domain) so far and will work on subsequent Getting Started steps accordingly. However, if you want to help with these updates, please go for it and edit accordingly! - Tantek 15:06, 7 May 2013 (PDT)

Currently working on:

Improve Why Explanation

 * create subsections on why for frustration, fear, death
 * provide good photo/summary page links (e.g. lightboxes of screenshots) for all corp site failures on site-deaths and why pages.
 * copy each "why" citation for a silo to a Criticisms or Downtime section for that silo

Tagboards
Create additional Tagboards (e.g. http://tagboard.com/indieweb ) for IndieWeb related things, and any tags used/mentioned by @indiewebcamp (or @indiewebcampuk) and link them to the respective wiki pages here.


 * The link to the tagboard is dead - do we need that? 11 Apr 2022

Process Criticism

 * If/when you see IndieWeb critical (or silo apologist) articles, add to: challenges


 * Go through challenges and analyze the articles, extracting new FAQs and specific challenges for the IndieWeb to overcome.

Blog Update to Call For A Distributed Web
(more than one person blogging about this would be good)


 * Blog an update of the 2+ year old http://brewster.kahle.org/2015/08/11/locking-the-web-open-a-call-for-a-distributed-web-2/ from an IndieWeb perspective, what IndieWeb technologies have solve the problems in the original post, status of the experimental tech the original post mentioned, etc.


 * Include references to https://rhiaro.github.io/thesis/ since it is newer than Brewster's post and has lot broader coverage of projects, efforts etc.

Bonus, also integrate the points / proposals / projects mentioned in https://www.oreilly.com/ideas/what-if-we-build-the-internet-we-always-wanted into the post such that the post responds to both at the same time (there's a lot of overlap).

Blog State of the Interoperable Decentralized Web
(more than one person blogging about this would be good)

Follow-up to previous blog post and dci.mit.edu/assets/papers/decentralized_web.pdf (Internet Archive link, and PDF, sorry, academic source) with case studies on some projects from that blog post and the 2016 Decentralized Web Summit

Consider also explicitly citing and following-up to:
 * https://metaverse.wordpress.com/2017/09/10/decentralized-web-pt-3-indieweb/

Document from most to least interoperably deployed decentralized web solutions.

Noting second to last anything mentioned in the MIT report that is deployed with real users but single-project monoculture with all the downsides of that, fragility etc.

Noting last anything mentioned in the MIT report that is either not deployed (e.g. academic / theory / hand-waving / hype), or experimentally deployed, but no real (even selfdogfood) users.

Blog on Open Standards for the Decentralized Web
(more than one person blogging about this would be good)

Follow-up to previous blog posts and ’s OSBridge 2016 talk on the topic, focusing first and mostly on:


 * Well deployed interoperable web standards (10+ interop impls with real world daily users across systems)
 * Webmention
 * Micropub
 * microformats2 (h-entry, h-card, h-feed, etc.)
 * Emerging interoperable web standards (3+ interop impls with real world daily users across systems)
 * WebSub
 * Maybe LDN? Double-check actual software/systems/sites in use.
 * Other standards being implemented (1+ impls, maybe interop, with real world daily users within systems)
 * ActivityPub - e.g. on Mastodon etc.
 * Monoculture standards - "standards" only implemented (often driven by) a single implementation, summarize such monoculture problems etc.
 * Dat
 * Ethereum
 * IPFS

IndieWeb Homepage Live Modules

 * site-homepage

Archive sessions and chat logs
Refer to Etherpad: Archiving IndieWebCamp notes.
 * 2022/Düsseldorf/Demos watch video and take notes similar to 2021/Düsseldorf/Demos.
 * 2019/Düsseldorf/Demos from chat logs
 * 2018/Nuremberg/Sessions
 * 2018/Düsseldorf/Demos
 * 2016/Berlin/Schedule

Move YouTube archived content to archive.org
As we've moved to storing new sessions on archive.org, you can volunteer to move old sessions there that were recorded on YouTube...and maybe even watch them as well.

If each of us take a few when time permits...we can get through them easily.

Instructed parties can enquire in chat for the credentials for our archive.org account if you do not have them.

Use What You Make
Goals: create an actual use what you make page separate from eat what you cook, and replace general use of selfdogfood with use what you make.

This needs multiple steps:


 * ✅ extract the "use what you make" principle and supporting text/quotes from the eat what you cook metaphor and create a new page for use what you make rather than a redirect (may need to delete & recreate so it shows up as new), as the complement to make what you need.
 * analyze the selfdogfood page for content that would make sense to include or move to the new use what you make page, and turn selfdogfood into more of a metaphor-focused & historical page similar to scratch your own itch
 * analyze which pages link to selfdogfood, manually decide if they should reference and link to use what you make instead, and update those refs/links accordingly.
 * ^ similarly, analyze which pages link to eat what you cook, manually decide if they should reference and link to use what you make instead, and update those refs/links accordingly.
 * ✅ after creating the new use what you make page, update principles to link directly to it in principle 4

Update brainstorming page
For brainstorming page:


 * Describe what it is, and how to create a Brainstorming section as part of wikifying
 * list the existing specific brainstorming pages we have and includes a section about "Brainstorming" sections on wiki pages per expand_a_page.