jabber/gtalk not seeing full_name for G+ contacts anymore

[cj@…]

Starting last night, G+ contacts which I access via jabber/gtalk (per the setup at ​https://wiki.bitlbee.org/HowtoGtalk ) no longer seem to recognize the full_name of the contacts, for nick_setup. A friend I was chatting to just switched over to using the random-characters nick. I'd seen this a month or two ago, as well, but in that case it was solveable via an 'account gtalk off' followed by 'account gtalk on'. I've tried that now, too, but with no success. I've also tried re-setting 'account gtalk set nick_format %full_name' prior to the off/on, and I've tried bouncing Bitlbee entirely.

I do have about half of my gtalk contacts showing up as real names, but it's possible those aren't G+ accounts.

Using bitlbee 3.5.1, and libpurple 2.10.11 (not sure if it actually uses libpurple for this or not). Let me know if there's any other info I can provide!

[CJ K <cj@…>]

Ah, interesting - I just found out about bitlbee's "rename" command, which lets me rename these random-char nicks to something more human-readable. That's an easily-manageable solution for myself, given my relatively small friends' list, at least. May not be suitable for others, though.

[bdb]

I'm encountering the same issues as of today (2019-04-08). Bitlbee version 3.6-1.

Attempts to recreate the gtalk account in hopes of resolving this proved futile. Perhaps G+ is no longer handing out the information on nicknames anymore? The odd part is that only one contact is listed as their nickname instead of first name, so this is beyond wild. Have tried (with no success):

• full_name
• first_name
• nick
• account

[anonymous]

I have the same with bitlbee 3.5.1. All my google hangout contacts changed back from %full_names to the "random chars" for nick a week or so ago... My bitlbee is compiled without libpurple support.