POPULARITY
11 episodes with WebRTC
7 episodes with WebRTC
4 episodes with WebRTC
7 episodes with WebRTC
4 episodes with WebRTC
5 episodes with WebRTC
10 episodes with WebRTC
7 episodes with WebRTC
2 episodes with WebRTC
LiveKit is a platform that provides developers with tools to build real-time audio and video applications at scale. It offers an open-source WebRTC stack for creation of live, interactive experiences like video conferencing, streaming, and virtual events. LiveKit has gained significant attention for its partnership with OpenAI for the Advanced Voice feature. Russ d'Sa is The post LiveKit and OpenAI with Russ d'Sa appeared first on Software Engineering Daily.
LiveKit is a platform that provides developers with tools to build real-time audio and video applications at scale. It offers an open-source WebRTC stack for creation of live, interactive experiences like video conferencing, streaming, and virtual events. LiveKit has gained significant attention for its partnership with OpenAI for the Advanced Voice feature. Russ d'Sa is The post LiveKit and OpenAI with Russ d'Sa appeared first on Software Engineering Daily.
Hi friends, today I'm kicking off a series talking about the good/bad/ugly of hosting security services. Today I talk specifically about transfer.zip. By self-hosting your own instance of transfer.zip, you can send and receive HUGE files that are end-to-end encrypted using WebRTC. Sweet! I also supplemented today's episode with a short live video over at 7MinSec.club.
For the full show notes and links visit https://sub.thursdai.news
Dan Anderson Oculum has a video conferencing solution for Service Providers. The solution is 100% white label. OmniUC™ is a white label video conferencing and unified communications platform designed specifically for the telecom industry. OmniUC is a turnkey solution that easily layers into existing voice applications with minimal development. Fully developed on WebRTC, OmniUC requires no apps, plug-ins or downloads and is compatible across all modern browsers and mobile devices. Customizable branding enables telecom providers to set the appropriate look and feel for their customers while a rich feature set offers options such as conferencing, collaboration, messaging, encryption, among many others. To learn more about Oculum's OmniUC™ white-label video conferencing and unified communications platform solutions, click here. Oculum is a PaaS (Platform as a Service) modeled technology leader and innovator of video conferencing for Telecom Service Providers and select technology industry verticals. With the support of 19 years of proven unified communications (UC) platform development, 110+ patents, and millions of subscribers, Oculum is uniquely positioned to deliver world-class virtual experiences on any type of user's device (mobile or browser).
Today Trey Ford and RSnake sit down with MirrorTab which aims to thwart client side malicious plugins from reading data meant to banks, and other sensitive websites, using clever WebRTC and video tricks.
News includes the archiving of the “Phoenix Sync” project, a major update to Gettext that enhances compilation efficiency, the release of ErrorTracker v0.2.6 with new features like error pruning and ignoring, and José Valim highlighting UX issues with ChatGPT's new UI. We were also joined by Alistair Woodman, a board member of the EEF (Erlang Ecosystem Foundation), who explained the EEF's recent efforts to stay ahead of legislation and technical regulatory shifts that may impact developers soon. Alistair discussed the changing regulatory landscape in the US and the EU due to high-profile exploits, outages, and nation-state supply chain attacks. We learned how the EEF supports Elixir and BEAM developers and what they need from the community now, and more! Show Notes online - http://podcast.thinkingelixir.com/220 (http://podcast.thinkingelixir.com/220) Elixir Community News - https://github.com/josevalim/sync (https://github.com/josevalim/sync?utm_source=thinkingelixir&utm_medium=shownotes) – The "Phoenix Sync" project has been archived with no immediate explanation yet. - https://github.com/elixir-gettext/gettext/blob/main/CHANGELOG.md#v0260 (https://github.com/elixir-gettext/gettext/blob/main/CHANGELOG.md#v0260?utm_source=thinkingelixir&utm_medium=shownotes) – Gettext has a big update to version 0.26.0 which includes a more efficient compilation. - https://github.com/elixir-cldr/cldr (https://github.com/elixir-cldr/cldr?utm_source=thinkingelixir&utm_medium=shownotes) – Gettext feels similar to how ExCldr allows defining a custom backend. - https://elixirstatus.com/p/TvydI-errortracker-v026-has-been-released (https://elixirstatus.com/p/TvydI-errortracker-v026-has-been-released?utm_source=thinkingelixir&utm_medium=shownotes) – ErrorTracker v0.2.6 has been released with key improvements like a global error tracking disable flag, automatic resolved error pruning, and error ignorer. - https://github.com/mimiquate/tower (https://github.com/mimiquate/tower?utm_source=thinkingelixir&utm_medium=shownotes) – Tower is a flexible error tracker for Elixir applications that listens for errors and reports them to configured reporters like email, Rollbar, or Slack. - https://x.com/josevalim/status/1832509464240374127 (https://x.com/josevalim/status/1832509464240374127?utm_source=thinkingelixir&utm_medium=shownotes) – José highlighted some UX issues with ChatGPT's new UI, mentioning struggles with concurrent updates. - https://x.com/josevalim/status/1833176754090897665 (https://x.com/josevalim/status/1833176754090897665?utm_source=thinkingelixir&utm_medium=shownotes) – José postponed publishing a video on optimistic updates with LiveView due to an Apple announcement. - https://github.com/wojtekmach/mixinstallexamples (https://github.com/wojtekmach/mix_install_examples?utm_source=thinkingelixir&utm_medium=shownotes) – A new WebRTC example was added to the "Mix Install Examples" project. - https://github.com/wojtekmach/mixinstallexamples/pull/42 (https://github.com/wojtekmach/mix_install_examples/pull/42?utm_source=thinkingelixir&utm_medium=shownotes) – The WebRTC example shows how to use the ex_webrtc Elixir package in a small script, compatible with Mix.install/2. - https://github.com/elixir-webrtc/ex_webrtc (https://github.com/elixir-webrtc/ex_webrtc?utm_source=thinkingelixir&utm_medium=shownotes) – The Elixir package used for the WebRTC example. - https://x.com/taylorotwell/status/1831668872732180697 (https://x.com/taylorotwell/status/1831668872732180697?utm_source=thinkingelixir&utm_medium=shownotes) – Laravel raised a $57M Series A in partnership with Accel, likely related to their Laravel Cloud hosting platform. Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Discussion Resources - https://en.wikipedia.org/wiki/CyberResilienceAct (https://en.wikipedia.org/wiki/Cyber_Resilience_Act?utm_source=thinkingelixir&utm_medium=shownotes) - https://news.apache.org/foundation/entry/open-source-community-unites-to-build-cra-compliant-cybersecurity-processes (https://news.apache.org/foundation/entry/open-source-community-unites-to-build-cra-compliant-cybersecurity-processes?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.cisa.gov/sites/default/files/2024-05/CISA%20Secure%20by%20Design%20Pledge_508c.pdf (https://www.cisa.gov/sites/default/files/2024-05/CISA%20Secure%20by%20Design%20Pledge_508c.pdf?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.whitehouse.gov/wp-content/uploads/2024/02/Final-ONCD-Technical-Report.pdf (https://www.whitehouse.gov/wp-content/uploads/2024/02/Final-ONCD-Technical-Report.pdf?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.infoworld.com/article/2336216/white-house-urges-developers-to-dump-c-and-c.html (https://www.infoworld.com/article/2336216/white-house-urges-developers-to-dump-c-and-c.html?utm_source=thinkingelixir&utm_medium=shownotes) - https://en.m.wikipedia.org/wiki/CE_marking (https://en.m.wikipedia.org/wiki/CE_marking?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.cisco.com/c/en/us/services/acquisitions/tail-f.html (https://www.cisco.com/c/en/us/services/acquisitions/tail-f.html?utm_source=thinkingelixir&utm_medium=shownotes) - https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act (https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.nist.gov/ (https://www.nist.gov/?utm_source=thinkingelixir&utm_medium=shownotes) - https://en.wikipedia.org/wiki/XZUtilsbackdoor (https://en.wikipedia.org/wiki/XZ_Utils_backdoor?utm_source=thinkingelixir&utm_medium=shownotes) - https://en.wikipedia.org/wiki/Log4j (https://en.wikipedia.org/wiki/Log4j?utm_source=thinkingelixir&utm_medium=shownotes) - https://en.wikipedia.org/wiki/Heartbleed (https://en.wikipedia.org/wiki/Heartbleed?utm_source=thinkingelixir&utm_medium=shownotes) - https://en.wikipedia.org/wiki/2024CrowdStrikeincident (https://en.wikipedia.org/wiki/2024_CrowdStrike_incident?utm_source=thinkingelixir&utm_medium=shownotes) - https://news.stanford.edu/stories/2024/06/stanfords-deborah-sivas-on-scotus-loper-decision-overturning-chevrons-40-years-of-precedent-and-its-impact-on-environmental-law (https://news.stanford.edu/stories/2024/06/stanfords-deborah-sivas-on-scotus-loper-decision-overturning-chevrons-40-years-of-precedent-and-its-impact-on-environmental-law?utm_source=thinkingelixir&utm_medium=shownotes) - https://openssf.org/ (https://openssf.org/?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.fcc.gov/broadbandlabels (https://www.fcc.gov/broadbandlabels?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.cve.org/ (https://www.cve.org/?utm_source=thinkingelixir&utm_medium=shownotes) - https://erlef.org/wg/security (https://erlef.org/wg/security?utm_source=thinkingelixir&utm_medium=shownotes) Guest Information - https://www.linkedin.com/in/alistair-woodman-51934433 (https://www.linkedin.com/in/alistair-woodman-51934433?utm_source=thinkingelixir&utm_medium=shownotes) – Alistair Woodman on LinkedIn - awoodman@erlef.org - http://erlef.org/ (http://erlef.org/?utm_source=thinkingelixir&utm_medium=shownotes) – Erlang Ecosystem Foundation Website Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern)
Justin Uberti, creator of WebRTC and now Founder of Fixie.ai, shares insights into the development of AI.town, a platform for engaging with AI personalities through voice, and the potential impact of conversational AI on various industries.Please support this podcast on Patreon! http://www.patreon.com/aiinsideshowINTERVIEW TOPICS- Introduction to Justin's background (WebRTC, Hangouts Video, Duo, Stadia)- The shift towards conversational AI and voice interactions- Fixie.ai and AI.town - enabling voice conversations with AI characters- Transitioning from text-based to voice-based AI interactions, potential use cases- Creating AI characters, enabling role-play conversations- Ethical considerations and voice cloning technology- The nature of human conversation (filler words, turn-taking protocols)- Incorporating human conversational quirks into AI speech- V1 vs V2 voice technology (speech recognition - text - speech vs. direct speech-to-speech)- Open-source speech AI model Ultravox.ai, leaderboard for fastest AI models (thefastest.ai) Hosted on Acast. See acast.com/privacy for more information.
We try Omakub, a new opinionated Ubuntu desktop for power users and macOS expats.Sponsored By:Core Contributor Membership: Take $1 a month of your membership for a lifetime!Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices!Kolide: Kolide is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps.Support LINUX UnpluggedLinks:
This is a recap of the top 10 posts on Hacker News on March 18th, 2024.This podcast was generated by wondercraft.ai(00:33): YouTube now requires to label their realistic-looking videos made using AIOriginal post: https://news.ycombinator.com/item?id=39746468&utm_source=wondercraft_ai(02:08): 900 Sites, 125M accounts, 1 VulnerabilityOriginal post: https://news.ycombinator.com/item?id=39742422&utm_source=wondercraft_ai(04:07): Dear Paul Graham, there is no cookie banner lawOriginal post: https://news.ycombinator.com/item?id=39742578&utm_source=wondercraft_ai(05:43): Stability.ai – Introducing Stable Video 3DOriginal post: https://news.ycombinator.com/item?id=39749312&utm_source=wondercraft_ai(07:38): Cranelift code generation comes to RustOriginal post: https://news.ycombinator.com/item?id=39742692&utm_source=wondercraft_ai(09:19): EPA bans asbestos, a deadly carcinogen still in use decades after partial banOriginal post: https://news.ycombinator.com/item?id=39746806&utm_source=wondercraft_ai(11:05): WebSockets vs. Server-Sent-Events vs. Long-Polling vs. WebRTC vs. WebTransportOriginal post: https://news.ycombinator.com/item?id=39745993&utm_source=wondercraft_ai(12:42): Nvidia CEO Jensen Huang announces new AI chips: ‘We need bigger GPUs'Original post: https://news.ycombinator.com/item?id=39749646&utm_source=wondercraft_ai(14:35): Elegant open source project tracking, Trello like but self-hostedOriginal post: https://news.ycombinator.com/item?id=39742114&utm_source=wondercraft_ai(15:59): Paris cycling numbers double in one year thanks to investmentOriginal post: https://news.ycombinator.com/item?id=39744932&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai
In this special episode, we kick off a brand-new series that dives into the world of Elixir—but with a twist. We're exploring the systems surrounding the language and what it takes to support and run a company or team that uses Elixir. Join us as we engage in insightful conversations with various industry voices, starting with Tyler Young, about the practical systems and solutions used by businesses like Felt.com and SleepEasy.app. This series promises to be an enlightening journey for anyone curious about the behind-the-scenes workings of an Elixir-based product. Tune in to hear the unique challenges and successes experienced by others in the field and more! Show Notes online - http://podcast.thinkingelixir.com/191 (http://podcast.thinkingelixir.com/191) Elixir Community News - https://github.com/erlang/otp/pull/8111 (https://github.com/erlang/otp/pull/8111?utm_source=thinkingelixir&utm_medium=shownotes) – Erlang's potential new OTP json module is showing significant performance improvements in recent benchmarks. - https://twitter.com/michalmuskala/status/1759932700624912832 (https://twitter.com/michalmuskala/status/1759932700624912832?utm_source=thinkingelixir&utm_medium=shownotes) – Michał Muskała shares insights online about future Elixir idiomatic wrapper around the new OTP json module. - https://www.erlang.org/news/167 (https://www.erlang.org/news/167?utm_source=thinkingelixir&utm_medium=shownotes) – OTP 27-RC1 was released with new features like the maybe expression and Triple-Quoted Strings. - https://github.com/erlang/otp/ (https://github.com/erlang/otp/?utm_source=thinkingelixir&utm_medium=shownotes) – Official repository for Erlang/OTP where the 27-RC1 release can be found. - https://twitter.com/uwucocoa/status/1758878453309505958 (https://twitter.com/_uwu_cocoa/status/1758878453309505958?utm_source=thinkingelixir&utm_medium=shownotes) – Tweet mentioning that Erlang 27.0-rc1 runs natively on ARM64 Windows. - https://fly.io/blog/tigris-public-beta/ (https://fly.io/blog/tigris-public-beta/?utm_source=thinkingelixir&utm_medium=shownotes) – Fly.io announces a new globally distributed object storage solution that supports the S3 API. - https://github.com/elixir-webrtc/ex_webrtc (https://github.com/elixir-webrtc/ex_webrtc?utm_source=thinkingelixir&utm_medium=shownotes) – New WebRTC library for Elixir called exwebrtc is introduced. - https://blog.swmansion.com/introducing-elixir-webrtc-a37ece4bfca1 (https://blog.swmansion.com/introducing-elixir-webrtc-a37ece4bfca1?utm_source=thinkingelixir&utm_medium=shownotes) – Blog post introducing exwebrtc, detailing the motivation and development of the new WebRTC library for Elixir. - https://membrane.stream/ (https://membrane.stream/?utm_source=thinkingelixir&utm_medium=shownotes) – Membrane Framework site; although exwebrtc was created due to certain challenges with Membrane, Membrane is noted for its pipeline model. - https://www.w3.org/TR/webrtc/ (https://www.w3.org/TR/webrtc/?utm_source=thinkingelixir&utm_medium=shownotes) – The W3C WebRTC specification, which exwebrtc implements in Elixir, is more JS focused. - The Erlang Ecosystem Foundation recently celebrated their 5 year anniversary, highlighting the community's achievements. - https://github.com/gleam-lang/gleam/releases/tag/v1.0.0-rc2 (https://github.com/gleam-lang/gleam/releases/tag/v1.0.0-rc2?utm_source=thinkingelixir&utm_medium=shownotes) – Release of Gleam v1.0.0-rc2 which includes a bug fix for the compiler. - Announcement about ElixirConf US, with a call for training classes and upcoming call for talks. Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Discussion Resources - https://felt.com/ (https://felt.com/?utm_source=thinkingelixir&utm_medium=shownotes) - https://sleepeasy.app/ (https://sleepeasy.app/?utm_source=thinkingelixir&utm_medium=shownotes) - https://twitter.com/TylerAYoung/status/1730253716073148470 (https://twitter.com/TylerAYoung/status/1730253716073148470?utm_source=thinkingelixir&utm_medium=shownotes) – Tyler shared on X when he bought his physical hardware - https://sentry.io/for/elixir/ (https://sentry.io/for/elixir/?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.appsignal.com/elixir (https://www.appsignal.com/elixir?utm_source=thinkingelixir&utm_medium=shownotes) - https://felt.com/blog/startup-and-shutdown-for-phoenix-applications (https://felt.com/blog/startup-and-shutdown-for-phoenix-applications?utm_source=thinkingelixir&utm_medium=shownotes) - https://retool.com (https://retool.com?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.heap.io/ (https://www.heap.io/?utm_source=thinkingelixir&utm_medium=shownotes) Guest Information - https://twitter.com/TylerAYoung (https://twitter.com/TylerAYoung?utm_source=thinkingelixir&utm_medium=shownotes) – on Twitter - https://github.com/s3cur3 (https://github.com/s3cur3?utm_source=thinkingelixir&utm_medium=shownotes) – on Github - https://fosstodon.org/@tylerayoung (https://fosstodon.org/@tylerayoung?utm_source=thinkingelixir&utm_medium=shownotes) – on Fediverse - https://tylerayoung.com/ (https://tylerayoung.com/?utm_source=thinkingelixir&utm_medium=shownotes) – Blog Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern) - Cade Ward - @cadebward (https://twitter.com/cadebward) - Cade Ward on Fediverse - @cadebward@genserver.social (https://genserver.social/cadebward)
Russ d'Sa is Founder of LiveKit, the real-time streaming audio, video, and data infrastructure platform for developers. Their open source project, also called livekit, provides the end-to-end stack for WebRTC and has over 6K stars on GitHub. In this episode, we dig into LiveKit's unique founding story with the idea coming from the founders' experience building a Clubhouse competitor and using Agora, early interest from companies like Pinterest that gave indications that there was a need for an open source alternative to Agora and Twilio, why Conversational AI will be a big driver for LiveKit & more!
Elon quiere la GPU de tu Tesla / Aviones espía para encontrar tesoros / ESA + SpaceLab / Aerotaxis en Nueva York / Nvidia sorprende con las nuevas H200 Patrocinador: Si eres autónomo o una pequeña empresa, ya sabes que necesitas contar con los mejores. Por eso Vodafone Business presenta la nueva tarifa Negocio a Medida. Tendrás fibra de 600 Megas y dos líneas de móvil 5G, y servicio de reparación y sustitución de dispositivos por tan solo 54,54€/mes más IVA. Elon quiere la GPU de tu Tesla / Aviones espía para encontrar tesoros / ESA + SpaceLab / Aerotaxis en Nueva York / Nvidia sorprende con las nuevas H200
Ayush Ranjan is the Co-Founder and CEO at Huddle01, whose mission is to democratize WebRTC and make it more private, secure, and scalable. Why you should listen Huddle01 is building a decentralized real-time communication network. Developers can leverage their suite of developer-friendly SDKs to enable powerful audio/video experiences on your app with just a quick plug in. Ayush talks about privacy concerns with video communication platforms like Zoom and how that led him to create Huddle01, a peer-to-peer video calling platform with added layers of security and scalability. Ayush explains how WebRTC works and its evolution from peer-to-peer to server-based communication. He highlights the challenges of centralization, such as lack of content encryption and latency issues caused by distant servers. Ayush discusses the concept of a people-powered communication network, where individuals can become nodes and power calls without relying on centralized servers. This leads to increased privacy, reduced latency, and the creation of a new bottom-up economy. Ayush also highlights features of Huddle01 that differentiate it from platforms like Zoom, such as seamless integration with popular streaming sites, enhanced privacy options, crypto primitives for avatars, and cheaper call recordings using filecoin storage. Andy acknowledges the importance of building user-friendly platforms regardless of users' familiarity with web3 technology. The conversation then shifts to the concept of "DePIN," which refers to leveraging blockchain technology for decentralized physical infrastructures. Examples include Helium's approach to creating a decentralized 5G mobile network and Filecoin's role in enabling individuals to become storage providers. The discussion concludes by emphasizing the need for more affordable communication infrastructure in order to reduce costs currently associated with centralized systems. Ayush describes the different layers of Huddle01, including the app layer for consumers, the SDK layer for developers, and the protocol layer for miners and validators. Ayush envisions a future where Huddle powers all communication platforms, making calls more immersive and solving global problems more effectively. Looking ahead, Ayush sees a utopian future where humans explore outer space and achieve higher levels of energy consumption through advanced infrastructure systems like Dyson Spheres. Supporting links Bitget Bitget Academy Bitget Research Bitget Wallet Huddle01 Andy on Twitter Brave New Coin on Twitter Brave New Coin If you enjoyed the show please subscribe to the Crypto Conversation and give us a 5-star rating and a positive review in whatever podcast app you are using.
Ubuntu 23.10 ‘Mantic Minotaur' is out! Focusrite helps out a Linux developer, Debian Bookworm powered PiOS, and self-hosting your own WebRTC server.
In this podcast, Christian Stredicke, CEO and President of Vodia, and Doug Green, Publisher of TR, discuss how in-office and intra-company video calling is making the post-Covid workplace more spontaneous, more human and perhaps even more fun. Christian and Doug discuss how video calling can help build trust in hybrid/remote environments, and the real-time combination of voice, text and video will ultimately become the new norm for office cultures. "If you think about it," Christian says, "having a video call in your private bedroom would have been unthinkable, but today's it's normal, so a lot of things have changed and I believe it will go on." Christian and Doug also discuss the challenge of translating between SIP and WebRTC via a cloud PBX, so everyone in a company can talk to everyone else, no matter their device of choice. Visit www.vodia.com
Join us for an inspiring episode of the Degree Free Podcast, where Sean Dubois shares his personal journey of finding tech success without a degree. He discusses how working at Amazon opened doors for him and made job interviews easier. Sean encourages listeners to prioritize personal growth and happiness over societal expectations. Key Discussion Points: - Sean and Ryan talk about programming and open-source projects, emphasizing the importance of solving problems you're passionate about and saying yes to opportunities. - They discuss the benefits of open source projects, such as having control over your destiny and contributing to projects you care about. They also mention the challenges and rewards of creating your own projects. - The importance of self-discovery and self-actualization in motivating oneself to work hard and succeed is discussed. They highlight the inner motivation to persevere through failures as being more important than specific programming languages or projects. - Sean talks about finding a niche in the WebRTC space and the concept of doing things in public to create opportunities and connections. They also challenge the significance of job titles in the software industry. - The conversation tackles the relationship between money and happiness, acknowledging that while money doesn't guarantee happiness, it can provide financial stability and freedom. Personal anecdotes about the impact of financial stability are shared. - The episode ends with Sean explaining why he helps others, emphasizing paying it forward and the mutual benefit of helping motivated individuals. Ryan reflects on his own experiences and expresses a desire to do more. - Sean advises that solving personal problems, finding self-confidence, and enjoying what you do can lead to career success and fulfillment. Don't miss this enlightening episode of the Degree Free Podcast, where Sean Dubois and Ryan Maruyama share their experiences and insights on success, personal growth, and finding happiness. Tune in and be inspired! To keep up with everything Degree Free check out our website: degreefree.co Join the Degree Free Network and get the support you need to get hired, get that promotion, and achieve your career goals! You'll get access to our free resources such as the 5 Degree Free Pathways and 7 Day Get Hired Challenge Course: degreefree.co/network Learn job hunting skills and learn how to land your dream job in 7 days: degreefree.co/gethired/ Starting your degree free journey but don't know where to start? Check out our free ‘5 Degree Free Pathways' Course: degreefree.co/pathways
In episode 131 of Jamstack Radio, Brian speaks with Christian Stuff and James Hush of Daily. This talk explores virtual meetings, WebRTC, and video technology. Christian and James share insights on building a video call experience in the browser and rising to the demand in recent years for world wide virtual events.
In episode 131 of Jamstack Radio, Brian speaks with Christian Stuff and James Hush of Daily. This talk explores virtual meetings, WebRTC, and video technology. Christian and James share insights on building a video call experience in the browser and rising to the demand in recent years for world wide virtual events.
The 16:9 PODCAST IS SPONSORED BY SCREENFEED – DIGITAL SIGNAGE CONTENT Using existing network infrastructure has long been talked up as an efficient way to manage and deliver digital signage solutions in large companies, but the concept has been clouded by concerns - like the cost of additional AV hardware and the impact of all that video on the company network. But we now live in a world where companies support countless video conferencing sessions with piles of users, with little or no latency. Other technologies have also caught up, and computing just keeps getting more powerful. Which is why I was interested in chatting with Shane Vega, VP of Marketing for the Silicon Valley software firm Userful, about his company's AV over IP solutions. The company has its roots in Calgary, Alberta and still does a lot of the R&D work there. Userful first showed up in digital signage circles talking about a different way, using software and endpoints, to drive video walls. But in the last few years it has been much more focused on a broader IP-driven solution that tends to start with control rooms and operations centers, but can also drive things like meeting room displays and digital signage around corporate campuses. There's been a lot of discussion about AV needs converging with IT interests, but from Vega's perspective, that convergence is already firmly in place. Subscribe from wherever you pick up new podcasts. TRANSCRIPT Shane, thank you for joining me. Where are you today? Shane Vega: I am in sunny Tampa, Florida, where although it's not all that sunny today, we've got some rain, but that's per the norm now. Now, Userful is in Silicon Valley, but a lot of the developers are in Calgary, right? Shane Vega: Yeah, that's correct. All of our R&D, engineering team, and the like, they're all up in Calgary, Canada. So you're missing the Calgary Stampede this week? Shane Vega: I am missing the Stampede. But you know what, I believe they deserve a bit of some good time because they spend the majority of the time avoiding the minus 30-degree weather. Yeah, I spent a number of years in Calgary, and it's an interesting weather city. Shane Vega: Yeah. You know it's bad when they've developed an entire infrastructure of walkways between buildings to avoid having to go outside. Yeah, just like Minneapolis. Shane Vega: Exactly. All right, so we had a quick chat in the LG booth at Infocomm, and you explained what Userful was up to with its Infinity platform and AV over IP and AV as a Service and so on, and I've seen that. I will wholeheartedly admit I don't totally get it, but how you explained it to me was very interesting, and I thought this would be useful for a lot of people to understand the infrastructure and distribution side of digital signage. We spend so much time talking about the content and business strategy and all those sorts of things, but behind-the-scenes stuff is awfully important, and maybe we could start out by just explaining what Userful is and does and where you came from because when Userful first came out, it was presented to me as video wall software, and I had a hell of a time wrapping my brain around what it was all about. But I know you guys have evolved quite a bit. Shane Vega: Yeah. I appreciate that, Dave. To answer your question, Userful has grown exponentially in the last 5+ years. John Marshall, our CEO came on board about 7 years or so ago. My timing might be a little bit off, and when he came into the organization, we were a perpetual software company, so we weren't software as a service, we weren't selling subscriptions. We were selling perpetual software… You'd buy a license and then get that supported? Shane Vega: Yeah, you'd buy a license then we support it for the duration of however long you wanted to use it, and the license for the software was pretty siloed, right? It was, “Hey, you can buy this operations center license.” Where, to your point, we were just managing content on a video wall. And it was mostly control rooms, right? Shane Vega: Mostly control rooms, almost exclusively for a time, and then we evolved into the digital signage world, and it was cloud-based digital signage exclusively. So what most folks are familiar with is hosting up in AWS, giving you some access to dynamic tools for creating templates and the like. During Infocom, what we've launched and from the time that I just mentioned until about, maybe two and a half years ago or three years ago, we've pivoted the company from perpetual to subscription-based software as a service, and that's who Userful is. We are a software company, and we've been a software company tailored to the needs of the AV industry. Most currently, we've just released our newest platform, and that's really been the biggest evolution, which is moving away from application-specific deployments into more of a platform approach for AV over IP and that is really the biggest breakthrough development that we've had here, because in the older version of our software, we were a monolithic code base. Again, we were just selling either the operation center software or we were selling some digital signage. Everything was monolithic. It was difficult for our engineering team to manage updates, firmware, bug fixes, and the like. We've now moved to a distributed code base that has given us exceptional flexibility with how we develop our software for the various use cases and applications in the AV industry. So if you think about what you've seen in the conversations you and I have had, essentially, and you hit the nail right on the head, this isn't just about fancy software managing content on a video wall. Can we do that? Of course, we've got feature sets for various different use cases, but there's also the infrastructure piece, and this was my “aha moment” through a different lens at Infocomm. AV over IP has matured through the years from IP addressable matrix switchers where everything was still very much centralized into IP addressable nodes, encoders, decoders, transmitters, receivers, and all the different AV manufacturers out there have now standardized on this proprietary hardware version of AV over IP, and I started to ask myself the question: what is their value proposition in doing that? And I overheard quite a few folks during this past Infocomm talk about the value of this distributed architecture: enabling flexibility, scalability, augmenting workflows, the total cost of ownership being lower, and I sat there a little bit baffled because these are all the same things that we talk about at Userful and so it really opened up an area where I feel like we do need to evangelize a little bit more about how Userful do AV over IP differently, and that we don't necessitate all of the hardware infrastructure. We truly are a software platform, but because of the IT protocols that currently exist, that's how we developed our software. So when you think about Userful, I've actually positioned us a little bit more as an IT solution than an AV solution, even though our entire solution is built around the AV industry and its needs. The reason I say that is because we're literally a server, non-proprietary, and an endpoint, and that endpoint is software, so our uClient application. In between the two is network infrastructure. There are no end encoders, decoders, transmitters, receivers, and the list goes on. Because we are able to transmit content and aggregate content, meaning we can pull in sources of visual information and audio information into a data library or data store that we manage on our server and distribute that information to any destination or any screen and we do that all with IP protocols. The same IP protocols, by the way, and this is how I usually get people to have the “aha moment.” If we were having this over a Teams meeting, Dave, or a Zoom meeting, we would be transmitting video two ways. In many cases, multiple participants from multiple regions of the world share two-way audio and video. We would be able to share content from our local computers into that meeting, and nobody would have to go out and buy a proprietary encoder and decoder to make that happen. So using that same infrastructure or those IT protocols that are currently at work, IP protocols like WebRTC for instance, we're able to build a solution that leverages those same advancements for the purposes of AV over IP. It's a bit of a mouthful, but that's what we're doing. So you wouldn't have been able to do some of that 10-15 years ago because the network infrastructure is a lot of larger corporations hadn't really caught up with that, so you would flood a network if you were using a lot of video and so on, but things have changed. Shane Vega: Things have changed substantially, and I would even say it's been not even 10-15 years ago, just 5-10 years ago, and the reason I say that is because there are the laws of engineering and physics like Butter's Law, Kryder's Law, Moore's Law, which talks about how rapidly the advancements of, let's say, fiber optic networks, which are doubling every nine months, the amount of bandwidth that you can get between the fiber optic cable or the amount of processing speed that you can get out of a CPU and how fast these advancements are happening. What we're doing and the way that we're doing it is taxing the CPU of that server. It's also taxing the GPU of that server, the graphics card because those are the two major components that we use for our solution. If you think about just two years ago, Dave, our servers that we were deploying in the field were 8 cores of processors. Right now, I have a server that we've certified that's 192 cores of processors, so we're able to do exceptionally and exceedingly more on a single server, which is why we've actually built our solution to be a data center solution by and large, where you take a big beefy server, you put it in your data center, and you're virtualizing all of the traditional hardware that you would need, and you're managing a wide range of AV endpoints, whether it's digital signage, meeting rooms, operations centers, or what have you. Is there a baseline for what you need in terms of the network infrastructure? I'm definitely not an IT Architect, but do you need a CAT6E, or can you do this over Wifi, I don't know, and I suspect a lot of people don't know. Shane Vega: Yeah, so it's a good question. So again, because we're optimizing for IT protocols, we're able to do a lot, right? From the screen to the switch, we're just really looking for that one-gigabit uplink, which is standard. Most folks are going to have that. From the server to the source to the server and all that infrastructure pulling into the server, we're looking for the 10 gigabit uplink. So there are some requirements for the network, but nothing that is outside the realms of standard network topology. The real intricacies or the real areas where we get into some deeper discussions are when they have multiple networks that we have to traverse. When you start getting into DOD environments where things have to be air-gapped and there's no internet connectivity and when networks start to get a little bit more complex, that's where we have to begin to get a little bit more intentional about how we design it. Now that said, we haven't yet met a deployment that we couldn't meet the network requirements for, even though some of those were those complex ones. There were two things that particularly interested me. The first was, as you laid out earlier, that you don't need all these encoders and other bits of hardware to layer into a network to make this happen. So you're cutting out conceivably a lot of capital costs and a lot of potential fail points, and I guess the other thing that intrigues me, and you can talk about that next is or after. The first question would be the idea that you can use this for multiple aspects. I suspect there are control room data dashboards, and software platforms out there, but one of the things you talked about at Infocomm is that you can cascade this out to do all kinds of different things from operation centers to experience centers off of the same platform. Shane Vega: Yeah, exactly, Dave, and to answer the first question, you hit the nail on the head with one of my areas of confusion when I was at Infocomm, and I heard people talking about the low total cost of ownership, and they were tying it to these encoders and decoders. We don't require those things. So when I think about the total cost of ownership, I think about the hard work upfront costs that you don't need to have and the additional BTU output from all of that hardware that you would normally need, that's no longer going to be there, which is going to drive your HVAC costs, right? You don't have all the power consumption. So for green initiatives and companies who are looking to do things, and this is a big one moving forward, folks want to be more green, and get green initiatives going like lower carbon emissions, lowering power consumption by not having all that hardware is yet another total cost of ownership benefit for Userful. Again, our encoding happens at the one server that we require in that Nvidia graphics card. The decoding is done by a piece of software we developed called the uClient application. Now, where that uClient application resides, we give you tons amount of flexibility. We have integrated it into certain endpoints like Web OS or Tizen or Android. And that gives us the flexibility to be able to load that client application in various different environments and use cases, depending on the display type if it's an LCD, if it's a direct view LED, and how we manage that. In some cases, we do have a small appliance that you might need at the edge, and that would be one additional piece of hardware per display, depending on the display type, and that's an Android box that we load our uClient application onto if the display doesn't have the ability to integrate with our software. So if it's a smart display that already has a system on a chip on it, conceivably you don't need that Android box? Shane Vega: Correct. So now what you're left with, as I said, is just a server with software at the edge, and network infrastructure in between. So ongoing maintenance costs are substantially lower. Initial hardware costs are lower. Your total cost of ownership around all the things I mentioned earlier is going to be lower. Therefore, your refresh costs are going to be lower. Because with hardware, every three to five years, in some cases five to seven years, you're having to do a hardware refresh. It's always tied to CapEx because it's usually proprietary. They have to budget for CapEx renewals of all this hardware. Because of Userful's deployment model, we can take on an OPEX model for those folks who would benefit from that because your hardware refresh can be built into your standard IT refreshes because you own the hardware. In many cases, as many as we can possibly, push for, we don't provide the server, we want the end user to provide the server, and that way, it gets built into your traditional OPEX refresh, and that way, the only recurring cost is the software. To your next question about what we spoke about and the benefits of the platform. This is where our software really begins to shine, right? Because our platform is accessible through a web browser, so no proprietary software needs to be downloaded for a user to access it. You access our software through a traditional HTML5 web browser. Once you access the software through a web browser, the first thing you're going to notice is we have six applications that any user can take advantage of. In most cases, folks aren't trying to eat the elephant hole, right? They'll have a use case like digital signage, or they'll have a use case like meeting rooms or experiential centers or what have you, and that's one of the reasons why we are licensing the server. We're licensing the CPU cores and the number of graphics cards that you need on that server so that if you have a smaller use case, your out-of-pocket costs are gonna be lower because you need a smaller server. But when you log in for the first time, you're gonna see, “Oh, I got this for digital signage, but I didn't know I could run my meeting room here.” or, “I didn't realize that I can do these artistic video walls,” or “I didn't realize I can incorporate these data dashboards from Power BI or Tableau as a native source and share those to any display that Userful is managing.” The value is seen almost immediately, and so what we do is try to help people understand the peripheral or parallel use cases. So I use digital signage quite a bit, and I gave you this analogy regarding airports at Infocomm, Dave, where at least half a dozen times in the last six to eight months, I've had conversations with various airports, and most of them are pulling us in because they have an operation center. Airport operations center, or security operations center, or what have you, and they'll say, “Hey, we want the Userful software to run the content on these displays and video walls in the operation center,” and when we have these discovery calls, I'll typically ask, “Hey, have you guys thought about the advantages of using our platform to help you with the signage?” And I'm usually shot down rather immediately, and most folks know Airports are convoluted in the way that they deploy their technology. They got various different groups. They're typically siloed, but specifically the airport operations centers, I'll just say, “Hey, look, I get that, but let me just throw this use case out there and see if it lands and hits you as showing value.” You're in an airport operations center. Wouldn't you want to be able to manage the entire network of screens that are currently being used to show baggage, arrivals, departures, signage, and all your wayfinding screens? Would it not be valuable to be able to manage those as part of your airport operations, also, I've noticed in many cases, they'll incorporate security into their AOC. Some of them have independent security operations centers, but in either event, I would tell them. What happens if you have an incident at the airport? Wouldn't you want to be able to take over those screens from the command center that's responsible for monitoring and sending strategic messages to people, depending on what the situation is? If there's a fire, “evacuate.” If god forbids, there's an active shooter, “take shelter in place,” and be able to send strategic messages to various screens all from within your operation center? Well, you can't currently do that because you've got multiple systems driving all of these different AV endpoints. If you had a single platform, it doesn't just give you the ability to scale your deployment, it gives you the ability to scale your workflow and become more flexible to augment those workflows where I can send strategic messages to screens, I can manage arrivals and baggage from my AOC, if that's such a thing that I need. In addition, we could help you with your meeting rooms. You can walk into a meeting room, and I can help you cast some content in a meeting room and have an impromptu meeting on a drop of a dime, as just a few use cases of what our platform can do. Sometimes, when you have these platforms that say they can do, in your case, at least six different things, there can be compromises. In other words, “Yeah, we can do all these things. That's just none of them are particularly deep, or maybe one of them is deep, and the other ones are so so.” Do you get that question at all? Shane Vega: Ironically, no. We don't get that question. But it's a question most people should be asking David, and I'll tell you that when that does come up, and it's only come up a handful of times, I'm always very candid about what we can't do as well as what we can do. And there is truth in the fact that we are software as a service, and so there are certain applications that still have roadmap features, candidly, that we're going to continue to augment and build them out. If you could probably imagine the top three or four of our use cases would be: operations centers, digital signage, meeting rooms, and data dashboards. We do those very well. With experiential environments, we manage those artistic video walls very well. Now when you talk about experiential environments, there are some things that some folks might want to get involved with, but we might have to have some deeper conversations, right? And that really is around interactivity. Do you want multi-touch video walls, like in a museum for kids or something like that? Where we have some roadmap items to help ensure that multi-touch is what people would expect, where you don't want to have the lag, you don't want to have any of those issues when people are trying to have that fun experience as a child or what have you. So there are certain features that are still roadmap items, but what I will bookend that with is, before coming over to Userful, I worked with one of the larger AV firms globally, and while I worked there, part of my interaction with customers was, “Man, I wish I could do more of these things with a single solution, I have to farm it out to so many folks.” But more than that, I would have feature requests for the stuff that was out there, and it was always in one ear, out the other. I don't care which manufacturer it was. If I went to some of these larger manufacturers and I said, hey, you really would benefit if you did this or this. It just didn't go anywhere, and then I had a similar conversation with the Userful back in about 2018 at a trade show, I said, look, your software is good, but it really needs these four or five things to really be a competitor in the space that you're looking to deploy, which at the time it was operation centers. I'd say if it was six months, it was a long time. So within six months, I got a call from the then VP of Sales who said, “Hey, I want to have a meeting with you, Shane. We've incorporated all of your requests into our software,” and that really pivoted my approach to looking at users as, alright, these guys are the future of AV and, little FYI, we actually got that award at Infocomm, the Future of AV award. But the reason for that was, look, if we're going to be software as a service, then we have to prioritize feature requests from our customers above our own market research or our own gut check, and so that's part of my role here at Userful as VP of Marketing is that I'm also over Product Marketing, which is over the roadmap, and so I get involved in customer calls quite a bit, and I'll hear some of these features that to your initial question is, “Hey, how do you go deeper with these applications?” I look for that feedback, and then I get to go back to the roadmap and go, “Hey, we need to prioritize this, this, and this feature. Push out the other features to the next release. Let's get these done because it's revenue dependent. We've got customers who would value this. Let's get it done!” We take that very seriously here at Userful, and we're at four releases a year, so you'll never have to wait all that long. So you referenced Airports. I'm curious, in the context of third-party software development, if there's a software company that works in the Airport realm but isn't doing digital signage or some of the things you do, but they want to visualize information on displays, is there an API or something that they could develop to work with Userful or does it have to be Userful development to add that capability on? Shane Vega: We have an entire program around API. So we do have our own API, currently, it's A REST API, so we can receive tons of different messages and calls to trigger certain reactions within our software. But additionally, that's got its own roadmap in and of itself. So we have our software application roadmap, and then we have our API roadmap where we're going to be developing even deeper integrations and capabilities including, but not limited to, even wanting to create possible easy configuration tools for customers who can use our API to do whatever they want, onsite. Are control rooms and operations centers the gateway for the initial point of contact, the thing that gets people interested, and then other things cascade out of that? Shane Vega: That has been our experience. We call that our land. So we're land and expand through our platform. Let's find the use case. Let's land where it makes sense, and then let's show the power of our expansion, and just because of how the company has evolved, operation centers have been kind of the tip of our spear, and it makes sense because operation centers will use two or three of our applications out of the gate, right? They'll use the operation center software, they'll use meeting rooms for war rooms or situation rooms. They'll also use our trends for dashboards and Power BI integrations, depending on what type of operation center it is, so they usually get value from several of our use cases and applications out of the gate. And if it's a large enough organization and we're typically targeting LDOs (large distributed organizations), they'll have multiple operations centers, which gives us multiple points of connection and interaction and engagement to open up opportunities to talk about the meeting rooms beyond your war room and situation room, or some operation centers are fishbowls, where they want to bring folks in their data center and they just want to use it as a showpiece to show their customers how well they manage their data, and so they might have welcome screens outside, and we'll let them know, “Hey, we can manage those welcome screens for you as well,” and that evolves into a larger digital signage strategy, corporate communications, so on and so forth. These large organizations, do they have separate AV and IT departments, or are they pretty much hiving into IT now? Shane Vega: So more and more, IT is taking over, but what's happening is it used to be that they have AV specialists on staff, and by and large, it was for the meeting rooms, and in some cases, the digital signage where they had AV technicians or AV specialists on-site, and those were the guys were the gatekeepers to decide what technology gets deployed. Yeah, and get everything working before the meeting starts somehow. Shane Vega: Exactly. “Who's got HDMI? Who's got DVI?” So to that point, people keep talking about the convergence of AV and IT, and I don't know why. That convergence happened years ago. People are now starting to realize that because of that convergence, the IT organization or the IT departments within these larger organizations are going to be the ones holding the budget and are going to be the ones responsible for managing any AV resources on the network. And so, we have intentionally built our product to cater to those IT stakeholders in the organization. When you say things like, “Hey, you can centrally monitor the entire platform from a web browser,” they really get that right. When you say, “We're an IT solution, we're not an AV solution, which means we're not going to put all this IP addressable hardware on your network,” a lot of the walls come down from their security concerns. You then begin to tell them that, look, you can augment your roles-based access control, and integrate with LDAP. Plus, we give you tools that are IT specific to help you monitor things like, what is the impact on my network? What is my current CPU utilization, or what's my current GPU utilization on the server that we're licensing? We give them all of those tools built into our software. So it's not just AV end-user tools that we're giving. We're also giving those IT tools that help the IT stakeholders manage deployments because we recognize these are going to be larger in scale. They're going to be responsible for a lot. Let's make it easy for them. When you talk about AV as a service, it's a term I've heard for a while, but you guys go at it quite a bit differently from what you're saying. Shane Vega: Yeah, we do, and Dave, I struggle with that, because we were flirting with the term AV as a service, and we started to use it quite a bit. But I know, coming from the integration world, that AV as a service historically meant we're going to just finance this stuff, right? We're going to get a leasing program, and we're going to build in the hardware, the software, the services, whatever we can into a monthly payment that makes it nice and easy for you guys. We approach it differently by saying, we are software as a service that's for the AV industry. Therefore, we are AV as a service, meaning, we don't have all that hardware that you have to purchase. You're truly able to deploy all of these AV use cases and manage an entire host of AV applications from within our platform. And we are a software that you pay for based on subscription, typically three-year plans. That's what we mean when we say AV as a service. It's exactly that. It's a software as a service, which is which is the actual term, which is software as a service for the AV world. This strikes me as something that probably has a learning curve, as every software platform does, but it is almost something you kind of have to ease your way into? Shane Vega: Believe it or not, not really, and I think that would be more pertinent if somebody was wanting to say, “Hey, I want to use your entire platform right now.” But as I said earlier, most folks are saying, “Hey, I want this operation center,” and they're familiar with Operation Center softwares. They know what they want. They know they want to be able to build custom layouts. They want to manage big, beautiful video walls. They want to be able to interact with sources with soft KVM functionalities so that they're not just visualizing the sources but they can engage with them because they've got tools, right? They got video management tools, and they've got access control, what have you, and so that software that we're providing isn't going to look and feel a whole lot different than a lot of the other softwares they're used to using. Now, we do it differently. So the real benefit, rewinding all over to the beginning of this conversation, is, yes, we're giving you all these software applications and features, but it's the infrastructure that really differentiates us. Along with removing different hardware components from this kind of a network, you're also removing potentially different software applications that you'd also need because you've got this stack of different things you can do? Shane Vega: Yeah, exactly. To that point, Dave, when I showed this at Infocomm, when I gave my demos there, typically when you deploy an AV solution, let's call it digital signage, that's the background that you're most familiar with. In digital signage, let's say, you use it for corporate communications; you'll have screens all over the office. In some cases, they'll want to be able to integrate that digital signage into their meeting rooms as well, and when the screens are in standby mode, they want to be able to have some of those corporate communications as part of the digital signage strategy, managing those meeting rooms. But when you go into the meeting room, they'll typically need some type of infrastructure to support those meetings and local collaboration. Usually, it's a network of AV infrastructure, HDMI cables, or what have you, go into some form of a matrix switch that's going to be some type of tablet controller that can give you the ability to manage what laptop is being viewed on what screen. With Userful, because the software does so much, the screens that we manage are not tied to any one specific application, and that's really the beauty of it. So I can walk into a room where they're showing corporate communication. I can sit down, open my laptop, and immediately start a meeting by screencasting whatever's on my laptop onto the screen in that room without connecting a single AV cable. I could then open up my operations center software on that same screen and turn it into an impromptu war room or situation room where I'm pulling in multiple sources and building out customized layouts, and navigating through a crisis. So there are a lot of things that we can do, and it's not dependent on the screen, and, to your point, we've reduced not just the hardware need but the software as well. All right, Shane, that was super interesting. I know much more about this space than I did half an hour ago. Shane Vega: It's been great talking to you, Dave. I appreciate it.
Allen Wyma talks with Kwindla Hultman Kramer, Founder and CEO of Daily, and João Neves, Staff Engineer at Daily. Daily provides SDKs for building video applications on top of the WebRTC standard using Rust. Contributing to Rustacean Station Rustacean Station is a community project; get in touch with us if you'd like to suggest an idea for an episode or offer your services as a host or audio editor! Twitter: @rustaceanfm Discord: Rustacean Station Github: @rustacean-station Email: hello@rustacean-station.org Timestamps [@00:00] - Introduction to Daily [@05:00] - WebRTC Implementation and sharing across different platform [@10:31] - The challenges of integrating C++ with WebRTC [@19:16] - Signaling in WebRTC - Session setup and initial configuration [@22:45] - Challenges in implementing WebRTC standards [@27:21] - Handling and working around platform and browser differences when implementing WebRTC [@30:51] - Daily's mono repo approach for code sharing [@33:30] - The process of building and releasing code in relation to different platforms and dependencies [@35:57] - Integrating Rust, C, Objective C, and Swift for iOS development [@37:20] - Daily's automated testing processes [@42:24] - Daily's network simulation layer in their testing process [@44:00] - The use of Rust in implementing network simulation for testing purposes [@49:15] - Using WebAssembly alongside native code in an application, and the potential obstacles to consider [@50:52] - Crates that are being used by Daily [@52:44] - What would differentiate Daily compared to other solutions? [@55:48] - Daily vs Zoom [@56:38] - Other open-source projects from Daily [@1:01:20] - Parting thoughts and how to get in touch with Daily Credits Intro Theme: Aerocity Audio Editing: Plangora Hosting Infrastructure: Jon Gjengset Show Notes: Plangora Hosts: Allen Wyma
Kwindla Kramer has always been interested in building things, and his parents gave him lots of opportunity. He spent his early days learning to program on the Commodore 64, and playing old games like Loadrunner. He was super interested in the internet while in College, and in 1996, he got the opportunity to be apart of the MIT Media lab. Outside of tech, he is a quasi vegan, and enjoys the foggy beach living on the western edge of San Francisco.After exiting his last startup, Kwin took some time to figure out what he wanted to do next. During that time, he just started coding on projects, and came across WebRTC, which allowed real time communication for the web. This tech catalyzed a tipping point in his mind, and led him to build video experiments on top of it.This is the creation story of Daily.SponsorsCipherstashTreblleCAST AI FireflyTursoMemberstackLinksWebsite: https://daily.coLinkedIn: https://www.linkedin.com/in/kwkramer/Support this podcast at — https://redcircle.com/code-story/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy
Serene is a hacker in the truest sense of the word. She's applied a hacker mindset to learn coding, piano, and blend art and engineering in fascinating ways. You'll find her collaborating on-stage with Grimes one night and coding censorship resistant technologies the next day. As a self-taught coder she was the first engineer hired into Google Ideas when she was just a teenager. At Google she pioneered work on WebRTC proxies that she continued as a fellow at the Open Tech Fund and was eventually released as a Tor-enabling tool called Snowflake. Serene took a hiatus from working as a full-time engineer to pursue a career as a concert pianist where she quickly gained recognition for her incredible talent. She became one of the few self-taught concert pianists to perform Rachmaninoff's Piano Concerto No. 3 (which I highly recommend checking out on YouTube). Serene is also known for the audiovisual artistry of her shows which is drawn from her own experiences with synesthesia that results in her seeing music as colors. As the conflict in Ukraine started, Snowflake started to see exponential usage patterns as Russian citizens looked to circumvent state censorship and Serene decided to build a company around the technology to enhance development and build independent deployment models. That company is called Snowstorm. With Snowstorm, Serene is focused on saving cyberspace from balkanization and censorship and ensuring that all global citizens have unfiltered access to the Internet. In this OODAcast, we explore Serene's career and then dive into ways we can preserve the original intent of the Internet with censorship resistant and privacy enhancing technology stacks that can be easily deployed and scaled. Official Bio: SERENE is a concert pianist from a most unexpected trajectory. Though she never attended conservatory, her solo performances have been described by The Paris Review as a “spectacle to match the New York Philharmonic”, and today Serene has become one of the most talked about young talents in classical music, and beyond. Beyond concertizing, Serene enjoys other collaborations such as her role as composer for Kanye West's Opera, premiered at Lincoln Center & Art Basel, as well as pianist & technologist with Blue Man Group's founder, bringing futuristic innovations at the intersection of music and technology while also highlighting her own audiovisual synesthesia. Previously, Serene was a computer scientist, Google Engineer, and senior research fellow on various projects, before leaving to fully focus on the piano. In the brief years since, she has cultivated a disciplined, personal, and spiritual approach to her music. With her intersections of many disciplines, plus the “ability to enthrall audiences”, she has grown an international following. Serene is one of very few self-taught pianists who've performed Rachmaninoff's Piano Concerto No. 3, which was described as “unprecedented” —Liszt Academy. Serene loves sharing the beauty and power of classical music with all audiences, everywhere, in all venues ranging from the Vienna Musikverein, to a full orchestra in Golden Gate Park, to a decommissioned Boeing 747. Additional Links: Official Website Snowstorm Serene on Instagram Serene Rachmaninoff Concerto Book Recommendations: A Thousand Years of Non-linear History The Making of the Atomic Bomb The Metamorphosis of Prime Intellect: a novel of the singularity Accelerando
Cloud Connections 2023 CPaaS Showcase Evan Kirstel “What's most compelling are the real word stories about how CPaaS is being used,” says Evan Kirstel, a leading thought leader, writer, podcaster, and influencer, who's B@B practice has paid a lot of attention to the communications sector of technology. In this podcast Evan Kirstel joins Kevin Nethercott, Managing Partner of the CPaaSAA as they discuss what they will be looking for as judges in the upcoming CPaaS Showcase to be held at the inaugural Cloud Connections event next week in Fort Lauderdale. The event is being hosted by the Cloud Communications Alliance. Kirstel describes CPaaS as a type of technology that can deliver the type of breakthrough solutions that AI is beginning to deliver across the technology field. We learn that the judges of the showcase are looking for real world applications. “I think what you're looking to do is to empower innovators and developers to build things we don't have yet,” says Kirstel, noting how apps such as Uber brings together several different technologies such as location, payment, SMS and much more into a seamless customer experience. Kirstel notes that WebRTC began as a novel idea, while now it has become “baked-in”, a path we might see with CPaaS. Kevin Nethercott In this podcast series and at the CPaaS Showcase we will not only learn about the importance of this technology but the larger transformative picture of how this technology is set to revolutionize the way people communicate by voice, by video and much more. Visit Cloud Communications Alliance Visit Cloud Connections 2023 Visit CPaaSAA Visit Evan Kirstel
XFCE 4.18 is out! OBS adds support for WebRTC, Pine64 talks about the PineTab 2, and no Raspi 5 in 2023.
TalkingHeadz is an interview format series featuring the movers and shakers of enterprise communications - we also have great guests. In this episode, we check in with Sid Rao, the GM of Amazon Chime SDK. I fondly remember Biba, a WebRTC video/messaging startup . There was a lot of excitement over WebRTC about ten years ago. Biba was acquired by Amazon and relaunched as the Amazon Chime app in 2017. Chime was a lot like Webex and Zoom, but worked entirely in a browser. Both Vonage and CenturyLink (now Lumen) were early resellers of the meeting application. The app worked well, but wasn't a bit hit. Vonage moved to its own video solution, and CenturyLink turned to apps such as Zoom and Teams. AWS discovered that its customers were more interested in Chime's underlying WebRTC than the meeting app. Amazon created WebRTC APIs, effectively making WebRTC a service rather than a tech stack. This model was a better fit for AWS, so at its reInvent conference in 2018, AWS launched the Chime SDK. Then came the pandemic and a boom in most things video. AWS customers and partners used Chime to create all kinds of solutions. K-12 education, for example, needed video for remote education. Chime obliged, and did so with simple hardware requirements for end users. Blackboard presented its success story at reInvent 2021. As for the original Chime app, it's been getting better thanks to new capabilities of the Chime SDK. The Chime app isn't particular popular,, nor marketed. It does well within Amazon, both as an internal meeting and chat app and with many of AWS's large customers.
What makes Google's new OS so secure, a critical WiFi vulnerability in the Kernel, and why Linus is tapping the hype breaks for Linux 6.1.
Tsahi Levent-Levi LinkedIn profileBlogGeek.me websiteTweaking WebRTC Video Quality Blog Post---------------------------------------------------Join our LinkedIn Group so that you can get the latest video insider news and participate in the discussion.Email thevideoinsiders@beamr.com to be a guest on the show.Learn more about Beamr
mmasakiさんをゲストに、HLSやRTMPなどの配信技術、WebRTCを利用した配信技術とアーキテクチャ、そのスケーラビリティとトレードオフなどについて語っていただいたエピソードです。 話したネタ 低遅延ライブ配信を支える技術 - NTT Com Open TechLunch #1 Smart vLive 配信とは？ YouTube や Twitch 古くはどういう技術で、どのような仕組みで配信が行われていた？ RTMP、MPEG-DASH、HLS HTTPストリーミングでパケットが落ちたらどうなる？ キャッシュ、HTTPにのっかることのメリット HTTPベースストリーミングにおける進化 HTTP Rangeリクエスト CMAF、Ultra Low Latency HTTPベースによる遅延限界は何秒ぐらい？ Sub Secondを狙った WebRTCによる配信 なぜ、HTTPベースの配信は遅延が大きいのか？ 超低遅延配信って、ビジネス的なユースケースってあるの？ End-End はどのような技術で使われている Upstream としてRTMP、クラウド内転送のSRT、DownStreamにWebRTC RTMPってどういうプロトコル？ WebRTCの負荷とスケーラビリティ スケーラビリティと遅延とのトレードオフ 実績では10,000クライアントまで、puppeteerにより確認済み 負荷試験の負荷が難しい GStreamer をRustから制御 FECやRTXは利用している？ WebRTCでプロキシを通す工夫、TURNサーバーの利用 環境が異なるクライアントに対して、体験を高める工夫は？ WebTransport、WebCodecsの現状 43. WebTransport、HTTP/3、WebCodecs w/ yuki_wtz 中途採用募集中: 低遅延ライブ配信サービス「Smart vLive」や、これに続く新たなプラットフォームを開発するソフトウェアエンジニア
Mike Ryan (bluetooth.expert) joins us once again to talk SDR's, bluetooth, and more! If you need some consulting help, you can find him at ice9.us. Here are some links to things we talked about: Episode with Jiska Episode with Michael Ossmann Toorcon Toorcon 13 Badge Ice9 Consulting Web of Make Believe on Netflix Caltrain MTVRE Hacking Electric Skateboards Video @ DEFCON23 Inspectrum Rapid Radio Reversing Talk by Michael Ossmann NRF24 Ubertooth CC2400 Yardstick One Waterfall display/plot OOK FSK URH Baudline GNU Radio Companion Fcc.io Alvaro's Quadcopter Reversing (github) SMC Connector RF Attenuator RF Splitter Natalie's webRTC talk where the fuzzer “Fred” is mentioned WirelessUSB BLE Coded PHY HOGP (HID over GATT Profile) You Can Lose in So Many Colors HackRF BladeRF USRP Polyphase channelizer Wireshark Wireshark's extcap Kismet Dragorn Other Mike Ryans: Michael W. Ryan - Murderer Dr. Michael J. Ryan - Epidemiologist Dr. Michael J. Ryan - Paleontologist Have comments or suggestions for us? Find us on twitter @unnamed_show, or email us at show@unnamedre.com. Music by TeknoAxe (http://www.youtube.com/user/teknoaxe)
What is more annoying than watching the big game, texting your friends about it, and then realizing they're ahead of you by 30 seconds? More than just being annoying, latency actually prevents certain business transactions, like remote-betting or live virtual voting, from occurring. As an avid sports fan and former NHL Board of Governors member Roy Reichbach, CEO of Phenix Real Time Solutions, immediately saw the massive potential for this company. Learn more about how the future for Phenix includes unlocking incredible experiences in the metaverse, as wild as you can imagine, including dancing on stage with Kanye. This is a special part of our Communications Series on #ITVisionaries. Tune in to learn more in this series about the frontier of connectivity, streaming, and communications from experts and executives at companies including Comcast, Zayo, and Axis Communications! Tune in to learn:How Phenix is solving latency issues in video streaming (04:45)What re-analyzing and seeking to improve WebRTC looked like (09:23)How Phenix is built to handle the wide range of video quality, up to 16K (14:02 )How Roy became involved with Phenix (24:29)That Phenix has the speed to be able to run real-time virtual auctions with in-person bidders (29:24)How Phenix is keeping up with the aggressive pace of innovation (32:56)IT Visionaries is brought to you by Salesforce Platform. Did you know, streaming now on Salesforce+ you can watch “Legends of Low Code”? In this series three teams of Trailblazers race to build the best low-code app. Check this out... Mission.org is a media studio producing content for world-class clients. Learn more at mission.org.
What is WebRTC, and why do you want to use it? While at NDC London, Carl and Richard talk to Liz Moy about WebRTC, the open-source library that is used by many of your favorite video chat applications. Liz talks about taking advantage of the hard work already done to control video and audio devices through the browser, as well as the various strategies for actually connecting to other people through firewalls and NAT routers. The conversation also explores where and when you would want to have integrated video, audio, screensharing, and data transfer capabilities.
Jonas Birmé LinkedIn profileEyevinn websiteWHIP protocolWHPP protocolStreaming Media Sweden 2022 Presentation on WHIP and WHPP---------------------------------------------------Join our LinkedIn Group so that you can get the latest video insider news and participate in the discussion.Email thevideoinsiders@beamr.com to be a guest on the show.Learn more about Beamr
What is WebRTC, and why do you want to use it? While at NDC London, Carl and Richard talk to Liz Moy about WebRTC, the open-source library that is used by many of your favorite video chat applications. Liz talks about taking advantage of the hard work already done to control video and audio devices through the browser, as well as the various strategies for actually connecting to other people through firewalls and NAT routers. The conversation also explores where and when you would want to have integrated video, audio, screensharing, and data transfer capabilities.Support this podcast at — https://redcircle.com/net-rocks/donations
Jeni Barcelos is the Co-Founder and CEO of Marvelous, the world's most beautiful all-in-one teaching platform. Chad talks with Jeni about what makes Marvelous different from other teaching platforms out there, the importance of elevating women to leadership positions, and why applying for and getting accepted into an accelerator program was the right path for the company. Marvelous (https://www.heymarvelous.com/) Follow Marvelous on YouTube (https://www.youtube.com/channel/UCJZ_kWoBcXJuSKP1iofXsAw), Instagram (https://www.instagram.com/heymarvelous/), or LinkedIn (https://www.linkedin.com/company/marvelous-software/). Follow Jeni on LinkedIn (https://www.linkedin.com/in/jenibarcelos/). Follow thoughtbot on Twitter (https://twitter.com/thoughtbot) or LinkedIn (https://www.linkedin.com/company/150727/). Become a Sponsor (https://thoughtbot.com/sponsorship) of Giant Robots! Transcript: CHAD: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Chad Pytel. And with me today is Jeni Barcelos, the Co-Founder, and CEO of Marvelous, the world's most beautiful all-in-one teaching platform. Jeni, thank you so much for joining me. JENI: Thank you for having me, Chad. I'm excited to be here and excited for our conversation. CHAD: So I'm really excited to dig into more about Marvelous as well. So why don't we start there? What makes Marvelous different than other teaching platforms that are out there? JENI: Marvelous is different in that we prioritize design, I would say more than any other competitive platform. And we also prioritize live events in a way that I think is pretty unique. So we started in the wellness space. We primarily are serving wellness creators, although all kinds of other creators use our tool as well. So we specifically built Marvelous with the goal of serving their unique needs, which involves a lot of teaching live classes and having a really great community space where students and clients can build relationships with each other. And then, because our audience has a particular design aesthetic and is non-technical, we've created the tool in a way that makes it really easy to make something look beautiful very quickly and simply. CHAD: So what caused you to differentiate yourself based on design? JENI: I think just personal preference and aesthetic, to be honest. As we were building the platform, I realized very quickly that people were choosing us...one of the big reasons people were choosing us was because of the simple nature of the user interface and because of the design that it produced. And so we decided really early to prioritize that. And I would say it's also just I care deeply about design, and I don't like the idea of using tools that make that an afterthought. And so I thought if I'm going to use it, and I do, I mean, we definitely dogfood our own platform and teach our own courses, we run our own communities there, I want it to look beautiful. [laughs] I want it to be a place that people enjoy spending time. We all spend more time, I think, than we want looking at screens. And so when you are going to engage in that practice and engage with other people on the internet, I think it's really nice to do it in a space that feels welcoming, and gentle, and beautiful. CHAD: So you have a co-founder, Sandy. Are either of you designers or have a background in design? JENI: Nope, not at all. Although I was one course away from minoring in art history in school. [laughter] No, I'm a lawyer. So I'm the opposite of a designer, although I think there's a part of me that thinks of myself as an artist. I wish that were my identity. CHAD: So, given the importance of design that you discovered, how did you go about executing on that? JENI: Hiring really great people, I would say, and having a really critical eye. And so, there's a tremendous amount of feedback that goes into our process. And now we have a head of brand in our company, and she can hold space for that design across both marketing and within product. So that hire, I think, has been critical for us to be able to maintain that as a priority. CHAD: Where were you in the product life-cycle and business stage where you were able to hire really great people? JENI: I would say within the last two years. So we are one of these startups that was in the right place at the right time when COVID hit. So luckily and unluckily, maybe we grew really fast in the wake of the pandemic, the beginning of the pandemic. And so that positioned us to hire pretty rapidly over the last two years. And that's when we really had the resources and the capacity to bring in that level of talent. I'll say our creative director was working with us for many years before that but just in a part-time capacity so, you know, running her own agency. And we were hiring her out as we could because we were bootstrapped. And so it wasn't until we reached a certain level of growth where we could bring her on as a permanent fixture in the company. CHAD: Yeah, that's often a way that I hear from founders to help get things off the grounds, particularly if you know of someone and would love to work with them and you know what they can produce, but you just can't afford to bring them on full-time as a member of the team at that point. Contracting with them, working with them part-time can be a great way to get that started. So let's rewind even further and tell me about the fateful day where you and Sandy first met each other. JENI: Yeah, so we first met in Colorado Springs at an entrepreneurship event. And it was for an online program we had both been in that was teaching us how to start a SaaS company. And we are two of the only people that had actually done it and gotten to paying customers within six months, which was a pretty audacious goal, I would say to go from being non-technical and having no experience in the startup world to having a product or at least an MVP with paying customers within six months and no funding. So we were 2 of maybe 5 or 6 people out of 550 in the program who did that. So we automatically kind of gravitated towards each other. And we were two of the only women also in the program. So we met at that event and got to know each other over the course of a number of days and retreated together. And then we just started really being accountability partners to one another as we were each building our own companies independently. And then that went on for another year, year and a half before Sandy joined my company. CHAD: Okay, so you were already working on Marvelous? JENI: Yeah. It had a different name at the time, but yes, I was six months into it when I met her. CHAD: How did you convince her to do that? JENI: We were actually growing...for a solo founder, we were growing to the point that I couldn't manage the company really on my own anymore. And so I applied to an accelerator just because I felt like I had other kinds of career experience but had, again, zero background in tech startups. And so, I came from teaching at a law school and building and scaling a nonprofit. And my background was in politics prior to that. So I had no idea what I was doing. Like, I didn't know what I didn't know, and so that thought scared me. And I just wanted to go immerse myself in an environment where I could ask a lot of questions and have access to resources and mentorships. So anyway, I applied to an accelerator and got accepted contingent on having a team and having co-founders. And I was like, [laughs] well, that's why I need to come here because I don't know how to do that. Like, I don't know how I would do that. And so I reached out to Sandy because I mean, she had been more closely involved in the company than anyone else because we were constantly working together online and going on Zoom and helping each other build our companies. She knew more than anyone else really what was involved. And she was always commenting how she wished she had started [chuckles] a company like this because it's just in the sector. Her background is in clinical wellness, and Marvelous really was serving yoga and wellness teachers. And so I said, "Well, why don't you come on board? I need to have at least one co-founder." Well, I was told I needed to have two, but I convinced them actually to accept me into the program with just one. So Sandy and I went into the accelerator together. CHAD: I feel like that's a great sign that you were able to convince them to bend the rule. [laughs] JENI: Yeah, I mean, I think that's actually my MO in life. So I also applied and got into graduate school at Yale without taking the GRE. So I have a history of these kinds of convincing arguments, I guess. CHAD: [laughs] JENI: And I'm a lawyer, right? So I was made for this. [chuckles] CHAD: Yes. You sound like a very enjoyable person, though. So I find it hard to believe that you're... [laughs] No, I'm kidding. JENI: I'm a human rights lawyer. So the only person I've ever represented in court was a pod of killer whales. So I'm a human rights and environmental attorney. So I'm not a corporate attorney by any means. CHAD: So some people might describe going after things, bending the rules as ambition. And I was reading some of the things that you've written, so I'm not pulling this out of thin air. But I know that you talked before about how sometimes ambition, particularly from female-identifying people, can be seen as a problem. Why is that? JENI: I mean, the short answer to that is the patriarchy of which we're all a part. Both men and women and non-binary people are all impacted greatly by the patriarchy. I mean, I think it's how girls are socialized. So that's a whole, I think, a whole other podcast conversation to have. But I mean, just even recently, I have a young daughter, and she was told not to raise her hand as much in school because she was so eager and raises her hand for every question that's asked. And that's unacceptable to me. But I was also told those things. And I think just men and women are judged very differently in our culture, and that's just a fact of life. I mean, just look at, I mean, this is maybe opening up a can of worms. But if you just look at the way the Elizabeth Holmes trial played out versus so many other startup stories, and yes, there are differences, but it's really common in our culture to villainize female ambition and to look at it as problematic. CHAD: Yeah, you're absolutely right that this is a whole podcast topic in and of itself, but I think it's an important one. But I'm curious; it can feel angering and powerless when something like that happens at school or in a system where it's very hard to control it or change it. But when it comes to your own company, you are in charge. So what have you done to try to make this different at Marvelous? JENI: Well, I would say elevating women to leadership positions to the extent that we've been able, I mean, we're definitely a female-run company. We make decisions. Also, just even the way we provide benefits and salaries, it's in my mind done from a more holistic standpoint than I would say a lot of other small startups are doing. We prioritize people and their families and try to treat people like human beings versus just kind of pawns in our scheme to build a company, I would say. It's not perfect. But I really think that so much of what goes on around kind of the women in tech stories so much of that and the women in fundraising stories has to do with women or non-binary people really having to prove themselves to a degree that is unrealistic in order to have the same treatment or the same opportunities as white men. So we are obviously very acutely aware of that. And so, in our own company, we're still very small but always trying to elevate the opportunities that women and people of color have in our company. CHAD: And as you said, this permeates. It's systemic. And so, what might you do when you have a male manager with the best of intentions in a female-led company? I'm of the opinion that it's not enough to just assume that, oh, well, in that environment, this stuff won't happen because it is so ingrained. So are there other things that we can do as founders, as people, and leaders, as a company to create an environment where it's better for everybody? JENI: I definitely don't have all the answers for this. But I would say we've put a lot of attention into coming up with core values that we really strongly affirm and reaffirm in the company and make sure that everyone is aware of those. I also just I'm constantly watching what's going on and noticing subtle cues when people start to pull back from contributing or some voices are much louder than others; just trying to notice that and not wait for something to be brought to my attention. I think so much of it is also the culture, and it's hard in a situation like ours where we're a fully remote team with people across the world with their own different, you know, they're bringing their own cultures and their own values to the company. I mean, it's definitely hard. It's harder than I ever would have expected to get people on the same page. And, I don't know, I don't have really good advice other than to say the founders should really agree on the core values. And then, those core values should be shared constantly. And I think it starts with the founder or the co-founder and the leadership team holding everyone to those values and standards. CHAD: So as someone who, like you said earlier, you're not a software developer, you're not a designer, yet you are working on this idea and bringing it out into the world. How did you manage to do that? What did the very early steps look like for you? JENI: So I started a company when I was essentially on maternity leave. I naively thought that that would be like a fun, little hobby project for me to start a tech company. Partly because I was spinning off what had really been a research project that was funded and incubated at a major university. I was spinning that off into a nonprofit with another co-founder, another lawyer. And I spent a great deal of time and energy fundraising and was constantly going and having meetings or drinks or dinner with people or even flying out to different foundations and meeting with donors. And I was like, this is for me who...I have a body of work and have developed expertise as a climate change expert. And that word is problematic but, you know, someone who knows quite a lot about climate change in the law, edited one of the major textbooks in the area, taught some of the first curriculum on energy and the environment. I was constantly having to just go out and raise money all the time and mostly from people who had cashed out of tech companies. So I was in Seattle at the time, you know, Microsoft and Amazon. There are a lot of people with significant wealth, and those are the people that are donating to organizations. And so I just thought I'm as smart and capable as these people. Like, why don't I have a revenue source that helps to fund the work that I want to do in the world? Which was a lot of human rights law and environmental law that's really underfunded really at that intersection of climate change and human rights. And so I thought, well, I'm on maternity leave. I'm really interested in the wellness industry. I see it really being broken. I had gone through yoga teacher training like right at the tail end of law school just for my own mental health and wellbeing. And I just saw all of these friends and colleagues of mine struggling, and I just thought something wasn't quite right. So the first thing I did was I decided I'm going to try to build something to help them. And I set out to interview 75 yoga studio owners or managers in North America and did some research on the biggest markets at the time. CHAD: Why 75? JENI: Because I just thought that was a good number. If I talked to 75 people, I'd be able to have some good information. And I will say I had just come off of a couple of major projects where I had put together a big international conference in my field in climate justice. And I had also put together sort of a retreat of leaders in the field of scenario planning around that. So I had really learned a lot and elevated my real career at the time by reaching out to people who I thought were thought leaders and experts in the field across different disciplines and having really honest, frank conversations and interviews with them. And I had been able to essentially tease out an entire field of work for myself from doing that. So I brought my research and academic skills to bear, which was like, if I talk to enough people, I'm going to start to find some patterns. And I was curious, like, I couldn't quite understand. This wellness industry had been growing for over a decade at that point. It was this massive industry, and yet no one I knew who worked in the industry made any money. And I thought that was really weird. And I'm like, why is all the money going to apparel companies or a couple of big brands? Something is really broken in this model. I don't think the technology...tech hadn't really arrived to wellness at that point. I came up with the idea to start doing this at the end of 2013, and so it was a long time ago. So I was just like, I'm going to talk to as many people as I can who are running businesses in the major metropolitan areas that are big yoga centers and just see what I can figure out. And so that's what really started it. And then, the idea for what was then called Namastream and is now called Marvelous came from those conversations. And it wasn't long; it was maybe six weeks into the research that I really started to...like, there were three or four ideas that I thought, well, here are product ideas that could really make a difference. And so what I did is I sent out about 200 cold emails, and I had 74 interviews from that. And then I agreed to create a report like a white paper because, again, this is what I knew how to do as an academic is like I'm going to do a bunch of interviews, and then I'm going to write a report about it. And I'm going to share it with people. So I agreed to share the research with everyone who agreed to an interview. And so I think that's part of why they agreed to talk to me. So yeah, so that's where the idea came from. And then again, I had no background in tech. I watched some trainings on how to do UX design, I think, like YouTube videos and stuff, and then I just did it. And I made the first prototype like a clickable prototype in Keynote because I knew how to use Keynote. CHAD: Yeah, that's so great. Talking to people, using whatever tool you're comfortable with, Keynote, PowerPoint, that kind of thing to do clickable prototypes that's the exact kind of thing I encourage, we encourage our thoughtbot early-stage founders to do. So you were spot on. I don't know if you realized it at the time. But that's really great. What problem did those 74 or some strong subset of them have that streaming helped them with? JENI: It was really interesting because there were a couple of studios. There were two studios at the time in Southern California that were doing this, and the bigger studios in these other major cities knew that. And so because there were so few, they were very well known way back. I mean, most of those conversations were in 2014 that I was having. Some of the studios, I mean, one of them is still a major company now. You know, most studios had like 2,000 members. Like, a studio that I would interview had 2,000 customers on their list, like, possible customers. Some of those were people who were drop-ins or punch cards or whatever. And then the studios that were streaming had like 30,000 customers. And so that was starting to be known. And people had no idea how to do any of that themselves. And so the problem that we are solving was when I would interview studios in the Boston area because that was one of the metropolitan areas I targeted; there were certain days out of the year that for snow closures like the studio would just lose all their revenue that day. In the south, there were studios that were impacted by hurricanes that were trying to figure out...and I'm a climate change lawyer, so I see this trend. I was looking at it from a disaster response scenario planning lens which was this is only going to get worse. I had no idea about the pandemic. CHAD: Little did you know. [laughs] JENI: Right? [laughs] I just thought like, wow, okay, the hurricanes are increasing in severity and duration. That's not going to change. Sea level rise is happening. Storms are becoming more unpredictable. Like, places that are cold are getting colder and have more snow on average. So all these people were complaining about lost revenue for these cataclysmic weather events. I just thought that as being a huge opportunity for a solution. So that was one reason why this idea really stood out to me. And then also just knowing that...this actually goes back again to my own story. I used to work for Al Gore. I was one of the people that led his environmental outreach on his presidential campaign when I was a teenager. And then I ended up being one of the first people trained to give the climate presentation that he made famous in An Inconvenient Truth. And so, I had been developing presentation materials in my legal and academic career that I was sharing with that organization. And I had to figure out how to record myself and then try to get it on a thumb drive and then send it to Nashville so they could watch it and learn how to present the slides that I was making. And so I actually had this very different use case where I was like, it was really hard. I was on the board of another nonprofit that was bringing together environmental leaders once a year to learn new training materials and then go back out across the world to disseminate them. Again, the same thing. I was like; there is going to be such a need for some kind of streaming tool that's accessible by whoever wants to use it to be able to share knowledge and information. So both as a business tool, but it also kind of scratched this other itch that I had seen in my previous career, like, the career I thought I was taking a short break from. And so I just was like, this is the future. And I had moved during this time across the country for my husband's job and had a new baby. And I missed my own yoga teacher. And so I thought, like, wow, I'm in North Carolina in this small town, and I really miss the Seattle community. And I miss my teachers there. I wish I could take these classes. So for all of those reasons, I saw this as being a trend that wasn't going away, and that was only going to be more in need. And it was really early adopters at that point, like definitely not 74 studios telling me they needed this. But it was a big enough chunk of early adopters that I thought this is when you get to make something new that changes the industry. Mid-Roll Ad: I wanted to tell you all about something I've been working on quietly for the past year or so, and that's AgencyU. AgencyU is a membership-based program where I work one-on-one with a small group of agency founders and leaders toward their business goals. We do one-on-one coaching sessions and also monthly group meetings. We start with goal setting, advice, and problem-solving based on my experiences over the last 18 years of running thoughtbot. As we progress as a group, we all get to know each other more. And many of the AgencyU members are now working on client projects together and even referring work to each other. Whether you're struggling to grow an agency, taking it to the next level and having growing pains, or a solo founder who just needs someone to talk to, in my 18 years of leading and growing thoughtbot, I've seen and learned from a lot of different situations, and I'd be happy to work with you. Learn more and sign up today at thoughtbot.com/agencyu. That's A-G-E-N-C-Y, the letter U. CHAD: So you have the clickable prototype, and you feel like this is something here. What was the next step for you? JENI: So I went back to everyone that had validated that idea, and I tried to sell it to them. [laughs] I had people PayPal.Me money in order to build it. I said, "You can become a founding customer, and you'll get access for a year included and with a payment." I think I was charging people; I don't know, a couple of thousand dollars. I don't even remember. It was a long time ago. It was under $2,000. "So you can get in now. You'll have a 20% discount on anything we make forever. If you want to participate, you can be in this founding member circle with me. And as it's getting developed, you can provide feedback and help to shape exactly what it becomes." So I had enough people throw some money into the pot PayPal.Me money. I also had no idea how to take money from anyone. It was sort of like pre-Stripe being a normal thing. So I just had random people PayPal.Me money. And I took the money, and I hired a developer to build a prototype. CHAD: How did you find that developer? JENI: That was hard. So through this entrepreneurship course that I ended up meeting Sandy in, there was somebody who was a classmate, sort of like a mentor-level classmate who had done the course before who was an engineer at Microsoft. So I asked him to help me. I reached out and asked him to. And if I hadn't reached out to him, I would have reached out to other developers that I knew, just people in my extended circle of friends and stuff. CHAD: So how long did it take from that point to get a product that people could actually use for their classes? JENI: Early use, I would say like four months. So it was very, very, very beta. It's humiliating what it was. CHAD: It should be. It should be humiliating. JENI: Yeah, it should be. So it was like kind of a WordPress plugin. It was basically a glorified WordPress plugin, and that took about four months. And so I onboarded our early adopters who had given me the money, the checks, the PayPal money. That was the beginning of the summer that year. And I said, "You're the only people that are going to have access to it for the first three months," and that was part of the deal. So I really worked around the clock helping them, working with my developer to solve any problems that were coming up, making changes. And then, in September, about three months later, I just figured out how to run Facebook ads. [laughs] So I just made up Facebook ads that ran to a one-on-one demo and let people book one-on-one demos with me through Facebook ads. CHAD: So in those early days, if you had to do it over again, is there a lesson you learned that you might do it differently? JENI: I don't think so, honestly. I feel like that first year; I feel pretty good about everything that I did. I mean, obviously, it would have been great to have someone like Sandy come in early on. But, I mean, I needed to figure some stuff out that I didn't need another person around to figure out, I guess. And I guess now, in like 2022, we're having this conversation. I wish I had dumped money into Facebook ads to have more demos because they were so cheap. [laughter] CHAD: Right. Right. JENI: It was so cheap for me to run ads. It was the golden days of online advertising, I guess. So I was probably paying like 40 cents a lead or something. [laughs] So yeah, maybe that. Because I was very much not wanting to put my own money into it. Like, once I raised the money to fund the prototype, I think I maybe in that first year put in like seven grand or something, but by the end of the year, I paid myself back. CHAD: That's great. JENI: I could have maybe put in a little more money. But I didn't know if it was going to work. Like, I wasn't really willing for...again, I wanted something that was very validated. And I expected fully to be going back to my career as soon as I got this thing launched. I was like, oh, this is just like a side hustle. This is going to be passive income. I did not understand that building a software company was not at all passive. I think I really bought into this idea that, like, oh, it's the internet. It will be passive income. CHAD: When did it become clear to you that it wasn't? JENI: Oh, I mean, I would say, you know, so I had a moment to go back to work, not my exact same job but to do work in my field between one month and two months after I launched and started running ads. I turned down a really incredible job offer, and I think that's when I knew it. I was like, if I take a job, if I go back to work full-time...and I have the kind of career that's all-encompassing, and I sort of, whatever, I'm going to give 150% to whatever I'm doing. And so I knew that this thing would kind of die, but it was taking off. And so, I think I knew at that point I had to make a choice. CHAD: And is that when you decided to apply to the accelerator? JENI: No, it was like another nine months of growing it on my own before I applied to the accelerator. And I just kept doing what I was doing, and it was working. But I was doing things that didn't scale, so that was the problem. And so I didn't know, I mean, there's only so many one-on-one demos that the founder can do before you start to realize [laughs] you need to make some changes because I was doing them around the clock. And then, at some point, I switched to webinars. I taught myself how to do webinars. And so then I was trying to do demos to multiple people at a time, but also, I didn't understand email marketing. I didn't understand copywriting. I was figuring everything out myself as I went, and I was burning out. So that's when I decided, like, oh, not everyone does this. I can't grow Microsoft or Amazon by doing this. I can't become that company. So obviously, I need to figure out how to scale. So that was when I decided to apply to the accelerator. CHAD: Why apply to an accelerator as opposed to start fundraising, for example? JENI: Oh my God. Well, so the whole reason I did this was so that I didn't have to go out for drinks with people and ask them for money. [laughter] I mean, I was not interested in that at all. And then I soon realized that that's what happens when you join an accelerator [laughs] is you basically just start learning to fundraise. But I didn't know that. I knew nothing. And so, I knew nothing about startups. I knew nothing about anything like this. I literally had no idea. So the idea of going and sending emails to wealthy people to go have a drink with them was actually the last thing I was willing to do. And I don't think any VC fund would have met with me. I didn't even really know what that was. Like, I had no idea. So it didn't strike me as something that there was a lot of money that somebody would pour into it. That, honestly, wasn't even an option to me in my mind at that time. CHAD: How did the accelerator help you? JENI: It helped me bring on a co-founder, which I would say was invaluable. [chuckles] And I learned a lot. I mean, I'm a person who's super curious and asks lots of questions. And so there was always somebody I could ask questions to, which was great, saved me a lot of time. And I also got to be in a cohort with other founders and see how they were growing their companies. So if you've never been around that stuff before, it's super helpful, I think, to just learn what other people are doing, like what other models there are, what other teams look like. And I also realized, like, we were one of the only companies that had any revenue. I had no idea how we compared to anything else. And so I realized, oh, we're growing, and we're making money, and we're profitable. And it's really different than what a lot of other people are doing. So I knew that there was something to it also. I knew that we were really onto something. And then I will also say that fast forward a number of years, and our leader, one of the directors of our accelerator, I ended up hiring him to be our Chief Product Officer. So that was also very fortuitous [chuckles] and really an amazing story and outcome as well. CHAD: Did you end up raising money coming out of the accelerator? JENI: Nope. We soft circled around and had an opportunity to take an additional tranche from the accelerator, and we walked away from that at the time. And it was a really hard decision. Mostly because Sandy is Canadian, I don't know if that was made obvious, and I'm American. And we never envisioned wanting...like, building a remote company still in 2016 was not normal. And there was no way we were going to be in the same place. And the potential investors we were talking to, one of them in particular, was pretty adamant that we needed to be in person and have an actual office set up. And that was not negotiable for us. And so we had been doing this fine. I mean, we were fine building a company together. And our first developer was in Asia, and then our designer at the time was in another part of the United States. So I was like, why would we do that? Why would we spend money and have to buy things like a fax machine and chairs? Why would we do that? CHAD: [laughs] JENI: That doesn't make any sense. And so that was one kind of red flag for me. And then also in the accelerator, I pitched to tons of people because you're sort of pitching, but also it's kind of practice. And I don't know how much of that was actual pitching. And I don't know how many of those investors were actually considering making investments, or they were just being nice and giving you their time and feedback. But I pitched a ton, and the only people that we had soft circled were women. And I just had some negative experiences with some of the investors that we had pitched to, which that's also another podcast episode. And I was really bothered by, in particular, one conversation that I had. It was like a situation where someone said something really inappropriate to me, and I just absolutely did not want to do that. So that all factored in. CHAD: Have you ever taken any investment? JENI: Yeah. So this year, we have...because we have a situation where it makes sense to pour fuel on our...it made sense from a marketing standpoint to pour some money in. So we've just taken a small investment from angels, and we may take a little more as well. We're open-minded, I would say, right now about fundraising. I have, in the last two years, taken a lot of meetings. So I've talked to lots of firms and lots of angels and get emails every day and so take a number of those meetings. So I've just tried to be really open-minded about it. So yeah, I would say I don't have such a negative association as what I had before. But I also would say my company is in a really different position now, and fundraising means something else to us. CHAD: It sounds like you're in a little bit more control over the situation. And by working with individual angels probably, you're able to maintain that, I would guess. JENI: Yeah. And it's definitely something where I think that there are...you know, I don't think it's helpful to be closed off to fundraising because I see that there are absolutely opportunities especially to go into new markets where being bootstrapped isn't practical because of the cost to go into those markets. And so, if it's something that's heavily regulated, for example, it's not a feasible option. So allowing us to have options and actually to be able to think through those options is important to me. CHAD: So now that you've done that, what's next for Marvelous? What's the next challenge you're ready to tackle? JENI: I would say we had this tremendous growth early in the pandemic, which really kind of unearthed, not really unearthed, I mean, I knew it was there [laughs] but really publicly unearthed a lot of technical debt. And that's, I think, normal for bootstrapped companies as well who are growing slowly and up to a point that they're not anymore. And so we spent a solid 18 months, I would say. Up until the end of 2021, there was a solid 18 months of really rebuilding the platform from the ground up. And so we've done that, and now we're in growth mode. We're focusing on letting people know that we exist because I think we're quite well known in the wellness industry and in the yoga space in particular, but we're not as well known outside of that in other creator niches. And so it's about brand awareness. It's about really showing up as thought leaders in the space as well. We do a lot of writing and a lot of blogging and podcasting. And in particular, we serve women and non-binary creators in a way that I think no one else does. And so it's about disseminating the information that we have and the teachings that we have and letting people know we exist, and we're a resource for them. CHAD: Yeah. Well, like you said, you have a strong reputation, and you have those roots in the wellness space, but you've expanded beyond that. If someone's out there listening, what would make them a potential customer or an ideal customer for Marvelous? JENI: So anyone who's teaching, training, or coaching online, the software is really industry agnostic. And so we're just, again, not as well known yet in those other spaces. But especially someone who's integrating any cohort-based learning, or really heavily integrating coaching and live streaming, or group programs, or one-on-ones into an online course or a membership, for example, Marvelous is really second to none with all of that. Because again, live streaming and the integration of live teaching with on-demand content was what we started with and what we are known for. And so it's not an afterthought the way that I think a lot of online teaching platforms and edtech companies have slapped on live streaming as like, oh, now you can integrate with Zoom or whatever. And for us, we have an integration with Zoom that's not like anything else. And then we have other WebRTC-based live streaming options, and everything is very well thought out and makes it really easy for the end-user so for the students and clients to be able to use the tool, which I think our audience really cares about that it's easy for their clients. CHAD: I'd be remiss, and since this is a podcast, if I didn't mention that you and Sandy have a podcast. JENI: We sure do, yeah. Thank you so much. laughs] CHAD: It's called the And She Spoke Podcast, and where can folks find it? JENI: So obviously anywhere that they listen to podcasts, but our website for the podcast is andshe.co. So I would love it if you're interested in conversations about women in tech, female founders, women, money and power, online business resources, and training. And that's mostly what we talk about. We're doing a crypto series right now, sort of like exploring crypto and the intersection of women and crypto, so that's going to be coming out shortly as well. CHAD: Cool. If folks want to try out Marvelous or find out more or get in touch with you, where are all the places that they can do that? JENI: So our website is heymarvelous.com. And we are @heymarvelous on Instagram. That's where we hang out the most. But we're also on TikTok, and Pinterest, and Facebook, and pretty much everywhere else as well. But Instagram, I would say, is the best place. CHAD: That's great. Jeni, thanks so much for joining me and sharing your story and your advice. I'm sure people will really appreciate it. JENI: Yeah, thank you so much for your time, Chad. I appreciate you having me. CHAD: And you can subscribe to the show and find notes for this episode along with a complete transcript at giantrobots.fm. If you have questions or comments, email us at hosts@giantrobots.fm. And you can find me on Twitter at @cpytel. This podcast is brought to you by thoughtbot and produced and edited by Mandy Moore. Thanks for listening, and see you next time. ANNOUNCER: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success. Special Guest: Jeni Barcelos.
Craig and James beg for your forgiveness as the podcast has been on hiatus for a while. But with guests like Bluewave Technology Group and Vodia, like Die Hard 3, they are back with a vengeance. Well-known channel figures Curt Allen and Eric Brooker are new to Bluewave, but not the channel. These gents talk with the guys about the unique business model the company offers and the flood of investment money coming into the industry. Next up is Christian Stredicke, president and CEO of Vodia Networks. You might know him best as the founder of Snom. Stredicke will discuss WebRTC and other technologies impacting the IP PBX market. And it wouldn't be a podcast without a discussion of Channel Partners events. We'll have a preview of Channel Evolution Europe, less than two weeks away. Moreover, the MSP Summit in September will be here before we know it. And we're introducing the inaugural Channel Partners Leadership Summit that we are co-locating with the event. All that plus the 2022 MSP 501 reveal is almost here. We'll get you excited for that and tell you about a webinar where you can get a sneak peak of the top winners.
When your architecture operates securely, you do not need to worry about external security add-ons or end-users manually implementing best practice security. Robert Cooper, President, and Managing Director of Wildix Americas, goes on to explain to Don Witt of The Channel Daily News, a TR publication, how elements of the secure-by-design architecture include DDOS protection, WebRTC architecture, encryption and other security components. Threats will continue from Russia electronically, but Wildix eliminated one of Russia direct threats by moving 200 employees and members me from Ukraine before any of the conflict started. Listen in to hear about this well thought out product offering. Robert Cooper 100% SECURITY WITH NO FURTHER APPLICATIONS Traditional PBXs and UC&Cs require the addition of SBC and VPN infrastructures to work remotely: they are barriers that protect your system from cyber-attacks and external viruses. SBCs and VPNs are not included in the traditional PBX package you purchase and require constant maintenance and attention, otherwise, your data is in danger. You will end up spending more and still expose yourself to high risk: a failure to update these infrastructures can bring you million-dollar damage. Would you feel safe knowing you are buying a PBX that needs additional, expensive applications to be safe? YOUR PBX MUST BE INHERENTLY SAFE WITHOUT NEEDING ADDITIONAL INFRASTRUCTURES. Wildix is secure-by-design: it does not need SBCS or VPNS: voice and data are ALWAYS protected because it is created with a native encryption system. For more information, go to: https://www.wildix.com/
It's time to shoot for the stars with Dan Isla, VP of Product at itopia, to talk about everything from astronomical importance of reliability to time zones on Mars. Dan's trajectory has been a propulsion of jobs bordering on the science fiction, with a history at NASA, modernizing cloud computing for them, and loads more. Dan discusses the finite room for risk and failure in space travel with an anecdote from his work on Curiosity. Dan talks about his major take aways from working at Google, his “baby” Selkies, his work at itopia, and the crazy math involved with accounting for time on Mars!In this episode, we cover: Introduction (00:00) Dan's work at JPL (01:58) Razor thin margins for risk (05:40) Transition to Google (09:08) Selkies and itopia (13:20) Building a reliability community (16:20) What itopia is doing (20:20) Learning, building a “toolbox,” and teams (22:30) Clockdrift (27:36) Links Referenced: itopia: https://itopia.com/ Selkies: https://github.com/danisla/selkies selkies.io: https://selkies.io Twitter: https://twitter.com/danisla LinkedIn: https://www.linkedin.com/in/danisla/ TranscriptDan: I mean, at JPL we had an issue adding a leap second to our system planning software, and that was a fully coordinated, many months of planning, for one second. [laugh]. Because when you're traveling at 15,000 miles per hour, one second off in your guidance algorithms means you missed the planet, right? [laugh]. So, we were very careful. Yeah, our navigation parameters had, like, 15 decimal places, it was crazy.Julie: Welcome to Break Things on Purpose, a podcast about reliability, building things with purpose, and embracing learning. In this episode, we talked to Dan Isla, VP of Product at itopia about the importance of reliability, astronomical units, and time zones on Mars.Jason: Welcome to the show, Dan.Dan: Thanks for having me, Jason and Julie.Jason: Awesome. Also, yeah, Julie is here. [laugh].Julie: Yeah. Hi, Dan.Jason: Julie's having internet latency issues. I swear we are not running a Gremlin latency attack on her. Although she might be running one on herself. Have you checked in in the Gremlin control panel?Julie: You know, let me go ahead and do that while you two talk. [laugh]. But no, hi and I hope it's not too problematic here. But I'm really excited to have Dan with us here today because Dan is a Boise native, which is where I'm from as well. So Dan, thanks for being here and chatting with us today about all the things.Dan: You're very welcome. It's great to be here to chat on the podcast.Jason: So, Dan has mentioned working at a few places and I think they're all fascinating and interesting. But probably the most fascinating—being a science and technology nerd—Dan, you worked at JPL.Dan: I did. I was at the NASA Jet Propulsion Lab in Pasadena, California, right, after graduating from Boise State, from 2009 to around 2017. So, it was a quite the adventure, got work on some, literally, out-of-this-world projects. And it was like drinking from a firehose, being kind of fresh out to some degree. I was an intern before that so I had some experience, but working on a Mars rover mission was kind of my primary task. And the Mars rover Curiosity was what I worked on as a systems engineer and flight software test engineer, doing launch operations, and surface operations, pretty much the whole, like, lifecycle of the spacecraft I got to experience. And had some long days and some problems we had to solve, and it was a lot of fun. I learned a lot at JPL, a lot about how government, like, agencies are run, a lot about how spacecraft are built, and then towards the end a lot about how you can modernize systems with cloud computing. That led to my exit [laugh] from there.Jason: I'm curious if you could dive into that, the modernization, right? Because I think that's fascinating. When I went to college, I initially thought I was going to be an aerospace engineer. And so, because of that, they were like, “By the way, you should learn Fortran because everything's written in Fortran and nothing gets updated.” Which I was a little bit dubious about, so correct folks that are potentially looking into jobs in engineering with NASA. Is it all Fortran, or… what [laugh] what do things look like?Dan: That's an interesting observation. Believe it or not, Fortran is still used. Fortran 77 and Fortran—what is it, 95. But it's mostly in the science community. So, a lot of data processing algorithms and things for actually computing science, written by PhDs and postdocs is still in use today, mostly because those were algorithms that, like, people built their entire dissertation around, and to change them added so much risk to the integrity of the science, even just changing the language where you go to language with different levels of precision or computing repeatability, introduced risk to the integrity of the science. So, we just, like, reused the [laugh] same algorithms for decades. It was pretty amazing yeah.Jason: So, you mentioned modernizing; then how do you modernize with systems like that? You just take that codebase, stuff it in a VM or a container and pretend it's okay?Dan: Yeah, so a lot of it is done very carefully. It goes kind of beyond the language down to even some of the hardware that you run on, you know? Hardware computing has different endianness, which means the order of bits in your data structures, as well as different levels of precision, whether it's a RISC system or an AMD64 system. And so, just putting the software in a container and making it run wasn't enough. You had to actually compute it, compare it against the study that was done and the papers that were written on it to make sure you got the same result. So, it was pretty—we had to be very careful when we were containerizing some of these applications in the software.Julie: You know, Dan, one thing that I remember from one of the very first talks I heard of yours back in, I think, 2015 was you actually talked about how we say within DevOps, embrace failure and embrace risk, but when you're talking about space travel, that becomes something that has a completely different connotation. And I'm kind of curious, like, how do you work around that?Dan: Yeah, so failing fast is not really an option when you only have one thing [laugh] that you have built or can build. And so yeah, there's definitely a lot of adverseness to failing. And what happens is it becomes a focus on testing, stress testing—we call it robustness testing—and being able to observe failures and automate repairs. So, one of the tests programs I was involved with at JPL was, during the descent part of the rover's approach to Mars, there was a power descent phase where the rover actually had a rocket-propelled jetpack and it would descend to the surface autonomously and deliver the rover to the surface. And during that phase it's moving so fast that we couldn't actually remote control it, so it had to do everything by itself.And there were two flight computers that are online, pretty much redundant, everything hardware-wise, and so it's kind of up to the software to recover itself. And so, that's called entry descent and landing, and one of my jobs towards the end of the development phase was to ensure that we tested all of the possible breakage points. So, we would do kind of evil Gremlin-like things. We actually—the people in the testbed, we actually call Gremlins. And [laugh] we would—we—they inject faults during the simulation.So, we had copies of the hardware running on a desk, the software was running, and then we'd have Gremlins go and say like, “Hey, flight computer one just went out. You know, what's going to happen?” And you watch the software, kind of, take over and either do the right thing or simulate a crash landing. And we find bugs in the software this way, we'd find, like, hangs in the control loops for recovery, and we had to fix those before we made it to Mars, just in case that ever happened. So, that was like how we, like, really stressed test the hardware, we did the same thing with situational awareness and operations, we had to simulate things that would happen, like, during launch or during the transit from Earth to Mars, and then see how the team itself reacted to those. You know, do our playbooks work? Can we run these in enough time and recover the spacecraft? So, it was a lot of fun. That's I guess that's about as close to, like, actually breaking something I can claim to. [laugh].Julie: Well, I have to say, you've done a good job because according to Wikipedia—which we all know is a very reliable source—as of May 9th, 2022, Curiosity has been active on Mars for 3468 sols or 3563 days, and is still active. Which is really amazing because I don't—was it ever intended to actually be operational that long?Dan: Not really. [laugh]. The hardware was built to last for a very long time, but you know, as with most missions that are funded, they only have a certain amount of number of years that they can be operated, to fund the team, to fund the development and all that. And so, the prime mission was only, like, two years. And so, it just keeps getting extended. As long as the spacecraft is healthy, and, like, doing science and showing results, we usually extend the missions until they just fall apart or die, or be intentionally decommissioned, kind of like the Cassini project. But yeah.Julie: Well, you've heard it here first, folks. In order to keep funding, you just need to be, quote, “Doing science.” [laugh]. But Dan, after JPL, that's when you went over to Google, right?Dan: Yeah, yeah. So, it was kind of that transition from learning how to modernize with cloud. I'd been doing a lot with data, a lot with Amazon's government cloud, which is the only cloud we could use at JPL, and falling in love with these APIs and ways to work with data that were not possible before, and saw this as a great way to, you know, move the needle forward in terms of modernization. Cloud is a safe place to prototype a safe place to get things done quick. And I always wanted to work for a big tech company as well, so that was always another thing I was itching to scratch.And so Google, I interviewed there and finally made it in. It was not easy. I definitely failed my first interview. [laugh]. But then try it again a few years later, and I came in as a cloud solution architect to help customers adopt cloud more quickly, get through roadblocks.My manager used to say the solution architects were the Navy Seals of cloud, they would drop in, drop a bunch of knowledge bombs, and then, like, get out, [laugh] and go to the next customer. It was a lot of fun. I got to build some cool technology and I learned a lot about what it's like working in a big public company.Julie: Well, one of my favorite resources is the Google SRE book, which, as much as I talk about it, I'm just going to admit it here now, to everybody that I have not read the entire thing.Dan: It's okay.Julie: Okay, thank you.Dan: Most people probably haven't.Julie: I also haven't read all of Lord of the Rings either. But that said, you know, when you talk about the learnings, how much of that did you find that you practiced day-to-day at Google?Dan: In cloud—I've mostly worked in cloud sales, so we were kind of post-sales, the experts from the technology side, kind of a bridge to engineering and sales. So, I didn't get to, like, interact with the SREs directly, but we have been definitely encouraged, I had to learn the principles so that we could share them with our customers. And so, like, everyone wanted to do things like Google did, you know? Oh, these SREs are there, and they're to the rescue, and they have amazing skills. And they did, and they were very special at Google to operate Google's what I would call alien technology.And so, you know, from a principles point of view, it was actually kind of reminded me a lot of what I learned at JPL, you know, from redundant systems and automating everything, having the correct level of monitoring. The tools that I encountered at Google, were incredible. The level of detail you could get very quickly, everything was kind of at your fingertips. So, I saw the SREs being very productive. When there was an outage, things were communicated really well and everyone just kind of knew what they were doing.And that was really inspiring, for one, just to see, like, how everything came together. That's kind of what the best part of working at Google was kind of seeing how the sausage was made, you know? I was like, “Oh, this is kind of interesting.” [laugh]. And still had some of its big company problems; it wasn't all roses. But yeah, it was definitely a very interesting adventure.Jason: So, you went from Google, and did you go directly to the company that you helped start, right now?Dan: I did. I did. I made the jump directly. So, while I was at Google, you know, not only seeing how SRE worked, but seeing how software was built in general and by our customers, and by Google, really inspired me to build a new solution around remote productivity. And I've always been a big fan of containers since the birth of Docker and Kubernetes.And I built the solution that let you run, kind of, per-user workloads on Kubernetes and containers. And this proved to be interesting because you could, you know, stand up your own little data processing system and scale it out to your team, as well as, like, build remote code editors, or remote desktop experiences from containers. And I was very excited about this solution. The customers were really starting to adopt it. And as a solution architect, once the stuff we built, we always open-source it.So, I put it on GitHub as a project called Selkies. And so, Selkies is the Kubernetes components and there's also the high performance streaming to a web browser with WebRTC on GitHub. And a small company, itopia, I met at a Google conference, they saw my talk and they loved the technology. They were looking for something like that, to help some of their product line, and they brought me in as VP of Product.So, they said, “We wanted to productize this.” And I'm like, “Well, you're not doing that without me.” [laugh]. Right? So, through the pandemic and work from home and everything, I was like, you know, now is probably a good time to go try something new.This is going to be—and I get to keep working on my baby, which is Selkies. So yeah, I've been itopia since beginning of 2021, building a remote desktop, really just remote developer environments and other remote productivity tools for itopia.Julie: Well and, Dan, that's pretty exciting because you actually talked a little bit about that at DevOpsDays Boise, which if that video is posted by the time of publication of this podcast, we'll put a link to that in the show notes. But you're also giving a talk about this at SCaLE 19x in July, right?Dan: Yeah, that's right. Yeah, so SCaLE is the Southern California Linux Expo, and it's a conference I really enjoy going to get to see people from Southern California and other out of town, a lot of JPLers usually go as well and present. And so, it's a good time to reconnect with folks. But yeah, so SCaLE, you know, they usually want to talk more about Linux and some of the technologies and open-source. And so yeah, really looking forward to sharing more about selfies and kind of how it came to be, how containers can be used for more than just web servers and microservices, but also, you know, maybe, like, streaming video games that have your container with the GPU attached. The DevOpsDays Boise had a little demo of that, so hopefully, that video gets attached. But yeah, I'm looking forward to that talk at the end of July.Jason: Now, I'm really disappointed that I missed your talk at DevOpsDays Boise. So Julie, since that's your domain, please get those videos online quickly.Julie: I am working on it. But Dan, one of the things that you know you talk about is that you are the primary maintainer on this and that you're looking to grow and improve with input from the community. So, tell us, how can the community get involved with this?Dan: Yeah, so Selkies is on GitHub. You can also get to it from selkies.io. And basically, we're looking for people to try it out, run it, to find problems, you know, battle test it. [laugh]. We've been running it in production at itopia, it's powering the products they're building now.So, we are the primary maintainers. I only have a few others, but, you know, we're just trying to build more of an open-source community and level up the, you know, the number of contributors and folks that are using it and making it better. I think it's an interesting technology that has a lot of potential.Jason: I think as we talk about reliability, one of the things that we haven't covered, and maybe it's time for us to actually dive into that with you is reliability around open-source. And particularly, I think one of the problems that always happens with open-source projects like this is, you're the sole maintainer, right? And how do you actually build a reliable community and start to grow this out? Like, what happens if Dan suddenly just decides to rage quit tech and ups and leaves and lives on his own little private island somewhere? What happens to Selkies?Do you have any advice for people who've really done this, right? They have a pet project, they put it on GitHub, it starts to gain some traction, but ultimately, it's still sort of their project. Do you have any advice for how people can take that project and actually build a reliable, growing, thriving community around it?Dan: Honestly, I'm still trying to figure that out [laugh] myself. It's not easy. Having the right people on your team helps a lot. Like, having a developer advocate, developer relations to showcase what it's capable of in order to create interest around the project, I think is a big component of that. The license that you choose is also pretty important to that.You know, there's some software licenses that kind of force the open-sourcing of any derivative of what you build, and so that can kind of keep it open, as well, as you know, move it forward a little bit. So, I think that's a component. And then, you know, just, especially with conferences being not a thing in the last couple of years, it's been really hard to get the word out and generate buzz about some of these newer open-source technologies. One of the things I kind of like really hope comes out of a two-year heads-down time for developers is that we're going to see some, like, crazy, amazing tech on the other side. So, I'm really looking forward to the conferences later this year as they're opening up more to see what people have been building. Yeah, very interested in that.Jason: I think the conversation around open-source licenses is one that's particularly interesting, just because there's a lot involved there. And there's been some controversy over the past couple of years as very popular open-source projects have decided to change licenses, thinking of things like Elastic and MongoDB and some other things.Dan: Yeah. Totally.Jason: You chose, for Selkies, it looks like it's Apache v2.Dan: Yep. That was mostly from a Google legal point of view. When I was open-sourcing it, everything had to be—you know, had to have the right license, and Apache was the one that we published things under. You know, open-source projects change their license frequently. You saw that, like what you said, with Elastic and Mongo.And that's a delicate thing, you know, because you got to make sure you preserve the community. You can definitely alienate a lot of your community if you do it wrong. So, you got to be careful, but you also, you know, as companies build this tech and they're proud of it and they want to turn it into a product, you want to—it's a very delicate process, trying to productize open-source. It can be really helpful because it can give confidence to your customers, meaning that, like, “Hey, you're building this thing; if it goes away, it's okay. There's this open-source piece of it.”So, is instills a little bit of confidence there, but it also gets a little tricky, you know? Like, what features are we adding the add value that people will still pay for versus what they can get for free? Because free is great, but you know, it's a community, and I think there are things that private companies can add. My philosophy is basically around packaging, right? If you can package up an open-source product to make it more easier to consume, easier to deploy, easier to observe and manage, then you know, that's a lot of value that the rest of the free community may not necessarily need.If they're just kind of kicking the tires, or if they have very experienced Kubernetes team on-site, they can run this thing by themselves, go for it, you know? But for those, the majority that may not have that, you know, companies can come in and repackage things to make it easier to run open-source. I think there's a lot of value there.Jason: So, speaking of companies repackaging things, you mentioned that itopia had really sort of acquired you in order to really build on top of Selkies. What are the folks at itopia doing and how are they leveraging the software?Dan: That's a good question. So, itopia's mission is to radically improve work-from-anywhere. And we do that by building software to orchestrate and automate access to remote computing. And that orchestration and automation is a key component to this, like, SaaS-like model for cloud computing.And so, Selkies is a core piece of that technology. It's designed for orchestrating per-user workloads, like, remote environments that you would need to stand up. And so, you know, we're adding on things that make it more consumable for an enterprise, things like VPN peering and single-sign-on, a lot of these things that enterprises need from day one in order to check all the boxes with their security teams. And at the heart of that is really just increasing the amount of the productivity you have through onboarding.Basically, you know, setting up a developer environment can take days or weeks to get all the dependencies set up. And the point of itopia—Spaces is the product I'm working on—is to reduce that amount of time as much as possible. And, you know, this can increase risk. If you have a product that needs to get shipped and you're trying to grow or scale your company and team and they can't do that, you can slip deadlines and introduce problems, and having a environment that's not consistent, introduces reliability problems, right, because now you have developers that, “Hey, works on my machine.” But you know, they may have—they don't have the same machine, same environment as everyone else, and now when it comes to reproducing bugs or even fixing them, that you can introduce more problems to the software supply chain.Julie: I mean, that sounds like a great problem to solve and I'm glad you're working on it. With your background being varied, starting as an intern to now where you personally are being acquired by organizations. What's something that you've really learned or taken from that? Because one thing that you said was that you failed your first Google interview badly? And—Dan: Yes. [laugh].Julie: I find that interesting because that sounds like you know, you've taken that learning from failure, you've embraced the fact that you failed it. Actually, I just kind of want to go back. Tell us, do you know what you did?Dan: It was definitely a failure. I don't know how spectacular it was, but, like, [laugh] google interviews are hard. I mean—and that's just how it is, and it's been—it's notorious for that. And I didn't have enough of the software, core software experience at the time to pass the interview. These are, like, five interviews for a software engineer.And I made it through, like, four of them. The last one was, like, just really, really, really hard and I could not figure it out. You know, because this is, like, back in the day—and I think they still do this, like, where you're, like, coding on a whiteboard, right? Like, okay, right, this C code on a whiteboard, and it has to work. You know, the dude is, like, right, there compiling it, right? Like, “Okay, [unintelligible 00:23:29], boy.” [laugh].So, not only is a high stress, but it has to be right as well. [laugh]. And so, like, it was just a very difficult experience. And what I learned from that was basically, “Okay, I need to, one, get more experience in this style and this domain of programming, as well, as you know, get more comfortable speaking and being in front of people I don't know.” [laugh].So yeah, there's definitely components there of personal growth as well as technical growth. From a technical point of view, like, my philosophy as being an engineer in general, and software developer, is have a really big toolbox and use the tools that are appropriate for the job. This is, like, one of my core philosophies. Like, people ask, you know, ‘what language do you use?' And I'm like, “Whatever language you needed to solve the problem.”Like, if you're writing software, in a—with libraries that are all written in C, then don't try to do that in, like, Java or something, in some other language that doesn't have those language bindings. Don't reinvent the language bindings. You follow the problem and you follow the tech. What language, what tool will best solve this problem? And I'm always working backwards from the problem and then bringing in the right tools to solve it.And that's something that has paid off in dividends because it's very—problem-solving is fun and it's something I always had a passion for, but when you have a toolbox that is full of interesting gadgets and things you can use, you get excited every time you get to use that tool. Like, just like power tools here, I have a—I don't know, but it's like, “Yeah, I get to use the miter saw for this thing. Awesome. I don't have one? Okay, I'm going to go buy one.” [laugh].Julie: That's actually—that's a really good point, one of the talks that I gave was, “You Can't Buy DevOps.” And it was really all about letting developers be part of the process in choosing the tools that they're going to use. Because sometimes I think organizations put too many constraints around that and force you to use these tools that might not be the best for what you're trying to accomplish. So, I like that you bring up having the ability to be excited about your toolbox, or your miter saw. For me, it would be my dremel. Right? But what tool is going to—Dan: [crosstalk 00:25:39] cool.Julie: Yeah, I mean, they really are—what tool is going to be best for the job that you are trying to accomplish? And I think that that's, that's a big thing. So, when you look to bring people onto your team, what kind of questions do you ask them? What are you looking for?Dan: Well, we're just now starting to really grow the company and try and scale it up. And so we're, you know, we're starting to get into more and more interview stuff, I try to tell myself, I don't want to put someone through the Google experience again. And part of that is just because it wasn't pleasant, but also, like, I don't know if it was really that useful [laugh] at the end of the day. And so, you know, there's a lot about culture fit that is really important. People have to be able to communicate and feel comfortable with your team and the pace that your team is working at. And so, that's really important.But you know, technically, you know, I like to see a lot of, you know—you got to be able to show me that you can solve problems. And that can be from, you know, just work that you've done an open-source, you know, having a good resume of projects you've worked on is really important because then we can just talk about tech and story about how you solve the problem. I don't have to—I don't need you to go to the whiteboard and code me something because you have, like, 30 repos on GitHub or something, right? And so, the questions are much more around problem-solving: you know, how would you solve this problem? What technology choices would you use, and why?Sometimes I'll get the fundamentals, like, do you understand how this database works at its core or not? You know, or why is it… why is that good or bad? And so, looking for people who can really think within the toolbox they have—it doesn't have to be a big one, but do they know how to use the tools that they've acquired so far, and really, just really, really critically think through with your problems? So, to me, that's a better skill to have than just, you know, being able to write code on the whiteboard.Julie: Thanks for that, Dan. And earlier, before we started the official recording here, you were talking a little bit about time drift. Do you want to fill everybody in on what you were talking about because I don't think it was Doctor Strange and the Multiverse of Madness?Dan: No. [laugh]. I think there were some—we were talking about um…clocks?Julie: Clocks skew.Dan: Daylight savings time?Julie: Yeah.Dan: Clock skew, clock drift. There was a time at JPL when we were inserting a leap second to the time. This actually happened all throughout the world, where periodically that the clocks will drift far enough because the orbits and the rotation of the planet are not, like, perfectly aligned to 365 days in a year and 24 hours in a day. And so, every so decades, you have to insert these leap seconds in order to catch up and make time more precise. Well, space travel, when you're planning, you have to—you're planning to the position of the stars and the planets and the orbital bodies, and those measurements are done at such a large scale that you have—your precision goes, like, way out, you know, many, many decimal places in order to properly plan to the bodies up big.And with the Mars Rover, one of these leap seconds happened to come in, like, right, before we launched. And it was like, oh my gosh, this is going to be to—change all of our ephemeris files—the data that you use to track positions—and we had to do it, like, synchronize it all, like, right, when the leap second was going in. And we tested this extensively because if you get it wrong with your spacecraft is traveling, like, 15,000 miles an hour towards Mars, and a one-second pointing error from Earth means, like, you missed the whole planet, you won't even get there. [laugh]. We're not talking about, like, missing the landing site of, like, a few kilometers. No, it's like thousands of kilometers in pointing error.So yeah, things are astronomical [laugh] in units. Actually, that's why they're called AU, astronomical units, when you're measuring the distance from the Sun. So yeah, it was a pretty fun time. A little bit nerve-wracking just because the number of systems that had to be updated and changed at the same time. It's kind of like doing a rolling update on a piece of software that just had to go out all at the same time. Yeah.Jason: I think that's really interesting, particularly because, you know, for most of us, I think, as we build things whether that's locally or in the cloud or wherever our servers are at, we're so used to things like NTP, right, where things just automatically sync and I don't have to really think about it and I don't really have to worry about the accuracy because NTP stays pretty tight. Usually, generally.Dan: Mm-hm.Jason: Yeah. So, I'm imagining, obviously, like, on a spacecraft flying 15,000 miles a second or whatever, no NTP out there.Dan: [laugh]. Yeah, no NTP and no GPS. Like, all the things you take for granted, on Mars are just not there. And Mars even has a different time system altogether. Like the days on Mars are about 40 minutes longer because the planet spins slower.And my first 90 sols—or days on Mars—of the mission, the entire planning team on earth that I was a part of, we lived on Mars time. So, we had to synchronize our Earth's schedule with what the rover was doing so that when the rover was asleep, we were planning the next day's activities. And when it woke up, it was ready to go and do work during the day. [laugh]. So, we did this Mars time thing for 90 days. That was mostly inherited from the Mars Exploration rovers, Spirit and Opportunity because they were only designed to live for, like, 90 days.So, the whole team shifted. And we—and now it's kind of done in spirit of that mission. [laugh]. Our rover, we knew it was going to last a bit longer, but just in case, let's shift everyone to Mars time and see what happened. And it was not good. We had to [laugh] we had to end that after 90 days. People—your brain just gets completely fried after that. But it was bizarre.And there's no time. You have invent your own time system for Mars. Like, there's no, it was called LMST, or Local Mars Standard Time, local mean standard time. But it was all, like, relative to, you know, the equator and where you were on the planet. And so, Mars had his own Mars time that counted at a different rate per second.And so, it was funny, we had these clocks in the Mission Control Room that—there was this giant TV screen that had, like, four different time clocks running. It had, like, Pasadena time, UTC time, Mars time, and, like, whatever time it was at the Space Network. And I was like, “Oh, my gosh.” And so, we were always doing these, like, time conversions in our heads. It was mental. [laugh]. So, can't we just all be on UTC time? [laugh].Jason: So, I'm curious, with that time shift of being on Mars time and 40 minutes longer, that inherently means that by the end of that 90 days, like, suddenly, your 8 a.m. Mars local time is, like, shifted, and is now, like, hours off, right? You're waking—Dan: Yeah.Jason: Up in the middle of the night?Dan: Totally, yeah.Jason: Wow.Dan: Yeah, within, like, two weeks, your schedule will be, like, upside down. It's like, every day, you're coming in 40 minutes later. And yeah, it was… it was brutal. [laugh]. Humans are not supposed to do that.If you're actually living on Mars, you're probably okay, but like, [laugh] trying to synchronize those schedules. I thought you were going from East Coast to West Coast time, working remote was hard. And, like, [laugh] that's really remote.Julie: Dan, that's just astronomical.Dan: [laugh].Julie: I'm so sorry. I had to do it. But with that—[laugh].Jason: [laugh].Dan: [laugh]. [unintelligible 00:33:15].Julie: With that, Dan, I really just want to thank you for your time on Break Things on Purpose with us today. And as promised, if I can find the links to Dan's talks, if they're available before this episode posts, we will put those in the show notes. Otherwise, we'll put the link to the YouTube channel in the show notes to check for updates. And with that, I just want to thank you, Dan, and wish you a wonderful day.Jason: Before we go, Dan, do you have anything that you'd like to plug? Any projects that people should check out, where they can find you on the internet, stuff like that?Dan: Yeah, thank you guys very much for having me. It was a great conversation. Really enjoyed it. Please check out our new product, itopia Spaces, remote developer environments delivered, powered by Selkies. We launched it last fall and we're really trying to ramp that up.And then check out the open-source Selkies project, selkies.io will get you there. And yeah, we're looking for contributors. Beyond that, you can also find me on Twitter, I'm @danisla, or on LinkedIn.Jason: Awesome. Well, thanks again for being a part of the show. It's been fantastic.Dan: You're very welcome. Thanks for having me.Jason: For links to all the information mentioned, visit our website at gremlin.com/podcast. If you liked this episode, subscribe to the Break Things on Purpose podcast on Spotify, Apple Podcasts, or your favorite podcast platform. Our theme song is called, “Battle of Pogs” by Komiku, and it's available on loyaltyfreakmusic.com.
NVIDIA is open-sourcing their GPU drivers, but there are a few things you need to know. Plus, we get some exclusive insights into Tailscale from one of its co-founders. Special Guests: Avery Pennarun and Christian F.K. Schaller.
When you are teaching someone web development skills, when is the right time to start teaching code quality and testing practices? Karl Stolley believes it's never too early. Let's hear how he incorporates code quality in his courses. Our discussion includes: starting people off with good dev practices and tools linting html and css validation visual regression testing using local dev servers, including https incorporating testing with git hooks testing to aid in css optimization and refactoring Backstop Nightwatch BrowserStack the tree legged stool of learning and progressing as a developer: testing, version control, and documentation Karl is also writing a book on WebRTC, so we jump into that a bit too. Special Guest: Karl Stolley.
Lorenzo Miniero of Meetecho and Janus WebRTC speaks with Jonathan Bennett and Doc Searls on FLOSS Weekly about securing WebRTC streams with encryption and SecureRTP. For more, check out FLOSS Weekly: https://twit.tv/floss/674 Hosts: Doc Searls and Jonathan Bennett Guest: Lorenzo Miniero You can find more about TWiT and subscribe to our podcasts at https://podcasts.twit.tv/
Lorenzo Miniero of Meetecho and the author of the Janus open source WebRTC server, joins Doc Searls and Jonathan Bennett for an informative conversation regarding live streaming and broadcasting, new and better ways to bring in network devices, OBS, virtual and hybrid events, WHIP, the open source future of real time communication, and much more. Hosts: Doc Searls and Jonathan Bennett Guest: Lorenzo Miniero Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss Compiler - FLOSS
Lorenzo Miniero of Meetecho and the author of the Janus open source WebRTC server, joins Doc Searls and Jonathan Bennett for an informative conversation regarding live streaming and broadcasting, new and better ways to bring in network devices, OBS, virtual and hybrid events, WHIP, the open source future of real time communication, and much more. Hosts: Doc Searls and Jonathan Bennett Guest: Lorenzo Miniero Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss Compiler - FLOSS
谈及个人影响力，出书必然是一个排名靠前的选项，作为中华民族价值观最佳体现的「三不朽」中，也把立言作为一个非常重要且困难的事情。但作为个人品牌的重要组成部分，出书是一个无法绕过的话题。于是我们决定认真聊聊出书这个话题。今天，我们邀请 《WebRTC音视频实时互动技术》 的作者李超老师和编辑朱捷老师，跟大家分享一下关于出书写作的那些事。您将在本期节目中听到以下内容：嘉宾出书的经验和教训从编辑视角提供的出书建议不同人群适合的出书选择图书出版的流程嘉宾介绍李超，北京音视跳动科技有限公司，首席架构师。《WebRTC音视频实时互动技术–原理、实战与源码分析》一书作者、声网开发者社区 MVP，拥有10多年的音视频实时互动直播研发经验，多年的团队管理经验。参加并设计了多个高负载，大并发服务器架构。曾在全时云会议担任“Tang”平台研发经理。带领团队研发自主知识产权的全时音视频会议平台。该平台可以同时并发上万场会议，每场可以支持上千人实时互动。2015年底加入跟谁学团队，担任直播研发高级经理，带领团队研发在线教育直播平台，同一教室内可支持上万人。之后，先后任职沪江网高级架构师，以及新东方音视频技术专家。朱捷，拥有超过25年的丰富工作经验和多家知名外企（惠普、安捷伦和EMC）、国企（电信科学研究院）和私企的工作经历。曾运作出版：《生成对抗网络入门指南》、《手机安全和可信应用开发指南:TrustZone与OP-TEE技术详解》、《5G NR标准:下一代无线通信技术》、《MATLAB与机器学习》。魏星，前媒体人，五年以上IT社区技术媒体经历、五年B2B市场经历。现任声网资深技术内容布道师。热爱互联网行业，网络安全与开源项目爱好者，信奉黑客精神和技术的力量。制作团队主播 / 白宦成嘉宾 / 李超、朱捷、魏星后期 / 卷圈封面 / 丁丁产品统筹 / bobo录音间 / 华创资本关于「编码人声」编码人声是一档聚焦程序员成长的播客节目，由资深程序员和年轻开发者共同担任主播。邀请不同背景的程序员担任节目嘉宾，分享程序员职业成长、个人成长经验，为程序员听友答疑解惑。本节目由津津乐道播客网络与声网联合制作。对音视频技术感兴趣？可以到声网Agora RTC 开发者社区了解更多内容。声网Agora RTC开发者社区 | 公众号：声网Agora开发者 | 津津乐道播客官网版权声明 | 评论须知 | 加入听友群
Why Dirty Pipe is a dirty dog, the explosive adoption of Linux at AMD, and an important update on elementary OS.
Why Dirty Pipe is a dirty dog, the explosive adoption of Linux at AMD, and an important update on elementary OS.
Our guest on this week's Friday Fireside is Tsahi Levent-Levi, Analyst and Consultant for WebRTC, publisher of BlogGeek.me, and CEO of TestRTC. Tsahi takes us under the hood of this open-source technology that enables audio and video communications inside Web pages WITHOUT plug-ins. And he explains a critical benefit of WebRTC—significantly lower latency for live video. Low enough to permit in-game sports betting on television. That, RIGHT THERE, is reason enough for all of our viewers to ping Tsahi and learn more.
Every Business owner faces getting clients at one point or another. See how Gilsi went from 0 to 60,000 users with this method. "Go after the thing that makes your irritated at work and try to fix that problem for others." Check out the Clicks and Bricks Academy resources: https://clicksandbricksacademy.com/ Sponsor: https://mygosite.com/ About Crankwheel: CrankWheel is a bootstrapped startup, based in Iceland. It was founded in 2015 by Jói Sigurdsson and Gilsi Sigvaldason, childhood friends from Akureyri in Northern Iceland. Jói worked for 10 years at Google's Montréal office before moving back to Iceland to found CrankWheel with Gilsi, who had a wealth of experience in sales of insurance and finance solutions. Their different backgrounds are the pillar of CrankWheel; Jói was a tech lead at Google working on technologies such as the Chrome browser and WebRTC, whereas Gilsi had on multiple occasion driven hours simply to show a customer his laptop screen. The result was an application that allows salespeople to share their screens in real-time with customers during a sales call Contact the Team: Web URL: http://www.crankwheel.com/ LinkedIn: https://www.linkedin.com/company/crankwheel Facebook: https://www.facebook.com/crankwheel --- Support this podcast: https://anchor.fm/clicksandbricks/support (https://anchor.fm/clicksandbricks/support) Learn more about your ad choices. Visit megaphone.fm/adchoices
© 2020-2025 Ivy Podcast Discovery LLC
