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.
Comments on this site essentially stopped working because of a lack of support for OpenID in general and the deprecation of the OpenID 2.0 standard specifically. OpenID is (or was?) an open standard for authentication, and allowed you to log into websites using just one URL that that was hosted by an "OpenID provider." There were OpenID providers like myopenid for those who knew what OpenID was. But large companies like Google, Yahoo, and Facebook also acted as providers, hiding the underlying technology, allowing users to log in with their already existing accounts.
What was nice about OpenID was that I didn't need to ask users to create an identity on my site. They just used their identity from somewhere else. And because it was an open standard, I didn't need to write code for each provider.
It seems since I last actively used this site, OpenID 2.0 was dropped, replaced with OpenID Connect. Besides Google, I can't seem to find anything that uses OpenID Connect. (I could be wrong about this, but it sure is hidden). And even Google prefers you use their "Google Sign-In" over OpenID Connect.
Of course, you see "Sign in with Google" and "Sign in With Facebook" all over the web. But it seems to me that if I want people to be able to sign in with Google,Facebook or anything else, I have to handle each case separately. Which is really annoying.
In any case, until I do something about the situation, I have to disable comments.
We all declare for liberty, but in using the same word we do not all mean the same thing. -- A. Lincoln
Continuing from my previous discussion on degoogling my life, and particularly on not being a customer of what is ultimately an advertising company:
I had been using twitterfeed as the means for automatically publishing posts from this blog to facebook. IIRC, twitterfeed would read from the rss feed and publish the latest posts. Well, twitterfeed closed their doors on Oct 2016. I'll have to find a new solution.