No I'm not talking about the UI toolkit, I mean how do you start an application using a distributed database that runs in the browser? In the last post I mentioned relying on a host account, which can be queried in Gun via it's public key. One of my first additions to RSStream was a /host-public-key endpoint. I wanted to be able to start from just the static build files and have the startup process take care of itself, so the first thing the browser does on load is check if it has the host account's public key in local storage, otherwise it will fetch it.
 

if (!pub) {
  fetch(`${window.location.origin}/host-public-key`)
    .then(res => res.text())
    .then(key => setPub(key))
  return
}

setHost(gun.user(pub))
localStorage.setItem("pub", pub)

Once it has this, it knows how to find all the data associated with the account. The next step to a useful piece of software is user accounts. Since Gun is distributed, it's possible for anyone to create an account. This is because it's all done in the browser, there's no server required to verify your credentials. But this is not overly useful if users can't discover each other, or if you want some sort of control over the sign up process. RSStream deals with this by using invite codes. The sign up process requires a code, which is stored alongside your public key in the host account's data after your user account is created in Gun.

// The server logs into the host user account on start up:
const user = gun.user()
user.auth(alias, pass, auth)

app.post("/claim-invite-code", async (req, res) => {
  const data = {
    pub: req.body.pub,
    alias: req.body.alias,
    name: req.body.alias,
  }
  user.get("accounts").get(code).put(data)
})

So the invite code starts as a sign up requirement and becomes a reference to your account in the host's data. The sign up form allows you to choose a username and password like it's a normal process, but as you will see, the code you're given becomes the main reference point for your account. From here on, once an account has been created from an invite code I will refer to this value as the account code.

Hello and welcome! This blog will be documenting some new projects built around a distributed database called GunDB. The idea with these projects will be that they're local and offline first, and they keep a copy of everything they need to function in the browser. Gun ticks a lot of the boxes required to enable this type of functionality. There's other projects that offer similar features, but I'm going to skip the pros and cons of what else is available and jump into working with Gun.

The first project I've been working on is called RSStream. It's a feed reader that stores everything in Gun, but does the feed processing using SimplePie and Dobrado, which are other projects I've worked on. Those services run on the same server and push data to a Node app that has access to Gun.

Before looking at how to store data in Gun, there's a bit of a mindset change required when working with a distributed database. Your first question should be, if everything is distributed how can I protect my data? Gun solves this problem by providing user accounts that can encrypt, sign and verify data. This makes it possible to store data under an account that can only be written when the account owner is logged in.

RSStream uses this feature to create a host account on the server, which provides a central location for application data. Wow first post and we're already talking about centralising data in a distributed database? Well we actually want two things. Data should be distributed as widely as required, to support users. But control should also be available to the administrators of an application when running a hosted service.

With this in mind, creating a host account means we now have a reliable place to store data that can't be modified, even though that data is distributed to browsers and other servers. We've reached the first step to having a usable piece of software! Stayed tuned for more updates.