Why Gopher:// will never die?

Let me remind once again that thanks to the Dust Council
we have the opportunity to develop GopherSpace without
technical limitations.

Today I want to talk about the Gopher protocol once again.
Three months ago, Dust Council installed a statistics system
on our server. Before that, as you understand, I did not have
any traffic statistics. Here are the traffic statistics for the last
three months up to November 17. As they say, let's sum up
the results for 2.5 months and draw some conclusions.

month        rx      |     tx      |    total    |   avg. rate
------------------------+-------------+-------------+---------------
2024-09    895.23 MiB |   28.64 GiB |   29.52 GiB |   97.82 kbit/s
2024-10      3.93 GiB |   61.95 GiB |   65.89 GiB |  211.31 kbit/s
2024-11    719.36 MiB |   37.66 GiB |   38.36 GiB |  228.84 kbit/s
------------------------+-------------+-------------+---------------
estimated      1.26 GiB |   67.79 GiB |   69.05 GiB |

What we see? We see the statistics of the average traffic of
a thematic Web site of the https:// protocol with 1500-2500
unique visitors per day. But we should not forget that we are
talking about our Gopher:// protocol server, which is considered
obsolete, useless, etc. It seems to me that these figures prove
that the traffic of the project does not depend on the protocol
on which the project is implemented. Yes, in Gopher:// are only
about 350 servers online now. But it turns out that interest in the
project does not depend on the protocol, but on the content that
is hosted on the server. Seeing this traffic, I can once again say
that Gopher is much more convenient and relevant than FTP
and at the same time does not suffer from https:// diseases.
From mails with my visitors, I found out some problems of new
GopherSpace users. To my surprise, it turned out that almost no
one had dealt with the Windows audience in Gopher before me.
Therefore, there was no clear and precise chronological description
of browsers for viewing GopherSpace from Windows. This means
actual browsers, clients, and also necessarily Android devices.
By a strange coincidence, many believed that Gopher only works
in the Lynx browser.
Another else problem that I know from visitors is the lack of a clear
first welcome page in GopherSpace - simple and understandable.
This is the reason why I created Gophoogle as the first page of the
Internet. Of course, there is another problem with GopherSpace.
Links from most Gopher:// lead to nothing. Nobody checks them
or updates them. New people have no idea where to go, where to look
for what and which servers contain information. Again, empty servers
with the inscription "Hello World" also upset people. In general,
studying the problem of communication in GopherSpace, you can
known a lot of useful things. Obviously, there is interest in
GopherSpace among end users, but if you do not work with these
people or live in an ivory tower, then this audience will only be
a temporary splash of the wave. Therefore, make more good and
interesting GopherSpace projects, home holes and so on. Do not
feed the globalists from HTTPs with what can help the development
of alternative models and systems of communication between people.