Today, I`m glad to be pushing out one of the largest updates in this project`s history. This is monumental day and one we have been working towards for quite some time. Here are the updates on what you can expect over the next 8 weeks:
=====
I. Introducing ARISEN`s JavaScript SDK
=====
We have officially launched the new JavaScript SDK for ARISEN, which will allow developers to interface with ARISEN`s RPC-based API directly from the browser, as well as desktop applications. ARISEN`s JavaScript SDK, ultimately allows developers to execute actions within on-chain smart contracts, within the front-end of their applications, eliminating the need for any sort of web-based backend. It also combines many of ARISEN`s other JS libraries from the past, like arisenjs-api, arisenjs-ecc and arisenjs-fcbuffer, into one single SDK.
We will be pushing many new updates to ARISENSDK, which is now published under the package name “arisensdk” on NPM, over the next few days and weeks, so please stay tuned.
For more information on ArisenSDK, please visit https://github.com/arisenio/arisensdk
NOTE: ArisenSDK is a customized fork of EOSJS
=====
II. Introducing dCast
=====
In the next few days, we will debut the “dCast” library for the dWeb, which allows users of the dWeb to create end-to-end encrypted tunnels to other dWeb peers. dCast will be used for all kinds of peer-to-peer communication platforms that we`re developing beneath the surface, including dVoice and dPhone (see below). Developers can use dCast to programmatically create encrypted tunnels between peers for P2P communications.
In the next few days, we will be launching dCast`s Node.JS-based API here:
https://github.com/distributedweb/dcast
=====
III. Introducing dTree
=====
dTree is yet another way of storing data on top of a dDatabase. dTree is a distributed, append-only binary tree, that utilizes dDatabase as its distributed feed of choice. Binary trees, especially distributed binary trees are powerful in the sense that even if a Binary Tree (or BTree for short) has over a million entries, the tree can be traversed for a specific record in around 20 lookups. This gives way to dSearch and other decentralized search engines, that can effectively operate without a single centralized server. In other words, dSearch can utilize a multi-writer dTree, where websites are indexed by those who visit them (like through a browser like dBrowser). In other words, as you visit domains or keys via dBrowser, you as a user are automatically indexing this data via dSearch`s dTree. dSearch will be able to spider the entire dWeb faster than Google can spider the regular web. If you think about it, it`s quite amazing isn`t it? We`re excited about this one.
In the next few days, we will be launching dTree`s Node.JS-based API here:
https://github.com/distributedweb/dtree
=====
IV. Introducing dVoice
=====
dVoice is an experimental library, that allows two peers to have a dWeb-based phone call over a dCast-based tunnel. One peer can connect to the next quite easily and use the microphone on their computer to carry out the phone call. For now, this is a terminal-based application, but the fact that the concept works as well as it does today, should signal what we`re really working on the background :). HINT: Soon you will be able to do this from an iOS, Android and a PeerOS-based app. Wait did I say PeerOS? (Keep reading)
In the next few days, we will be launching dVoice`s CLI here:
https://github.com/distributedweb/dvoice
=====
V. Introducing dHub
=====
dHub is a new CLI tool for managing dDatabases, dDrives, dTrees and dWebTries from a single command-line interface. In fact, it`s the most powerful terminal-based dWeb developer tool yet! You can use commands you`re familiar with, like “ls”, “cat” and others, to see what`s within a dDrive, before you ever download it. It`s how a distributed file system should work — being able to “ls” and “cat” through dDrive`s from around the world, gives one the feeling of having one gigantic file system on their computer, when in fact, it`s all over the world. How amazing is that?
The dHub CLI will be launching by the end of February, or sooner, here:
https://github.com/distributedweb/dhub-cli
=====
VI. Introducing The dWeb SDK
=====
In the next couple of weeks, we will be debuting the dWeb SDK, which combines all dWeb`s many libraries, like “ddrive”, “ddatabase”, “dwebtrie” and now “dtree”, into a single software development kit. This means, developers can build applications natively using a single library and can implement features from each, with just a few lines of code. It`s super powerful and we`re actively using dWeb`s SDK to build things like dBrowser Mobile. Yes, I said it, you can now build mobile applications, using dWeb-based libraries (as long as you love React Native like the rest of us).
=====
VII. dBrowser Update + dBrowser Mobile
=====
As you just read, we`re pushing out a new update to dBrowser which includes integrations with dCast, dTree, dHub and dVoice, as well as the all-new dBrowser Mobile edition (for Android, iOS and yes… PeerOS), which will allow users to access dWeb network addresses from any mobile device (how sweet is that?). We should be pushing this out by the end of February, as the dHub CLI and the dWeb SDK are unveiled.
You can follow dBrowser updates via the official dBrowser GitHub:
=====
VIII. dWeb Core Library Updates
=====
Considering we have so many new dWeb building blocks rolling out, you know we had to push some new updates for dDrive and dDatabase and that`s exactly what we`re doing. All 80+ dWeb libraries for off-chain-based interactions, will all get new updates in the next two weeks.
To follow these updates, head on over to the official dWeb GitHub:
https://github.com/distributedweb
=====
IX. dWeb Docs
=====
We are in the process of launching a dWeb developer guide, to simplify dWeb-based development for newcomers. Many of you already know that we have been hard at work on dWeb`s official documentation and we`re still pushing out many sections for dWeb`s major updates, so please hang in there with us. For now, we have pushed out many new sections, although we are lacking several, like Authentication and others (we know). Those sections will definitely be launched by next week. In the meantime, head on over the docs site and check out what we have published thus far:
====
X. Launch Of ARISEN`s UAL and PeepsID
====
ARISEN`s Universal Authentication Layer and PeepsID for Desktop and Mobile devices (iOS, Android and PeerOS) will be launching in the next 3 weeks. We are already preparing all libraries for public consumption and testing things as we speak. PeepsID will allow just about anyone to login to our upcoming applications like dSocial and others, without having to worry about private keys or any that crazy cryptography stuff! In other words, signing into Peeps applications, thanks to PeepsID, will feel like they`re signing into Facebook. Pretty sweet huh?
I will be posting a link to PeepsID libraries in the next few days, once we have launched some of the initial libraries publicly.
=====
XI. Integration with Unstoppable Domains
=====
We`re going to integrate the upcoming dBrowser release with Unstoppable Domains, which already work with dWeb network addresses. In fact, you can go ahead and purchase domains at Unstoppable Domains, point it to your dWeb network address and in a few short weeks, dBrowser will be able to resolve your domain right to your dWeb network address. We`re still working on dNames but it`s quite the platform and will take around another month to finalize. In the meantime, dWeb developers deserve a domain system that works as of today and Unstoppable Domains is great!
=====
XII. dNames Development
=====
In my last update, I spoke on new updates to the dNames app. If you missed that update, we recently rolled out dNames ALPHA but are currently working on dNames BETA, which is completely decentralized. It will take another month or so to push out dNames BETA, which will allow domain owners to manage dDNS records and register domains beyond the character limit. It will also allow anyone to create/sell their own dTLDs via the dNames Marketplace (like .dcom).
Stay tuned, in the meantime, check out the centralized version of ALPHA:
=====
XIII. Drum roll……. YES!!!!!!…….PeerOS
=====
We have a new team working on the first release of PeerOS, which should be rolling out in a few weeks tops. We`re also working on tools so that anyone can make the switch from Android, import their contacts, move over their apps, and transfer other data. The first initial release of PeerOS will include the following applications:
- Phone
- Messages (SMS)
- Contacts
- Camera
- Media (Photos/Videos)
- dBrowser
- dWallet
- PeepsID
- Telegram
- ProtonMail
and several others.
In the coming days, I`ll be posting an update on the PeerOS dApp Store.
=======
THE STATE OF THE DWEB
=======
I know people are dying for dWeb-based applications but it`s important that we don`t put the cart before the horse. We must build a foundation that we can develop truly decentralized applications upon, for everyday people, before we can ever develop the applications themselves. That has been our goal since the beginning and it`s still our goal today. I know much of this isn`t “sexy” but it`s so important to what we`re trying to accomplish when it comes to restoring freedom on the Internet. Sure, we`re utilizing open-source software from all over the place, but we`re also rebuilding it and making it easier to use for the common man. Making sure the dWeb foundation is easy for anyone to develop upon and use, will ensure that the applications developed on top of these building blocks are even easier to use. That`s important.
We don`t just need alternatives, we need alternatives that work, and we need alternatives that people WANT to use. I feel like many people out there are rushing together solutions, just to be the first in line and I`m afraid that they will soon find out that these sorts of alternatives will be short-lived or will never succeed in gaining mass adoption in the first place. An application`s level of decentralization is crucial to its ability to survive a culture that is surrounded with mass censorship. Not to mention, a powerful and simple user experience, will allow it to succeed in growing its user base with those who are not technically savvy. That`s incredibly hard when it comes to decentralized software. So, in a way, one cancels out the other. The major challenge here, is ensuring that an application is fully decentralized, while also being simple to use — and that`s exactly what we`ve been hard at work on for the past 12 months.
I`m enormously proud of the work we`ve done and continue to do, but this is just the beginning. The updates above allow for us to FINALLY begin development of platforms that will change the way conservatives use the Internet. Really, it will change how everyone uses the Internet if those on the left finally see the light and choose our platforms over others. I`m speaking on social networks like dSocial, video networks like dVideo, as well as payment processors like dPay. Ecosystems that are not dependent on a single soul or a single entity, and ones that can be used by people like my mom, without a single barrier. From a computer science perspective, to be able to build applications like these, is an incredible achievement and a mountain we`ve been climbing for a while. In other words, the state of the dWeb has never been stronger than it is today and we`re nearing a point where you can build just about anything on top of it, ensure that it`s fully decentralized and useable by anyone with a computer — and that`s saying something.
Thanks to all who have been along for this ride.
- Jared Rice Sr
