Hacker News new | past | comments | ask | show | jobs | submit | newusertoday's comments login

this can't edit, its for viewing only. I use it regularly.

i wish there was something like this for wasm. There are wasm builds available but its not easy to extend them with your own functions.


if this app would have provided links to the startup it would be so much better even if they were defunct one could easily search more about them.


this should be faster https://github.com/webfft/webfft.github.io technically because it is using hardware for fft whereas current library is doing them on cpu but there is additional overhead with hw so we would actually have to test it.


you can use remotion which this project is using


i remember reading your blog and following your journey in the initial years it was quite inspirational and i learned so many things along the way thanks to you and @patio11. Thanks for sharing and be open about it.


reinstall bootstrap and be done with it. You can look at daisyui it is closest to bootstrap. There is also shadcn ui, ui looks good but it would take you effort to port styles to your phoenix project.


table has two parts to it, displaying of data and datawrangling. If you separate datawrangling part to api or sql or arquero than displaying of data becomes quite simple. You may not need ag-grid like library.


most likely xyflow


how are you able to get around ffmpeg licensing since it is client app which requires you to open your code if you use ffmpeg GPL?



FFmpeg is mostly LGPL and has very clear and helpful instructions about how to incorporate and distribute it in compliance.


It does not require that you do that. It only requires you to open source any modifications you've made to ffmpeg.


it is slightly more nuanced, if you do static linking it is considered derivative work and does requires you to open it. Since the app is based on ffmpeg which is GPL(core is LGPL) i am curious to know how it is getting used.


Static linking of LGPL content (thus making it derivative work) only requires that it must allow "modification of the work for the customer's own use and reverse engineering for debugging such modifications".

Making your own code public is not the only way to achieve this.

You can also make available to customer object files and build instructions to recreate your software with the (modified) statically linked LGPL content. (if it's LGPL > 2.1 you have extra requirements: you need to provide all toolchains/dependencies and it must be actually possible to install a modified version on the hardware)

Granted, this is not commonly used but I've used this on some projects where dynamic linking was not available/desired by client.


i didn't bundle the ffmpeg in the app. It uses homebrew to install ffmpeg on the user's device. this is the acceptable way since ffmpeg confirms it on twitter/X.

https://x.com/FFmpeg/status/1766649563891339510


This tweet also explicitly says "But still would be nice to have some credit.".

Why isn't FFmpeg mentioned on your app's website?

The same goes for ImageMagick by the way.


there is a dedicated page for credits: https://pimosa.app/credits


it uses homebrew to install the FFmpeg on the user's device. the app doesn't bundle any libs to comply with their license limitations.


O_o, well that was a short lived app.


FFmpeg is LGPL, not GPL. This means that you can link it in non open source apps and only have to open source modifications to FFmpeg itself.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: