unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: bo0od <bo0od@riseup.net>, "Bonface Munyoki K." <me@bonfacemunyoki.com>
Cc: 47660@debbugs.gnu.org
Subject: bug#47660: Add link to the ticket when someone reply
Date: Thu, 15 Apr 2021 19:51:27 +0200	[thread overview]
Message-ID: <41d350bee8ce1fa0d628bd9e833d6c6ced8765b8.camel@telenet.be> (raw)
In-Reply-To: <be8288f6-f500-3090-4612-975568d47882@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]

On Thu, 2021-04-15 at 17:00 +0000, bo0od wrote:
> To be honest i find this bad thing to use emails to do anything rather 
> than online registration and not necessary stuff (means being 
> encrypted,manipulated.. just not something important)

To be honest, I find it a bad thing that many projects (I'm looking at
GitHub here (*)) only have a web interface, that require registration
(and often have terms of service I would consider criminal).  Then there
are multiple web sites requiring registration that I need to keep track
of.

(*) Ok, GitHub has e-mail notifications.  But I can't directly reply to them,
    I need to go to the web interface.  At least, that was the case N years ago.

I like being able to perform all asynchronuous communication via e-mail,
instead of via a dozen platforms.  With e-mail, you get signing ‘for free’,
while with $PLATFORMS, you need to rely on each $PLATFORM infrastructure
or resort to ...

(my intepretation of your words, out of context, with encryption replaced with
 signing)
> extra tools, where you have to copy the message into the tool, let the
> tool verify the signature.  Or write a message into the tool, let the
> tool create the signature, and copy the message+signature into the web
> interface.

> Email sucks due to:
> * Messages are not encrypted by default which mean it need an extra tool 
> to do it and commonly used is GPG/PGP + it needs tool to implement this 
> encryption on the messages which mean mail reader/client most commonly 
> one used is thunderbird/icedove <- This method having tremendous 
> security issues check for example: [...]

Not relevant for our purposes.  Issues are public.  Only PGP for signing is
relevant here.  Also, PGP + Evolution works just fine for me, and evolution
doesn't download external attachements by default.

> * Most of the time (not always) heavily rely on clearnet which mean 
> issues of TLS/DNS which needs to be hardened otherwise they are exist by 
> names but does nothing.

I couldn't parse this.  What does ‘they are exist by names but does nothing’
mean?

> ..This is out of scope to discuss this in details, I just want to see 
> the bug URL linked to the bottom of the email i receive thats it.

Guix' bug tracking software is ‘GNU Bug Tracker’.  You could ask it on
that project's mailing lists.  Now I see you did that already:
<https://lists.gnu.org/archive/html/help-debbugs/2021-04/msg00000.html>.

I don't have anything else to say on this topic; I'm not sending further replies.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-04-15 17:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 17:38 bug#47660: Add link to the ticket when someone reply bo0od
2021-04-08 18:45 ` Leo Famulari
2021-04-09 20:44   ` bo0od
2021-04-10 10:45     ` Maxime Devos
2021-04-10 14:20       ` bo0od
2021-04-10 16:44         ` Maxime Devos
2021-04-10 20:13           ` bo0od
2021-04-15 14:24         ` Bonface Munyoki K.
2021-04-15 17:00           ` bo0od
2021-04-15 17:51             ` Maxime Devos [this message]
2021-04-16  2:38               ` bo0od
2022-03-18  2:56       ` Maxim Cournoyer

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=41d350bee8ce1fa0d628bd9e833d6c6ced8765b8.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=47660@debbugs.gnu.org \
    --cc=bo0od@riseup.net \
    --cc=me@bonfacemunyoki.com \
    /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).