@manu Vu que le cerveau aime généralement quan tout fait sens pour lui, et que tout mène à vouloir voir à l'endroit, à mon avis il sera plus "reposé" avec l'image dans le sens logique ;)
@manu en fait ça repose pas amha, le cerveau va travailler pour avoir la logique. Me semble qu'une expérience avait été menée où une personne avait un casque qui retournait la vidéo. Au bout de deux jours, le cerveau était habitué et remettait la vidéo à l'endroit.
J'ai laissé un soft de reconnaissance vocale (basée sur pocket sphinx) tourner pendant une partie de bomberman (à entendre de la musique + bruits d'explosions)
> the la la la up out on top up up up and what up one and been what what what what what are all the more that a lot of blood and then
@Shamar Sure. But I don't think this problem should be handled by the Jami app. A Jami client can offer (or not) the possibility for users who wants to get contacts from system apps.
Anyway it's not possible for now (maybe the KDE client from a contributor does that, but not the gnome client)
But any user can host a nameserver which works like they want if really needed.
If it's only stored locally, I don't have a problem with this. It's useful when you search one of your contacts. (I don't use this kind of apps anyway)
The best approach for that I think is to use the system contacts, like the contacts app for Android, gnome-contacts for GNOME, etc and inject it into Jami. This feature existed in the past in fact, but I removed it because it should be reworked.
For a personal vocal assistant I do, I manage accounts via a local webserver. So both methods are possible indeed.
I am not sure about what you mean by local/private phonebook? You mean like using gnome-contacts to manage your own contacts? In fact yes it's technically possible (Not available in the "official clients"). But it's purely a client feature to interact with a device phonebook.
sha1 is not really a problem here, you still need a pair of keys. And moving to another thing is not planned for now (this need a lot of work in OpenDHT I think)
It's only used to store usernames on ns.jami.net, so yes it is optionnal. If you still want a username, you can have your own name server (I just host a JSON file on my website for example)