arso-project / archipel Goto Github PK

support the possibility to upload directory trees into archives. Using

• either html5
• or by going directly through the backend.

Implement the possibility to access the content of shared/public archives via https

todo before: #6
url could be generated from state tree

archives should be mountable to archive.mounts = []

First step maybe csv. ...

todo before: #6 & #7

the active element of the ui should be monitored by the state.
which state variables would fit well for this purpose?

write tests for the different parts

in packages/common/util/authMessage.js

Probably use this implementation https://github.com/mafintosh/protocol-buffers-schema
In the End one should get an base64 only message

active job's (e.g. import of archives, files, videos) should be re-accessible, after leaving the respective dialogue. job's should have a status and should be resume after restarting the app.
where should the job list kept? workspace maybe.

After finding that CoboxCloud ¹ , not built on dat://, but on hyper://, have a working pre-release available now, it can be interesting to think about reusing their foundational infrastructure, since this repository does not appear to be maintained anymore, and focus on realising pleasant UIs for distributed, local-first repositories

Else I'm happy to see that archipel appears to continue in sonar, and would like to see how this aids self-organised communities. Am I right in concluding that it is the successor application, and rebuilds the same functionality as intended before during the Prototype Fund?

¹ https://wiki.fablabchemnitz.de/display/AFUS/CoBox++-+Building+blocks+for+a+co-operative+cloud

Das 'X' soll weg, alternative Idee: Wie bei Atom ein sich einblendener Button bei hover über rechte Kanteder Tableiste.