Phil Dreizen

indieweb
February 24, 2017, 2:47 am

The indieweb is a movement to own your presence, and data on the web. The idea is that you: own a domain that becomes your "home" - the center of your identity on the web. There you control all the data that you publish: the text, the pictures you took, the video. The look and formatting of your site is entirely your own. There's an emphasis on building your own tools. Though rarely explicity stated, the movement has a nostalgia for the web of old, where websites had character and charm and openness, compared to the blander, uniform "walled garden" of the modern web. But I don't mean to trivialize: this is not frivilous nostalgia. It's an effort to decentralize the web and take back ownership from corporate websites.

Their tagline on their main page: "The IndieWeb is a people-focused alternative to the corporate web." They call the big social media sites silos. (In fact, there's a quite a lot of lingo. Some, like selfdogfooding is pretty terrible.).

I love the idea: the indieweb is very much in the spirit of kupad.net, and embodies some of what I had in mind when I decided to have my own "home page" that I build myself. But I knew nothing about the indieweb until last week. (Indieweb has existed since at least 2010. And amazingly, it's still active!)

The movement is not the idea of independent websites, acting as isolated islands, trying to exist entirely on it's own. The indieweb has created protocols and tools for creating a websites that are both independent but can operate with one another by using these tools. The indieweb is meant to be de-centralized, but federated. Yhey promote an intuitive publishing model in which you publish content to your own page, before pushing it to the various social networks (Publish (on your) Own Site, Syndicate Elsewhere aka POSSE). (That's what kupad.net had been doing until twitterfeed shut down). Really, POSSE is a declaration of a pretty obvious thing to do.

So, I plan to start integrating some of their tools/protocols into the site and as I do it, I'll document it.

More: