I'm still playing around with svelte. There is a user session manager that is stateless on the server side. It works by having the server encrypt a token containing session information to the client which then returns it back as a cookie. Seemed kind of cool and I thought I might use it simply because it shows some working encryption using nodejs which should help me out when I get to the other pieces. It's here: https://github.com/pixelmund/svelte-kit-cookie-session I'm trying to get a clearer picture of the separation of client and server within the system. It seems that the main workflow is that for each page the browser loads some preferably static page with javascript and then uses a separate fetch to retrieve dynamic information. At first I thought that was not a great idea, because it involves two round trips, but it makes sense from a certain viewpoint. If you create a page with a nice "loading..." mode and fetch the data afterwards with javascript, it would seem faster to the user, because something gets displayed right away. I'm not planning on using captaindirgo.com for much, just an overview of the extension, how to download it, and a page to register and log-in (this will be a proof-of-concept, mainly, because I plan on integrating with other websites afterwards, using oauth or something like that) but it seemed like a logical place to start, because the extension will have to point to something.