Indieweb site

Context and Problem

I want to be able to publish content on the internet independently of intermediary third party publishing mediums. These platforms have some benefits, primarily (but not unquestionably) the benefit of reach, but many of them lack severely in other areas:

  • overreaching tracking practices and / or disregard for privacy
  • questionable or opaque usage of user data
  • black box algorithms
  • siloed users and content
  • excessive and / or invasive publicity
  • Terms & Conditions that are difficult to navigate and understand and which can evolve at a moment’s notice
  • unpredictable outcome of the platform itself, which can lead to unwanted loss of data

Having a website that implements the IndieWeb standards is a way to reclaim ownership over published content. It makes it possible to do so without having to forego access to many of the third party platforms mentioned above, albeit some make the task easier than others. It also opens up the possibility of connecting to other websites that implement the IndieWeb standards. A longer list of why make a website (from the IndieWeb perspective)

I want to make an IndieWeb site. This does take a bit of involvement and the acquisition of new understanding. It makes sense to make a new package indiesite that contains an indiewebified website template. This will allow me to track and document that work and to use the template.

Considerations

IndieWeb references:

Tools

Decision

I will work on the implementation of IndieWeb template in parallel to other parts of the project

🚧 WIP

  • using it as an excuse to pick up Rust