own your data



 own your data  is an IndieWeb principle with two key parts: 1) your data lives primarily under your own domain, and 2) you are able to retain your access over time.

Why
First, using your own domain gives you control over where people find and interact with you online. When you migrate to a new hosting provider or CMS, if your site stays on the same domain, everyone will still find you, regardless of whether they follow your site in a reader, land directly on your permalinks from other sites or search engines, or even type your domain directly into a browser.

Second, they say that change is the only constant, and web sites are no exception. Whether you stick with a host or CMS for a year, a decade, or a century, you're likely to change something eventually. When you do, you'll need usable access to all of your existing data. This includes export and import, data formats and standards, tools, protocols, permissions, rate limits, and more.

Also see why.

The Basics

 * Getting Started
 * own your links

Per Silo
Commit to owning your data by using your site, instead of a silo, for each silo you currently use.

Each silo you stop directly using (POSSE is ok), and use your own site instead, is a step forward in owning your data.

Per Post Type
Commit to owning each kind of post you publish, by using only your site to publish particular kinds of posts (again, POSSE is ok).

Each kind of post you stop posting directly to any/all silo(s), and use always use your own site to create instead, is a step forward in owning your data.

Per Post Type Per Silo
A more incremental but still significant step is stop posting a particular type of post to a particular silo, and always use your own site to publish that type of post instead of that silo.

IndieWeb Examples
 Add yourself here if you: and note what date you started owning your data of what kind(s) of posts, or instead of which silo(s).
 * have an indieweb site, and
 * are using it exclusively to post either
 * a particular kind of post (e.g. notes), and/or
 * if you are posting to your site completely instead of a particular silo (e.g. Twitter)

For the purpose of this page, please succinctly list, only
 * specific silo(s) you have replaced usage of with your own site. E.g.: I use my own site instead of Twitter (notes, replies, favorites)
 * post type(s) you use your own site for instead of / before any silo posts. E.g.: I post notes on my own site instead of Twitter, Facebook, Tumblr, etc.
 * post type(s) instead of specific silo - what post type you use your own site for instead of / before a specific silo. E.g.: I post notes & replies on my own site instead of Twitter.

Optional details, for each of the above post types / or "instead of silos", optionally note which projects or tools help you do so.

Examples of what doesn't count:
 * You post some notes on your own site, and some notes directly to Twitter.
 * Why: All or nothing. Either you've committed and are following through with posting all your content of a specific kind to your own site, or you don't yet "own your data" of that type.

Examples of what belongs on your user page instead:
 * owned other things besides post types / instead of silos (sites, domain names, project installs)
 * what other sites you post to

Examples of what doesn't disqualify you:
 * A small number of test posts on any given silo of any given content type, especially if you're doing it as research for how to best POSSE to that silo, especially if you document the results of your research here on the wiki. Though for research purposes, you really should create one or more separate test accounts on silos.

gRegor Morrill
has:
 * owned articles since 2002-01-26..
 * owned photos since 2017-04-15
 * POSSE manually to Instagram, occasionally POSSE to Twitter with Bridgy Publish, backfeed via Bridgy

Tantek
undefined has publicly:
 * owned his articles since 2002-08-08.
 * owned his notes since 2010-01-01.
 * owned his events since 2017-06-26.
 * instead of Twitter, posted on his own site:
 * notes since 2010-01-01, POSSE to Twitter since 2010-01-26
 * @-replies since 2013-05-12, POSSEd to Twitter (same day).
 * favorites as likes, since 2014-12-31, using Bridgy Publish to POSSE likes of tweets to favoriting those tweets on Twitter.
 * instead of GitHub posted on his own site:
 * issues since 2018-02-21
 * replies to issues (since 2018-02-19, post about)
 * replies to comments on issues (since 2018-02-21)
 * reactions to GitHub comments (since 2018-02-24), to GitHub issues (since 2018-02-26), to GitHub pull requests (since 2018-07-09

Notes:
 * not yet ownyourreplies. I can't say I yet I follow "ownyourdata" for ALL my replies, as I still post replies directly to Instagram posts, and the past have posted replies directly to posts on Facebook (stopped in 2020), whereas I should be posting even those replies on my own site first, and then POSSEing them to Facebook manually. Thus I've scoped my "ownyourdata" of replies to only being a replacement for my use of Twitter and GitHub to post replies.
 * not yet ownyourlikes. I also can't yet say I follow "ownyourdata" for ALL my likes, as I still like photos directly on Instagram, and posts on Facebook (stopped in 2020).
 * not yet ownyourRSVPs. While I have owned my public RSVPs (especially "going") since 2017-01-01, I still RSVP to private events on Facebook. I’m not sure how to avoid this short of giving up on private FB events. I also have been clicking the "I’m Going" on IndieWeb HWC Events pages without always posting an RSVP on my own site.
 * not yet ownyourissues. While I’ve owned 100% of my public issues posted to GitHub, I still post issues directly (and without my own copy) to Bugzilla.
 * no private posts yet. I don't have a mechanism for publishing private posts yet, so I am still manually posting those elsewhere, like Swarm checkins, comments, and likes, and private GitHub repos for example.

Snarfed
has:
 * owned his articles and notes since 2003-06-29


 * owned his photos since 2003-03-06
 * owned his replies/comments since 2013-10-02
 * owned his likes/favorites since 2014-02-02
 * owned his reposts since 2014-03-13
 * owned his events and rsvps  since 2014-01-15


 * instead of Twitter:
 * posted notes and photos on his own site always, replies since 2013-10-02, favorites  since 2014-02-02, retweets  since 2014-03-13
 * POSSEd via Bridgy Publish, backfed via Bridgy
 * read his Twitter stream via twitter-atom and responded via web bookmarklets and Android flow instead of Twitter's own web UI and app


 * instead of Facebook:
 * posted articles, notes, and photos on his own site always, comments since 2013-10-02, likes  since 2014-02-02
 * POSSEd via Bridgy Publish, backfed via Bridgy
 * PESOS backfilled articles and notes between 2009-10-15 and 2012-10-28  with freedom.io
 * read his Facebook news feed via facebook-atom and responded via web bookmarklets and Android flow instead of Facebook's own web UI and app


 * instead of Instagram, posted:
 * posted photos on his own site always, POSSEd manually, backfed via Bridgy
 * read his Instagram stream via instagram-atom instead of the Instagram app


 * instead of Google+, posted on his own site:
 * articles, notes, and photos always, POSSEd manually, backfed via Bridgy

Bear
has
 * owned his articles since 2003-12-18..
 * owned his own replies since May of 2014.
 * owned his own replies to others since November of 2014 but until I add in-reply-to markup I cannot call them comments'.

Aaron Parecki

 * owned his articles since 2006-04-14
 * owned his bookmarks since 2010-12-17
 * owned his notes and replies, and POSSE to Twitter since 2012-08-19. twitter copy
 * owned his photos since 2014-03-08 (launched at IndieWebCamp SF 2014) and occassionally manually POSSEs to Twitter since 2014-05-06on Twitter
 * owned his biking, running, and driving since 2014-07-30
 * owned his videos since 2014-09-10
 * owned his food & drink posts since 2014-10-17
 * owned his cat since 2014-11-01
 * owned his reposts since 2014-11-02
 * owned his likes since 2014-12-26 (launched as part of the 2015-01-01 commitments)

Kartik
Note: kartikprabhu.com links appear to have stopped working (2022-10-24 or earlier) without a redirect. Manually add www. at the start until these links have been fixed.

has:
 * owned his articles since 2013-06-01. Invictus.
 * owned his notes since 2014-03-08..
 * instead of Twitter, posted on his own site:
 * notes and POSSE to Twitter since 2014-03-20. original twitter copy — with original post permalinks until 2017-07-01 https://twitter.com/kartik_prabhu/status/881282109549277184
 * photos and POSSE to Twitter since 2014-07-27. original
 * instead of Google+, posted on his own site:
 * notes and manual POSSE to Google+ since ??
 * instead of on others blogs not supporting webmentions, posted on his own site:
 * replies and manual POSSE replies to others blogs not supporting webmentions since 2014-08-28. original

Sebastiaan Andeweg
has:
 * instead of Instagram, posted to his own site:
 * photos and POSSE to Instagram (since 2016-11-22, with import of all earlier photos)

Marty McGuire
has:
 * instead of Twitter, posted to his own site:
 * articles, notes, photos, and videos and POSSE to Twitter manually (since 2016-07)
 * instead of Facebook, posted to his own site:
 * events, notes, photos, and videos and POSSE to Facebook manually (since 2016-08)
 * instead of Goodreads, posted to his own site:
 * reads, with import from Goodreads ending 2018-03 and subsequent read posts only on his own site starting 2018-05.
 * instead of ... a non-existent silo to track podcast listens:
 * listens of podcast episodes to his own site since 2019-02.

Notes:


 * Not yet owning all replies. Still making some replies directly on Twitter, Facebook.
 * Can and does reply to IndieWeb-enabled posts on his own site since at least 2016-11.
 * Not yet owning all likes and reacji. Still like some posts on Instagram, Twitter, Facebook
 * Note: uses Perkeep to keep an archive of all tweets liked.
 * Can and does post likes of IndieWeb-enabled (and other) posts on his site since at least 2016-11. Reacjis since 2017-10.
 * Not yet owning all bookmarks. Still bookmarks privately with Pinboard, but posts some bookmarks publicly since 2017-04.
 * Not yet owning all RSVPs. Still RSVPs to some events on Facebook.
 * Can and does RSVP to IndieWeb-enabled events on his own site since 2016-06.

Previous Examples
These are examples who owned their data for periods of time, but either went offline, or resumed posting silo-first or silo-only content at some point.

Ben Werdmuller
has, since 2013-07-11, using Known:
 * instead of Twitter, posted to his own site:
 * notes and POSSE to Twitter until ~2022 or earlier (e.g. https://twitter.com/benwerd/status/1584334951243079681 and other recent native/exclusive-Tweets)
 * instead of Facebook, posted
 * notes and POSSE to Facebook until ????
 * instead of LinkedIn, posted
 * notes and POSSE to LinkedIn until ????
 * instead of Flickr, posted
 * photos and POSSE to Flickr until ????

The Dod
dubiousdod.org links appear dead as of 2022-10-24 (or earlier — need to check Internet Archive for when it went offline and document that here with permalinks to belowmentioned post types) had:
 * instead of Twitter, posted to his own site:
 * notes, replies, repost, favorites and POSSE to Twitter using his RedWind install since November 2014 until 2022 (or earlier)
 * Uses a bookmarklet to reply/reshare/fav stuff (including tweets).
 * Uses Bridgy to backfeed Twitter interactions as webmentions

Hashtag
# ownyourdata  is a rallying cry hashtag for aggregating content across indie web sites and 3rd-party silos about "owning your data", "owning your own data" etc.


 * Tagboard: #ownyourdata - hashtag aggregator across Twitter, Instagram, Google+.
 * Google News Search: ownyourdata


 * 1) ownyourdata posts tend to be a a subset of Posts about the IndieWeb.

Criticism
Following a discussion between  and  that was triggered by specific wording found in an indiweb critic post, namely the sentence: Legally, any and all content that you post to a silo is no longer  "your  content"


 * : https://help.instagram.com/581066165581870?ref=dp "We do not claim ownership of your content, but you grant us a license to use it"
 * [...]
 * : giving up your ownership means you can no longer do things with it yourself such as giving other people licenses
 * [...]
 * : one would assume [...] owning == option to grant and to revoke rights/access
 * : and with sending it to a silo, the revoking part is, most of the times, thrown away
 * : hence "owning" from that point on, is incomplete(?)