💾 Archived View for rawtext.club › ~sloum › geminilist › 006589.gmi captured on 2023-11-04 at 13:11:53. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Raph M. raph at raphm.com
Fri May 28 17:01:36 BST 2021
- - - - - - - - - - - - - - - - - - -
Gemini is human-focused, which implies to me that building a complicated
network of automated pingback/webmention/trackback-like things might
also be a poor fit. "Overkill" is the word that comes to mind.
I haven't actually published my notes on this, much less written an
implementation (the last couple of months in my life have been *crazy*
and all of my side projects have suffered), but one of the nice things
about the design as it's coming together in my notes is that sending a
geminimention can be done from any Gemini client by following a link and
pasting a URL. That's not clear from what I've published so far, of
course. One *could* automate it as part of a publishing workflow, but
you don't have to in order to participate.
A couple things come to mind. The first is that my statement above seemsas if it could be a criticism of geminimentions, which I _absolutely_did not intend! I am somewhat disenchanted with the way that some of theindieweb technologies have grown from "small and focused" to "everythingincluding the kitchen sink", and I let that emotion creep into themessage. I actually quite like the idea behind geminimention and I amvery interested to see an implementation!
Thanks for writing this. It looks pretty good; definitely easy to
understand, and doesn't require self-hosting to participate. I think the
goals of this and Geminimentions are pretty separate. My main goal with
Geminimentions is to help authors be notified of replies (which requires
the participation of the people replying, to be sure). This seems more a
means of gathering replies into a thread, which is probably more
generally useful, but also requires that all participants in the
conversation be monitoring the same instance for replies...
My immediate thought here is that it would be easy and probably veryuseful to create an automated hook in the GemThread service that wouldcall a geminimention URL whenever a response is added to a thread on aGemThread thread. There is nothing in the GemThread implementation thatautomatically notifies an author of responses, and I feel like that's apretty significant gap.
Perhaps I'll publish my unfinished notes as a response on this thread...
That would be great! There seems to be an obvious intersection betweenthese ideas. I'd be very interested to see your notes!
Thank you for the response, and I apologize again if my message came offas a criticism of geminimention. :)
Raph