#interpeer — Public Fediverse posts

Watching @jens's talks on #interpeer whilst @elletaryn's kitty watches our neighbour the brushturkey

I'm noticing similarities in what the #interpeer and #veilid projects are striving for. One key difference from my surface level inspection is the choice of C++ and Rust, respectively

Interpeer Architecture Part 3: Derived Architecture

https://makertube.net/w/voSWeRXDHkHLj4mRTNeqzX

Interpeer Archutecture Part 2: Alternative Architectures

https://makertube.net/w/3mvmdAcusMW5uXSkFH7hJj

Am morgigen Sonntag werde ich auf den #LinuxTagen in #Chemnitz um 17:00 einen kleinen Vortrag darueber halten, wie man Authorisierung auch verteilt hinbekommt.

https://chemnitzer.linux-tage.de/2023/en/programm/beitrag/139

Dazu gibt's einen Internet-Draft, zu dem man gerne etwas beitragen kann. Einen Anwendungsfall beispielsweise, oder etwas, was den Text klarer gestaltet, usw.

#CLT #CLT23 #CLT2023 #Interpeer

Let's have an #introduction for the #interpeer project.

The project's mission is to develop next generation, human centric internet technologies. Today, the internet is usually equated with the web. Most likely the most useful view is to see both together as a stack that enables distribution of knowledge, data and media, as well as apps. We're looking at the entirety of this.

The web is centralised. By design, it's decentralised, but its design contains elements that promote centralisation.

FYI, I moved the #Interpeer account from fosstodon over to here. There is no particular issue I'm addressing here, it just seems like a slightly better fit overall.

Since it came up a couple of times, here's a system architecture diagram that may help put all the different #interpeer projects into context.

It lives in its own repo at https://codeberg.org/interpeer/system-architecture

Some components have empty repos. Those will need future work.

One of the grants that #interpeer operates under comes from the @isoc_foundation . The grant focuses on R&D into a web-like architecture that is not as prone to centralization and invasion of privacy as the web itself is.

Yesterday afternoon, we had a brief reflection call with other grantees. One of the issues we're facing was raised by someone else: what do we do when the grant ends? How do we fund future work?

Our answer is the NGO - it permits us to run donation fundraisers, and opens...

@info_activism In a nutshell, this is why #interpeer is about distributed tech, not decentralization.

Decentralization sounds great: move power away from the center into multiple locations. But it really is nothing more than centralization on a smaller scale. A choice is better than no choice, but a choice of service is still servitude.

The only way to get back to that old idea about putting power into the hand of people is to cut out the middle person - or at least leave that possibility.

The #interpeer project aims to help create a human centric, next generation Internet by encapsulating human rights into every layer of the stack: https://datatracker.ietf.org/doc/rfc8280/

In simple terms, it means private by default, local first applications that give full control to the user over what to sync and share with whom - and by implication, no services or web apps that take that decision away.

We're making building blocks for this, not an app. We have ideas, but can't know what will suit people best.

@jens Btw, I am glad you are working on turning swords into ploughshares with your #interpeer project.

I'm simply pointing out that the trends you are working against are part of a wide and ongoing conflict that is a natural consequence of the nature of the system.

@jens re #interpeer : why don't include at least an oneliner about what channeler is? TBD isn't quite descriptive. Other components could use a "what this does" as well.