📣Jami team is pleased to introduce the new version of Jami: Εἰρήνη.☮️
As you'll discover, this release brings remarkable advances from months of silent work, sure to delight loyal Jami users and newcomers after the announcement of Skype's shutdown.
We invite you to update and try the latest version of Jami! 🙇
👀 Want to know more about Εἰρήνη? Read our article : jami.net/eirene-to-make-new-us…
#Jami #opensource #P2P #App #PrivacyMatters
Εἰρήνη, to make new user onboarding simple and intuitive
☮️ Jami team is pleased to introduce the new version of Jami: Εἰρήνη.jami (Jami)
Kinetix
in reply to Jami • • •What in God's name is up with this project?
I've been trying out Jami the past couple of weeks as there had been some mentions around about giving it a try, it might be a possible Skype replacement. Here's what I found:
* when setting up the Android client and adding a person to have a conversation with, getting a message to/from that other person might not work at all. Much toying of settings in the apps ensued. This is, to me, the most basic function of the app, and it was broken. It might work after a time, it might not. It might work if you changed networks. It might work if you fiddled with DHT or uPNP settings. It might not.
* Later, and after an app revision update or two, I tried setting up a conversation with a user on IOS. I have received messages from the IOS user, but they have not yet received a message from me. This is even after an update to this super-duper release you're posting about.
I've been to the project's website, wiki (which is not a wiki), forums, both code repo sites, followed your fedi account, and here's what I've
... Show more...What in God's name is up with this project?
I've been trying out Jami the past couple of weeks as there had been some mentions around about giving it a try, it might be a possible Skype replacement. Here's what I found:
* when setting up the Android client and adding a person to have a conversation with, getting a message to/from that other person might not work at all. Much toying of settings in the apps ensued. This is, to me, the most basic function of the app, and it was broken. It might work after a time, it might not. It might work if you changed networks. It might work if you fiddled with DHT or uPNP settings. It might not.
* Later, and after an app revision update or two, I tried setting up a conversation with a user on IOS. I have received messages from the IOS user, but they have not yet received a message from me. This is even after an update to this super-duper release you're posting about.
I've been to the project's website, wiki (which is not a wiki), forums, both code repo sites, followed your fedi account, and here's what I've seen:
* Your fedi account, until just now, hadn't posted since August, and it appears to be a one-way account that doesn't respond to people.
* Your website has quirks on it like, for the Android download page "Download Jami from Jami.net" which links to f-droid.org (jami.org != f-droid.org) - someone's filed a bug about this. This doesn't really smack of trust, though.
* You don't seem to have anyone paying attention to the forums - there's a couple of people (who don't appear to be, or identify as being part of the Jami project) sort of trying to help, kind of, sometimes, maybe, but otherwise there seems to be little interest taken in the issues people are having. People are moving to proprietary solutions because of the jank in the app
* Up until a few days ago, git.jami.net, where links to file bugs go to, and most code repo links that people find go to, which is apparently a mirror of review.jami.net, wasn't mirroring properly for a month, so it looked like the project may have been abandoned.
* I posted a bug report about the broken mirroring several days ago. While it appears the mirroring is fixed now, the bug report was deleted. Not responded to, not closed, not resolved, just gone.
To me, it seems like this project is super inwardly focused, whose only existence seems to be to try to do something for corporate use (I honestly can't imagine), but is completely missing the ball with people who are trying to communicate that they're not having a good time with the product, at all.
I don't know what kind of community you're trying to build around the product, but I don't see projects like this as very trustworthy (appearing to be on the brink of shutdown, refusing to have 2-way communication with the user base).
This is in no way a critique of the developers at all - this just appears to be a project that's lost and could probably find it's way if it would pay attention.
I suspect this post will fall on deaf ears, sadly.
Jami
in reply to Kinetix • • •@kinetix Hello, and no, your message has not fallen on deaf ears! Thank you for taking the time to share your experience with us. We hear your concerns and truly appreciate your detailed feedback. You’re right on many points.
We are aware of past connectivity issues on mobile, and significant improvements have been made over the last few months. The experience should now be much smoother.
1/3
Jami
in reply to Jami • • •@kinetix We're also resuming communication more actively, and we understand that our lack of updates may have caused frustration. Regarding the specific issues you mentioned:
The F-Droid download link issue has been resolved.
The repository mirroring has also been fixed.
Your bug report was submitted to the wrong repository, which is why it was removed. If you ever encounter issues again, please don’t hesitate to email us directly: we’d be happy to help.
2/3
Jami
in reply to Jami • • •@kinetix
As a small team, we’re doing our best to meet the community’s needs while continuously improving Jami. It’s not always easy, which is why feedback like yours is so valuable. We hope you’ll give the latest updates another try.
This is the kind of community we’re striving to build: one where members, like you, understand the challenges of a platform like ours and help make it better.
Thanks again for reaching out!
Kinetix
in reply to Jami • • •Hi there, and thanks for responding! As you know, I was sceptical that @jami@mstdn.io was anything but a one-way account.
I'm still concerned that you're continuing to say that things should be so much better now, but I only started in the 'now' and have only been on very recent/latest releases of the Jami client. Problems exist even on the newest releases, and my experience has been anything but 'smooth'.
I do appreciate that this account is apparently listening, and that some other issues mentioned (the F-Droid link, the git repo mirroring) have been resolved.
I'm not sure how prudent it is though to suggest that one is filing bugs to a "wrong" repo, when there's no repo that fits very well for your online service issues such as your git repos or website, and the closest repo that seemed to make sense, the "jami-project" repo, was open and available to accept issues at the time I filed. I see that repo is now archived and my issue was moved to the "opendht" repo, whic
... Show more...Hi there, and thanks for responding! As you know, I was sceptical that @jami@mstdn.io was anything but a one-way account.
I'm still concerned that you're continuing to say that things should be so much better now, but I only started in the 'now' and have only been on very recent/latest releases of the Jami client. Problems exist even on the newest releases, and my experience has been anything but 'smooth'.
I do appreciate that this account is apparently listening, and that some other issues mentioned (the F-Droid link, the git repo mirroring) have been resolved.
I'm not sure how prudent it is though to suggest that one is filing bugs to a "wrong" repo, when there's no repo that fits very well for your online service issues such as your git repos or website, and the closest repo that seemed to make sense, the "jami-project" repo, was open and available to accept issues at the time I filed. I see that repo is now archived and my issue was moved to the "opendht" repo, which seems as "wrong" as anywhere else for an SCM mirroring issue. Why not create a new repo for specifically filing bugs about the website, forum, SCM platforms, etc. - things that aren't a specific piece of software, rather than suggesting users trying to get your attention on what seems like the most logical place as "wrong"?
Last, I'm curious what more you'd like one to do with the latest releases when they're still having the same issues with getting messages through as were there in not-the-latest releases? I've tried, I've followed the last several updates, and if the basics don't work, they don't work. I appreciate it's a small team, but I think there's still some work that needs to go in to getting the basic message handling much more reliable before breaking out the news releases and trying to get a disappointing app in the hands of many more people. I suspect things are pretty close to it being quite a compelling app, but I couldn't recommend it to anyone as of today.