This post on the blog highlights some of the ways users have to manage apps differently from those that depend on servers:

@strypey great necessary article that is relevant to many decentralised technologies. Very important to spell it out like this for users. I really appreciate the solutions that the Jami devs come up with, and how easy they make for users to use them. For example, I love their solution for decentralised group video talk: one user becomes the server, which can be decided by the group beforehand considering their bandwidth and computing power, I guess.

> one user becomes the server

This wasn't made clear by the UI when the group tested Jami. It would be better if the subnetwork formed by a group chat could dynamically assign the server role to the most powerful node (factoring in both computing power and available bandwidth). That would allow the person who started the group chat to leave without everyone else having to start a new one from scratch, to keep talking.

@strypey it’s an interesting idea. I wonder how it handles that at the moment. I learned about it in this post I think:

@stragu there's been a number of major updates to Jami since we ran our test, including making their update repo more accessible to @trisquel users:

I'm keen to run another test of Jami voice chat to see if the UX has improved, ideally with a few more people (5 or more), to see how well it scales. Anyone keen? We currently coordinate using:

@strypey I’d be happy to help, depending on availability! See you on Matrix.

Sign in to participate in the conversation
Mastodon - NZOSS

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