Re: [GNU-linux-libre] DSFG in perpetuity

[Isaac David]

I was about to say that, although worrisome, spyware capabilities
have no impact in determining whether a piece of software belongs
in a FSDG distro or not. Good thing I double-checked with the
guidelines, because they actually do.

Luke wrote :
> [A]s of the date of the e-mail there
> was still some freedom issues and plenty of links to Google.com which
> could still be stripped out.
>
> List of good patches:
> https://github.com/Eloston/ungoogled-chromium/tree/master/resources/patches
>
> Compare to QTWebengine's (outdated) Chromium:
> https://github.com/qt/qtwebengine-chromium

This doesn't tell us much unfortunately.

> - Debian freedom patches not applied, e.g. files missing licenses:
> https://github.com/Eloston/ungoogled-chromium/blob/077e441e6654e4658de37c9d665e58f61b262961/resources/packaging/debian/buster/source/lintian-overrides
> https://github.com/qt/qtwebengine-chromium/blob/b45f07bfbe74c333f1017810c2409e1aa6077a1b/chromium/tools/trace/trace_data.js

What does that mean exactly? If I were to guess, lintian incorrectly
confused trace_data.js for a blob, and ungoogled-chromium is reversing
that overstep.

> - There may still be connections made to Google API.
> https://github.com/qt/qtwebengine-chromium/search?p=2&q=%22www.googleapis.com%22&type=&utf8=%E2%9C%93
>
> I'm just
> not convinced they completely resolved it in their fork. So far
> ungoogled-chromium is the only project I've compiled and ran with
> Wireshark that did not have random connections to Google.com while the
> browser is idling.

By *the only project* do you mean you also tested with Qt
Webengine-based programs? Conclusions about Chromium need
not apply to Qt Webengine.

--
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
Ring: c8ba5620e080bef9470efb314c257304ff9480f5
Tox: 
0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C
<https://isacdaavid.info/donate>