domain to domain video soon?

Privacy. That's Huddle01.

Come chill with us and our frens @xmtp_ @metaworklabs @0xTPH @PhoenixGuildHQ @superwomenDAO @OgclubDAO @BuidlersTribe at @BLRxZo 🤝🏻 🍻 🗓 12th May, 6PM IST onwards. RSVP now ↳ eventbrite.com/e/gm-bangalor…

Registrations for #FILBangalore are now OPEN 🎟 ✨ Get ready for 2 days of turbo-charged learning & networking with global web3 trailblazers & ecosystem leaders, powered by @filecoin & @huddle01com 🗓 3rd-4th Dec, 2023 📍 Sheraton Grand 👉 Register now: fil-bangalore.io/

Anddd we’re live with @dvcoolster & @pratapyps for EP.01 of #HUDLOfCommons🎙 RT to invite your frens and tune in for a very special giveaway - the creator of @zostel and @the_zo_world is dropping some exclusive insights and alpha here ✨ 👀 nitter.app/i/broadcasts/1YpJkwOAw…

EP.01, #HUDLOfCommons🎙 goes on air soon with @dvcoolster as our 1st guest to talk about building the most desired lifestyle club, culture & infrastructure for individuals in a permission-less world. Tune in here to 🎧 live on X at @huddle01com 🗓 5th Oct, Thursday ⏰ 11PM IST

When we collaborate, great things happen. Presenting to you #FILBangalore, organised by Huddle01 🚀 A 2-day celebration of the power of web3 community where we connect, learn and build together. Register now 👇 fil-bangalore.io/ @Filecoin

🔵 Introducing Huddle01 SDK v2.0 ◆ Multi-region cascading ◆ Scalable upto 10,000 peers ◆ 90% reduction in latency ◆ 0 downtime during releases ◆ Seamless network switching ◆ Improved DX 👉 Read the full update: huddle01.com/blog/introducin…

Do everything great or die

Hey @naruto11eth — while I strongly agree with the push for dogfooding, and strongly agree with replacing centralized apps/systems as quickly as possible, these are complex decisions with lots of variables. I’ll say more here because it’s a good learning moment for a lot of people building decentralized web3 products. We’re finally getting to see good products emerge and many builders out there are dogfooding and face these decisions all the time. For context, we definitely wanted to use Huddle initially, but had to play it safe this time. Reasoning below. With more time we would’ve done it, and we planned to shift over to Huddle next FIL Bangalore. First though, Huddle is well on its way to matching and exceeding zoom UX on a lot of parts — it’s actually astonishing that a team so small has pulled off such a remarkable feat so quickly 🎉 — for ex, recently I’ve had to switch many calls away from Zoom and to Huddle because the p2p AV quality & delay is so much better in many countries’ networks than over zoom’s relays. I already default to Huddle over Zoom for many uses, though not yet all. Huddle is already used for lots of event streaming, and in my experience has worked very well. I’m frankly very impressed with the product success all things considered — true david v goliath story. So, reasoning for this event: - Dogfooding is hugely valuable in itself - and we should all try to do it - Valuable for Huddle to claim the victory of using the product for this - but: products take an enormous amount of work to perfect in all edge cases - we’re talking thousands of little features interacting in complex ways. - Zoom has had the benefit of 10 more years, thousands of people (vs ~20) perfecting the product over those years, and many orders of magnitude more product stress testing over Huddle (trillions of meeting minutes, millions of events, etc.) - Lots of people are way more familiar with zoom today, so AV team and others much more used to zoom today. - Live event streaming — while already happens on huddle already — hasn’t been as high priority as other use cases, so there’s unknown product surface area where issues may appear. With millions more minutes and thousands of events, those issues will be ironed out. - Live events have very little margin for error - even slight hiccups can cause a lot of problems and make the experience bad for attendees, speakers, event staff, etc. - sometimes a problem unrelated to the software (eg in physical AV setup, user familiarity with the product, network issue) could be mistaken as a problem in the software. - Last minute additions (like this one) have little or no chance for testing & training staff, so you have to reduce likelihoods of something going wrong (including user familiarity) - this was the big one here: had we had any time to test, we could’ve tried it. - All of these issues would reflect poorly on Huddle regardless of whether it was a software issue on their end at all or something else. So, while I very much agree with dogfooding, and replacing centralized things asap, we also have to do it responsibly. I very much want to see any calls on next FIL Bangalore (and many other events) over Huddle, and am sure the team will deliver 🎥💙🎉

The uprising against centralized cloud control begins in less than 24 hours. Take notes, here's everything you need to know to join us for the Battle of Open Realm against the CloudLords ⚔️ 🫂📜 ↓

best team. also, hi dubai! let's talk DePIN.

Founders put their decks to the test — refining, rehearsing, and getting real feedback from mentors.

We have something cool for our DeFrens! Yo, @DeGodsNFT @y00tsNFT how about we host the New Holder Orientation on @huddle01com Spaces? Let’s call it De[Meet]; a token-gated Audio Space for the community. What say @frankdegods? 👀

Share a piece of lore about yourself

A new era in communication is about to begin. Power to the people is imminent. Huddle01 Media Nodes Coming 🔜 🌐 find out more at: huddle01.com/