[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [directory-discuss] FSF opinion on chromium, QtWebEngine, electron
From: |
Adonay Felipe Nogueira |
Subject: |
Re: [directory-discuss] FSF opinion on chromium, QtWebEngine, electron |
Date: |
Tue, 14 Nov 2017 10:50:43 -0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
Also, Riot-im has a talk page [1] in the Free Software Directory
describing some of the issues both for riot-web, riot-android, and also
its GNU/Linux client.
[1] <https://directory.fsf.org/wiki/Talk:Riot-im>.
bill-auger <address@hidden> writes:
> david - it is the very point of this thread to determine that - as i
> said, i gave atom and vscode only as examples - AFAIK this issue equally
> affects all software derived from chromium, qtwebengine, or electron -
> that includes irridium, ungoogled chromium, atom and vscode, qupzilla,
> riot matrix, the qtwebengine library itself, and countless other programs
- [directory-discuss] FSF opinion on chromium, QtWebEngine, electron, bill-auger, 2017/11/03
- Re: [directory-discuss] FSF opinion on chromium, QtWebEngine, electron, David Hedlund, 2017/11/04
- Re: [directory-discuss] FSF opinion on chromium, QtWebEngine, electron, bill-auger, 2017/11/04
- Re: [directory-discuss] FSF opinion on chromium, QtWebEngine, electron, David Hedlund, 2017/11/05
- Re: [directory-discuss] FSF opinion on chromium, QtWebEngine, electron, bill-auger, 2017/11/05
- Re: [directory-discuss] FSF opinion on chromium, QtWebEngine, electron,
Adonay Felipe Nogueira <=
Re: [directory-discuss] FSF opinion on chromium, QtWebEngine, electron, Adonay Felipe Nogueira, 2017/11/14
Re: [directory-discuss] FSF opinion on chromium, QtWebEngine, electron, Adonay Felipe Nogueira, 2017/11/25