ffmpeg.wasm VS Postwoman

There's already ffmpeg wasm. I've used it in projects. Works great.

https://github.com/ffmpegwasm/ffmpeg.wasm

There's a low-hanging fruit that I think would make ffmpeg more helpful for regular people.

There's a million terrible websites that offer file conversion services. They're ad-ridden, with god-knows-what privacy/security postures. There's little reason for users to need to upload their files to a third-party when they can do it locally. But getting them to download fiddly technical software is tough - and they're right to mistrust it.

So, there's a WASM version of ffmpeg, already working and hosted at Netlify [1]. It downloads the WASM bundle to your browser and you can run conversions/transformations as you wish, in your browser. Sandboxed and pretty performant too!

If this tool a) was updated regularly b) had a nicer, non-CLI UI for everyday users and c) was available at an easily-Googlable domain name - it would solve all the problems I mentioned above.

[1]: https://ffmpegwasm.netlify.app/

As their github page says, based on https://ffmpegwasm.netlify.app ...

I'm guessing no one did GPU-optimizations? I saw a web app (not an ffmpeg transpilation) that went clever and used WebGL so it can access the GPU and use its parallel processing capabilities...

ffmpeg.wasm: The engine making all these happen. However, I’m a bit concerned about its current situation. The repo has not been updated for more than six months now, and that’s not a healthy sign for an open-source project. Clearly I was reading the commits wrong. The author mentioned “speed up x264 with SIMD intrinsics” in their roadmap (https://github.com/ffmpegwasm/ffmpeg.wasm/discussions/415), which, if landed, could make such on-device video editors much more competitive.

I use https://github.com/ffmpegwasm/ffmpeg.wasm and I want my FFMPEG commands to be hidden from others.

Possibly using this? https://github.com/ffmpegwasm/ffmpeg.wasm

You could try using something like ffmpeg wasm which is a way of using ffmpeg client side in browser. Unfortunately WebAssembly only supports files less than 2 gigabytes, which is a problem for videos. And I don't know if ffmpeg wasm contains ffprobe, so you might have to find another project or try to compile ffprobe to wasm yourself. This stuff is out of my wheelhouse so I can't offer much help.

How can Hoppscotch help you intercept the API calls? 👽

We need you help to constantly improve Hoppscotch so that we can make it easier for you to build better software! Write to us at [email protected] or head over to our GitHub repository if you have any feedback about Hoppscotch 💚!

For the past five years, Hoppscotch 🛸 has been quietly transforming the way developers tackle their work in the API development world. Our mission has always been to make developer's lives easier and their workflows smoother, all from the comfort of their browser. And guess what? We might have evolved and gotten strong, but we are staying true to our goal of simplifying things for developers everywhere. Today, we're here to spill the beans on the simple yet powerful productivity hacks that Hoppscotch offers. Get ready to level up your development game in ways you never imagined.

Hoppscotch is a powerful yet simple-to-use API testing suite. It removes a lot of complexity, making it easy for anyone to get started with API testing. Try Hoppscotch now!

Hoppscotch - HTTP client used for sending notifications through the Google API.

We began as a web-based API client at hoppscotch.io, where anyone can easily initiate API testing. Ever since then the Hoppscotch Desktop app has been a highly requested product by our community. We've been listening and are excited to announce that the day has finally arrived - today marks the launch of the public alpha version of the Hoppscotch Desktop App for macOS, Windows, and Linux!

We’re building an open-source Postman alternative.

1.6m+ users, 100k+ monthly active users, 55k+ GitHub stars.

Web app: https://hoppscotch.io

The collective efforts and commitment of our team has led Hoppscotch towards remarkable improvements on its path to transforming the API development ecosystem. But, the speed of evolution we've experienced wouldn't have been possible without the open-source nature of Hoppscotch. A significant portion of our success is attributed to our dedicated contributors who have resolved existing issues, filed bug reports, authored blogs, created tutorials, and spread the word about Hoppscotch within their networks 🤝 .