242 karma · joined March 20, 2018
socials: - x.com/whizzaf - zafer@algora.io - github.com/zcesur
The ads is a new feature, the cool thing is they don't interrupt the stream and show across all platforms.
I've been building this since early this year. Over the past few months, developers like Daniel Roe (Nuxt.com maintainer), Chris Griffing, Andras Bacsai (Coolify.io maintainer) have been livestreaming with Algora their coding sessions, office hours, product launches, podcasts, and more.
Algora TV supports free multistreaming to Twitch, X, YouTube, custom RTMPs [1] and aggregates live comments from these platforms.
I chose to build Algora in Elixir because of a few reasons: 1) Productivity gains from using Phoenix LiveView are unparalleled as a solo developer 2) OTP is super helpful for handling complex streaming pipelines. Things like multistreaming, mirroring chat messages, capturing thumbnails etc. can fail at any time, and OTP makes it easier to build fault-tolerant processes 3) BEAM clustering allows distributing the system across multiple nodes with ease, which helps reduce latency between streamers and viewers.
As the sole maintainer of the project, I'd love to get your help with improving Algora! If you're up for contributing, I've put up a bunch of bounties [2] to prioritize some issues.
In any case, I'd love to hear from you if you have any feedback or questions!
Any S3-compatible storage should work fine! That being said it would require a lot more work to set it up as you also need to worry about caching, replication, distribution etc. For a livestreaming platform it's super important to ensure livestreams are available globally to minimize latency for viewers.
Tigris has all of this built-in, so it already behaves like a CDN. It's what we use on https://algora.tv and we wanted to make getting started as easy as possible for our contributors and anyone who's looking to self-host.
btw you have the most beautiful docs i've ever seen https://www.highlight.io/docs/getting-started/client-sdk/rea...
and sorry about that, can you send me a link to the bounty? the list on the homepage should already be sorted by availability
Normally it's the maintainers who create the bounties using our Github app, however in this case our experimental "community bounties" feature was used by Wasmer to create a bounty in someone else's repo (Zig). I think that's where everything went wrong
We have updated the feature [2]. Community bounties are now by default shared privately with the maintainers only, and maintainers can decide to complete the bounties themselves, share them with the contributors, or discard them. That way community bounties are never intrusive to maintainers' time, roadmap & governance while also acting as a sponsorship if accepted
We're sad to see our tool enabling this drama and hope the feature update will prevent this from happening again
[1]: https://algora.io
Following your feedback, perhaps community bounties should be by default only shared with maintainers, and then the maintainers can choose whether to complete them themselves [1], or make them public, or disregard
This approach would prevent situations like the above and hopefully also helps with FOSS sustainability
[1]: https://twitter.com/algoraio/status/1703115434055082086
Also some sort of acceptance criteria have to be in place, and "first viable solution gets the reward" is reasonable enough
People have agency to make decisions such as trying to solve a bounty (to get experience, feedback from peers/maintainers & maybe a reward) but you decided to shut them down, delete their comments and get offended on their behalf
You're not obligated to entertain, review or merge code you don't approve and it was your right to shut down the initiative by Wasmer
We've seen contributors author PRs together and split bounties. Also contributors in the Zig thread were actually trying to collaborate on a solution (comments were deleted)
> Instead of scouting for a suitable candidate
Open calls have faster turnaround & lower overhead
> clear contract ... payout
Sometimes design & implementation is not decided and spec'ed in advance and multiple perspectives & sometimes PoCs are required, at which point the maintainers can choose a plan of action and assign a developer without much duplicate work. That's classic OSS dev with or without bounties.
https://news.ycombinator.com/item?id=37543536 there's more replies here that I agree with
--
I also suggest you checkout the discussions deleted by Zig for a full perspective https://pastebin.com/nDA0LD3N
As a matter of fact the initial convo on the thread proved contrary to the every point made regarding competition and "battle royal dynamics" as people attempting the bounty were actually collaborating. We've seen quite a few cases where people authored PRs together and split the rewards on Algora.
In addition there was no "pressure on the development team to accept the winning submission" it was explicitly stated that the work did not need to be merged upstream, and that the sponsorship would be awarded as soon as the technical requirements were met.
--
Ultimately, bounties are a tool. It's in maintainers' discretion whether or not to use it.
The optimal design for a bounties platform is still a work in progress. We're two bootstrapped founders (one developer) figuring things out along the way, trying to give folks a good experience and trying to learn.
There's also an experimental use case where FOSS users themselves create bounties to pay contributors/maintainers to ship new updates and features. We call these 'community bounties'. The $5,000 WASIX support bounty in Zig was created by Wasmer, but the Zig maintainers didn't welcome it (which is totally fair, it's their choice) and this blog post is a rant about it I guess?
We've been lucky to serve incredible orgs & contributors and we hope to see the community grow :) Some projects today include:
---
Trigger.dev (YC W23, 4.3K stars, typescript) • The Background Jobs framework for Next.js • https://algora.io/org/triggerdotdev
Cal.com (23K stars, typescript/nextjs/trpc) • Scheduling infrastructure • https://algora.io/org/cal
ZIO (3.9K stars, scala) • A type-safe, composable library for async and concurrent programming • https://algora.io/org/ZIO
Highlight (YC W23, 5.7K stars, typescript/go) • The open source, full-stack monitoring platform • https://algora.io/org/highlight
Remotion (17K stars, typescript/react) • Make videos programmatically with React • https://algora.io/org/remotion
Qdrant (12.7K stars, rust) • Vector Database & Search for AI applications • https://algora.io/org/Qdrant
Million.js (12.6K stars, typescript/react) • The Virtual DOM Replacement for React • https://algora.io/org/aidenybai
Capgo (355 stars, java/swift) • OTA and Testing for capacitor apps • https://algora.io/org/Capgo
Refact (806 stars, python/javascript) • Open-source AI code assistant for JetBrains and VS Code • https://algora.io/org/smallcloudai
Dozer (1.2K stars, rust) • Turn data sources into real-time REST/gRPC APIs • https://algora.io/org/getdozer
Hanko (2.2K stars, typescript/go) • The authentication solution for the passkey era • https://algora.io/org/teamhanko
OramaSearch (6.3K stars, typescript) • Fast, in-memory, typo-tolerant, full-text search engine • https://algora.io/org/oramasearch
Documenso (3.6K stars, typescript/nextjs) • The Open Source DocuSign Alternative • https://algora.io/org/documenso
Tigris (793 stars, typescript/go/python) • Storage Platform For Real-Time Apps • https://algora.io/org/tigrisdata
Rosenpass (855 stars, rust) • Formally verified, post-quantum secure VPN using WireGuard • https://algora.io/org/rosenpass
WunderGraph (1.9K stars, typescript/graphql/go) • Build, manage & compose APIs • https://algora.io/org/WunderGraph
Rowy (5.1K stars, typescript) • Open-source low-code backend platform in the browser • https://algora.io/org/rowyio
Novu (24K stars, typescript/react) • The open-source notification infrastructure • https://algora.io/org/novuhq
tRPC (28.6K stars, typescript) • End-to-end typesafe APIs made easy • https://algora.io/org/tRPC
Plate (3.8K stars, typescript/react) • The rich-text editor framework for React • https://algora.io/org/Udecode
Mudlet (645 stars, c++/lua) • A cross-platform, open source, and super fast MUD client • https://algora.io/org/Mudlet
erxes (3.1K stars, typescript) • Single experience operating system (XOS) • https://algora.io/org/erxes
Shelf (1.1K stars, typescript/remix) • Open source Asset Management Software • https://algora.io/org/Shelf-nu
IHP (4.1K stars, haskell) • Batteries-included web framework • https://algora.io/org/digitallyinduced
crowd.dev (735 stars, typescript/vue) • Centralize community, product, and customer data • https://algora.io/org/CrowdDotDev
Upstash (839 stars, typescript) • Serverless Data for Redis and Kafka • https://algora.io/org/upstash
Meteor.js (43.7K stars, javascript) • The JavaScript App Platform • https://algora.io/org/meteor
shuttle (YC S20, 3.6K stars, rust) • Making Rust the next language of cloud-native • https://algora.io/org/shuttle
Keep (YC W23, 2K stars, python) • The open-source alerts management and automation platform • https://algora.io/org/keephq
Prisma (33.7K stars, typescript) • Prisma makes working with databases easy • https://algora.io/org/prisma
https://algora.io/org/smallcloudai/bounties
disclaimer: i'm a cofounder of algora, the platform enabling these bounties
I'm personally using Cal.com, it's free and I'm very happy. I'm also very biased because we interviewed the co-founder/co-ceo [1] and Cal.com uses our platform to reward its open source contributors [2]
what I love most about Cal is how young developers from around the world learn modern tech by contributing (and getting trained by the team) [3], support is crazy good [4] and the company builds in public, even their salaries and metrics are open [5]. I cannot not be a fan honestly
[1] https://youtu.be/gymNEH-skAY
[3] https://github.com/calcom/cal.com/pulls
we soon realized these interviews had a lot of gold nuggets which we had to share with the world, so we started publishing these on youtube [2]
since then it's naturally evolved into a podcast series and we think this initiative actually made a big difference for us. ymmv
[1]: https://www.linkedin.com/feed/update/urn:li:activity:7077280...
disclaimer: i'm a founder at algora.io, the platform that enables these paid contributions