From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id E024949A2F for ; Sat, 27 Apr 2024 10:54:11 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 077BD68D2A7; Sat, 27 Apr 2024 13:54:08 +0300 (EEST) Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 97A7D68D164 for ; Sat, 27 Apr 2024 13:54:01 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id CCD9BC0002 for ; Sat, 27 Apr 2024 10:54:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1714215241; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=O4WmXYUJn3WN716GvJjO0IlosqKG+VFFsg7rpMbB/gs=; b=T5a9wsgCbRCDucXl+KpBMx2KidCzEfx+1mtugbN/hh0X6fD87l0/m2AFAcZyiA/31/gxdE CrYlCTlftXty3khgMsgCX+nzLf1YIKd1zSRXL2MnuRlwRrGO4uwi0xKcF2q7uaPjAKa67M tSyOuOpDs/20Bph2A3dQTuMplkPYKYECJVKC7gLzkoh3A61ADLKz+NBKKxL8PCEL6hoLaZ c0eGL2qlalSUp9iEexFD+YZDqfDVzIq/ZXzwdiUr9mUIGUjp0O6UqU+6o7aIKU8FghhGmd pZRRGlUklEwYdKSArKEn9Ytv/pqocQyTvVN6eJ0e9LSgthIElzunGhff+/T8CA== Date: Sat, 27 Apr 2024 12:53:59 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240427105359.GC6420@pb2> References: <20240417135832.GJ6420@pb2> <20240425000702.GW6420@pb2> <585c2c9d567fca5a778d3f86a657e78c32c833cd.camel@haerdin.se> MIME-Version: 1.0 In-Reply-To: <585c2c9d567fca5a778d3f86a657e78c32c833cd.camel@haerdin.se> X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [RFC] 5 year plan & Inovation X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============8788480083264103721==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============8788480083264103721== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="sBx1l70Xr1x9fsLk" Content-Disposition: inline --sBx1l70Xr1x9fsLk Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 25, 2024 at 12:26:00PM +0200, Tomas H=E4rdin wrote: > tor 2024-04-25 klockan 02:07 +0200 skrev Michael Niedermayer: > > On Thu, Apr 25, 2024 at 12:50:02AM +0200, Tomas H=E4rdin wrote: > > > ons 2024-04-17 klockan 15:58 +0200 skrev Michael Niedermayer: > > >=20 > > > > * ffchat > > > > =A0=A0=A0 (expand into realtime chat / zoom) this would > > > > =A0=A0=A0 bring in more users and developers, and we basically have > > > > almost > > > > =A0=A0=A0 all parts for it already but some people where against it > > >=20 > > > You mean inventing a new chat protocol? If so then please don't. We > >=20 > > If theres an existing protocol that serves the purpose then theres no > > need to invent a new one > >=20 > > I think at a minimum it should have "secure and private by default > > and always" > > (there are many solutions already when one is willing to give up > > security/privacy) >=20 > "Security" and "privacy" are relative terms. yes, more security and privacy is better >=20 > If you want end-to-end encryption in a federated system then XMPP+OMEMO > is the way to go. Or Matrix I guess, but it isn't standardized last > time I checked. >=20 > If you want metadata resistance then Briar is the way to go. It's a > peer-to-peer store-and-forward network that tunnels all its internet > traffic through Tor, and also supports synchronizing messages over WiFi > Direct and Bluetooth. >=20 > There's also GNUnet and its associated protocols like psyc. >=20 > Short of using some complicated thing involving data diodes you're not > likely to do better than what's already out there. And nothing beats > not using computers at all. sure, i agree, we should use existing protocols whenever one exists for a purpose already ... libavformat supports, RTP, RTSP, MMS, HLS, RTMP and probably more we support audio, video, data and text packets/streams So adding support for some more secure/private protocols is within the scope of libavformat. And it would allow all multimedia players to use these more secure means of communicating. As well as writing dedicated secure chat applicatio= ns on top of libavformat. This would bring in more users and developers thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I have often repented speaking, but never of holding my tongue. -- Xenocrates --sBx1l70Xr1x9fsLk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZizZQwAKCRBhHseHBAsP q0rnAKCGs7SkKUgPH8bWIUPN1K0SOiRqpwCfUZefdcQozEhExWCxG7vA0u1Grmw= =oP08 -----END PGP SIGNATURE----- --sBx1l70Xr1x9fsLk-- --===============8788480083264103721== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============8788480083264103721==--