From: bo0od <bo0od@riseup.net>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: 48793@debbugs.gnu.org
Subject: bug#48793: Make guix room available over matrix
Date: Thu, 3 Jun 2021 19:52:57 +0000 [thread overview]
Message-ID: <de3e60b5-b9c7-2d23-8ff2-605772c27aa1@riseup.net> (raw)
In-Reply-To: <874kef9d2a.fsf@disroot.org>
> In the registration process they encourage the use of Google captcha.
Thats true, but comparing google captcha which only need to allow JS
while using Tor VS you cant even access or register unless you use real
IP address = No question google captcha has less privacy impact in this
scenario.
OFTC was an example, Hackint and other IRC provider provide as well Tor
access without even these boundaries.
So whether changing the IRC server or having matrix room bridged to IRC
both solve the problem.
Bone Baboon:
> bo0od writes:
>
>> if guix irc migrated to OFTC
>
> OFTC has a problematic registration process.
>
> In the registration process they encourage the use of Google captcha.
> Further there is no mention during the registration process of any
> alternative account registration options.
>
> The use of Google captcha is problematic because of freedom, privacy,
> ethical and philosophical reasons. There is a freedom problem because
> JavaScript has to be enabled and Google captcha is not free software.
> There is a privacy issue demonstrated by the Tor browser documentation's
> security settings section which says that JavaScript is disabled when
> the safest setting is
> used. <https://tb-manual.torproject.org/security-settings/> Then there
> is an ethical issue of people doing free labor for Google. Then there
> is a philosophical issue if that free labor is used to train artificial
> intelligence (Google is working on artificial intelligence
> <https://en.wikipedia.org/wiki/Google>) as this raises the issue of
> artificial intelligence safety.
> <https://en.wikipedia.org/wiki/AI_control_problem>
>
next prev parent reply other threads:[~2021-06-03 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 18:42 bug#48793: Make guix room available over matrix bo0od
2021-06-02 20:22 ` Julien Lepiller
2021-06-02 21:46 ` bo0od
2021-06-02 21:50 ` Julien Lepiller
2021-06-02 21:57 ` bo0od
2021-06-03 15:34 ` Bone Baboon via Bug reports for GNU Guix
2021-06-03 19:52 ` bo0od [this message]
2021-06-02 20:32 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-06-02 21:39 ` bo0od
2021-06-02 22:20 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-06-03 19:39 ` bo0od
2021-06-03 21:18 ` Julien Lepiller
2021-06-07 22:35 ` bo0od
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de3e60b5-b9c7-2d23-8ff2-605772c27aa1@riseup.net \
--to=bo0od@riseup.net \
--cc=48793@debbugs.gnu.org \
--cc=bone.baboon@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).