Glad you are being able to get back into Tildeverse Netnews now.
Though I saw from the `Path:` of your post
that you posted from Tilde.club;
so I take that A. SSH forwarding on Aussies.space didn't work for this,
and B. you finally solved the auth'signing algorithm issue
in your normal client, or have worked around it.
(How? If you don't mind telling)
On Mon, 17 Jul 2023, The Free Thinker wrote:
GitHub really annoyed me this month
by starting to require Javascript
in the web view of Git repos
just to browse directories and source code.
Yeah, noticed that for some time now.
Interface-wise, it's now no better than the JavaS'creep-infected GitLab-- while GitLab is still a libre software.
Now Gitea/Forgejo is way better in this regard,
so as SourceHut, Gogs, Savannah, SourceForge/Apache Allura;
or even barebone things like CGit, GitWeb, or Stagit
in a specific browse-only department. [1]
My answer is GophHub:
gopher://tilde.club/1/~freet/gophhub/
Thanks for writing this,
it is indeed a needed workaround for plebs like us
to deal with projects that somehow want to cling there for whatever
(usually corporate, inertia, sunk cost) reason.
Though it's still my stance that a proper long-term solution
is advising people to get off that code-laundering (dis)service,
refrain from participating (sending bug reports/patches) there [3],
and/or avoid getting involved with projects which insist on such disservice
to be a sole public participation channel in the first place.
Regards,
~xwindows
-----
(WARNING:
Rants ahead,
and you probably already know most of this;
so they are intended for as "to other people reading this reply")
[1]
To other people reading this reply: I will remind you
that the original and proper way for an *external* developer
to contribute a change to a public software project managed in Git
is the way that is currently used in kernel Linux development [2];
i.e. `git format-patch origin/master` and `git send-email`
to the maintainer or project mailing list.
(There is a very specific format of email message involved [4]
which allows the maintainer to commit the change directly from MIME file. Easier alternative for less stringent projects
[tilde-related projects counts in this category too]
is one can simply write email to the maintainer
to explaining what the fixes do,
and attach the patch files produced from the first command)
The "pull request" style of "contribution"
(which needs infrastructure)
is rather invented by GitHub to brainwash people
to believe that such submission
would inherently require on centralized service;
in order to capitalize on network effect
(i.e. you need account on single web service to submit changes).
It is not even a natural way to maintain public participation
in this SCM.
[2]
Kernel Linux is the original software project
that Linus Torvalds wrote Git for,
and the name "Git" was a reference to himself;
supposedly for being stupid enough to fall
for BitKeeper SCM's proprietary bait'n'switch ploy
in spite of other people's warnings,
and got burned by that in the end.
[3]
This do not imply that you cannot submit bug report or patches,
if they publish contact email,
mail those to them. [1]
If they tried to redirect you to the disservice,
you got declined,
or treated with silence;
simply share them as if you got responded WONTFIX on your report:
post them the old way on your website,
describe what they do,
the copyright license you are publishing them under,
as well as the exact HEAD/branch/repo
that your patch series is intended to apply;
optionally with your own reasons why they didn't get submitted
on the "official channel".
[4]
When I submit change to a tilde project (like Tilde.club Wiki),
I personally don't use `git send-email`,
but rather craft my own MIME file manually
from what `git format-patch` gave me,
then `sendmail -t` the result (or import to Alpine and send);
allowing me to have a discussion message in the front
(usually me describing what the patch is and what it fixes/adds)
and the patch content itself following right next to it in the message
(rather than as an attachment) for a quick review,
separated from each other by thin a scissor line "-- >8 --".
Apart from maintaining one-mail-per-commit relation,
this also allows the maintainer side to select Pipe command
inside a TUI mail client to run `git am --scissors`
and issue a commit right there if he approves.
(I usually include an instruction too, whenever `--scissors` is needed)
Different people might prefer different way to do this though:
`git --format-patch --cover-letter`
which produces an email thread is one of the other choices.
--
Contains ventilated prose,
manually typed up in RFC 2646
"text/plain; format=flowed" whitespace encoding;
might read like poetry in some newsreaders.
--- Synchronet 3.19a-Linux NewsLink 1.113