Notices tagged with jami
-
lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Friday, 18-Nov-2022 17:56:15 EST 
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 (lnxw48a1@nu.federati.net)'s status on Tuesday, 24-May-2022 08:47:02 EDT
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 (lnxw48a1@nu.federati.net)'s status on Sunday, 22-Aug-2021 14:09:44 EDT
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 (lnxw48a1@nu.federati.net)'s status on Thursday, 28-Jan-2021 13:13:51 EST
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 (lnxw48a1@nu.federati.net)'s status on Friday, 06-Nov-2020 13:42:32 EST
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 (lnxw48a1@nu.federati.net)'s status on Monday, 19-Oct-2020 14:19:27 EDT
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 (lnxw48a1@nu.federati.net)'s status on Sunday, 04-Oct-2020 20:33:27 EDT
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 (lnxw48a1@nu.federati.net)'s status on Saturday, 26-Sep-2020 22:33:03 EDT
lnxw48a1
Related: https://jami.net/why-is-jami-truly-distributed — an explanation of some of #Jami’s network architecture. -
lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Saturday, 26-Sep-2020 22:28:33 EDT
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. -
Strypey (strypey@mastodon.nzoss.nz)'s status on Friday, 03-Apr-2020 08:13:13 EDT 
Strypey
@onymous have you tried #Jami, a P2P app for text/ voice/ video chat? It's more like social networking than social media.
-
Strypey (strypey@mastodon.nzoss.nz)'s status on Friday, 03-Apr-2020 08:03:38 EDT
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 (strypey@mastodon.nzoss.nz)'s status on Wednesday, 01-Apr-2020 23:53:47 EDT
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?
-
lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Monday, 23-Mar-2020 14:23:53 EDT
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. -
Joseph Nuthalapati :fbx: (njoseph@social.masto.host)'s status on Sunday, 22-Mar-2020 23:53:13 EDT 
Joseph Nuthalapati :fbx:
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.
-
Strypey (strypey@mastodon.nzoss.nz)'s status on Thursday, 27-Feb-2020 23:00:37 EST
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 (strypey@mastodon.nzoss.nz)'s status on Sunday, 16-Feb-2020 15:42:54 EST
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.
-
lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Saturday, 15-Feb-2020 12:47:40 EST
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. -
Nobody (Linux Walt ALT) (lnxw37d2@nulled.red)'s status on Wednesday, 20-Nov-2019 15:07:42 EST 
Nobody (Linux Walt ALT)
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 (strypey@mastodon.nzoss.nz)'s status on Thursday, 14-Nov-2019 09:42:15 EST
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 (strypey@mastodon.nzoss.nz)'s status on Sunday, 28-Jul-2019 04:46:18 EDT
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.
All Jonkman Microblog content and data are available under the