cool

Thu Aug 27 2026 19:19:24 EDT from IGnatius T Foobar Subject: Re: Recovering form Citadel DB crash

<osborne> By the way, the new UI is just days away from feature complete, and I can't wait to show it to you! </osborne>

Noting that the git page seem to have gone away. I was looking at it.

I do think that the new interface is a step up.

Some time ago, I made a node.js class for talking to the main server. I called it node-citadel and told this site about it. (I don't know if the people have changed.)

Anyway, I started working on it again. This time to make it more useful.  And, this time, I will put it up on npm and possibly others.  

I have a lot of modules for a fairly distributed type of group publishing. I have a lot to do to finish. I have had nice working versions  Recently, someone broke into my house and stole my cheap server where a localized version of all that was running. So, I decide to do a minimal node that could stair step out to a bigger concern if the manager of the concern so desires. Perhaps, there is a need to greatly expand documentation on architecture, etc. 

To keep it short, I will point to github repos, I will be glad to point to the site examples in about a week. And, I hope the citadel code will help speed it up. 

I started a web interface for mail to fit within what I call a human page. So, I have been making one:

https://github.com/copious-world/copious-mail

I am using a local web server such as serve-htttp to show the page in test/index.html. You can use npm run web

(The page uses a mushroom menu that slides out, and the plan is that page should sit in a iframe on a page that can navigate between views by controlling the iframe source. Each iframe source might be like a room (maybe?).  

The human page idea is that the frame resident apps are not required to be from a single provider and are chosen by the user - the human page owner. Yet, each frame resident can be a front end to a service chosen by the user. 

So, if a concern provides a blog list viewer, the human could pick to see citadel server blog posts in it.

For a larger system, I have tested versions of my stack that handle upload tracking, publication and removal via back-end that sends messages out to searchers, view counters, streamers, etc, where the messages are views of meta data descriptors. l first tested it with IPFS, but then I decided that a repository bridge would allow users to select the distributed storage for their media assets. The larger system definitely requires an increase in resources from a small node. But, does not necessarily require anything huge like a server farm. And, I am hoping to make this whole thing distributed, federated, and consensus friendly. Cycling through the stuff is a bit much,,, to be real about.)

The code for node-citadel is here https://github.com/copious-world/node-citadel

I have been making changes very quickly over the last few weeks.

I an very interested in distributed/federated networks. My Intergalactic ID is supposed to be a distributed (decentralized) identity. For this I have to go back to the W3 standards,  because I made an ID before they released their spec,

I already have tested login mechanisms, etc. with it.  I am interested in a wider idea of session, and perhaps there is something like a blockchain (or network consensus) approach that can be implemented.

What I call the "human page" is part of this. The page is supposed to be delivered from a URL unique to the human who creates an identity (currently at of-this.world -- also needs some work because I did not setup sys control for it yet.)

The unique URL allows sand-boxing private information in the local indexedDB. I had it set up for uploading and downloading local db data to a USB (say). The human page negotiated permissions by allowing concerns to sit in an iframe. The resident app in the frame basically logs into the user (the human page frame container), establishes a session and then asks permission of the human page for everything through a fixed set of messages,

You can send an email to rleddy@copious.world