The talk felt good, but for timing reasons, I had to hurry and there was no room left for discussion. Feedback afterwards was good, though. I'll post video when I have it.

There’s a new interview up on Safety Detectives where I get to discuss the origins, motivation and direction of the Interpeer Project as a whole. It’s been a great conversation, and I think one of the better summaries of the project from the beginnings to where we are now.I also get to make some predictions for the Internet that make me rather sad, but help illustrate why the project is taking the architectural approach that it does.Interview: https://www.safetydetectives.com/blog/jens-finkhaeuser-interpeer-project/

If you ever wondered why the Interpeer Project was running on an .io domain, the reasons are historical. The short version is that we needed to avoid name clashes, and the choice predated the formation of the non-profit.Today, the first step in moving off that TLD is completed: the main website is now running on https://interpeer.orgThere are a few things that need to happen before all is moved over. But at least there's a start now.(Yes, this is prompted by the recent #io news)

@pluralistic on how "Interoperability Can Save the Open Web"https://spectrum.ieee.org/doctorow-interoperabilityHere's the thing, though: the web stack is pretty good at NOT providing interoperability. Why?Let's compare e.g. IP and HTTP on the one hand, and a web API on the other hand. The first two are built on standards. Fulfill the standards, and you can largely communicate.Web APIs are producer defined. Each producer can provide an API that lets consumers do more or less the same thing, but each producer can...