💾 Archived View for rawtext.club › ~sloum › geminilist › 001580.gmi captured on 2020-11-07 at 02:19:25. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2020-09-24)

-=-=-=-=-=-=-

<-- back to the mailing list

"Wide load" status code(s)?

solderpunk solderpunk at SDF.ORG

Fri Jun 12 13:32:51 BST 2020

- - - - - - - - - - - - - - - - - - - 

On Fri, Jun 12, 2020 at 07:21:03AM -0400, Natalie Pendragon wrote:

Okay, I will jump on the update train!
GUS now provides, by default, size information for every result*.
It's also exposed as a new query filter, in case you want to explore
more on your own. I put an example query below to show usage, but you
can find more documentation on the about page [0].

These are fantastic updates, well done!

Out of curiosity, can you use your GUSly powers to easily tell us, say,the mean and median size of resources served via Gemini?

How do you feel about the (wonderful!) GUS statistics page being updatedto give information on the size distribution? Perhaps you could binresources into size ranges, say semi-open intervals, [0, 1Kib), [1Kib,10Kib), [10Kib, 100Kib), etc, etc?

Since I am being greedy and asking you to do things, let me close bysinging the praises of GUS!

Back when new Gemini content was popping up at an insane rate, I wouldspend a lot of time exploring and reading. Weeks later I wonder thingslike "where did I read that great retrospective write-up on the careerof a recently deceased motorsport legend? I wonder if the author haswritten anything more?", have absolutely *no* recollection of who wroteit, or where it was hosted, or much else (I'm not a motorsport fan atall so did not remember the names of any people, cars, courses, etc.involved - but the thing was so well written and full of evident passionthat I enjoyed reading it as a complete outsider). So I'd GUS for somerandom small detail I could recall like "oil pressure" and, boom, thereit is.

Anybody who follows my phlog knows that one every few months I'll referto something I read in gopherspace but that I have forgotten the sourceof and could not find later by checking likely places, so I have toleave a note saying "if this was you, or you remember who it was, pleaselet me know!". I'm thrilled that Geminispace may never have thisproblem.

Seriously, Gemini search is already, somehow, a hundred, nay a thousandtimes better than Gopher search has ever been, despite the greatdisparity in time and attention between the two. I would love tounderstand why, and if there is some difference in the protocols thatexplains it. I have always suspected that Gopher's complete absence ofmachine-readable signalling of whether a request succeeded or failedmust be a huge impediment to building a reliable indexer, but I have noidea if that's actually the reason for the dramatic difference.

Anybody have any insight?

Cheers,Solderpunk