A network of digital cooperative networks requires a web operating system that focused on creating trust between people within networks and between the networks themselves.

The least important bits of this operating system will be the code. The most important bits will be the norms that allow consent-forward mutually beneficial agreements within the cooperatives and the network.


If you're interested in exploring what a collectively owned web-based operating system designed to cultivate networks of mutual aid and mutual benefit
@anaulin and I will be doing an ensemble coding session tomorrow as we work on some of the (blockchain free!) financial infrastructure tomorrow from 6pm to 8pm PT at twitch.tv/zeespencer

OK! We're live! twitch.tv/zeespencer

Feel free to drop in, chat at us, and ask questions. We'll be mostly reviewing + merging PRs, then moving on to tuning the PaymentForm feature.

So far, we've merged in some upgrades to some JavaScript packages; and now we're moving into cleaning up and hardening our TextBlock feature; which is a way to place static written content onto a given page.

The underlying premise is that each "Space" in a Convene deploment (AKA "Neighborhood") serves as an independent website, similar to a Wordpress site.

But instead of sites being _content_ first; they're _component_ first. With the owners of the Space arranging and configuring Components (AKA "Furniture") to represent their distinct needs from ther web presence.

So, instead of developers of Internet-forward applications needing to host it's own server(s); shifting costs for App hosting and maintenance away from the _producers_ of the App onto the _distributors_ and _consumers_ of the "App."

(This may seem similar to Dapps, except instead of running on a shared Raspberry Pi; they're running on normal-boring-infrastructure).

Convene provides the "OS" level stuff; like:

- Authentication (knowing who is acting in the Space)
- Authorization (knowing what permissions someone has within the Space)
- Data Input, Persistence, and Output
- Data Security when interacting with other computer(s) or Services.

We're still roughing out the design of how it all works (coding ~2 hrs a week doesn't move things forward very quickly!)

OK! Todays session was hella productive! We:

- Learned more about how Tailwind works in regards to providing affordances for well-styled textual content (i.e. the @tailwindcss/typography package)
- Made our TextBlock Furniture use afore-mentioned well-styled typography
- Removed a gradient that was hiding list items
- Made an explicit dependnecy implicit, and made it possible to create arbitrary Items; paving the way for a simpler StructuredData Persistence API .

I really have no idea what I'm doing when it comes to operating system design; so of course I'm building a Multi-User, Web-Forward Operating System; where the User-land runtime is shared between the Browser and the Server.

But it's good to have @anaulin involved so we can bounce things off each other!

@Zee @anaulin This was very interesting to watch! I'm usually a python dev, so watching rails experts work was enlightening.

@elplatt @anaulin “experts” is a bit of a stretch, but thank you!

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!