gnome-online-accounts recommends non-free software/service

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Raghav "RG" Gururajan
Owner
unassigned
Submitted by
Raghav "RG" Gururajan
Severity
normal

Debbugs page

R
R
Raghav "RG" Gururajan wrote on 8 Feb 2019 22:31
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
2zq895hJo11nLuSkRQ0RYFr_3Z9Qu2VLk4x0HydlCgVaD7P4CCcPsU7MACAQpaHCbZ_t1JYO-iG7lc7sl4rGjBxPrBtw7nggOn4y2rYdmAE=@mail.raghavgururajan.net
Hi,

I just found out in my GuixSD that gnome-online-accounts in system settings is showing options for Google, Facebook, etc.

Regards,
Raghav Gururajan
Attachment: file
Attachment: publickey - rg@mail.raghavgururajan.net - 0x996B359F.asc
Attachment: signature.asc
L
L
Ludovic Courtès wrote on 9 Feb 2019 06:09
(name . Raghav "RG" Gururajan)(address . rg@mail.raghavgururajan.net)(address . 34399@debbugs.gnu.org)
87va1tt5o7.fsf@gnu.org
Hello,

"Raghav \"RG\" Gururajan" <rg@mail.raghavgururajan.net> skribis:

Toggle quote (2 lines)
> I just found out in my GuixSD that gnome-online-accounts in system settings is showing options for Google, Facebook, etc.

gnome-online-accounts provides options for the services you mention; it
does not refer to non-free software, though.

The notion of “non-free” cannot be applied to a service. A service
might be SaaSS (“service as a software substitute” as RMS puts it), but
that’s not the case here because gnome-online-accounts runs locally and
interacts with the services via HTTP.

Of course these services are a serious threat to user privacy. However,
Guix is committed to the FSDG and in that context there is no valid
reason to exclude or modify gnome-online-accounts in Guix.

Thanks,
Ludo’.
L
L
Ludovic Courtès wrote on 9 Feb 2019 14:10
control message for bug #34399
(address . control@debbugs.gnu.org)
87va1spq9p.fsf@gnu.org
tags 34399 notabug
close 34399
?
Your comment

This issue is archived.

To comment on this conversation send an email to 34399@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 34399
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch