Notices tagged with jami

@onymous have you tried #Jami, a P2P app for text/ voice/ video chat? It's more like social networking than social media.

@hambibleibt the biggest problem with #Tox from a #UX POV is the fragmentation across OS platforms. Apps for some OS have group chat, while others don't. Anyone could develop an app compatible with the protocol set #Jami uses, but the dev team has an app for each major OS, and features roll out across all of them at the same time. Jami also seems to progress steadily, while Tox dev seems to have been in hibernation for some time.

I've been testing #Jami again after a number of software updates. Text chat performance has improved markedly. It's delivering each message quickly, and in order. Users can now send both voice messages and video messages, which is great for doing voice/ video chat on patchy network connection. Now I'm excited for the group text chat feature to ship!

Have you looked at #BigBlueButton and the #Greenlight front end? If you don't want the hassle of running a server, #Jami is pretty good for voice calls, probably video too. Ironically their text chat is the bit that needs work.
@leah @sqozz

@rek2 you left out #Jami, which has a much more consistent #UX across platforms than #Tox (eg none of the Tox mobile apps I've tried support group chat). You also left out #BigBlueButton, which I keep hearing is much less of a resource hog on the server-side than #JitsiMeet, and I can confirm JM is a massive resource hog on the client-side. I haven't used #Discord but I've heard #Riot (#Matrix client) is a pretty good substitute?

#ShowerThoughts I wonder if Scuttlebutt could use a #blockchain to map its gibberish user IDs ("public keys") to human-readable usersnames, like #Jami does?
https://jami.net/why-is-jami-truly-distributed/

@mark certainly can be done. After all the #Session folks forked the #Signal apps and rebuilt them to run on the #Loki #blockchain. I'd love to see someone do the same using #Matrix instead of Loki. Not sure how they'd do the voice/video chat, maybe using #Jami protocols? Session doesn't have realtime voice/video anyway.

This post on the #Jami blog highlights some of the ways users have to manage #P2P apps differently from those that depend on servers:
https://jami.net/the-jami-quirks/

Help the #Jami team choose the new default #ringtone for their #P2P chat app:
https://framaforms.org/help-us-choose-jamis-default-ringtone-1565722509

@ajeremias My understanding is that Hubzilla is more like a federated CMS (eg Wordpress or Drupal) than a social media tool. SSB, unlike the fediverse apps, is totally distributed (P2P). Like #Briar or #Jami.
@liaizon

@clacke I've suggested before that delta.chat could implement the P2P voice chat protocol developed by #Jami, which would increase the #NetworkEffect of both apps. It seems to work pretty well despite requiring no servers.
https://write.as/c7fda5x13qzve.md

@badrihippo

@hexmasteen can such nodes be run on servers that are not themselves used as chat clients? Does Session handle delayed delivery to a user who is offline when a message is sent to them, and remains offline when the sender goes offline? This is something #Jami can't do yet.

@hexmasteen
> I just posted an overview.

Link please?

> one I'm not very familiar with and generally skeptical towards.

For good reason ;) Perhaps Session offers something not possible with non-blockchain chat P2P like #Jami and #Tox apps, or the many existing #blockchain-based social media projects:
https://git.feneas.org/feneas/fediverse/-/wikis/blockchain-social-apps

But the burden of proof is definitely on them.

@clacke I've suggested before that delta.chat could implement the P2P voice chat protocol developed by #Jami, which would increase the #NetworkEffect of both apps. It seems to work pretty well despite requiring no servers.
https://write.as/c7fda5x13qzve.md@badrihippo@fosstodon.org

I'm also pretty sceptical of the decision to make #Signal the default SMS app. I'm aware that of the #FreeCode chat apps that support both text and voice/ video, all are either walled gardens (eg Signal, #Wire, #Keybase) or painfully bleeding edge (eg #Riot, #Jami, #Tox, #Delta.chat). But I've discussed the reasons for my mistrust of the Signal and the cult-of-personality around it's founder at length.

@Blort
* #Jami: not ready for primetime yet. No group text chat, no message sync between clients (which client happens to receive the message keeps it), message delivery is horribly unreliable. Voice chat/ conference is pretty good, especially for a P2P app, but be aware the user who initiates the conference is hosting it, so pick the user with the most powerful computer and largest bandwidth. Will be great one day.