From: Ricardo Wurmus <rekado@elephly.net>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: Felix Lechner <felix.lechner@lease-up.com>,
Robby Zambito <contact@robbyzambito.me>,
Sarthak Shah <shahsarthakw@gmail.com>,
guix-devel@gnu.org
Subject: Re: A Forum for Guix Users
Date: Mon, 17 Jul 2023 09:37:51 +0200 [thread overview]
Message-ID: <87mszvf0is.fsf@elephly.net> (raw)
In-Reply-To: <20230716103340.iy2ton3oxcc4kuqc@thebird.nl>
Pjotr Prins <pjotr.public12@thebird.nl> writes:
> If the xapian indexer also analysed mailing list output (through
> publicinbox, for example) and maybe debbugs and IRC logs it would be
> complete.
It does index the IRC logs, but there’s a bug in the deployment:
https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/goggles.scm#n56
>> 5. Substitute availability is good, but download speeds can be poor
>> due to peering issues.
>
> That is a matter of money, I guess.
Peering issues can only be avoided by distributing the artifacts to many
different locations. We’ve previously paid for distribution via AWS,
which was rather expensive.
It might be better to revive the distribution over IPFS.
--
Ricardo
next prev parent reply other threads:[~2023-07-17 7:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 13:52 A Forum for Guix Users Sarthak Shah
2023-07-13 14:05 ` Robby Zambito
2023-07-13 15:21 ` Csepp
2023-07-14 11:31 ` Msavoritias
2023-07-15 13:43 ` Attila Lendvai
2023-07-15 21:00 ` MSavoritias
2023-07-16 5:55 ` Julien Lepiller
2023-07-15 2:45 ` kiasoc5
2023-07-15 13:59 ` Attila Lendvai
2023-07-15 13:14 ` Tobias Geerinckx-Rice
2023-07-14 21:10 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-07-15 13:27 ` Attila Lendvai
2023-07-16 10:33 ` Pjotr Prins
2023-07-16 23:30 ` Csepp
2023-07-17 17:41 ` Attila Lendvai
2023-07-17 7:37 ` Ricardo Wurmus [this message]
2023-07-17 8:17 ` MSavoritias
2023-07-17 20:29 ` Csepp
2023-07-13 14:40 ` Andrea Rossi
2023-07-13 22:38 ` vidak
2023-07-17 7:58 ` Etienne B. Roesch
2023-08-19 12:47 ` Simon Tournier
2023-07-18 1:52 ` Wilko Meyer
2023-07-18 16:39 ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-07-18 21:12 ` Ricardo Wurmus
2023-08-19 11:54 ` Simon Tournier
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 20:19 Andy Tai
2023-07-14 21:17 ` Sarthak Shah
2023-07-14 21:26 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-07-14 22:12 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-07-14 23:50 ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-07-21 13:30 ` 宋文武
2023-07-18 11:45 Distopico
2023-07-21 8:37 ` Etienne B. Roesch
2023-07-23 16:17 ` Ahmed Khanzada
2023-07-24 2:41 ` Csepp
2023-08-19 10:59 ` Simon Tournier
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=87mszvf0is.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=contact@robbyzambito.me \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
--cc=shahsarthakw@gmail.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).