It’s been a year since Waasabi's first prototype was conceived, so amidst the ongoing planning of our second large conference and onboarding of new early-adopters to Waasabi Beta it's time we discussed what's already done and what we sets ours sights on for the the upcoming updates.
It was November when last year the first version of Waasabi powered rustfest.global. Like many other events, we too were forced to migrate into cyberspace, and Waasabi was our way response to seeing the lack of creativity and missing tooling in the online event space. Since then we have been moving our learnings and code from that experimental version into an open and flexible framework under the Waasabi Framework's umbrella.
In the past months multiple events (Rust Berlin meetup, Rust Hungary meetup), even our own development stream the Waasabi Live stream has used Waasabi as we worked to constantly evolve and expand its feature set through this feedback.
The work is still far from done, though Grant for the Web has enabled much experimentation and laid the foundations upon which we may continue expanding the initial scope as we dive deeper into creating the tool that will enable the engaging interactive experiences we have envisioned.
All Waasabi components are open source, released under the Apache-2.0 license on Bay Area Tech Club's GitHub.
Waasabi set out to
"solve the hard problems of event streaming"
and through this, to enable event organizers build custom experiences, quickly. The toolkit's underlying concept is to create a coupling of efficient live streaming and a variety of realtime integrations (such as chat, captions, interactive experiences and more). Waasabi is the "hub" that aggregates data from all these systems and provides a unified API, as well as real-time event notifications (e.g. of incoming messages or when a new live stream is started).
Instead of a single, long-running live video stream — which is how most online events today are usually structured — Waasabi encourages a single stream per program and will take care of starting & switching between streams automatically. It may even multiplex multiple simultaneous live streams, for example to allow showing the live stream and a live sketchnoter, side-by-side.
Waasabi's Core module extends the open source Strapi content management system with its own preset template. Waasabi's template is used by the installer (see below) when creating a new Waasabi instance from scratch.
The Strapi administration interface of the instance can be used to manage Waasabi's events and broadcasts. Strapi's API can be used from any existing website to integrate streaming functionality. The Waasabi Installer also provides a "Live Event starter kit" that can be used for the live experience and further customized if needed (more on this later).
The current Beta focuses on public events, while built-in registration, ticketing and user management has also been previewed at RustFest Global 2020, and is coming to the suite in the next version.
Waasabi aims to be a collection of tools
"…for [event] organizers who want to experiment with new event formats and business models…"
It intends to encourage & help organizers fully embrace that online events come with a completely different set of limitations, when compared to in-person events, but also have their unique advantages. For example, people might be less focused and less present during day-long digital events: in-person events bring with them a very different headspace, that cannot be replicated from home. On the other hand, given enough flexibility and organizer support, features like Waasabi's instant replays, captioning and other affordances can make online events orders of magnitude more accessible, with a much larger, potentially global reach.
During RustFest we wanted to use Web Monetization for more than just a revenue source for the event: we wanted it to serve as an incentive for the true producers of the conference content, the speakers and artists.
The way this is currently implemented in Waasabi, is that every session can be assigned a Payment Pointer and Waasabi takes care of switching to the correct payment pointer during the session’s runtime. While this works, it’s a crude solution that raised multiple other issues:
- What happens if a session has more than one speaker/collaborator?
- Having all speakers and artists register & share their Web Monetization-enabled wallets was cumbersome and many missed the opportunity due to this friction;
- Making sure the attendees had Web Monetization-enabled clients (subscription with the required extensions installed) resulted in even more friction.
With increased awareness and adoption some of the above issues could be alleviated, but we are also looking into Rafiki, and exploring hosting our own Interledger service within Waasabi, which could provide a lot more flexibility in these micropayment integrations and open up more creative ways to utilize Web Monetization in Waasabi with greatly reduced friction.
Initially we had planned to enable using Web Monetization as an access control mechanism: gating some of the content, or enhancements such as higher resolution streaming behind streaming payments. Watching the evolution of online community conferences, it quickly became clear that:
- in order to have the best possible, global reach and make community events accessible to all a free event or free tier is needed;
- in fact, many seem to came to expect online events to be free, with costs covered mainly by corporate sponsorships;
- but one can still capture funds via “ticket” sales by providing extra features, especially when employees can forward these costs to their employers.
Due to these, Web Monetization access control to these additional features or the stream itself became a lower priority and this first Beta focuses on publicly available events.
We are looking at potentially implementing video access control and monetization via Peertube, a new video backend we integrate with. Peertube is receiving first-class Web Monetization support via another GftW grantee’s project and making this available within Waasabi is something we are looking into.
Waasabi’s goal is to enable everyone create their own custom digital event experience. This means we need find ways to allow people create highly customized instances relatively easily.
Our initial approach focuses on the Waasabi Installer, a cross-platform command line tool focusing on the more technologically adept users of Waasabi. This tool allows configuring all of Waasabi’s features and generating a new instance, that can be ran locally for testing or deployed directly on a server.
Currently direct server/cloud deploys are not implemented yet, but the configuration files generated by this tool makes it rather trivial to run Waasabi on any cloud or webserver that is based on Debian, or one that at least can run Ubuntu containers or virtual machines.
Waasabi and the Installer runs well in WSL, so Windows users can also configure and test Waasabi instances before deployment.
As noted before, Waasabi’s core provides an API to embed the live streaming functionality directly into one’s existing website. We plan to provide more “batteries-included” tools for this in the future (such as iframe-based integrations, and plugins for popular website tools, such as Wordpress), but currently this needs to be done manually.
To make Waasabi usable even without the need for lengthy manual integration, we provide an out-of-box experience with the Waasabi Live Page. This interface can be configured under a subdomain of the existing website and provides complete functionality of Waasabi: streaming, Web Monetization, chat integrations and more. Some in-development upcoming features such as registered user management are coming soon as well.
One of Waasabi’s fundamental goals was stated to be:
"[allow organizers to] integrate their live events into their existing community infrastructure"
Waasabi explicitly opts for not reinventing a wheel, and does not provide a built-in chat within the live stream page itself, but instead chooses to integrate with existing chat providers. Many communities who do live streaming already have an existing community chat which they often end up wanting to integrate with their live streaming platform of choice anyway, so Waasabi circumvents this by going the other way right off the bat.
Multiple integrations are planned for Waasabi, but the currently implemented one in the beta builds on the robust and fully open source Matrix network. Currently this means messages sent on the linked chat rooms are relayed to the live stream.
Once the work-in-progress account management pieces land users will be able to join private channels from the Waasabi interface. This feature was initially used at RustFest Global, and allowed attendees to be added to specific conference channels automatically or on request. Ensuring proper access control of the event chat is really important (especially for publicly accessible live events), and allows hosts to perform better moderation, enforcement of the event’s code of conduct and keeping the conference chat safe for all participants.
As noted, we are still looking into integrating with more chat services, especially looking at Discord and Slack to allow event hosts to bring their existing community into their events, as well as use their events (meetups, streams, etc.) as a funnel to bring more community members onto their community chat of choice.
Waasabi tries to offer as much flexibility on the axes of content ownership and full control as possible. Administrators of the instances can configure Waasabi with the Mux.com streaming backend provider for a reliable conventional streaming service, or choose Peertube and many other planned self-hosted video backends that fit their requirements. The framework allows for making these decisions in accordance with one’s requirements, expectations, scaling needs and other individual needs.
We are also experimenting with tools for automated captioning, improved transcripts and similar accessibility improvements. You may learn more about our experimental work as part of this grant to bring machine learning and speech recognition to Waasabi without third-party dependencies by reading our last detailed report!
Waasabi exposes the low-level building blocks of live streaming. This has already made functionality like instant replays and web monetization possible, and we are constantly experimenting how could we use these possibilities in novel, unconventional ways.
Waasabi is also embracing various peer-to-peer technologies in a form of another grant. The Peertube video backend is one of the first early results of this effort. We strongly believe peer-to-peer technologies allow for better positioning these self-owned and individually controlled streaming hubs, further improving discovery, robustness and reach of the instances, allowing Waasabi to provide a viable alternative to large corporate silos.
In the name of unparalleled flexibility we set out to encourage a Waasabi ecosystem of
“[…] a growing library of open source plugins and integrations
contributed back by the community building on Waasabi”
There is no point of pushing for plugin development before the stabilization and proper documentation of Waasabi’s API, but once these pieces fall into place we are looking forward to people building new integrations and contributing back to the commons. Until then, of course, Waasabi instances can be customized in the ways mentioned further above, and of course bugfixes and feature contributions to Waasabi’s open source codebase are appreciated and encouraged as well.
Waasabi’s website has recently went live and is continuously being expanded with documentation, guides and updates. We are also waiting for Waasabi’s first branding to be delivered to dress the project into a brand new exciting and playful gown.
Waasabi’s development live stream is currently offline as it is being upgraded to the latest Waasabi version, and shall be returning with development updates in the coming weeks.
We are constantly looking for early adopters interested in experimenting with this early release of the Waasabi suite (and are in contact with few already), and we plan to bring back the RustFest conference this fall, this time around using the open source Waasabi suite instead of the experimental version from 2020.
We are ready to answer any questions and discuss Waasabi’s future in our dedicated Matrix channel at
The development of Waasabi continues, there are many things to look forward to!
- Accounts and registrations (e.g. for ticketing)
- An advanced event administration interface, provided by the “event-manager” Strapi plugin of the Waasabi template
- Subscribe to events on the live page (email notifications, add-to-calendar, RSS and more)
- P2P enhancements, distributed streaming and connecting to decentralized networks
- Independent automatic captioning and transcript-augmentation via customizable machine learning detection
- Further Web Monetization and Interledger-experiments using Rafiki
Some of these features above we plan to experiment with and test on our upcoming RustFest conference this fall, and other early-adopters.
Interested or have questions? Join our Matrix channel and talk to us!
Want to run your own event? Please reach out, we’d love to help!
Like what we are doing? Consider supporting the project on Open Collective.
Find links to all of these channels below.