Notices tagged with jami

@stertorous
> It does lack video/voice chat though

True, and this is a major fail for a mobile chat app. If it could handle (optionally encrypted) #SMS like #Silence does, it could be the text chat app, with another tool provided for voice/video comms. Or, see my shower thoughts about adding #Jami protocols to delta.chat for voice/video calling:
https://mastodon.nzoss.nz/@strypey/102449805868311056
@gael

In fact, the ultimate comms #UX might be a native client that could speak #email, #XMPP, and #Jami protocols. It would accept messages from either #Jabber or email servers, and deliver them to either a chat UI or a long-form email, depending on message length (a sane default # of characters that users can change in settings). When XMPP presence protocols and/or Jami protocols told users contacts are online, they could make a voice/video call using Jami protocols.

The UI of the #Jami mobile app is pretty good, but it could use work on the desktop client. Here's a side-by-side comparison with the #Wire desktop client, on the default desktop of #Trisquel GNU/Linux. The differences are subtle, and hard to fully appreciate without seeing them in use, but something about the Wire UI just feels more ... polished. If I could even had the option to change the colours in Jami to a darker palette, that would help I think.

The UI of the #Jami mobile app is pretty good, but it could use work on the desktop client. Here's a side-by-side comparison with the #Wire desktop client. The differences are subtle, and hard to fully appreciate without seeing them in use, but something about the Wire UI just feels more ... polished. If I could even had the option to change the colours in Jami to a darker palette, that would help I think.

If #delta.chat (or a fork of it) added voice/ video chat using the #Jami protocols, allowing Jami accounts to be associated with email accounts, that might be the best of both worlds. A reliable, federated transport and storage for text messages, file attachments, and voice mails, and a fairly robust #P2P voice/ video chat experience (both one-to-one chat and group conference). Same if native #Jabber apps like #Conversations supported #Jami for voice/video chat.

#Jami does an amazing job of allowing two or more people to do #voice or video chat without any centralized servers involved. But I'm having a lot of trouble getting it to sync my contacts and text messages between apps on different devices, even when I have them open and running at the same time for quite a while. It's also too easy to lose your account if users remove the apps from all their devices without making a backup, and that doesn't seem to be possible with the #Android app.

Apparently #Jami is now packaged for #Debian, which meant that it made it into the #Ubuntu 19.04 repos, which means eventually it will be in the #Trisquel repos!

@teaneedz the team developing #Jami has existed for more than a decade. It used to be called #GNU #Ring and is still part of the GNU project. It originally started as a SIP client called #SLFphone. Given that the routing is serverless and relies on other clients, the design must aim for zero knowledge #E2EE. Auditing the implementation of the encryption, and whether it achieves that, is definitely above my paygrade ;)

@teaneedz I can tell you that the team developing #Jami has existed for more than a decade. It used to be called #GNU #Ring and is still part of the GNU project. It originally started as a SIP client called #SLFphone. Given that the routing is serverless and relies on other clients, the design must aim for zero knowledge #E2EE. Auditing the implementation of the encryption, and whether it achieves that, is definitely above my paygrade ;)

@teaneedz I think that would be essential to making the system socially and legally practical, yes. #Jami is an example. My understanding of the way it works is that by running a Jami client, I am contributing timeslice to the distributed computer that helps users connect with each other (and maybe even routes call data). But I can't see anyone else' communications over Jami and I'm not responsible for their contents or consequences (morally or legally).

@imacrea #Jabber with #OMEMO is production-ready AFAIK, but it relies on the servers and clients at both ends supporting OMEMO (it's an optional extra) and implementing it correctly. At this point I would probably use #Briar (if you're both on Android) or #Jami, no servers, less attack surface. If you need something noob-friendly, #Wire (I don't trust or use #Signal for various reasons but some people say it's noob-friendly and their #E2EE tech is widely used).
@bortzmeyer

#ShowerThought corporate #DataFarms that promote themselves as #SocialMedia are #P2P (Peer-to-Peer) from a user perspective, but not from a technical perspective. Users can connect and communicate directly, but not without the #DataFarm as an intermediary in the background. #BitTorrent is #P2P from a technical perspective, but not from a user perspective. There's never direct one-to-one contact between any two users). messaging apps like #Jami and #Briar are #P2P in both ways.

@dazinism so #Briar is quite different from #Jami, which AFAICT can only do realtime chat, no delayed delivery of messages. I'm curious now to try Briar and also Serval. I still don't have a new enough version of #Android to run #Manyverse (SSB client for mobile)
@k3b @tootbrute

I just installed the #Jami (formerly #Ring) app on my Android. I was able to 'export' my Jami account from the GNU/Linux app and I've now got both apps set to start when the system starts. My username, like here, is 'strypey'. If anyone who wants try it out, feel free to message or call me.

@AmarOk so as with torrents, you can be a "seeder" when you can use WiFi and plug in your device, and be a "leacher" when you're using the cell network and need to conserve charge? Is #Jami able to automate that, or does the user need to manually switch back and forth?
@k3b @tootbrute

@tootbrute
> wish more stuff had built in mesh server functionality...

I want to see a serverless app like #Jami with a UI like #Conversations (#XMPP app for #Android). That way, the #UX is as seamless as that of an app for a centralized service, but as with #BitTorrent, everyone who's running the app is also "running a server", in the sense of sharing bandwidth and processing power with the network.

@rysiek
> I am more interested in Briar

Speaking of full #P2P, have you looked at #Jami (formerly #Ring)? I've successfully made one-to-one voice calls on it, and I believe they're currently working on group calls. Not great for delayed delivery of text messages yet though.

@noorul I can't wait until I can say "use #Jami"! I have had one pretty good experience using it for a one-to-one voice call. But it's going to be a while before it has feature parity with chat apps like Signal or Wire. The ability to deliver text messages when one contact is offline is a pretty basic feature that is still missing.

#Jami (formerly #Ring and still a #GNU package) is a #P2P chat app, but up until recently the project has maintained a centralized service for associating human-readable usernames with the unique hash codes the app uses as addresses. That service uses #SmartConstracts on the #Ethereum #blockchain, and they've recently modified it to allow other operators to run nodes, so the name service can be distributed too. Great stuff!
https://jami.net/the-jami-blockchain-switches-from-proof-of-work-to-proof-of-authority/