💾 Archived View for rawtext.club › ~sloum › geminilist › 004771.gmi captured on 2024-02-05 at 11:18:41. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Côme Chilliet come at chilliet.eu
Thu Jan 7 20:08:12 GMT 2021
- - - - - - - - - - - - - - - - - - -
Le jeudi 7 janvier 2021, 17:25:36 CET Johann Galle a écrit :
from <gemini://gemlog.lanterne.chilliet.eu/GAMS.en.gmi> (revision 1):
When someone wants to register..., it sends...
I think that should be "they send"?
Yep, fixed.
... gemlog ...
I assume you are referring to a capsule in the format of the companion
specification "subscribing to gemini pages" with this. Maybe I am being overly
pedantic, but it might be nice to point it out explicitly.
I am referring to this specification when using the word «gemfeed» in the section «The board». I could link to it, but thinking about it we may also live out of the specification which feed format are supported, if a board author wants to support atom or rss it would work too, they just have to indicate it to potential members.
* convention for thread page naming?
You have taken a quite liberal approach with the rest of the specification, so
I don't think you'd need to add this to it.
Well the idea was to be able to link to the board thread before it is created, from the post creating the thread. For this it helps if the thread URI is predictable. But yeah, it may be specific to a board. In my tests so far I use a truncated sha1 of the URI of the first message.
The date must not be in the past or future.
Seeing that the crawler will probably not pick up the post in real time, this is
a bit strict. Maybe relax it to something like "not before the last post",
because I think that's what would most likely be used in practice: Filter out
any posts that are older than when the board last checked that gemlog.
This is bad wording. What I meant was that if you post a post on january 6th but date the post january 5th, the specification does not garantee that the board will see it.Of course when the board crawls a feed, it fetch all messages dated from last visit (but last visit may be in the same day, in which case all messages dated today are fetched).Feel free to suggest modifications to the text to make this clearer.
..., containing the tag enclosed in square brackets in the title.
I personally would think of the tag as including the brackets, but that is
bikeshedding.
More importantly: It might be simpler if the tag was just a URL/domain of the
board or something like that. On the other hand that would eliminate something
like posting to mulitple boards with the same tag. But that practice would IMHO
only create problems e.g. when replying to someone on one board and it also
shows up on another, but the OP is not there. And using the URL/domain would be
a nice way to make sure the tags are unique.
The tag needs to be in the message link from gemlog index, other links are not fetched, so board URL is too long to be used here.
When creating a new thread, link to the board homepage instead.
[...]
* Handling of errors, like first link to unknown page
I think it would be the easier solution to create a new thread if the first
link is to an unknown page, or if there is no link at all. If you think about
how threading works with e-mail, it also works that way. And yes sometimes it
breaks if the headers are not set right, but it will not be possible to build a
perfect system with this eiter.
Hum yeah that may be the best in practice. But I liked the idea of pointing to the board when posting a thread, so that people which do not know about the board can find it. But it may be just good practice and not specification per se.
Thank you for your input.
Côme