> <https://pr.pico.sh/> is an open source server for letting contributors make a pull request using SSH. I think it would be a great addition to Sourcehut, because the mail workflow is confusing, especially for beginners coming from GitHub. What do you think?

This looks like a very interesting tool, thanks for sharing!
I would also be in favor of sr.ht supporting this when time allows.

> I mean, really [1]? If you really want to use CVS, then get help,

> If you want to use SVN in your free time, then you probably need
> to get help as well, but probably more in terms of a rehab clinic
> then a lunatic asylum.

This is no way to reply to someone, however you feel about their question.
This is a common mailing list so please do not spam people to insult 
someone.

I don't know how moderation works on sr.ht but this type of behavior 
should earn at least a strike or a temporary block IMO.

T

Hi there, I don't know whether it's an aftermath of the outage, but I 
got an issue from the tests pushing on one of my repos:

     remote: Build started:
     remote: https://builds.sr.ht/~tfardet/job/1131978 [.build.yml]
     remote: Error sending webhook: Post 
"https://sr.ht/webhooks/git-repo/13453": context deadline exceeded 
(Client.Timeout exceeded while awaiting headers)
     To git.sr.ht:~tfardet/OrgMatt
        f7eb778..afeda4b  main -> main

And the build shows "success" but does not seem to be able to fetch the 
logs (Error fetching logs for task "None"): 
https://builds.sr.ht/~tfardet/job/1131978

> It would be easier (especially for new visitors) if there was such a
> link (generated automatically), p.e. as an additional tab next to
> summary, tree, log, and refs. (Or is there a link that I overlooked?)

Agreed, I think this point (and more generally improving srht 
navigation) was already mentioned several times and is in a todo 
somewhere (maybe for the beta?).

T

> I went ahead and added this to robots.txt, but I'm not making any
> special priority to roll out the change so it'll show up over the next
> few weeks.
> 
> Not going to block any IP ranges, odds are it would result in collateral
> damage.

I understand, thanks!

I saw on the Fediverse that, following the news of OpenAI providing an 
opt-out tool for robots.txt (not amused), some people have listed a 
bunch of IP ranges associated to their crawlers.

https://mathstodon.xyz/@filipw/110852364162684071

I was wondering whether it would be reasonable for sourcehut to block 
these IP ranges (and potentially those of Google, MS, etc, if they can 
be found).

Best,
Tanguy

> I do not consider this a flaw, you can remove the comment yourself if
> you so desire and your email address is not considered private on
> SourceHut.

There's one issue I see with the current situation, though: it is not 
obvious that the keys are visible (comments included) as this is written 
on a very small line below the add-key form.

If comments are to be kept (I'm not sure what benefit it brings, 
honestly), then it might be good to add some more visible disclaimer 
that the whole entry will be shown to the public.

> That was my thinking too. Going there there's a button to add ssh keys, but
> not to delete them. There's a button to add gpg keys, and another one to
> delete them.
> 
> I can't be the only one in that case?

I have a "Delete" button on the right of each SSH key line, same as for 
PGP keys.

T

Hi Drew, one test is failing but I don't think this is related to the
changes I made.
Is there anything I should do?

Best,
T

> HTML emails are now supported but it is opt in for the list admin

There seem to have been a misundeerstanding: html email are not (and
will not be) supported.
I merely added the possibility to "support" mixed html/plaintext emails
in the sense that the html part would be discarded to keep only the
plaintext instead of replying with an error to the sender.
But that still means that only pure text emails are sent in sourcehut
mailing lists.

Also note that, though the code has been added, the database migration
still needs to be done to make this possible in existing mailing lists.
Once migration is done (hopefully I'll send the patch during the
week-end), allowing mixed html/plaintext email will become possible