From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] Expired SSL certificate
Date: Sat, 6 Apr 2024 19:18:14 -0700 [thread overview]
Message-ID: <ZhICZuuNfpq2wZBh@wopr> (raw)
In-Reply-To: <5f0b93d67d15366f@orthanc.ca>
On Sat, Apr 06, 2024 at 05:41:16PM -0700, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
> Kurt H Maier writes:
>
> > it'll probably stay that way. it doesn't really hurt anything. if
> > someone has a compelling reason I'm open to putting a new cert in, but I
> > don't really see the point at the moment. traffic remains encrypted.
>
> But it will scare away non-Plan 9 users browsing the code with
> a web browser. That's a bit anti-social.
>
> --lyndon
More or less antisocial than just taking the server down?
Feel free to take whatever code you need to socialize and host it
elsewhere.
khm
next prev parent reply other threads:[~2024-04-07 2:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 15:04 mrunix00
2024-04-06 18:29 ` Kurt H Maier
2024-04-07 0:41 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-04-07 0:49 ` Stanley Lieber
2024-04-07 2:18 ` Kurt H Maier [this message]
2024-04-07 16:47 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-04-07 17:02 ` Kurt H Maier
2024-04-07 17:33 ` Stanley Lieber
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=ZhICZuuNfpq2wZBh@wopr \
--to=khm@sciops.net \
--cc=9front@9front.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).