Oh my mistake. Should be accessible now.

Welcome!

Honestly it's just nice to know that anyone else out there is using it
and cares. My personal enthusiasm for Gemini has waned since I wrote
Stargazer. But it's the most substantial project I've created that I can
share in the open (not for work) and I'm proud of it.

Though it's far from perfect. If I had a lot more time, energy, and will,
I'd make some substantial changes. I'm not really happy with the config
layout, and I think the current way routes are defined can be unintuitive
and confusing. Maybe one day I'll redo it and there'll be a Stargazer
2.0 with a new config syntax!

Thanks! I appreciate you taking feedback and making changes.

To git@git.sr.ht:~zethra/stargazer
   5e4baa2..57a58ab  main -> main

If you have the inclination, it'd be good to add a functional test to
./stargazer/scripts/gemini-diagnostics to ensure that it doesn't break in
some other way later. But this isn't required. I may add one myself at
some point.

I plan to cut a new release containing this feature within the next week,
when I have time.

Hello,

Thank you for contributing to stargazer! You patch mostly looks good
but, there are a few issues. The two main ones are with the tests you
provided. 

First, you are using the `from_bits` IP addr functions, which are
unstable. Please only use code that compiles on stable Rust, preferably
code that compile on the currently documented MSRV. Second please use a
different random number library than osrandom. The C component won't
compile on my system in debug mode because it throws a warning
(`_FORTIFY_SOURCE requires compiling with optimization`) and it has
warnings as errors set. Additionally, it appears to be unmaintained. It
has one version uploaded 2 years ago and the GitHub repo linked on it's

Thanks! This version works great.

Thanks for the patch, and glad you figured out the issue.

What distro are you running and where does it get col from? NixOS and Fedora
get col from util-linux and that doesn't seem to remove the control character
from the groff output. That's why I had the sed command removing them before.

It's okay. I very rarely get patches, and I'd also like to know what the 
issue is.

Jul 31, 2024 19:40:36 ttocsneb <ttocsneb@benjaminja.info>:

> So sorry about all of this.
>
> The build failed again due to the patch not applying. It should since I
> made sure that the patch was made with the latest main commit. I'm 
> worried
> that the problem comes from me using protonmail.
>
>> From git-send-email.io/#step-2
>> Be advised that Protonmail is generally known to be a pretty bad email

> For sure, I'll split up the patch and see what I've messed up with CI.
> Should the typo fix and formatting change both be in the same patch 
> with
> different commits or have a total of 3 patches: typo, formatting, and
> proxy?

Three separate patches as a patch series would be optimal.

Hello, thanks for the patch!

It appears it failed to apply in CI. Could you make sure your patch it based off of the latest commit on the main branch? Do a git rebase if necessary. Also, would you be able to split this into multiple commits? With the typo fix and formatting change being their own commits. I can review the change in more depth in a few days.

Out of curiosity, what is your use case for this? I'm not familiar with this protocol.

---
Hiya! I love the small and indie web too.
 _site_listings/sashanoraa.gay.md | 4 ++++
 1 file changed, 4 insertions(+)
 create mode 100644 _site_listings/sashanoraa.gay.md

diff --git a/_site_listings/sashanoraa.gay.md b/_site_listings/sashanoraa.gay.md
new file mode 100644
index 0000000..9498bfb
--- /dev/null
+++ b/_site_listings/sashanoraa.gay.md
@@ -0,0 +1,4 @@
+---
+pageurl: sashanoraa.gay
[message trimmed]