Follow

Hey people on fedi, if I were to start a pod that is generated from Markdown source files, which link mode would feel the most natural for Gemini?
github.com/makeworld-the-bette

· · Web · 6 · 3 · 4

@rysiek None of those options are ideal, but "copy" is the least intrusive in my opinion.

You could also edit the generated Gemtext to make the links more coherent on their own.

@masterofthetiger @rysiek

"At-end" would be great if everything you wrote fit on one screen. 🤔 Otherwise "paragraph" is the way to go, but stay aware of how it looks and reads when composing so you don't ruin the pacing with link clutter.

@pixelatedfist @rysiek I think one of the issues is that the mental model for links in Gemtext is semantically different than the mental model for links in Markdown or HTML, so it's hard to convert one to the other without losing something.

@rysiek I think Gemini benefits from much less links in general. My wiki generates links after each paragraph, so [foo](bar) in a paragraph results in the following addition:

=> bar foo

Writing for the web, I'd sometimes have three or four links per paragraph, and it just looks and reads terribly.

My solution has been to link less, and adapt my writing style, so now my web pages also contain fewer links, and my preferred form of linking is something like this:

> I like quotes to go with my links.
=> URL title

@kensanata interesting, thanks! I do link *a lot* in my writing, so I might need to think about it a bit.

@rysiek The “paragraph” one is I think the best compromise between readability and accessibility, but the aesthetics with the repeated link might benefit from some adjustements. Like: instead of NUMBER: repeated link maybe go with ...last two words before the number[NUMBER]

@rysiek

Rereading my comments I feel I should clarify. I like the in-text reference system of “paragraph”, but I don't like its lack of description at the link level, for which I prefer the “copy” approach instead.

It would be nice to have a hybrid approach that does in-text references and link descriptions.

@rysiek The problem is of course that if the gemini client adds its own numbered references it's going to be a quaint little mess ;-)

@rysiek The page you linked has a sample screenshot from a client that seems to do just that, or am I reading it wrong?

@rysiek my site (m0yng.uk) generates Gemini from markdown. It puts links after the paragraph.
Feel free to browse and see how it feels for you!
Source code for the generator is available at git.m0yng.uk

@rysiek I’m surprised that “at the end” option was so unpopular. I voted that option.

@szczezuja yeah... on one hand it helps with the flow when reading, but on the other makes it difficult to get a relevant link when you are most interested in it (i.e. when you are reading the part of the text where it is linked)

@rysiek I have made that python package into a free API endpoint, if you're interested in using it?

(I'm making a HTML --> Gemtext API with a Markdown intermediate step. There's a Markdown -> Gmi endpoint as well as the main one for HTML)

@rimu thanks, I prefer my infrastructure and publishing pipeline to not rely on third party endpoints. Nice project though.

@rysiek Yes, me too!

I only made the API because I'm making a WordPress plugin but couldn't find any suitable PHP libraries... Also really wanted to try FastAPI.

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!