Tinyssb dev in chrome

[tschudin]

the JS+HTML code with a virtual backend for Chrome tabs, as presented in the Dec 22, 2024 meeting

[mixmix]

This is great!

This PR has a few things it's merging

1. Terminology
2. docs about the current Android app design
3. Chrome-tabs app

I think (3) could be a stand-along module. I'd like to try splitting out so I can play, understand, and then hone it so that others can also build with it. It seems to include files that are not used at all (yet), so would like to prune some of those too.

I'll loop back when I've done some testing

[mixmix]

aha, this branched off of #4
So 1 + 2 are not relevant at all!

I'd like to show you how to make a PR which proposes merging into another branch sometime. Makes the diff clearer?

[tschudin]

aha, this branched off of #4 So 1 + 2 are not relevant at all!

I'd like to show you how to make a PR which proposes merging into another branch sometime. Makes the diff clearer?

As I understand, this is the result of two things:
a) time

• first the slides from 20241222 were put into a PR just to get that TODO done, into the doc directory
• later, the dev-in-chrome branch came along where it made sense to include these slides so the directory is self-contained with all the required docs

b) file policy / where do things belong

• Per "mini project" like the chrome-tabs-app, or one central "doc" directory? So far I opted for having-everything-there-where-it's-needed (virtual backend slide in the dev-4-chrome directory).