Default commit message, part of an automated flow.

agora ranking.md

@@ -4,5 +4,5 @@
   - 1. a hack in [[agora.py]] which upranks users [[@agora]], [[@flancian]], [[@vera]], [[@neil]] in that order -- essentially admins in order of entry. This was hotfixed in when some long content that didn't render well (due to garden conversion issues) grabbed top position in interesting nodes. It's not a stable setup and I don't like that this kind of list could grow into a fixed hierarchy.
   - 2. client-side, as implemented by [[vera]] -- see, in the same node handler in [[agora.py]], the /uprank/ functionality. This is called by client side code for sorting.
 - I think we should start working on actual better ranking.
-  - One simple alternative would be to introduce upvotes/emoji reactions in the interface, and store those either in git (as a reaction log) or in, say, sqlite. This could be treated as 'volatile' data -- treating all data not derivable from the [[agora]] main repo transitively as volatile seems like a good design decision to me.
+  - One simple alternative would be to introduce upvotes/emoji reactions in the interface, and store those either in git (as a reaction log) or in, say, sqlite. This could be treated as 'volatile' data -- treating all data not derivable from the [[agora]] main repo transitively as volatile seems like an OK design decision to me (it would be optional, so wouldn't add to the initial setup cost).
   - Another alternative would be to support explicit upranking *within nodes*. So, for example, if I write [[uprank]] [[@neil]] in [[flaneur]], the Agora would render Neil's node above mine.

journal/2021-11-06.md

@@ -28,4 +28,6 @@
     - [[luandro]] https://ipfs.distributed.press/ipns/two.compost.digital/uncivilizing-digital-territories/
     - [[blue marbles]] https://ipfs.distributed.press/ipns/two.compost.digital/a-confluence-of-waters/
 - [[agora ranking]]
-- [[h atom]]
+- [[project snapshot]]
+- [[h atom]]
+- [[ward]] updated https://wiki.c2.com with an interesting new UI!