Idea to transfer this project over to Google

[YpePoortinga]

This GridView makes Google Meet usefull. The standard Google Meet functionality is lacking on some basic functions which are included in this GridView, See the advantages below.

Google changes their Meet-setup nearly daily, which effects this plugin and I notices that the developmentteam is not strongly re-actief, maybe it is better to contact Google (meetteam) and ask them to take over this product.

Killer-advantages of this Grid-View

• Seeing yourself equals to all other participants. If you don't see yourself in a digital meting, then it is equal as when you are looking to a TV-screen. Your attention is flowing away. Seeing yourself makes you aware how the others see you and that you are part of an meeting..
• the blue border when someone is talking, This helps in finding out who has microphone problems and disturbing the meeting
• Seeing the screen you are sharing. This makes you aware you are still online and everyone can see when you accidentilly go to another screen.

[ricren]

According to this blog:

https://cloud.google.com/blog/products/g-suite/introducing-some-new-meet-features

they plan to bump up the number of the people that you can see at the same time to 49.

Still they (I mean, the gmeet team) should be more careful and not break this every time they change something.

[Eagle-Man]

Quite honestly, this code would be almost useless to Google. Since there is no Meet API which allows access to internal Google functions, much of this is parsing through what's available in the structure of the actual page (which is why it breaks so often). Google , on the other hand, would have direct access to the behind-the-scenes capabilities directly, which would vastly alter how they would code this solution (though, sizing/placement code, especially for pinned video could still be helpful).

That said, Google increasing their Tiled view to 49 may be an indication that they are planning to keep increasing the number over time. The difference between the extension and Google is that if Google implements something natively, then it must be robust enough to work for everyone out there who uses Meet, and Google needs to ensure that their servers can support it. Thus, they tend to roll things out slowly, either to just groups of users at a time, or by slowly scaling it up.

@ricren The problem is that Google is not beholden to their 3rd party extension creators. They can't be, there are just too many of them. They are responsible for doing whatever they need to do to improve their own product, and it's up to the extension creators to update their products as a result.

[Adambean]

A better route for this would be to open up the license to allow able contributors to submit maintenance/compatibility changes. If you put something good up on Github and allow others to work on it, others will work on it, for the benefit of everyone.