Meeting recording (local or cloud)

[hyunbinseo]

Support for meeting recording, either on the client or in the server.

It works by launching a Chrome instance rendered in a virtual framebuffer and capturing and encoding the output with ffmpeg. — Jibri, JItsi BRoadcasting Infrastructure

Similarly,

• plugNmeet Recorder uses Chromium and FFmpeg.
• Nextcloud Talk Recording uses Firefox and FFmpeg

[AdityaKotkar47]

a similar feature exists in Zoom [both local and cloud video recording]
this feature in orange will be highly appreciated

[balupton]

I've also asked about this on the Cloudflare discourse: https://community.cloudflare.com/t/recording-of-cloudflare-calls/663716?u=balupton

[Vaib215]

Is there any update on this thing

[dpurnam]

Bump

[danjenkins]

Not a cloudflare employee but honestly the most annoying thing is getting "bump" and "is there any update on this thing" on issues, especially feature requests that no-one from Cloudflare has said they're going to implement. Bumping it won't get it worked on. It's a demo app, if you want that functionality why not write a pull request? Or pay someone to write it if you can't.

You can also 👍 to the original post to show support for wanting it added.

[balupton]

Not a cloudflare employee but honestly the most annoying thing is getting "bump" and "is there any update on this thing" on issues, especially feature requests that no-one from Cloudflare has said they're going to implement. Bumping it won't get it worked on. It's a demo app, if you want that functionality why not write a pull request? Or pay someone to write it if you can't.

You can also 👍 to the original post to show support for wanting it added

@danjenkins they are building a developer platform for calls and video and live streaming and storage, it is appropriate and reasonable to ask their plans regarding inevitably mixing these into call recording, especially on their demo repo that advertises these technologies for dev uptake on their platform, and especially before the community tries to implement something; getting first-partied hurts. I've been an independent open-source developer for 20 years, I know that pain and loss all too well. No one should invest and waste time into building a feature/technology for a commercial platform that they do not control nor do not have a statement about. The proper onus for this dev platform feature is with cloudflare, maybe even in partnership with their customers, but certainly not their community. Secrets can be a competitive edge in business, but they are harmful to community.

that no-one from Cloudflare has said they're going to implement

They haven't said anything contrary either, which is a big first-partied warning-sign/red-flag to anyone from the community wanting to undertake this. It is a need, and bumping that need is appropriate until there is a statement either-way; or say word on a cloudflare customer, business partner, or competitor financing/building/spearheading an intermediate solution with all the secrecy risk associated with it.

The community isn't going to spend their precious time ever competing with cloudflare, that is bankruptcy, we are going to spend our precious time leveraging cloudflare in a way that never competes with them. That's our place, we don't build features that could be in their platform, we leverage their platform features to build our own community and business features. We know our place, and we know where we stand.

Business partners from the community might be able to leverage in ways that the open community cannot; however business partners are not competing with cloudflare; they are leveraging closed privileged relationships and positions to push the platform forward while maintaining their competive edge; an affordance the open community is without.

It's a demo app, if you want that functionality why not write a pull request? Or pay someone to write it if you can't.

But yes, noted that you think the open community should foot the bill for building an enterprise company's closed platform features. Got it.

[danjenkins]

Asking in discourse is the appropriate place. As you had already done. Others bumping an issue and asking for updates for a demo app isn't very open source friendly is it - as an open source developer you should know that pain too. "Bumping" an issue that's actually a feature requests is rude. I'll leave it there.