geminispace.info

gemini search engine
git clone https://git.clttr.info/geminispace.info.git
Log (Feed) | Files | Refs (Tags) | README | LICENSE

commit 8bcf71965e48a9954bf3efdba115b084a1062f5d
parent 53ce6aa50539d49837f9a9ef3f3ed9f9e50dfd2c
Author: Natalie Pendragon <natpen@natpen.net>
Date:   Sun, 17 May 2020 10:30:58 -0400

Update README TODOs

Diffstat:
MREADME.md | 14++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md @@ -33,15 +33,12 @@ as this guide to [mailing list etiquette](https://man.sr.ht/lists.sr.ht/etiquett - **add more statistics**: this could go in the index statistics page, and, in addition to using the index itself, could also pull information from the jetforce logs. - - server uptime - - num new servers per week/month - - num broken links - - num GUS queries per day - - most common queries (not sure about this one) - - num redirects - - num non-trivial redirects (i.e., more than just - removing/adding trailing slash) + - server uptime (from indexes) + - num new servers per week/month (from indexes) + - num GUS queries per day (from server logs) + - most common queries (not sure about this one) (from server logs) - num cross-domain redirects + - num domains with robots - **add tests**: there aren't any yet! - **add functionality to create a mock index**: this would be useful for local hacking on serve.py, so one does @@ -51,3 +48,4 @@ as this guide to [mailing list etiquette](https://man.sr.ht/lists.sr.ht/etiquett type of construct in the Gemini spec now, so I should probably add a TODO to refactor the extract_gemini_links function to exclude any links found within such a block. +- **track number of inbound links**