zcesur

I like your take here, thank you

You stream from your OBS directly to Algora, just like Twitch. And we let you multistream to YouTube, X, Twitch just like Restream.

The ads is a new feature, the cool thing is they don't interrupt the stream and show across all platforms.

Most of our users multistream to Twitch, YouTube and X through Algora! We also support aggregating live chat comments from these platforms and embedding them on your screen, and more recently, livestream monetization via in-video ads

Creator of Algora here, thanks for sharing! This was a pleasant surprise :) I posted about our Elixir bounties yesterday on Reddit, and I was not expecting to see it on HN front page the next day.

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!

[1]: https://algora.tv/docs/streaming/multicast

[2]: https://algora.io/org/algora/bounties

Duly noted, we're probably going to add local accounts at some point. For the time being, limiting to GitHub auth has been really helpful to keep the platform focused on developers and combat spam.

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.

I work in a relatively small TS monorepo and waiting on VSCode Intellisense to load the types breaks my flow quite often. A plugin like this would help identify the complex types in the codebase

The challenge is to build an open source MIT-licensed VSCode plugin that shows you the time-to-load of a type in TypeScript

https://tsperf.algora.io

Daniel Roe (Nuxt maintainer) is livestreaming his attempt! https://tv.algora.io/danielroe/latest

algora cofounder here, thanks for the mention! and you're right, we're working to rank up on search results

thanks a lot james! you guys pioneered the video bounty use case, was so impressive seeing 10 videos submitted in just a single day!

https://github.com/triggerdotdev/trigger.dev/issues/249

thank you so much jay! it's been a privilege to work with you

btw you have the most beautiful docs i've ever seen https://www.highlight.io/docs/getting-started/client-sdk/rea...

(algora cofounder here) thank you!

and sorry about that, can you send me a link to the bounty? the list on the homepage should already be sorted by availability

the list on the homepage is sorted by availability so all unclaimed bounties are at the top. you can further customize the sorting in-app!

Hey HN, I'm one of the creators of the tool [1] that was used to post this bounty

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

[2]: https://algora.io/bounties/new

Agreed on all 3 points here, thanks for sharing your thoughts, super helpful

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

I don't think people discussing approaches, asking questions & looking to collaborate is battle royale. In healthy-enough OSS projects that happens with or without bounties

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

Can you show me the 10 people that made duplicate work?

> competition at the expense of cooperation

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.

This year 498 bounties ($53,410) have been rewarded to 166 contributors from 45 countries, they were funded primarily by commercial open source founders/maintainers to support product & devrel (get more work done, grow community, reward contributors, gain visibility). These are the projects https://news.ycombinator.com/item?id=37457921

There's also been a few cases where FOSS users themselves created 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. And this blog post is a rant about it I guess.

I'm one of the founders of Algora.io the platform supporting these open source bounties. Happy to answer questions