From: Philip McGrath <philip@philipmcgrath.com>
To: Maxime Devos <maximedevos@telenet.be>, guix-devel@gnu.org
Subject: Re: Excessively energy-consuming software considered malware?
Date: Sun, 20 Feb 2022 09:59:28 -0500 [thread overview]
Message-ID: <2002319.M0vKPVJpBW@bastet> (raw)
In-Reply-To: <675b6da5-e33a-fbaf-800a-83a949844ac3@gmail.com>
On Sunday, February 20, 2022 7:44:18 AM EST Taylan Kammer wrote:
> On 20.02.2022 13:37, Maxime Devos wrote:
> > The points about slippery slopes, research and niche use-cases seem
> > reasonable to me. I do see follow-up questions though, should the
> > description in Guix warn about potential issues? And should the
> > description focus on research uses? ...
> >
> > More concretely, the p2pool description is:
> >
> > ‘Monero P2Pool is a peer-to-peer Monero mining pool. P2Pool
> > combines the advantages of pool and solo mining; you still fully
> > control your Monero node and what it mines, but *you get frequent
> > payouts like on a regular pool.*’
> >
> > This is quite a bit different from, say, aircrack-ng which seems
> > to be mostly about assessing security, whereas the p2pool description
> > is about gaining money (see ‘payouts’), and without mentioning that
> > mining costs a lot of energy (and hence money, and possibly the money
> > that is gained by mining is smaller than the amount lost due to energy
> > costs!).
> >
> > My dislike for the description of p2pool might just be my views on
> > money leaking through, though.
> >
> > Greetings,
> > Maxime.
>
> I guess a different description would be better. It sounds almost
> like a sales pitch with the mention of making money. :-)
>
> I'm not familiar with Monero/P2Pool so I don't know what a better
> description might sound like though.
This description sound like it is promising that, if you run this software,
you will "get frequent payouts". I don't think that's a claim Guix can or
should make. I guess there's maybe some tension about to what extent package
descriptions are speaking on behalf of the package or on behalf of Guix, but I
don't think it usually causes too much confusion for the description of a
package like `pypy3` to say what the program's developers think its merits
are, without Guix as a project appearing to take a position on which is the
best Python implementation. However, a package description claiming that you
will get money if you use it seems like quite an extreme case.
(More generally, I share both the concerns about the impacts of crypto mining
and the concern that for Guix to refuse to package such software might have
problematic implications.)
-Philip
next prev parent reply other threads:[~2022-02-20 14:59 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 10:05 Excessively energy-consuming software considered malware? Maxime Devos
2022-02-20 10:48 ` Tobias Platen
2022-02-20 11:13 ` Martin Becze
2022-02-20 16:52 ` Maxime Devos
2022-02-20 20:39 ` Martin Becze
2022-02-24 9:23 ` Hartmut Goebel
2022-02-24 11:18 ` Martin Becze
2022-02-25 0:27 ` Christine Lemmer-Webber
2022-02-25 12:41 ` Bengt Richter
2022-02-25 13:04 ` Tobias Geerinckx-Rice
2022-02-25 16:14 ` Bengt Richter
2022-02-25 16:32 ` Ricardo Wurmus
2022-02-25 16:49 ` Paul Jewell
2022-02-25 17:05 ` Maxime Devos
2022-02-25 17:35 ` Taylan Kammer
2022-02-25 19:00 ` Leo Famulari
2022-04-04 8:00 ` Attila Lendvai
2022-04-04 9:43 ` Maxime Devos
2022-04-04 10:15 ` Maxime Devos
2022-04-04 12:49 ` Attila Lendvai
2022-04-04 10:16 ` Maxime Devos
2022-04-04 10:37 ` Maxime Devos
2022-04-04 11:22 ` indieterminacy
2022-04-04 18:39 ` Liliana Marie Prikler
2022-02-24 9:13 ` Hartmut Goebel
2022-02-24 9:36 ` Attila Lendvai
2022-02-20 11:08 ` Ekaitz Zarraga
2022-02-20 11:27 ` Compiling blender Ricardo Wurmus
2022-02-20 11:34 ` Ekaitz Zarraga
2022-02-20 12:19 ` Faster "guix pull" by incremental compilation and non-circular modules? Maxime Devos
2022-02-20 16:47 ` Philip McGrath
2022-02-20 17:47 ` Semantics of circular imports Maxime Devos
2022-03-27 14:12 ` Philip McGrath
2022-03-27 14:19 ` Maxime Devos
2022-03-27 14:24 ` Maxime Devos
2022-03-27 14:33 ` Maxime Devos
2022-03-27 14:55 ` Maxime Devos
2022-03-28 4:24 ` Zhu Zihao
2022-03-30 4:50 ` Maxim Cournoyer
2022-02-28 13:17 ` Faster "guix pull" by incremental compilation and non-circular modules? Ludovic Courtès
2022-02-28 18:50 ` Maxime Devos
2022-05-31 4:54 ` Gábor Boskovits
2022-05-31 8:49 ` Maxime Devos
2022-05-31 10:23 ` Ricardo Wurmus
2022-02-20 15:54 ` Compiling blender Ricardo Wurmus
2022-02-20 16:14 ` Ekaitz Zarraga
2022-02-20 12:20 ` Excessively energy-consuming software considered malware? Taylan Kammer
2022-02-20 12:37 ` Maxime Devos
2022-02-20 12:44 ` Taylan Kammer
2022-02-20 14:59 ` Philip McGrath [this message]
2022-02-20 18:53 ` Christine Lemmer-Webber
2022-02-20 20:34 ` Jonathan McHugh
2022-02-20 12:32 ` Paul Jewell
2022-02-20 18:26 ` Liliana Marie Prikler
2022-02-20 19:36 ` Ryan Sundberg
2022-02-21 9:29 ` Attila Lendvai
2022-02-21 13:06 ` Maxime Devos
2022-02-21 18:56 ` raingloom
2022-02-21 23:02 ` Attila Lendvai
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=2002319.M0vKPVJpBW@bastet \
--to=philip@philipmcgrath.com \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).