P2P News

There is no excerpt because this is a protected post.

Ship a command as a standalone binary that updates itself peer-to-peer. swap is an applied demonstration of a peer-to-peer installable self-updating single-operation program. This is the first in our Ecosystem Spotlight series, looking at the libraries, tools and applications growing out of the Ecosystem of Pears.

A few weeks ago we shared the story of how Pear has evolved from a single application platform to an embedded runtime supported by CLI tooling. Today those changes are officially live in Pear CLI v3.0.0. We have also completely reworked our documentation so getting started on Pear or transitioning to the new architecture is easier.

What if a terminal application could update itself without relying on servers, package registries, or centralized infrastructure? Introducing Hello Pear Bare, a new boilerplate for building standalone Bare executables with peer-to-peer over-the-air updates built in. Package your application and runtime into a single binary, distribute it anywhere, and let updates flow directly between peers. This article explores the architecture behind the next generation of peer-to-peer software distribution.

Pear is evolving. What began as a peer to peer application runtime inside the Pear CLI is now becoming something far more flexible: an embeddable runtime library that can integrate into any JavaScript environment. This shift marks a major step forward for the Pear ecosystem, making peer to peer over the air updates, distributed deployment, and Bare workers available beyond the CLI itself. In this article, we explore the history behind Pear, why the runtime architecture is changing, and what developers need to know as Pear moves toward a more modular and production ready future.

Most password managers encrypt your vault and upload it to the cloud. PearPass does something radically different: your data never leaves your devices. No central server. No cloud copy waiting to be stolen. This deep dive explores the peer to peer architecture behind PearPass, from Hypercore and Hyperswarm to Autobase and end to end encrypted device syncing — and why removing the server changes everything.

You want two computers to talk directly to each other. No server in the middle, no middleman, no monthly bill. Sounds simple — the Internet is a network, after all. But the moment you try it, you discover something uncomfortable: the Internet was never designed for this. Here’s why, and how Hyperswarm punches through anyway.

Your passwords. Your devices. Nothing in between. PearPass is a fully local, open source password manager built by Tether Data. Unlike traditional tools that store your vaults in the cloud, PearPass keeps your data on your devices — encrypted, private, and under your control.

WhereFam is a secure, real-time location-sharing app that uses peer-to-peer (P2P) technology to enable private, scalable communication—without relying on centralized servers. Built with Pear Runtime, the app allows users to share their live location directly with trusted contacts, maintaining full control over who sees what, and for how long.