I’m running into another inconvenience. I’m setting a URL for an avatar image when I create my JWT token, and it displays fine for the user who joins with that JWT:
But the avatar image does not display from the client of any other user - only their own.
Both of these screenshots were taken in the same room of the same two users from opposite ends. I’ve looked around some, and I can’t see why this issue might be happening. In the developer console when the meeting loads I see this:
Which is odd because I have no references to Gravatar anywhere in my code.
Again, the images display as-expected on the client of the user who’s avatar it’s supposed to be, but it just looks like letters of their name like normal on the screens of other users. How do I fix this?
What kind of certificate issue? What do you mean by that? Remember that the avatar images display 100% fine for the user that uses the token to log in.
Here these are. There’s no point in continuing my half-baked effort to hide my domain name, so have fun. You might find a token or something in there too if you look hard enough.
I took a sneaky look at your config.js and noticed that you have set disableThirdPartyRequests: true.
This has the unfortunate side-effect of also blocking avatar requests.
What I didn’t expect however is for the client to attempt loading from gravatar with that setting enabled. @damencho is blocking of avatar still an expected outcome of disableThirdPartyRequests, and if so then the gravatar access is a bug?
nice! BTW, apologies if I overstepped by peeking at your live deployment.
@damencho, I would except I cannot repro the issue on my deployment. When I set disableThirdPartyRequests, participant avatars drop off as expected but I don’t see any stray calls to gravatar.
@Taran what version of jitsi-meet are you running?