jami-project issues
https://git.jami.net/savoirfairelinux/jami-project/-/issues
2022-05-23T08:29:58Z
https://git.jami.net/savoirfairelinux/jami-project/-/issues/1435
Add *account name*, *account type* to notifications
2022-05-23T08:29:58Z
ovari
Add *account name*, *account type* to notifications
It can be hard to determine which account has an incoming call as the notification does indicate the account.
# JAMI account
![JAMI account](/uploads/5e03ae22567819a67591bd240d0b04f2/JAMI_account.png)
````
If ProfileName <> BLANK then...
It can be hard to determine which account has an incoming call as the notification does indicate the account.
# JAMI account
![JAMI account](/uploads/5e03ae22567819a67591bd240d0b04f2/JAMI_account.png)
````
If ProfileName <> BLANK then
Account_Name = ProfileName
else if Username <> BLANK then
Account_Name = Username
else
Account_Name = Identifier
end if
````
1. Change string from `Missed call` to `Jami account %1$S has %2$S missed call` (singular) / `Jami account %1$S has %2$S missed calls` (plural)<br>
`%1$S` is the Jami account name<br>
`%2$S` is the number of missed calls<br>
inspiration [%1$S received %2$S new message](https://transvision.mozfr.org/?recherche=%251%24S+received+%252%24S+new+message&repo=gecko_strings&sourcelocale=en-US&locale=fr&search_type=strings) / [%1$S received %2$S new messages](https://transvision.mozfr.org/?recherche=%251%24S+received+%252%24S+new+message&repo=gecko_strings&sourcelocale=en-US&locale=fr&search_type=strings)
2. Change string from `Incoming call` to `Incoming call on Account_Name Jami account`
# SIP Account
![SIP account](/uploads/552a775405a3873adf7f81e94518ea50/SIP_account.png)
````
If ProfileName <> BLANK then
Account_Name = ProfileName
else
Account_Name = Username
end if
````
1. Change string from `Missed call` to `SIP account %1$S has %2$S missed call` (singular) / `SIP account %1$S has %2$S missed calls` (plural)<br>
`%1$S` is the SIP account name<br>
`%2$S` is the number of missed calls<br>
inspiration [%1$S received %2$S new message](https://transvision.mozfr.org/?recherche=%251%24S+received+%252%24S+new+message&repo=gecko_strings&sourcelocale=en-US&locale=fr&search_type=strings) / [%1$S received %2$S new messages](https://transvision.mozfr.org/?recherche=%251%24S+received+%252%24S+new+message&repo=gecko_strings&sourcelocale=en-US&locale=fr&search_type=strings)
2. Change string from `Incoming call` to `Incoming call on Account_Name SIP account`
# Other images
![Incoming call](/uploads/d27dd8531d9dc2407c068ff0f5d82875/Incoming_call.png)
![New message](/uploads/b5008f5dc5f002a8f47e9daa7b120cbb/New_message.png)
![Notifications](/uploads/39a309c98193e87622296868400955c6/Notifications.png)
![Printer Notification](/uploads/697569f049a4cf6169840bc00da7510f/Printer_Notification.png)
What do you think?
Thank you
https://git.jami.net/savoirfairelinux/jami-project/-/issues/1274
Agent: port on android
2021-07-07T13:49:07Z
Sébastien Blin
Agent: port on android
Ideally with minor changes, but the agent will have a basic view
Ideally with minor changes, but the agent will have a basic view
Backlog
https://git.jami.net/savoirfairelinux/jami-project/-/issues/811
Federation/Discovery for name servers
2022-10-17T17:35:28Z
Markus Wamser
Federation/Discovery for name servers
Username <-> ID mapping is useful for easy contact discovery.
As the character '@' is not a valid character for usernames it can be used for seamless integration of multiple name servers.
```
user1@ns.jami.net -> lookup user1's ID on ns...
Username <-> ID mapping is useful for easy contact discovery.
As the character '@' is not a valid character for usernames it can be used for seamless integration of multiple name servers.
```
user1@ns.jami.net -> lookup user1's ID on ns.jami.net
user2@ns.ring.cx -> lookup user2's ID on ns.ring.cx
```
An even better solution would be to look up name servers through SRV-records in DNS, so
```
user1@jami.net -> get name server from SRV record: ns.jami.net -> lookup user1's ID on ns.jami.net
```
This enables organisations to easily set up their own (read-only) name servers and re-use eMail-Adresses as usernames.
However, lookup behaviour has to be defined, documented and implemented consistently across clients.
https://git.jami.net/savoirfairelinux/jami-project/-/issues/610
Unsecure connexion indicator when calling on SIP
2020-10-01T19:30:21Z
François Naggar-Tremblay
Unsecure connexion indicator when calling on SIP
Users should be aware when their SIP call is not secure (tls).
Users should be aware when their SIP call is not secure (tls).
https://git.jami.net/savoirfairelinux/jami-project/-/issues/467
Move i18n translations from Transifex to Weblate
2024-01-26T02:46:43Z
anna
Move i18n translations from Transifex to Weblate
Unfortunately Transifex is still a proprietary solution.
Alternatively Weblate could be used instead to develop the future of Ring's translation.
It's GNU GPLv3 and has a GitLab integration as well.
So i think it will be a more ethical s...
Unfortunately Transifex is still a proprietary solution.
Alternatively Weblate could be used instead to develop the future of Ring's translation.
It's GNU GPLv3 and has a GitLab integration as well.
So i think it will be a more ethical solution in the sense of Free Software and in the sense of GNU philosophy.
You will find more informations on their website https://weblate.org/en/
and in their latest docs as well https://docs.weblate.org/en/latest/
Here is a small article why another Free Software project (elementary OS) moved from Transifex to Weblate
https://medium.com/elementaryos/adios-transifex-weve-gone-to-weblate-59870dea06b2
What do you think?