While the base URL remains configurable, this patch reverts back to using
Gravatar.

We noticed high latency with libravatar and contacted them. They are in the
process of migrarting to a better infrastructure (it's a single personal server
at the moment) so we'll re-evaluate once that has happened.

As for why not leave the default and change it on the meet.jit.si installation,
we don't want to kill their server :-)

As per @fremzy, the "Save Logs" feature generates a json
file with a bevy of technical information about the
meeting. This log contains the server name, server IP
address, participant's IP addresses (only in p2p sessions)
e.t.c. While this may be a useful feature for the
admin-like 'moderator', it creates unnecessary exposure
when made readily available to all users in the meeting.

This commit fixes #8036 by a config.js option to enable
the link (disabled by default), thus giving the owner of
the deployment the choice of enabling it or not.

When trying to auto pin screenshare, always select the endpoint even though it happens to be the large video participant in redux. The auto pin screenshare logic kicks in after the track is added.  If the screenshare endpoint is not among the forwarded endpoints from the bridge, it needs to be selected again.

If limitLastN values are specified and channelLastN < limitLastN, configure channelLastN on the conference.

Also, default to libravatar.

Closes: https://github.com/jitsi/jitsi-meet/issues/4927

This is needed for the torture clients to determine the video type for the remote participants when testing desktop share.

fix(jaas) replace only the first slash in a pathname

Follows me and switching to tile view, still works.

chore(deps) lib-jitsi-meet@latest

We stopped providing a way to set them, so don't render them either.

Also cleanup some leftover config options.

* fix(Toolbox) Maintain overflow button visible at all times

* Make changes only on desktop browser

Safari 14.1 has a bug where it returns 720p for every simulcast stream when RTCRtpSender.getParameters is called even though the stream resolutions are different.
By using the encodings config used when source was added, on every RTCRtpSender.setParameters call, we ensure that simulcast stream resolutions don't change.
chore(deps) lib-jitsi-meet@latest

* feat: Drops filmStripOnly mode.

* squash: Let's make lint happy again.

* squash: Drop some css.

This will make browsers not cache results in cleartext.

Co-authored-by: Tim Dittler <t.dittler@heinlein-support.de>

Bwrosers have not allowerd WebRTC on non-secure origins for a very long time
now.

Allow path separator of \ in addition to / in jQuery's path name.

Fixes: https://github.com/jitsi/jitsi-meet/issues/7900

fix(vpaas) fix invite url flicker for jaas users

Part of main-it.json uses characters like è, but some places still uses the è equivalent. Those character are not correctly rendered in the browser, therefore they are switched to their counterparts, as it was already done for other texts.

It has been `true` for a very long time.

* Fix layout
* Change background color & show image

fix(CalendarList): calendar.svg path.

Do not resize the desktop share to 720p by default when the desktop track resolution is higher than 720p. This is causing bluriness when presenter is turned on.
Remove the 'detail' contentHint setting for the desktop+presenter canvas stream as it forcing chrome to send only 5 fps stream for high resolution desktop tracks.
Move the desktop resizing logic behind a config.js option - videoQuality.resizeDesktopForPresenter.