One instance per browser tab. The client renders the UI, interacts with the user, and runs most of the logic — 90%+ of SilverBullet lives here. It reaches the Architecture/Service Worker (and, when online, the Server directly) through the HTTP API.
One instance per browser tab. The client renders the UI, interacts with the user, and runs most of the logic — 90%+ of SilverBullet lives here. It reaches the Architecture/Service Worker (and, when online, the Server directly) through the HTTP API.