Re: linphone, still free?

[Krzysztof Siewicz]

On 17.12.2024 02:57, Lorenzo L. Ancora wrote:
> > > > > > This issue seems to be about the android version I haven't found any 
> > > > > > information about this binary library being used in the desktop version.
> > > > > Can users of the free versions chat, audio-call or video-call with users of the 
> > > > > non-free binary?
> > > > It seems reasonable that they can.
> > > By reasonable, do you also mean acceptable when it happens without the user 
> > > knowing? What could be the ethical and safety implications?
> > Do you mean if I chat/audio/video from my computer with a free version of 
> > Linphone to a user on an android device with the nonfree version of Linphone
> Mr. Siewicz may not be done yet and I don't like putting pressure, so let's say 
> "from any free version to any non-free version, regardless of the platform".
> Then, we are calling the component non-free but I'm optimistic the source code 
> will be easily found around and it is really a non-issue. A good light thing to 
> discuss right about before Xmas.🎄
I would actually be grateful if someone who has more time checked how 
free and nonfree versions of Linphone talk to each other. That might 
also save us from continuing this discussion (although it would be great 
to continue it and come up with a general, ideal conclusion).
> > I should be responsible for the other's use of nonfree software?
> The answer would likely be "it depends on the context and on who you are" but 
> this is a philosophical can of worms which we are in no hurry to open right now: luckily 
> the thread subject is the Linphone project, not its userbase.😌
>
> I'll reformulate the questions more explicitly, sorry in advance for the 
> verbosity.
> ❔ Would you consider the project responsible if the user of the libre version 
> unknowingly includes a non-free client in a conversation?
> ❔ What could be the ethical and safety implications of not warning the free 
> user that this is happening? (so the free user can at least prevent or close 
> the conversation)
I am open to different outcomes, but it just occurred to me that we 
don't see an issue with free e-mail clients being able to send/receive 
e-mails from nonfree e-mail clients, do we?
> > I would simply make them aware of the nonfree software they are using and 
> > suggest they find a free software solution
> Initially, I tought the same simple solution, but I noticed a pitfall: how do 
> you know if your interlocutor(s) are using a non-free version?
> If there is no warning message before the communication is established, you may 
> not be able to do so.
>
> 〜Lorenzo
Best,
>
--
Krzysztof Siewicz | Licensing and Compliance Manager, Free Software Foundation
GPG Key: 6DC9 E663 36DB 9588 81AB 7E43 2671 24EF FC9C D84E
https://fsf.org

We moved! The FSF changed address, find us at: https://www.fsf.org/about/contact

Free software is important for a free society!
Build a better world with us by matching the average donation of USD $46.22
https://donate.fsf.org

Give the gift of an FSF associate membership:
https://my.fsf.org/gift-a-membership

Follow the FSF on Mastodon: https://hostux.social/@fsf

Sign up for the FSF's newsletter: https://www.fsf.org/fss

US government employee? Use CFC charity code 63210 to support us through
the Combined Federal Campaign. https://cfcgiving.opm.gov/