From IndieWeb
(Redirected from User:Tantek)

Tantek Çelik


Pronouns: he/him

Tantek is a co-founder of IndieWebCamp and works on open web standards at Mozilla.

Chat Nickname: tantek



IndieWeb talks

my indie web setup

All auto-POSSEing also automatically adds syndication links to my posts. For manual POSSE copies, I have to edit my posts to add syndication links.

authoring practices

In short, I write plain text for notes and similar posts (reply, photo, video posts), HTML for articles and similar posts (event, issue posts).

silo posting

In general I treat silos as building blocks for my own indie web architecture. They're just another [LEGO] brick in the wall as it were.

However there are a few content types that I still post to silos, and am using a PESETAS architecture with two destinations as a stopgap / copying mechanism.

Silos I'm using without a copy destination (in alphabetical order):


  • Foursquare - I treat my Foursquare checkins as semi-private to friends on that silo, and thus I don't have a public PESETAS setup for it. I'm hoping to skip the PESETAS/PESOS step with checkins and implement native checkins directly on my site, and POSSE them out to Foursquare (as Ben Werdmuller does with idno).


  • GitHub - I use GitHub for both some of my own open source projects, and to contribute to others. I have a redirect url of setup for now just so I can use URLs with a domain I control. This solution has restrictions/limitations, yet is still a stepping stone:
    • I am dependent on github's URL design for now - whatever they put after /tantek, I have to support after /github on my site.
    • I can delay design of my own non-vendor/silo-specific path (e.g. /source instead of /github) until the point in time when I feel like doing so.
    • I should eventually host my own source/issues/gists etc for all the usual reasons why
    • At that point, I can figure out the URL design of a generic source path (e.g. /source instead of /github), and implement the redirects from /github to /source (or whatever).


  • PBWorks - I have a wiki (AKA PBWiki) hosted there via redirect URL of - and again, hope to skip the PESETAS/PESOS step and directly switch to wiki pages on my own site.

previous silos

Past silos, which I either no longer post to, or have not really bothered with in a while:

  • Tumblr - - primary PESETAS destination, has a feed, and I've customized it with microformats2 h-entry and rel-author support. As of 2013-182 I'm PESETASing from:
    • ... no silo regularly
    • My hope was that by aggregating my silo posting into Tumblr with a microformats2 supporting theme, that as I add support for content types like photos, video, metrics, jams to my own site, it will be easier to port over past content to my site for historical reference.
  • Nike+ - (nearly) daily fitness activity/metrics, e.g. walking/running. Stopped using in 2016-12 when their iOS app would repeatedly just crash on launch. Caused me to switch to Strava which I've been using instead as of 2017-01.

my indie web projects

Stuff I've written to advance the Indie Web (and runs live on some of which you may be able to re-use hopefully for your own IndieWeb site!

need help with

Things I'm either stuck on, have been unable to make progress on, or appear to be taking me too long to get to that I'd welcome help with.

  • everything #indieweb_community - if you see something in the "indieweb community" list below you think you could help with, go ahead and let me know on IRC (!tell tantek ...) that you're working on it and go for it - no need to ask, just give me a heads-up and start (maybe add it to your own User page too per wikifying). Thanks!

more use-cases

These are a few roughly ordered longterm use-cases I want to solve, beyond what network-bound silo solutions offer, which may/often translate into specific working on items, but may also be large/challenging enough to generate a number of building block working on items.

  1. Taking photos with time/location information (optional manual location) captured/created offline, optional later posting to own site syndicating elsewhere (COOLPOSSE)
    1. Adding notes to such photos, at the time of taking, or later, both offline.
  2. Taking notes with time/location information (optional manual location) same COOLPOSSE.
  3. Tracking running with a series of times/locations (optional manual location) same COOLPOSSE
  4. Tracking venue arrival/departure semi-automatically, with optional manual checkin offline, like COOLPOSSE
  5. Falcon: More use-cases

working on

Rough order I'm trying to follow when working on things:

  1. Things to wiki
  2. Things to blog
  3. Things to design
  4. Things to code

to enable others, myself

Particular things I'm working on for IndieWebCamp and my own site.

personal site functionality

Personal indieweb site functionality (adding to using my own personal content publishing software Falcon

High level goals:

indieweb community

Community things I'm working on - which I welcome help and collaboration on, up to and including taking charge, though I'd like to at least contribute

And these too which need to get integrated by priority order into Falcon Working On / More use-cases sections:

  • citation UI - to provide simple copy/paste UI for citing posts (articles (done), notes, other) from my site.
  • webactions - to achieve and exceed UX parity with Twitter's UI on notes on my own site
  • wiki - I'd like to implement static-file based wiki-like editing/versioning functionality on the static pages on my site, perhaps with explicit "save" edits posted to my updates as d - diff, edit, change posts.

community projects

Other community projects that I contribute to to help enable the Indie Web and everyone owning their own data.


I used to contribute to these too:

  • - formats for sharing "activities", largely defunct except for a low value mailing list (google group). See ActivityStreams on this wiki for latest thinking.
  • - community/forum for discussing how to federate among indie web (and other) sites. Started a slow death after W3C took it over. Now just a noisy W3C mailing list populated mostly by armchair architects.

related blog posts


I am comfortable with the following indieweb creator skills:

  • coding (HTML, microformats, CSS, some javascript/PHP)
  • information architecture (taxonomy, hierarchy)
  • URL design
  • interaction design

I am working on learning better:

  • copywriting
  • typography
  • visual design

want to work especially with

  • visual designers - especially those who have an indieweb presence and want to discuss coding and information architecture improvements.
  • UX designers - can never work with too many UX folks.
  • good writers/bloggers
  • type nerds. who doesn't?

figured out

Things I feel like I've figured out pretty well, have shipped on my own site, can depend on, and am available to help explain to others.


Things from the above lists that I actually completed!

related talks



Why did you choose a single letter Twitter


/me renames self to "T" to increase max chars per msg - thus setting off single char name landgrab.


Use: tinbox << problem and possible approaches to add it here:

I'm collecting requests from IRC here when they're something I can't handle quickly and immediately. Roughly FIFO, feel free to re-arrange if you have reasons to suggest a specific prioritization

  • document existing Webmention sender/receiver interop beyond Webmention specification as minimal W3C Notes in (new if needed) repos. Minimal preamble/intro/abstract, conformance classes (publishers, receivers), what publishers should do (list 3 impls that do, link to more), what receivers should do (list 3 impls that do, link to more). minimize overlap between Notes.
    • WebStream — h-feed, h-entry as currently interoperably supported
      • h-feed
      • h-entry
      • all interoperably supported additional properties for various responses
      • superset (another way of documenting all) of the below Web* specs
    • WebComment - document how implementations that receive and detect a webmention reply:
      • use which properties for what (e.g. author name & photo, post name/contents).
      • commonalities in displaying comments
      • AKA WebComments or "Web Comments".
    • WebLike - document how implementations that receive and detect a webmention like:
      • use which properties for what (e.g. author name & photo, post name/contents)
      • commonalities in displaying likes
      • AKA WebLikes or "Web Likes".
    • WebRepost - document how implementations that receive and detect a webmention repost:
      • use which properties for what (e.g. author name & photo, post name/contents)
      • commonalities in displaying reposts
      • AKA WebReposts or "Web Reposts".
    • WebRSVP - document how implementations that receive and detect a webmention RSVP:
      • use which properties for what (e.g. author name & photo, post name/contents)
      • commonalities in displaying RSVPs
      • AKA WebRSVPs or "Web RSVPs".
    • post-type-discovery
      • document how existing consuming implementations parse for mf2
      • document and cite existing consuming implementations, link to more on indieweb wiki.
      • cite list of IndieWeb Examples of each post type in the spec
      • update to reference the above Web* specs
      • links from Response Type Discovery algorithm to WebComment, WebLike, WebRepost, WebRSVP accordingly
      • once a reply/like/repost/RSVP is detected, what to do
  • blog about, describe, how to do notification first design and text only design

See Also