Since I occasionally find people focused on the same kind of problem that I’m trying to tackle with this project, and I have a terrible tendency to share my thoughts informally, I figured it would be a good idea to post a kind of roadmap for the project.

This isn’t going to be fixed in stone forever. But its general outline should remain more or less intact.

The overall goal is to “fix” the problems of the World Wide Web by addressing the privacy and security needs of the users and by embracing that most users will use a multitude of devices, some of which are shared. Finally, it’s important to understand that real-time usages and eventually consistent usages of …

A few days ago, I managed to complete another milestone for the NGI0 grant agreement. It’s released as channeler on the Interpeer code page.

In a sense, this is more of an interim update. The grant agreement covers many more milestones in this repository, and as it stands, the code is highly work in progress.

But it demonstrates the basic channel establishment functionality – and while that doesn’t have any bells and whistles yet, it’s a good starting point for further iteration and refinement.

The protocol design largely follows the ideas laid out on the blog.

The next step will be to add per-channel reliability features, which is also a good reason to streamline the …

In my last post, I wrote about how REST architectural principles feed into the problem with surveillance capitalism that the world faces today. Today, I want to explore how we might approach an architecture for a better, more human centric Internet.

Internet or Web?

First, some quick disambiguation. The Interpeer Project’s aim is to provide infrastructure for a next generation human centric Internet – so why focus on REST, when that is specific to the web?

There is a practical consideration here as well as one rooted in the status quo: on the one hand, we need to work with existing Internet infrastructure in order to get software out there, so right now we’re not going to …

Remember the early 90’s and Salt-n-Pepa? No? Well, it’s about breaking taboos around talking about important topics. In a vaguely comparable way, we software engineers have a kind of taboo on talking about . Let’s break that.

See, most of you will know what REST means, right? And the majority of my readers will be able to tell me that it stands for REpresentational State Transfer. And yet, my experience is that just about everyone misclassifies things as RESTful that are not. Worse, when I bring that up the often-heard response is that “well modern REST means something else” as if two decades of misusing a term somehow invalidates the original idea.

So today, I …