-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ring was renamed to Jami #64009
Comments
See here how to properly deprecate a package: https://github.com/NixOS/nixpkgs/pull/62529/files |
Nice that there is a way to deprecate something. Not so nice that there is no documentation about how to do it. |
@matthiasbeyer right. let's create an issue (or the documentation directly)! |
Yes, sure! I'm not familiar with how the process works, though. |
Looks like the nightly releases are hosted here: https://dl.jami.net/ring-release/tarballs/ I'm evaluating a few (lower-hanging) decentralized chat clients, but if I swing back around to Jami/Ring I'll take a crack at updating the package. |
What clients were you looking at. |
I'll have a look on updating the package and adding the desktop client. I'm also interested what other decentralized chat clients @zeonin evaluated and what was the outcome? |
Ultimately, my use case was for real time voice over a roaming cellular data plan, so latency and bandwidth were my priorities. I ended up using mumble+murmur as that's what aligned best with my goals. That said, the most promising decentralized chat clients I found were part of the Tox ecosystem. |
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them. Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel. |
This is still relevant to me. |
Relevant to me, too See #83411 |
is anybody capable to pickup the work from @doronbehar ? This seems to be a tough nut to crack. Many have tried. On Guix, it works. |
I just use it using guix. I'm not going to work on this |
I marked this as stale due to inactivity. → More info |
#83411 (comment) points to a repo with nix expressions that seem to work for @viric so in principle it's "just" a matter of polishing/organizing them a bit and making a PR against nixpkgs. |
Please rename the package and URLs accordingly.
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/instant-messengers/ring-daemon/default.nix
https://git.jami.net/savoirfairelinux/ring-daemon
https://jami.net/ring-becomes-jami/
https://repology.org/project/jami-daemon/history
An update would be also good, but they havn't done a proper release. https://git.jami.net/savoirfairelinux/ring-daemon/issues/124
cc @taeer @olynch
The text was updated successfully, but these errors were encountered: