Github messages for voidlinux
 help / color / mirror / Atom feed
From: SpecialBomb <SpecialBomb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: srcpkgs/*: remove all cryptocurrency/blockchain packages
Date: Wed, 28 Jun 2023 16:56:36 +0200	[thread overview]
Message-ID: <20230628145636.UcmAsCaKc93JhKsns6d8zZTBASbTW67gRXXLfA9KjjE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44422@inbox.vuxu.org>

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

New comment by SpecialBomb on void-packages repository

https://github.com/void-linux/void-packages/pull/44422#issuecomment-1611600560

Comment:
I would like to preface this by saying that I am not telling any of you what to do, and I'm certainly not asking to revert this PR. I appreciate the Void Linux project and its maintainers, and I hate crypto grifts as much as the next person. I don't even dabble in cryptocurrency at all.

However, I and others have discussed this PR and what it entails, and I personally think it's a little shortsighted to remove cryptocurrency packages for the sake of it being associated with scams. While it's most definitely true that the current main use of cryptocurrency is for scams and dubious investments, that doesn't remove from the tangible utility that cryptocurrencies have for many people trying to make anonymous transactions for goods and services.

While I think it's the maintainers' rights to choose what gets added to the repo or not, seeing a decision made like this in such a manner as this doesn't evoke confidence in me or others even if we do think crypto is kinda stupid. I could care less about these packages, but I can't deny that the way they were removed wasn't very thought out or sensible. I do understand why you would want to remove them, and I probably would to, but I think seeing it from another perspective is helpful.

And of course, at the end of the day, it doesn't really matter since nothing is preventing anyone from obtaining and using any of this software from other sources. I just feel like the decision was too subjective.

  parent reply	other threads:[~2023-06-28 14:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14  5:59 [PR PATCH] " 0x5c
2023-06-15 19:47 ` paper42
2023-06-16  8:39 ` [PR PATCH] [Updated] " 0x5c
2023-06-16 19:26 ` ar-jan
2023-06-19  1:06 ` [PR PATCH] [Updated] " 0x5c
2023-06-26 20:07 ` [PR PATCH] [Merged]: " leahneukirchen
2023-06-28 14:56 ` SpecialBomb [this message]
2023-06-28 17:28 ` lemmi
2023-06-30 11:41 ` kevcrumb
2023-07-16  9:59 ` drizzt
2023-07-30  8:06 ` uberscientist
2023-07-30 17:37 ` 0x5c
2023-07-31 16:39 ` maciozo
2023-07-31 16:42 ` maciozo
2023-07-31 19:49 ` lemmi
2023-07-31 20:00 ` 0x5c
2023-07-31 20:07 ` maciozo
2023-07-31 20:09 ` maciozo
2023-07-31 20:12 ` ar-jan
2023-07-31 20:21 ` 0x5c
2023-07-31 20:36 ` maciozo
2023-07-31 20:37 ` lemmi
2023-09-03  4:59 ` Yorizuka
2023-09-03  5:28 ` Yorizuka
2023-09-03 22:01 ` Yorizuka

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230628145636.UcmAsCaKc93JhKsns6d8zZTBASbTW67gRXXLfA9KjjE@z \
    --to=specialbomb@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).