Updates tagged with jami on Jonkman Microblog!
lnxw48a1: In theory, I agree, but in practice, I have used #Ring, the earlier version of #Jami. The experience was so poor that I can no longer get my in-person contacts to try anything that is not #Facebook / #Instagram / #Zoom. And that's without ever trying the #videochat functionality ... we only used text chats and it was still a really poor experience. I've heard it got better, but of course, none of my in-person contacts will try it again. This also affects apps like #Briar and #Session.
lnxw48a1's status on Friday, 18-Nov-2022 17:56:15 EST
In theory, I agree, but in practice, I have used #Ring, the earlier version of #Jami. The experience was so poor that I can no longer get my in-person contacts to try anything that is not #Facebook / #Instagram / #Zoom. And that's without ever trying the #videochat functionality ... we only used text chats and it was still a really poor experience. I've heard it got better, but of course, none of my in-person contacts will try it again. This also affects apps like #Briar and #Session.
lnxw48a1: @lxo Unless the people using #Jami are pretty advanced, they won’t like it. Having to be online at the same time, difficulties trying to use the same ID on multiple devices, those are things that most people will not tolerate. Maybe they have fixed some issues since I last tried to use it, but it was unpleasant to use during and shortly after the GNU #Ring days.
lnxw48a1's status on Tuesday, 24-May-2022 08:47:02 EDT
@lxo Unless the people using #Jami are pretty advanced, they won’t like it. Having to be online at the same time, difficulties trying to use the same ID on multiple devices, those are things that most people will not tolerate. Maybe they have fixed some issues since I last tried to use it, but it was unpleasant to use during and shortly after the GNU #Ring days.
lnxw48a1: @geniusmusing @lxo This is important. #GNU #Jami used to only send when both parties were online simultaneously. If the parties in the conversation are in different timezones, that may not happen often. Users reasonably want end-to-end encryption (E2EE), but still want some basic usability. (The experience back in the GNU #Ring days was pretty bad. Even today, none of my contacts will reconsider it.)
lnxw48a1's status on Sunday, 22-Aug-2021 14:09:44 EDT
@geniusmusing @lxo This is important. #GNU #Jami used to only send when both parties were online simultaneously. If the parties in the conversation are in different timezones, that may not happen often. Users reasonably want end-to-end encryption (E2EE), but still want some basic usability. (The experience back in the GNU #Ring days was pretty bad. Even today, none of my contacts will reconsider it.)
lnxw48a1: Likewise, I’ve pretty much abandoned #Jami (or #Ring, if you used it previously) because all my contacts dumped it years back when an update forced everyone to re-add their contacts.
lnxw48a1's status on Thursday, 28-Jan-2021 13:13:51 EST
Likewise, I’ve pretty much abandoned #Jami (or #Ring, if you used it previously) because all my contacts dumped it years back when an update forced everyone to re-add their contacts.
lnxw48a1: So ... about GNU #Jami ... when I tried it, there were lots of annoyances that made it not ready for prime time. Has anyone looked at it recently?
lnxw48a1's status on Friday, 06-Nov-2020 13:42:32 EST
So ... about GNU #Jami ... when I tried it, there were lots of annoyances that made it not ready for prime time. Has anyone looked at it recently?
lnxw48a1: In any case, the pub outage tells me that #SSB, in its current design, is unsuitable for connecting regular people together. Maybe I'll look at #Jami again to see whether it's made progress toward fixing its issues. Or #Tox, or #Briar.
lnxw48a1's status on Monday, 19-Oct-2020 14:19:27 EDT
In any case, the pub outage tells me that #SSB, in its current design, is unsuitable for connecting regular people together. Maybe I'll look at #Jami again to see whether it's made progress toward fixing its issues. Or #Tox, or #Briar.
lnxw48a1: Okay look. *I* don't use #Signal ( and same for #Telegram ), because I don't want to give my telephone number to anyone except family and close friends. I have enough personal contacts that do use them so that they'd be personally useful if I didn't have that unbreakable obstacle. But I don't object to others choosing such end-to-end encrypted messengers over messaging apps such as (for example) #Facebook_Messenger. I personally use #Wire, #XMPP, #Matrix, and #WickrMe. (I tried #Jami, but it wasn't very usable yet; none of my contacts were willing to try #Tox or #Briar.) I've even considered getting a Google account again so I can use whatever their latest incarnation of messaging is (just because almost everyone I know has a Google account). It does bother me that Signal and Telegram and most other messaging services are centralized and non-federated. It seems we haven't learned from the 1990s & early 2000s when some friends had AOL Instant Messenger (AIM), some had MSN Messenger, some had Yahoo Messenger, some had ICQ, and a few had various other walled garden messengers (such as Excite's messenger). If I wanted to talk with all my friends, I needed to have accounts on every possible service. I should be able to communicate with my friends from whatever service I choose to use to whatever services they choose to use and not have to create accounts on every possible service. But that's a matter of educating our friends and family, not of dogmatically refusing to communicate with them on any service they might use.
lnxw48a1's status on Sunday, 04-Oct-2020 20:33:27 EDT
Okay look. *I* don't use #Signal ( and same for #Telegram ), because I don't want to give my telephone number to anyone except family and close friends. I have enough personal contacts that do use them so that they'd be personally useful if I didn't have that unbreakable obstacle. But I don't object to others choosing such end-to-end encrypted messengers over messaging apps such as (for example) #Facebook_Messenger. I personally use #Wire, #XMPP, #Matrix, and #WickrMe. (I tried #Jami, but it wasn't very usable yet; none of my contacts were willing to try #Tox or #Briar.) I've even considered getting a Google account again so I can use whatever their latest incarnation of messaging is (just because almost everyone I know has a Google account). It does bother me that Signal and Telegram and most other messaging services are centralized and non-federated. It seems we haven't learned from the 1990s & early 2000s when some friends had AOL Instant Messenger (AIM), some had MSN Messenger, some had Yahoo Messenger, some had ICQ, and a few had various other walled garden messengers (such as Excite's messenger). If I wanted to talk with all my friends, I needed to have accounts on every possible service. I should be able to communicate with my friends from whatever service I choose to use to whatever services they choose to use and not have to create accounts on every possible service. But that's a matter of educating our friends and family, not of dogmatically refusing to communicate with them on any service they might use.
lnxw48a1: Related: https://jami.net/why-is-jami-truly-distributed — an explanation of some of #Jami’s network architecture.
lnxw48a1's status on Saturday, 26-Sep-2020 22:33:03 EDT
Related: https://jami.net/why-is-jami-truly-distributed — an explanation of some of #Jami’s network architecture.
lnxw48a1: Wondering if #Jami is usable yet? I tried it a few years ago, and it wasn’t. Plus, it updated and forced me to reconnect to my contacts ... all of whom abandoned it when that happened.
lnxw48a1's status on Saturday, 26-Sep-2020 22:28:33 EDT
Wondering if #Jami is usable yet? I tried it a few years ago, and it wasn’t. Plus, it updated and forced me to reconnect to my contacts ... all of whom abandoned it when that happened.
strypey: @onymous have you tried #Jami, a P2P app for text/ voice/ video chat? It's more like social networking than social media.
strypey's status on Friday, 03-Apr-2020 08:13:13 EDT
@onymous have you tried #Jami, a P2P app for text/ voice/ video chat? It's more like social networking than social media.
strypey: @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.
strypey's status on Friday, 03-Apr-2020 08:03:38 EDT
@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.
strypey: @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?
strypey's status on Wednesday, 01-Apr-2020 23:53:47 EDT
@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?
lnxw48a1: Experience with #Jami's ancestor #Ring tells me that it needs a fairly technical user who is willing to tolerate some annoying deficiencies. My contacts have all dropped it, including one son who is a network engineer. Be careful about promoting it to people who are not willing to endure those things, or we can chase people away from all non-Facebook communications software.
lnxw48a1's status on Monday, 23-Mar-2020 14:23:53 EDT
Experience with #Jami's ancestor #Ring tells me that it needs a fairly technical user who is willing to tolerate some annoying deficiencies. My contacts have all dropped it, including one son who is a network engineer. Be careful about promoting it to people who are not willing to endure those things, or we can chase people away from all non-Facebook communications software.
njoseph: Jitsi is getting a lot of mentions here.I wonder if people are aware of GNU Jami, a P2P solution. https://jami.net/Jami has end-to-end encryption while Jitsi is only encrypted during transit. The Jitsi server has your packets available in unencrypted form. If you can't trust a Jitsi server and need end-to-end encryption, Jami can be a good alternative.#Jitsi #Jami #e2ee
njoseph's status on Sunday, 22-Mar-2020 23:53:13 EDT
Jitsi is getting a lot of mentions here. I wonder if people are aware of GNU Jami, a P2P solution. https://jami.net/ Jami has end-to-end encryption while Jitsi is only encrypted during transit. The Jitsi server has your packets available in unencrypted form. If you can't trust a Jitsi server and need end-to-end encryption, Jami can be a good alternative. #Jitsi #Jami #e2ee
strypey: 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/
strypey's status on Thursday, 27-Feb-2020 23:00:37 EST
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/
strypey: @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-appsBut the burden of proof is definitely on them.
strypey's status on Sunday, 16-Feb-2020 15:42:54 EST
@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.
lnxw48a1: @strypey So there's a lot to unpack in that document. The #Session onion routing protocol involves using a #blockchain called #Loki to make it difficult for an adversary to control a significant fraction of the nodes and prevent exposing the IP addresses (and therefore identities) of a user and his/her contacts to the same person or group. (As you noticed, Session is not yet using onion requests.) There's also swarms and attachments and message storage (including attachments), online vs offline messages, multiple device support, spam resistance, a modified version of #Signal's encryption protocol, group chats (3-500 member "closed" groups are end-to-end encrypted like the rest of Session; "open" groups are not, and require an account on a special group server [self-hostable]) Note that all this stuff happens under the covers. It seems that Session will handle most of it without the user ever seeing it. I'm going to query some family members and see whether any would be willing to try this as a secondary channel (for now #Wire is our primary channel). Just adding offline messages is a clear advantage over #Jami, but the lack of audio & video chats is going to limit its usefulness.
lnxw48a1's status on Saturday, 15-Feb-2020 12:47:40 EST
@strypey So there's a lot to unpack in that document. The #Session onion routing protocol involves using a #blockchain called #Loki to make it difficult for an adversary to control a significant fraction of the nodes and prevent exposing the IP addresses (and therefore identities) of a user and his/her contacts to the same person or group. (As you noticed, Session is not yet using onion requests.) There's also swarms and attachments and message storage (including attachments), online vs offline messages, multiple device support, spam resistance, a modified version of #Signal's encryption protocol, group chats (3-500 member "closed" groups are end-to-end encrypted like the rest of Session; "open" groups are not, and require an account on a special group server [self-hostable]) Note that all this stuff happens under the covers. It seems that Session will handle most of it without the user ever seeing it. I'm going to query some family members and see whether any would be willing to try this as a secondary channel (for now #Wire is our primary channel). Just adding offline messages is a clear advantage over #Jami, but the lack of audio & video chats is going to limit its usefulness.
lnxw37d2: @AvnSgt @oldvetcodes Thanks. This is a tough one. #Wire is the first and only privacy-centric tool that is in widespread use among my friends and family. Several of them tried #Ring (now #Jami) before that, but it was a bad experience all around and cries of "it got better" won't get anyone to try it.
lnxw37d2's status on Wednesday, 20-Nov-2019 15:07:42 EST
@AvnSgt @oldvetcodes Thanks. This is a tough one. #Wire is the first and only privacy-centric tool that is in widespread use among my friends and family. Several of them tried #Ring (now #Jami) before that, but it was a bad experience all around and cries of "it got better" won't get anyone to try it.
strypey: @mmin I think there is a variation of #ZookoTriangle here. Out-of-the-box, Riot is decentralized and user-friendly, but not encrypted. Turn on encryption, it's still decentralized, but not user-friendly. Same is true of #Jami, #Tox clients, and every other decentralized chat app I've tested that has encryption out-of-the-box, #UX hell. All the user-friendly systems I've seen that have encryption turned on out-of-the-box are centralized ones like Signal and Wire. @lnxw48a1
strypey's status on Thursday, 14-Nov-2019 09:42:15 EST
@mmin I think there is a variation of #ZookoTriangle here. Out-of-the-box, Riot is decentralized and user-friendly, but not encrypted. Turn on encryption, it's still decentralized, but not user-friendly. Same is true of #Jami, #Tox clients, and every other decentralized chat app I've tested that has encryption out-of-the-box, #UX hell. All the user-friendly systems I've seen that have encryption turned on out-of-the-box are centralized ones like Signal and Wire. @lnxw48a1
strypey: Here's the write-up for #VOICE testing session 2: https://write.as/c7fda5x13qzve.mdWe tested #Jami with three people and had a pretty good voice chat, although figuring out how to get group chat going took a bit of experimentation.
strypey's status on Sunday, 28-Jul-2019 04:46:18 EDT
Here's the write-up for #VOICE testing session 2: https://write.as/c7fda5x13qzve.md We tested #Jami with three people and had a pretty good voice chat, although figuring out how to get group chat going took a bit of experimentation.
strypey: 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!
strypey's status on Sunday, 14-Jul-2019 07:15:45 EDT
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!
lnxw48a1: @rw A few family members complain that I can’t see their calendar events, but the biggest annoyance I have with not being a #Facebook user is all the people that say “did you see what cousin so and so just said?” and then stick their phones in my face. If I wanted to see all that random garbage, I would still have an account. Yes, but how can we get in touch with you? Let me count the ways: * call * text * !XMPP * #Wire * #Ring / #Jami * e-mail * in person * contact any of my sons, nephews, siblings, my youngest niece, the cousin that lives in TX, or my mom and ask them to forward
lnxw48a1's status on Thursday, 11-Apr-2019 14:45:55 EDT
@rw A few family members complain that I can’t see their calendar events, but the biggest annoyance I have with not being a #Facebook user is all the people that say “did you see what cousin so and so just said?” and then stick their phones in my face. If I wanted to see all that random garbage, I would still have an account. Yes, but how can we get in touch with you? Let me count the ways: * call * text * !XMPP * #Wire * #Ring / #Jami * e-mail * in person * contact any of my sons, nephews, siblings, my youngest niece, the cousin that lives in TX, or my mom and ask them to forward
divert: @GatoOscuro @jobregon @juansantiago @arodha #Jami es el nuevo nombre del proyecto de #GNURing. Creo que merece que lo probemos más y sospecho que el número de usuarios mejora el servicio, recuerden que no hay servidor central, sino que es una red distribuida. Me pueden encontrar como Divert en Jami.
divert's status on Wednesday, 03-Apr-2019 11:31:34 EDT
@GatoOscuro @jobregon @juansantiago @arodha #Jami es el nuevo nombre del proyecto de #GNURing. Creo que merece que lo probemos más y sospecho que el número de usuarios mejora el servicio, recuerden que no hay servidor central, sino que es una red distribuida. Me pueden encontrar como Divert en Jami.
lnxw48a1: @bobjonkman I found our conversation about #Jami / #Ring. See https://nu.federati.net/conversation/2033439 CC: @davehunt, who was also trying it at that time.
lnxw48a1's status on Tuesday, 02-Apr-2019 17:33:14 EDT
@bobjonkman I found our conversation about #Jami / #Ring. See https://nu.federati.net/conversation/2033439 CC: @davehunt, who was also trying it at that time.
bobjonkman: That conversation would have been at least a year ago, and probably on #Wire -- my main laptop with all the comm clients on it has been relegated to to the basement to be a server (dead screen), and my currently laptop lacks the oomph to do things like #Ring / #Jami / #Wire
bobjonkman's status on Tuesday, 02-Apr-2019 17:02:57 EDT
That conversation would have been at least a year ago, and probably on #Wire -- my main laptop with all the comm clients on it has been relegated to to the basement to be a server (dead screen), and my currently laptop lacks the oomph to do things like #Ring / #Jami / #Wire
lnxw48a1: I think I had a brief text conversation on #Ring / #Jami with @bobjonkman a couple of months back, and that is the only one since November of 2017. . I think it is time to declare it dead and bury the carcass.
lnxw48a1's status on Tuesday, 02-Apr-2019 11:33:56 EDT
I think I had a brief text conversation on #Ring / #Jami with @bobjonkman a couple of months back, and that is the only one since November of 2017. . I think it is time to declare it dead and bury the carcass.
bobjonkman: Yup, I got an invite to add you to my #Jami addressbook (and did so). Sent you a reply -- I see a green dot on your avatar, which I think means you're online. But you're probably AFK, just like I was for most of the day.
bobjonkman's status on Sunday, 27-Jan-2019 19:32:15 EST
Yup, I got an invite to add you to my #Jami addressbook (and did so). Sent you a reply -- I see a green dot on your avatar, which I think means you're online. But you're probably AFK, just like I was for most of the day.
lnxw48a1: @davehunt @bobjonkman @mangeurdenuage I made the mistake of trying to get a group of family members to migrate to #Ring / #Jami about 18 months ago. At the time, there was no presence indicator, so it was "send message, hope the other party is there to receive it; oops, message is hung up trying to send, I guess they aren't online right now". Then came an update that meant needing to re-request connection with all my contacts, and that was it. A single contact confirmed connection, but I never again successfully sent or received a message*, and they all stopped using it. * I believe I successfully sent one message to BobJonkman a day or two ago, but he was away, so no answer was received.
lnxw48a1's status on Sunday, 27-Jan-2019 18:51:50 EST
@davehunt @bobjonkman @mangeurdenuage I made the mistake of trying to get a group of family members to migrate to #Ring / #Jami about 18 months ago. At the time, there was no presence indicator, so it was "send message, hope the other party is there to receive it; oops, message is hung up trying to send, I guess they aren't online right now". Then came an update that meant needing to re-request connection with all my contacts, and that was it. A single contact confirmed connection, but I never again successfully sent or received a message*, and they all stopped using it. * I believe I successfully sent one message to BobJonkman a day or two ago, but he was away, so no answer was received.
lnxw48a1: Logged into #Ring / #Jami to add @davehunt and @bobjonkman and see if it has improved since my contacts abandoned it after an update forced contact re-requests.
lnxw48a1's status on Saturday, 26-Jan-2019 19:46:21 EST
Logged into #Ring / #Jami to add @davehunt and @bobjonkman and see if it has improved since my contacts abandoned it after an update forced contact re-requests.
davehunt: @lnxw41a @bobjonkman I'm on #GNU #Jami now, and think I have it set to auto-answer calls.
davehunt's status on Saturday, 26-Jan-2019 11:26:11 EST
@lnxw41a @bobjonkman I'm on #GNU #Jami now, and think I have it set to auto-answer calls.
davehunt: Same here; I'll give it a bit more time, but it looks like it's not really ready for anyone. #jami
davehunt's status on Saturday, 26-Jan-2019 11:19:04 EST
Same here; I'll give it a bit more time, but it looks like it's not really ready for anyone. #jami
bobjonkman: With the inaccessible UI problems, the lack of store-and-forward messaging, and its lack of interoperability with other messaging protocols, I doubt I'll be using #Jami much longer. But it would be nice to have at least one exchange with someone! @davehunt
bobjonkman's status on Saturday, 26-Jan-2019 08:32:10 EST
With the inaccessible UI problems, the lack of store-and-forward messaging, and its lack of interoperability with other messaging protocols, I doubt I'll be using #Jami much longer. But it would be nice to have at least one exchange with someone! @davehunt
bobjonkman: I'm using #Mate as well, and it works for me, but I am visually dependent. #Jami offers no clues about keystroke shortcuts, and doesn't have the standard "File, Edit, Options, Help" style menu. It does not seem to have any navigation accessibility.
bobjonkman's status on Saturday, 26-Jan-2019 08:26:41 EST
I'm using #Mate as well, and it works for me, but I am visually dependent. #Jami offers no clues about keystroke shortcuts, and doesn't have the standard "File, Edit, Options, Help" style menu. It does not seem to have any navigation accessibility.
bobjonkman: My first thought about #Jami is "Oh no, not another #IncompatibleWithEverythingElse chat client. Seems lighter than #Wire, tho, so that's a thing in its favour.
bobjonkman's status on Friday, 25-Jan-2019 19:42:45 EST
My first thought about #Jami is "Oh no, not another #IncompatibleWithEverythingElse chat client. Seems lighter than #Wire, tho, so that's a thing in its favour.
amarok: #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 tasksAlso: 1, Finished the third page for Wabi. 2. Snow storm \o/ 3. I watched Brooklyn 99 (s04)
amarok's status on Sunday, 20-Jan-2019 14:24:08 EST
#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)
strypey: @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
strypey's status on Thursday, 10-Jan-2019 06:57:15 EST
@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
strypey: @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?
strypey's status on Monday, 07-Jan-2019 14:15:03 EST
@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?
mkwadee: #GNU #Jami (formerly #Ring) update: a few days ago, I got the #program to work over a #LAN and today I now know it works over a #WAN (home to work) both for #messaging and #video #calls. Good job and thanks to the developers.#VoIP #FreeSoftware
mkwadee's status on Monday, 07-Jan-2019 11:56:14 EST
#GNU #Jami (formerly #Ring) update: a few days ago, I got the #program to work over a #LAN and today I now know it works over a #WAN (home to work) both for #messaging and #video #calls. Good job and thanks to the developers. #VoIP #FreeSoftware
strypey: @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
strypey's status on Sunday, 06-Jan-2019 13:02:36 EST
@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
strypey: @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
strypey's status on Sunday, 06-Jan-2019 06:40:21 EST
@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
strypey: @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).
strypey's status on Sunday, 06-Jan-2019 05:29:50 EST
@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).
mkwadee: Finally got #GNU #Jami (used to be called #Ring) to work (i.e. communicate) with another computer. I need to experiment with it a bit more, I suppose.#FreeSoftware #VoIP
mkwadee's status on Friday, 04-Jan-2019 12:01:26 EST
Finally got #GNU #Jami (used to be called #Ring) to work (i.e. communicate) with another computer. I need to experiment with it a bit more, I suppose. #FreeSoftware #VoIP
strypey: @switchingsocial I know you've addressed this in your FAQ but I really want to challenge not listing #Wire on your list of messenger apps. It's much easier for non-technical people to understand and use than #Jami / #Ring (I've got my family using Wire with me). Also, unlike Signal, Wire can be used without supplying a phone number, and they have plans to implement server>server federation: https://github.com/wireapp/wire/issues/160#issuecomment-446551908
strypey's status on Friday, 28-Dec-2018 09:13:39 EST
@switchingsocial I know you've addressed this in your FAQ but I really want to challenge not listing #Wire on your list of messenger apps. It's much easier for non-technical people to understand and use than #Jami / #Ring (I've got my family using Wire with me). Also, unlike Signal, Wire can be used without supplying a phone number, and they have plans to implement server>server federation: https://github.com/wireapp/wire/issues/160#issuecomment-446551908
Alter TOS to allow for federation with other networks · Issue #160 · wireapp/wire