PEERD

Frequently Asked Questions (FAQs)

Why is the project named PEERD?

PEERD is a stylized version of the word peered, and is pronounced the same way. Inspiration for the name came from the fact that PEERD is focused on peer-to-peer networking, and from the computing concept of a daemon, a background process or service that is not under the direct control of a user and is traditionally named to end with the letter d. PEERD is always fully capitalized when standing on its own in text, and always lowercase when making up part of another name, such as the peerd-networking library.

What licenses does PEERD use?

Permissive licenses are preferred and used in the PEERD software project, specifically public domain licenses, in addition to using weak copyleft licenses when required.

What does the open web mean?

The open web refers to public, cooperative, and standardized web communications. It heavily relies on open source and open standards based software. It is a global public resource that is open and accessible to all, in a permissionless fashion. It provides a standardized development and production environment. It opposes private, exclusive, or proprietary solutions.

What does in-browser mean?

In-browser means built for, and usable in, modern web browsers, by using open standards to develop easily and widely deployable applications.

What is an open ecosystem?

An open ecosystem describes a software system that is based on open source and open standards (including related concepts like open collaboration, open content, and open formats), which can be freely adopted, implemented, and extended by users, and avoids centralization points such as proprietary services or tokens. It provides an open platform with well-documented application programming interfaces (APIs) that allow the software to function in ways beyond what the original developer conceived of, without requiring modification of the underlying source code (although that can be modified as well). Using these interfaces, anyone can integrate on top of the ecosystem to add features and functionality.

What licenses should be used in an open ecosystem?

Licenses used at the core of an open ecosystem should be limited to public domain, permissive (non-copyleft), and copyleft open-source licenses. Software that is built on top of an open ecosystem can use more restrictive licenses if desired. Typically, restrictive licenses are used for specific situations, such as commercial and private applications.

What is WebRTC?

WebRTC (Web Real-Time Communication) is a free and open-source standard that provides web browsers with real-time communication (RTC). It allows text, audio, and video communication to work inside web pages by allowing direct peer-to-peer communication, eliminating the need to install plug-ins or download and install native applications. It is supported by all major web browsers.

Why does PEERD use WebRTC?

WebRTC has been selected as the transport mechanism in PEERD because it provides a standardized, peer-to-peer communication mechanism which is supported by all major web browsers. It allows text, audio, and video communication to work inside web pages by allowing direct peer-to-peer communication, eliminating the need to install plug-ins or download and install native applications. Support and standardization are continuing to develop and increase, and can be expected to do so into the future.

What is Bitcoin?

Bitcoin is, by far, the predominant decentralized blockchain and cryptocurrency network. It uses cryptographic techniques to regulate the issuance of units of currency and verify the transfer of funds, operating in a permissionless and trustless way, independently of a central bank or control point. In simple terms, Bitcoin is the currency of the internet.

Why does PEERD not have its own coin or token?

In the interest of facilitating ease of adoption and working with, not against, Bitcoin, there is no platform-specific token in PEERD, other than bitcoin itself. Creating an original, fungible, value-routing token is viewed to be both needlessly reinventing the wheel, and antithetical to the PEERD ethos and vision since Bitcoin can be used for such purposes. By using bitcoin as its native token, or currency, PEERD and the applications built on top of it gain access to the broad and quickly growing Bitcoin network effects, without having to waste resources attempting to reproduce what Bitcoin has spent nearly a decade creating.

Why does PEERD target web browsers? I heard that is inefficient, not what they are designed for, or only going to cause issues. Is any of that true?

These concerns arise out of a line of thinking that views web browsers as only being for the web, while not appreciating the fact that what the web is defined as is constantly expanding. It used to be simple, static websites, but has since grown to be so much more, to the point where many popular applications are being designed with an in-browser version available. In recent years, the web has seen many exciting additions such as WebRTC, WebSocket, and WebAssembly. PEERD can be viewed as a similar type of attempt at expanding what the web is capable of by providing a powerful set of JavaScript libraries for web developers to use when creating decentralized web applications, termed dwapps.

What is Vanilla JavaScript?

Vanilla JavaScript is pure JavaScript, as shipped in web browsers, without any additional frameworks or libraries external to PEERD.