Research SaintMaker V2 Architecture

Krysztof

We currently have a fairly solid, distributed architecture. However, I'd like to research an even more distributed architecture so that we can get away from netlify. Ideally the V2 infrastructure is fully P2P with the ability for the application to be passed over an email/text message/etc; it could be hosted or it can stay offline.

Acceptance Criteria

a document/chart outlining the current V1 architecture and its problems
a document/chart outlining the possible V2 architecture and how it addresses those problems

TechpriestBaunach

@Krysztof I have been testing out Radicle, which looks like it would be a strong contender for distribution, and would allow for updates and changes to be tracked (it is essentially p2p Github). Though obviously being able to send the entire core of the program p2p over an email attachment or something similar would be the most ideal.

I know we've talked about Atacama privately before, and how the person behind it is dedicated to keeping it down to 8mb. Would be nice if we had a goal like that for how big the core application should be.

TechpriestBaunach

Haven't looked into it fully yet, but this might be useful: https://slingcode.net/

TechpriestBaunach

[unknown] After a little more investigation, while it looks incredibly interesting as a pattern to follow (it's all html+css+javascript, so it can be run locally on anything that has a browser), the project has been abandoned for 4 years.

I do think it's worthy of exploration as an exemplar, no real dependencies outside what the web already requires, easy to share, can be hosted as a static site that people can grab and it works completely offline after that.

That said, I don't think it would be a copy paste sort of thing. It uses a bunch of stuff that's probably not needed. If we follow the pattern but keep everything as close to vanilla html+css+javascript, we could make something that should work on any device or operating system.