Hi,

As far as I know, and I just looked at the documentation again for good
measure, there is no way to send GPG-signed patches with git-send-email.

However, I did find an interesting tool tool that integrates with it,
patatt[1]. Might be worth looking into it. If nothing else, its README
file explains why PGP-signed patches may not be a good idea.

-- 
Warmly,

James Pond

Applied, thanks!

I'm not quite sure what I contributed, but I'm fine with relicensing 
aerc to GPL :)

> The vision I have in mind for names.sr.ht is essentially to offer name
> registration as an eNom reseller, as well as DNS hosting (with or
> without a corresponding registration).

I have the same question as above, why eNom in particular? Considering
SourceHut may be moving incorporation to the EU at some point, I would
vote for a company like Gandi or, even better, ClouDNS[1].

ClouDNS in particular offers DDoS-protected anycast DNS with good uptime
and raw performance around the world, DNSSEC and white label support, an
okay API, and are incorporated in Bulgaria.

I chose them as the back-end provider to offer DNS hosting and domain
registration on my WordPress hosting business, and so far, have nothing

> You compete by offering a better service, with better uptime, better
> support, a more personal relationship with customers, demonstrating
> better ethics and industry leadership.

My personal issues with Automattic aside, they are a good example of a
company that openly offers their product to the world and do not whine
when someone creates an offering based on their code.

Several people are offering WordPress solutions, from hosting to
consultancy, "eating their lunch", but they welcome everyone with open
arms and even invest in "competitors" from time to time.

Warmly,

Drew,

> Are you a Spanish speaker or is this machine translated?

Portuguese speaker, with some knowledge of Spanish. The text was simply
copied from the Gmail one, though, as the steps are the same.

Warmly,

James Pond

Signed-off-by: James Pond <james@cipher.host>
---
 es/index.html | 13 +++++++++++++
 index.html    | 13 +++++++++++++
 2 files changed, 26 insertions(+)

diff --git a/es/index.html b/es/index.html
index 6eb2640..27a84fe 100644
--- a/es/index.html
+++ b/es/index.html
@@ -163,6 +163,7 @@
       <li><a href="#alot">alot</a></li>
       <li><a href="#evolution">Evolution</a></li>
       <li><a href="#fastmail">Fastmail</a></li>
[message trimmed]

Hi, all,

Somewhat related to this commit, it seems like images on the project hub
are broken due to this header[1], since the hub uses sr.ht instead of
git.sr.ht as the domain.

I could not find the NGINX configuration file for sr.ht anywhere, but I
can send over a patch if you point me to where it is.

Warmly,

James Pond

[1] https://i.cpimg.sh/vC5koOokZaQB.png

The color scheme for deleted emails should now match the old design,
making it easier to see when a message is deleted.

Signed-off-by: James Pond <james@cipher.host>
---
 config/default_styleset | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config/default_styleset b/config/default_styleset
index 8393a6b..78822e5 100644
--- a/config/default_styleset
+++ b/config/default_styleset
@@ -23,6 +23,7 @@ statusline_error.fg=red
 statusline_error.reverse=true
[message trimmed]

Hi,

> I've never done this (bounties) before, so I have no clue how this is
> going to work, but it sounds interesting.

In the past I used Bountysource[1] for this, but recent events[2] made
it clear to me that I did not do my research before using then, and they
are not to be trusted, so maybe we go manual for this one.

But basically, a person posts a bounty, and whoever delivers what was
asked, get to claim it. It is usually not a huge amount of money or
anything, but still a nice incentive to help a project out.

I live in Brazil, where one dollar equals five of my local currency, so