Notices tagged with jami, page 2

#weeklytoot
This week for #jami:
1. I merged my patches for the presence, should be improved with the next OpenDHT bump.
2. I also worked on implementing TCP in the lib we use to do the ICE negotiation. Needed for p2p file transfer + sync + lot of other things.
3. Do a lot of administrative tasks

Also:
1, Finished the third page for Wabi.
2. Snow storm \o/
3. I watched Brooklyn 99 (s04)

@noorul probably the main #UX different I've noticed between #Jami and other chat apps is that text messaging is not asynchronous. In other words, you can only text chat with other users when you are online and logged into Jami at the same time. My understanding is that asynchronous messaging is on the dev #roadmap, but won't be added any time soon.
@AmarOk

@AmarOk do you know what's happening with the #Ring #PPA with the name change to #Jami? Do I need to change to a new PPA? If so, do I need to uninstall, and reinstall?

@kawaiipunk I've been thinking about these for years, like #Serval, #GNU #Jami (formerly #Ring), #Tox, and others. But I struggle to find people to test them with, and when a "secure" chat app only has clients for iOS and Android, I struggle to take them seriously.
@bob @gentoorebel @noorul

@bikecurious AFAIK #GNU #Jami (formerly #Ring) is a serverless/ #P2P app, not a #SIP client. However, I do seem to have a knowledge gap when it comes to the relationship between SIP and #WebRTC. Any good links for filling that gap?
@gentoorebel @noorul @fdroidorg @finn @clacke

@greenjon if you want a similar service to Signal that isn't US-based, is planning to implement server>server federation, and is more friendly to the software freedom movement, I suggest trying #Wire. #GNU #Jami (formerly #Ring) is also worth a try, but much less user-friendly (at least last time I tried it).