This email causes my email client to prompt to send a delivery
notification. I believe it's caused by this header:

Disposition-Notification-To: Chinmay Dalal <chinmay.dalal.22012001@gmail.com>

Would it be okay if we filtered out this header? IIRC we already filter
out Return-Receipt-To.

Hi Drew,

It's been a while since I heard anything about names.sr.ht, is this
service still planned?

Hi,

Sorry for the delay in getting back to you.

This patch looks good - thank you for sending it. I'd like to merge
most of the changes like DynamicUser but I have a few questions about
how HTTP ACME challenges are done now.



December 22, 2020 7:07 PM, "somini" <dev@somini.xyz> wrote:

> - Default to using systemd socket activation
> - Improve security for service

December 25, 2020 12:13 AM, "Drew DeVault" <sir@cmpwn.com> wrote:

> I object to it on philosophical terms

Fair enough.

I would be interested to read your thoughts on CLI/TUI software should
you be inclined to write a blog post about it.

Somewhat off-topic... this email I'm replying to is showing a DKIM
failure:
https://lists.sr.ht/~sircmpwn/gmni-discuss/%3C20201224105059.ECB4A63C0043%40dd22736.kasserver.com%3E

But your previous email is passing.

December 24, 2020 2:04 PM, "Drew DeVault" <sir@cmpwn.com> wrote:

> Feel free to post the patch so that others can apply it downstream, but
> I am not interested in merging this upstream.

Just out of interest, why won't you apply this patch?

If it's because of the color, would support for https://no-color.org/
change your mind? I'd be happy to add in support for that.

Hi,

I removed the gitignore file in this commit:
https://git.sr.ht/~ancarda/tls-redirector/commit/227f60114868

I think it's better to catch these mistakes on the mailing list / in
pull requests -- which is a good opportunity to teach people about
`git rebase'.

If you want to be able to do `git add .', keep the file. Just include
the ignore file itself so it doesn't get checked in, like so:

    .gitignore
    tls-redirector

Hi,

Thanks so much for this patch! I'll review it soon.

Could you re-send it using `git send-mail' or whatever you used when you sent
the gitignore patch? That was recognized by SourceHut:
https://lists.sr.ht/~ancarda/tls-redirector/patches/16073

But this email wasn't for some reason.

Kindest Regards,
Mark

>> The IPv4 addresses being logged are not accurate (or stable).
> 
> Can confirm: on gmnisrv master, commit cb2c84b0.

I have also observed this on IPv6 - which made me think addresses are
intentionally obfuscated for privacy. Is this by design?

I've run into an issue trying to migrate a PHP project from GitHub to
SourceHut. Seeing a lot of my tools break is making me realize just how
dependent things can be on hosts like GitHub.

At the moment, I have a problem with Poser - a tool that produces README
"shields"/badges relevant to PHP projects; like how many downloads from
Packagist a project has. It's here: https://poser.pugx.org/

Poser pulls some data from the repo host and so unfortunately only
supports projects hosted on GitHub and BitBucket at the moment. I
started working on a patch to add in SourceHut support, but it occurred
to me this isn't fixing the root cause. Given an arbitrary URL, can
machine-readable information about the repo be discovered?

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 43c3c0a..ac0a30b 100644
--- a/README.md
+++ b/README.md
@@ -32,5 +32,5 @@ MIT
 [alps]: https://sr.ht/~migadu/alps
 [RFC 6186]: https://tools.ietf.org/html/rfc6186
 [Go plugin helpers]: https://godoc.org/git.sr.ht/~migadu/alps#GoPlugin
-[mailing list]: https://lists.sr.ht/~migadu/alps-dev
+[mailing list]: https://lists.sr.ht/~migadu/alps-devel
[message trimmed]