On 18 June 2023 5:02:54 pm NZST, saw@localhost wrote:
>> We need more leaders of color, women, LGBTQ representation, and others besides.
>
>Uh-huh. How come where equality is desired, so also is subordination?

I think a good-faith interpretation of this is not "we should be more subordinate to these groups" but instead that the author believes that people in those groups are being kept from becoming leaders, and that this is a bad thing, and that we will know when the issue is resolved when there are more such leaders with those characteristics.

Of course other people might also reasonably point out that having more female CEOs doesn't necessarily mean much to the average woman - to use an extreme example you could have a society like Elizabethan England with a Queen regnant and still the life of the average woman was to be subservient to her husband or father. But I think Drew is advocating here not "subordinate ourselves to women to fix sexism" but that sexism in general ought to be eliminated as an end of itself, and the means of doing that is promoting good female role models and eliminating such barriers that exist to the involvement of women in the free software community. (And the same if you substitute "women" for any other of the mentioned groups.) That is my interpretation of what he said.

It is generally advisable to try to interpret someone's words in the strongest light that you can. But hey, maybe you did and that was just the only interpretation you saw. How am I to know?

Kind regards,
Miles.

On 18 June 2023 5:02:54 pm NZST, saw@localhost wrote:
>> We need more leaders of color, women, LGBTQ representation, and others besides.
>
>Uh-huh. How come where equality is desired, so also is subordination?

Also your From address is set wrong: it shows up as "sam@localhost". This makes it difficult for anyone to reply to you off-list in order to let you know about any technical issues with your email, such as, for example, your From address being set wrong.

Cheers,
Miles.

What do you mean?  Prioritising text/plain over text/html if both are
available?  Only showing plaintext?  Showing the email in a terminal?
Converting non-plaintext emails into plain text?

I think every mail client can at least *view* plain text emails.  At
least, I've never heard of an email client that can't.  Please correct
me if I'm wrong on that.

Kind regards,
Miles

On Sun, Apr 25, 2021 at 03:50:05PM +0200, Amirouche wrote:
> The idea is to build search.sr.ht service that would allow project
> to setup search for their project hosted on source hut.
> 
> The goal of search is to find information that is hidden or not easy
> to find. In the context of sr.ht, a project is built out of several
> independent services repository, list, todo, and wiki: going through
> the search box of those services requires multiple clicks.

Is your idea to allow search within a project, between projects, or
both?  I find it hard to imagine where it would be useful to have
between-project search except in one very specific way: searching all
public Sourcehut projects' descriptions for a particular string or tags
for a particular tag.  The thing is, this already exists!

On Thu, Jul 30, 2020 at 03:07:31PM +0300, Greg V wrote:
> A nice benefit of the GitHub style fork & pull request workflow is that a
> git repo with the proposed patch is hosted publicly and can be used in
> package managers as a temporary override while the patch is not merged yet,

You push the code to a repository and then you use that repository as
the basis for a pull request.  But the code being available somewhere is
a function of the first part of that, not the second.  You created a
publicly available clone of the original repository that contains your
patched tree.  You can push your changes to a publicly accessible place
(GitHub, Sourcehut, a simple self-hosted git repository on your web
server, etc.) regardless of the method you use to notify the original
author of your patch.

On Sat, Feb 15, 2020 at 10:26:42PM -0700, Sean Whitton wrote:
> Right.  But it has that established meaning in people's minds so could
> cause confusion.  "Wait a minute, don't pluses in e-mails mean that part
> isn't really part of the address?"

This is much less likely to be the case when the plus is at the
beginning and what comes after is obviously meaningful.  What's more,
anyone familiar with the 'pluses in email addresses' convention is a
power user.  Power users should be able to learn new things and apply
critical thinking.