Indie Site

Indie Site is an implementation of a Federated Personal Web Site (FPWS).

But what is a Federated Personal Web Site? Good question. It’s:

  • Federated: FPWS owners can follow each other’s sites, talk to each other, and be notified of updates. Federation is achieved via the W3C ActivityPub protocol so they can also talk to any other ActivityPub compatible service (e.g., Mastodon).

  • Personal: An FPWS is for one person only: the owner of the site. It is a single-tenant application. We do not have (and do not want) the concept of “users.”

  • Web Site: apart from the above two qualifications, an FPWS is a regular web site. It is build using web technologies and experienced through a standard web browsers. Indie site functionality can also be experienced via native apps in the future that use its REST And WebSocket APIs.

May 2018, update: While Indie site requires a server component for findability and availability (two areas in which strictly p2p apps struggle), it will eschew the standard client/server model in favour of a peer-to-peer approach using an “offline first” approach to its web client and a replicated datastore. We are currently researching various conflict-free/commutative replicated data types/algorithms. Work on this is currently taking place on the Spikes section.

Sections

Screenshots

Indie Site is currently under development. These are some screenshots of the progress. It is currently not ready for testing as key functionality still has to be integrated from our various spikes. We hope to have a very basic functional initial version in April 2018.

Posting interface

The posting interface aims to be as unobtrusive as possible. We are experimenting with seamless What You See Is What You Get (WYSIWYG) Markdown support for advanced authors as well as a default experience that works for anyone, regardless of existing technical knowledge.

Indie Site Screenshot: posting interface

Settings screen

The Settings screen is where you can customise the site’s background colour (soon to be the theme colour) or background image, your profile image, and your name and bio. All are optional.

Indie Site Screenshot: settings screen

Initial setup

Initial setup involves picking a strong password. This password is not stored anywhere and is used to encrypt your private key for storage on the server. (What that means is that once we have implemented private messages, no one else will have access to them but you.)

Indie Site Screenshot: initial setup

Remote follow

As Indie Site is a federated personal web site (FPWS), other people who have a FPWS, Indie Site, Mastodon, or any other ActivityPub-compatible site/app/account can follow you. (And you can follow them.)

Indie Site Screenshot: remote follow

Author: Aral Balkan Last modified: 10/05/2018 Words: ~500 Reading time: 2 min