Our team will be more than happy to layout a FAQ document to help delegates understand the platform in better way
3 Likes
At Unlock Protocol DAO, we have been using Huddle01 for all of our regular DAO meetings and former Town Hall meetings. Yesterday, I started using the YouTube streaming function for the first time (we used to stream to Twitter), and it worked seamlessly.
Huddle is, in my opinion, not only a great piece of software and comes with an exceptionally supportive team, it also supports what we stand for as decentralized and blockchain-based communities. Instead of just talking the talk, let’s commit to walking the walk <3
7 Likes
I’m excited about this decentralization move!
I like recordings will no longer depend on someone’s personal account, they’ll be stored in a decentralized, public way, ensuring transparency and preventing any risk of them being deleted or lost.
Of course, it’ll take time for everyone to get used to the new tool, especially those who are used to Google Meet and traditional platforms. Some might feel uneasy about switching, and we might face issues with availability or user experience.
That’s why I believe testing is key. We need to make sure it’s stable, with no performance or connectivity issues, and no hidden bugs…Maybe starting testing in DAO meetings would be a good start 
7 Likes
Thank you for putting this forward, Paulo.
While we haven’t encountered any major issues that would necessitate this change, we always welcome the opportunity to support an Arbitrum-native project.
We share similar concerns and are therefore somewhat undecided on this proposal.
What would define the success of this test? Can we establish clear success criteria? It would be helpful to outline key benchmarks—specific outcomes we need to achieve during the trial—so that we can objectively assess whether to proceed with full adoption.
1 Like
Thanks to @paulofonseca for testing and understanding this product.
I believe that as an Arbitrum community we should support products created in our ecosystem.
Especially if it is high-quality and useful software for our needs.
I do not see a single downside: a cheap subscription that develops the project and, accordingly, an influx of users to Arbitrum
Even if it turns out that everyone does not like the product, the team quickly works on solutions and we can always return to Google Meet
2 Likes
Thank you @paulofonseca for doing the legwork and building this proposal. We should absolutely be using more Arbitrum-based tools, and this seems like a great place to integrate something from the ecosystem. Strongly in favor, with the caveat that I also think it would be key to have the kind of contingency planning @EzR3aL mentioned.
3 Likes
My organization SI<3> has been very active users of Huddle01 with their Business Plan and subdomain for our community. We use Huddle01 for our team meetings and community sessions, and have enjoyed supporting decentralized tech and engaging with their team for product feedback. Like Stella from Unlock shared earlier here in this thread, we believe in being engaged participants in this emerging tech we are all building. We have had some minor hiccups with Huddle01, mostly with our members that are in Africa with lower bandwidth. The Huddle01 team has been very supportive of our ecosystem and joins our larger community calls to monitor performance. They even added a node in Africa for us when we requested it.
8 Likes
In principle the prospect of a more decentralized alternative than anything google makes me excited, but in practice I want to reserve judgement until I’ve had a chance to run it through its paces.
I’m especially worried that it might be the kind of application that requires downloading custom components and apps, such as the iPhone app it was mentioned in the thread that someone had to use. It’s a sad reality that we now have to be hyper-aware of potential attack-vectors into our local systems in the crypto space now, so I’m hoping we won’t run into too many requirements like that.
3 Likes
It was integrated with one of our startups (meetwith.xyz) and I didn’t have issues with it but we got multiple reports of issues. We added other meeting options about 3 months ago, so people migrated to what they find familiar (zoom, hangouts, etc).
I see there were some specific potential issues with our implementation though:
So what Gauntlet is proposing here is the way forward IMO:
4 Likes
We like the idea, @paulofonseca, and see no harm in trying out Huddle01. If it doesn’t work as well as expected, it can always be rolled back to Google Meet.
We honestly don’t see any downside, with the exception of buggy calls, and we do agree that we should use apps on Arbitrum where feasible.
4 Likes
Thanks for the proposal Paulo.
Disclaimer: I just played around with Huddle a couple of minutes so maybe I haven’t grasped its full potential.
Nevertheless here are some functionalities of Google Meet I like (for the ARDC in my case) and that should be matched by whatever solution we choose:
- Recordings and transcripts (Google Business for ~12 USD a month including custom e-mail vs Huddle Pro for 20 USD a month)
- Easy integration with a range of AI note taking tools (for quick summaries I prefer Happyscribe over Google products)
On the rest I am torn, I believe we should try to use apps on Arbitrum on the other side e.g., within the ARDC as we are dealing with Service Providers it might create additional friction (or one could argue we expand the customer base for Huddle)
2 Likes
This is a thoughtful proposal, @paulofonseca, and I appreciate your initiative in seeking a more aligned solution for our DAO’s video calls. We should explore the move towards an Arbitrum-native tool like Huddle01, as it resonates with our commitment to the ecosystem.
Like many others, I see the clear advantages in terms of on-chain recording storage and the potential for more flexible host management, which addresses some of the current pain points with Google Meet.
However, the feedback from delegates like @danielo regarding past technical issues and the concerns of @JoJo and others about potential friction for users are essential considerations. Ensuring a smooth and reliable experience for all delegates is paramount for effective governance.
Therefore, I believe the proposed two-week trial is a crucial step. To make this trial truly valuable, I’d suggest we establish clear success metrics beforehand; This should include technical stability (mic/camera, login) and user experience feedback across different devices and geographies. A brief survey could be circulated after each test call to gather structured feedback.
Ultimately, while I’m enthusiastic about supporting Arbitrum builders, our primary responsibility as delegates is to ensure the efficiency and accessibility of our governance processes. A successful trial with robust feedback will be key in making an informed decision.
Melra 🜁 | Independent Delegate
2 Likes
Overall, great proposal @paulofonseca. Having listened to your own explanation of the thought process behind it, prior testing, relatively cheap costs, I’m all for backing and using something that is actually built on top of Arbitrum as opposed to evil Google tech.
However, I think there are some pretty valid concerns that warrant further testing, mainly:
- Bugginess
- Lack of integrations
- AI note-taking and transcripts, which might not be necessary for most but is a godsend for some of our hardest-working attendees
- Convenience/friction: right now attending call is pretty easy and there is pretty much little to no barrier, do we really want to add an extra layer of complexity to the whole thing?
I suggest doing some sort of trial run or perhaps proposing a joint period where both Huddle and Meet are used simultaneously to ease people in. Not sure if it’s possible, but that might be the best way to get this to pass without ruffling some feathers.
3 Likes
Thank you so much @paulofonseca for bringing up this great proposal.
As an event organizer and community builder at Ethereum Bolivia, as a community we have always struggled to have video meet tools that can help us host calls with mire that 10 people connected with no-time restricment and to have log reports to effectively know who attended or not our virtual events, and we found Huddle01 on socials and decides to try it out for a Q&A session for our last Buildathon ETH Bolivia 2024.
This experience was really extraordinary, as we had 46 attendees, we were able to record and post the recording in our social media accounts, had a log report as .csv file that served us as base to airdrop Unlock NFT certificates to all the attendees and have onchain impact report of the activity. Take into account that 90% of attendees were completely new to web3, so didn’t have a wallet and just connected through their emails or as guests with no need to give even an email.
From that date till now Huddle01 has made significant improvements, listening to all the user feedback, reports and even experiencing by first hand by joining calls to check how users are experiencing video calls in general, which shows an extreme commitment to make and improve the user experience of decentralized apps.
Would love to see this implemented into Arbitrum DAO calls and lead by example in this industry, supporting and using Arbitrum based products and apps, and strengthening the bond between layer-app to bring 1 Billion new users into Ethereum and Arbitrum.
5 Likes
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.
2 Likes
The following reflects the views of L2BEAT’s governance team, composed of @krst, @Sinkas, and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.
Although we like the idea of using Arbitrum products — and generally web3 products where it makes sense — we see little reason for the proposal to go through the governance process at this time, even if it’s just to get ‘ratified’. It would be more sensible to start using Huddle first, and, if it makes sense, have such a vote in the future.
This proposal could serve as a starting point to discuss a closer relationship between Huddle and the DAO. If we are to utilize Huddle and promote it as a DAO, then Huddle should also promote Arbitrum as a suitable platform for building, where builder support is available. Hopefully, this relationship turns into a success story we can leverage, and a field to experiment with more collaboration between the DAO and Arbitrum builders.
What we could do now is help build awareness about the existence of these tools and let delegates decide whether or not it makes sense to use them. Proposals, or rather discussion starters, like this should serve as a gentle nudge for people to try something new, which we recognise can be difficult due to the force of habit and familiarity.
As L2BEAT, we have already started using Huddle for the calls we recently set up, such as the SOS discussions. Unless any significant issues arise, we are open to continuing to use Huddle for DAO-related calls. We only encountered an issue once with a recording that randomly stopped, but after contacting the Huddle team, they appear to have resolved the issue
The idea of having recordings automatically stored in IPFS is also very appealing, as it ensures that the calls remain accessible and do not depend on any single entity’s or individual’s Google account remaining active.
With that in mind, we suggest continuing to experiment with using Huddle without any commitment to make it the standard tool, to see if there are any issues with people not being able to join calls with the same ease. If everything is working correctly, we can continue using it and encourage others to use it as well, without, however, forcing anyone to use it.
Disclaimer: The above is not an endorsement of Huddle as a software, but rather an attempt at practically supporting builders on Arbitrum.
7 Likes
From my experience using this product on Arbitrum calls, I have come to the following conclusions:
- The video picture is excellent, oddly enough - it is better in Huddles than in Google Meat.
- The sound is also good, I did not notice any bugs or noise, everything was as usual.
- Having reviewed the recordings of our calls, I was also pleased with the quality of the recording
- Perhaps the only downside, the feature that I lack in this application is transcription. Due to the fact that I am not a native English speaker, I turned on transcription for myself as a backup and this often helped me.
If the Huddles project can implement this feature, it will be ideal (maybe it exists, but I did not find it - tell me then please)
3 Likes
The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb), @Euphoria, and Hirangi Pandya (@Nyx), based on our combined research, analysis, and ideation.
Thanks, @paulofonseca for taking the initiative on this. We fully support the idea of using Web3 tools, and it’s even better that Huddle01 is built on Arbitrum. Using native tools shows our commitment to the Arbitrum ecosystem.
We’ve been in touch with the Huddle01 team for about a year now. We had integrated it into our product, Chora Club. Like any platform, there were some early issues. But the team was quick to fix bugs and very open to feedback. They added features based on our suggestions and worked to improve the platform. Because of this, we’re confident that if any issues come up while using it for DAO calls, the Huddle01 team will respond quickly and handle them well, as they handled the recent recording issue for one of the calls.
We also joined a few DAO calls, which were conducted using Huddle01 recently like the SOS calls and proposal discussions, and it worked smoothly for us on desktop. We haven’t tried the mobile app yet, so we can’t comment on that. A couple of small suggestions from our side after recent meetings:
- Like @cp0x mentioned, I’m also not a native English speaker, and I find live transcription (or closed captions) very useful in calls. It would be great if this feature could be added.
- And the “Raise Hand” feature is currently inside the emoji section; it might be better to move it outside for easier access during meetings.
We also wanted to ask how meeting links will be managed in the DAO. Will a specific person be responsible for sending out or hosting the links, or will any contributor be able to schedule meetings on their own?
And as @Sinkas said, we also think this shouldn’t go to snapshot voting just yet. It’s better to keep testing it in our regular calls for another month or two and let everyone get used to the platform. That way, we avoid forcing everyone to switch too early.
One small suggestion for the @ayushranjan & Huddle01 team: since more DAO calls are now using the platform, it would help if you could share a short guide or video showing how to use the platform. That could be posted on the forum to help both delegates and community members onboard easily before the calls.
We’re happy to support further testing of Huddle01 for DAO calls and are looking forward to seeing how it continues to improve.
4 Likes
thanks for sharing the feedback on the live transcription, we do have plan to introduce such features in the platform with time
right now, in near future we planning to bring the meeting transcript summary which might be helpful for people to grasp the summary of the meeting
3 Likes
for a subdomain, we have team section where different contributors can be added who can manage the subdomain and create the links and host the event and make other people host during the schedule process
this will prevent having dependancy on a single person for scheduling and hosting the calss
1 Like