I would like to look at the way that ‘files’ are created, stored, and made available in Cosmos via the capture, archiving, and publishing of audio, video, and text.
Issues of permissions, security, passwords, backups & disaster recovery, performance, and accessibility should all be considered and factor into a differential study of the actual set-up we currently have and a desired one to be grown into.
What is the optimal data architecture for our consciousness evolution…and human sanity?
Questions of personal use and style…how can we provide mutual support to use personal tech in healthier, better ways? How can Cosmos help with this in its own data architecture, workflows, and praxis templates?
Consider ethical design. Consider the value of open source vs. proprietary systems which may be more advanced (e.g., NextCloud (or similar) vs. Google Drive (or…)).
How can we make the data layer of Cosmos better organized, easier to use, safer and more secure, and more accessible to members?
Who needs tech support? Can we proactively help people start using the tools and systems provided by Cosmos?
What’s feasible, and what’s ideal? What needs time and what needs action? How can we productively relate with other emergent networks providing data services (e.g., Holochain) or apps?
The group should study the issues from all relevant perspectives, and no perspective—i.e., aperspectivally—and compile its finding and recommendations for council. The question then will be, what becomes action? For that, we may need to return to this study: How Do We Decide? The Ontology of Self-Governance [CCafe 7/24].
But this study would allow us to develop awareness of concrete technology issues within Cosmos, and begin see our options more clearly, as well as to share knowledge, skills, and seed-ideas for future developments. I would expect our next steps to become self-evident through the process of studying the problem.