From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] ipfsgateway: Remove default gateway Date: Wed, 24 Aug 2022 22:54:44 +0200 Message-ID: <20220824205444.GT2088045@pb2> (raw) In-Reply-To: <6019c79c02a70060448e88ac46d2f7614b73ff63.camel@acc.umu.se> [-- Attachment #1.1: Type: text/plain, Size: 3573 bytes --] On Wed, Aug 24, 2022 at 06:35:04PM +0200, Tomas Härdin wrote: > mån 2022-08-22 klockan 14:52 +0200 skrev Nicolas George: > > Tomas Härdin (12022-08-22): > > > I'd actually argue that in that case we should link a library that > > > implements IPFS, not split developer effort by trying to implement > > > it > > > ourselves. > > > > Is FFmpeg meant to be just a convenient set of wrappers for existing > > libraries, then? > > It Depends. > > If we could rid this project of all NIH:isms that would be great. Only > keep that which is strictly better than other existing libraries, for > example higher-performance decoders. For everything else we can do > subtree merges if people still insist the project should build "out of > the box". > > One excellent example of this is the recent discussion around libxml2. > I maintain that developer effort should go toward improving libxml2. > Only if that is a lost cause, if libxml2 is hopelessly slow or > irredeemably buggy, only then would a new XML parser be justified. It > seems most developers understand this. > But for some reason the notion > that the same applies to *all* parsers, including decoders and > demuxers, this notion is hard to swallow. And similarly for encoders > and muxers. I have yet to see a justification that is anything but > cargo culting. Its not hard to swallow, it simply is wrong. Why is there Tesla ? to build cars ? no "Tesla’s mission is to accelerate the world’s transition to sustainable energy." they could outsource everything, from chip design to batteries to software to the car seats and so on but they dont because its better to reach their goal to do them internally Replace Tesla by FFmpeg, now what is our goal ? Create some free multimedia framework ? I would say that is ultimately, wrong What we had done is to realize peoples multimedia needs and dreams. People wanted to watch all the propriatary formats on free platforms Now today you can play any multimedia file with FFmpeg on any free platform Other things that fit into that mission would be implement a streaming tool and infrastructure to replace youtube & tiktok Its multimedia and its something people want, no advertisements, no "advertisers first" Censorship resistant and private multimedia communication is another potential goal. Just a few days ago i read about some guy who got all his accounts terminated because his wife sent a picture from their son to their doctor using his phone. The police was then lookin through the guys pictures without his knowledge and determined its all fine but the police couldnt even contanct him because his phone number and all was terminated. This is not how communication should work, i mean if you send a picture from your son to your doctor NOONE should be able to look at that except your doctor. Not apple, not the police not the government These are ideas, they need people to work on them, iam just saying that IMNSHO these would belong into FFmpegs mission. now do we need a internal mxf demuxer and muxer for these ? It depends whatever is more efficient in reaching our goals. Personally i think internal mxf code is better but i could be wrong. ill send a 2nd mail more specifically about mxf [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Whats the most studid thing your enemy could do ? Blow himself up Whats the most studid thing you could do ? Give up your rights and freedom because your enemy blew himself up. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-08-24 20:54 UTC|newest] Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-10 22:27 Derek Buitenhuis 2022-08-11 12:08 ` Timo Rothenpieler 2022-08-11 16:26 ` Mark Gaiser 2022-08-11 16:49 ` Timo Rothenpieler 2022-08-11 17:21 ` Mark Gaiser 2022-08-11 17:35 ` Timo Rothenpieler 2022-08-11 17:56 ` Mark Gaiser 2022-08-11 19:18 ` Derek Buitenhuis 2022-08-11 20:18 ` Michael Niedermayer 2022-08-11 22:03 ` Timo Rothenpieler 2022-08-11 22:51 ` Derek Buitenhuis 2022-08-12 13:43 ` Mark Gaiser 2022-08-12 14:22 ` Vittorio Giovara 2022-08-12 14:30 ` Kieran Kunhya 2022-08-12 14:34 ` Mark Gaiser 2022-08-12 14:45 ` Kieran Kunhya 2022-08-12 14:48 ` Derek Buitenhuis 2022-08-12 14:50 ` Kieran Kunhya 2022-08-12 14:55 ` Nicolas George 2022-08-12 15:05 ` Michael Niedermayer 2022-08-12 17:01 ` Nicolas George 2022-08-12 17:18 ` Michael Niedermayer 2022-08-12 17:21 ` Timo Rothenpieler 2022-08-13 16:29 ` Michael Niedermayer 2022-08-13 19:06 ` Timo Rothenpieler 2022-08-14 18:00 ` Michael Niedermayer 2022-08-15 14:09 ` Nicolas George 2022-08-15 14:27 ` Jean-Baptiste Kempf 2022-08-17 15:03 ` Tomas Härdin 2022-08-18 14:31 ` Michael Niedermayer 2022-08-19 9:15 ` Tomas Härdin 2022-08-19 12:52 ` Mark Gaiser 2022-08-22 9:12 ` Tomas Härdin 2022-08-22 12:52 ` Nicolas George 2022-08-23 12:53 ` Ronald S. Bultje 2022-08-23 12:55 ` Nicolas George 2022-08-24 16:35 ` Tomas Härdin 2022-08-24 20:54 ` Michael Niedermayer [this message] 2022-08-27 7:05 ` Tomas Härdin 2022-08-28 14:14 ` Michael Niedermayer 2022-08-24 21:03 ` Michael Niedermayer 2022-08-24 21:18 ` Kieran Kunhya 2022-08-25 13:57 ` Michael Niedermayer 2022-08-25 14:41 ` Kieran Kunhya 2022-08-27 7:29 ` Tomas Härdin 2022-08-27 7:53 ` Paul B Mahol 2022-08-27 11:30 ` Tomas Härdin 2022-08-27 17:34 ` Baptiste Coudurier 2022-08-28 11:49 ` Tomas Härdin 2022-08-15 17:53 ` Michael Niedermayer 2022-08-15 19:35 ` Derek Buitenhuis 2022-08-15 19:37 ` James Almer 2022-08-15 21:47 ` Michael Niedermayer 2022-08-15 21:57 ` Nicolas George 2022-08-15 23:53 ` Mark Gaiser 2022-08-16 14:46 ` Michael Niedermayer 2022-08-14 13:24 thelostone123
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220824205444.GT2088045@pb2 \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git