I am in favor of experimentation here. Much of the supportive commentary to this point has been strong, so without rehashing I broadly agree with many of the delegates above.
An operational note not yet referenced:
– Given IPFS storage, we need to be cognizant of the limited ability to remove recordings from publication. Because of this, we should take steps such as structuring a standardized meeting kick-off process inclusive of notes such as “for those who don’t want to be recorded, please turn your cameras off now” – this is something Sinkas does regularly on the current meetings, and in an IPFS structure I’d say should be standard policy. There are likely other privacy and best practice considerations which would warrant a short discussion. Nothing critically blocking, but simply worth thought.
Then there are more standard meeting setup processes which would address some of the concerns of friction, barrier to entry, risk of performance. Simply:
- Begin testing huddle on ‘lower significance’ calls initially. So a structure for which types of calls early testing will start on and which would maintain the current google setup would be helpful.
- Ensure that there is a backup google meet link added into the description of invites testing huddle. At any point, the meeting organizer can route the audience toward the back up link.
With these two points added, and consideration for meeting recording processes, I see benefits in testing this then scaling up if it is well received.