From: Dan Callaghan <djc@djc.id.au>
To: supmua <supmua@googlegroups.com>
Subject: [sup] web site moved to supmua.dev
Date: Mon, 20 Oct 2025 18:14:50 +1100 [thread overview]
Message-ID: <1760944109-sup-8909@honeycomb.djc.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
In light of the recent dramas around RubyGems.org[1] I thought it would
be good to have some other independent distribution channel for Sup
releases, which is not reliant on the goodwill of some company.
I have also been thinking for a while about reducing dependencies on
GitHub, for a similar reason. So I was not keen to start publishing
releases on GitHub either, nor relying more on GitHub Pages.
I wish we still had Sup's old domain, supmua.org. Unfortunately that
domain lapsed a long time ago and is still held by domain squatters.
I went ahead and registered a new domain, supmua.dev. I have put up the
old Sup web site there:
https://supmua.dev/
and now the GitHub Pages site at https://sup-heliotrope.github.io/
redirects to the new domain.
I also made a few small tweaks to the content of the site, and added
a page with an archive of all existing Sup released gems:
https://supmua.dev/releases/
I also set up public-inbox[2] with a searchable archive of the current
supmua Google Group, as well as the old RubyForge mailing lists:
https://supmua.dev/lists/
Hit reply if you see anything amiss with the new domain.
[1] https://mensfeld.pl/2025/09/ruby-central-rubygems-takeover-analysis/
[2] https://public-inbox.org/
--
Dan Callaghan <djc@djc.id.au>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2025-10-20 7:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1760944109-sup-8909@honeycomb.djc.id.au \
--to=djc@djc.id.au \
--cc=supmua@googlegroups.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox