Rohan Kumar <rkumar at rkumar-dekstop> writes:
> Hello, Geminispace!
Yo,
welcome to gemini!
>
> [?]
>
> One last question: Gemininauts (please oh please let that be a word)
> with twinlogs, how do you decide what to cross-post and what to keep
> {WWW,gemini,gopher}-exclusive? I'm leaning towards keeping my weblog
> more "professional" and my gemlog less filtered, leaving the shortest
> bits for the Fediverse. I'm curious to know how you all handle this.
I?m serving the exact same content on both the HTTP and gemini version
(and, when I?ll eventually start serving the site under gopher I?ll
serve the exact same content there), but I see why one would like to
differentiate the content. In my case, I have a clojure script to
generate the sites and a edn file (think of it like a JSON if you
prefer) with a list of posts and pages, I think I can add a
:gemini-only? or :http-only? key to each post to decide where to post
to.
I see that you maintain two different version of each post, one in
markdown and one in gemtext and, if that?s fine for you, cool. I?m too
lazy to maintain two different version of the same content, so I?m
writing all the ?new? entries in text/gemini and converting them to HTML
for WWW consumption.
I?m happy with the replacement of markdown with gemtext, in my use case
at least. Before, I always had to double ? or triple ? check the posts
before publishing in a web browser to ensure that what I wrote was
exactly what the markdown parser thought (I cannot remember the correct
syntax for images/links and I always forget to put an empty line before
the lists, for instance). With gemtext I can write and publish directly
from my editor, and I?m confident that both the gemini and the WWW
version are OK. Another thing is the lack of inline formatting
(emphasis, code, etc). At first I found it limiting, but after I while
I got used to, and now I can see that I was exaggerating with the
formatting. The entries are more clear now, I think.
The result isn?t bad, the ?one link per line? can still be weird at
times, but with a bit of CSS it?s too bad, and my converter has a
heuristic: link to *(png|jpg) gets converted to inline images (I?m
serving less than 10 images, and all from my domain, so it works for
me).
> I just started writing a series on resilient git-based project setup,
> inspired by Sourcehut and all the conversations since the youtube-dl
> takedown (and subsequent re-instatement).
looking forward to it ;)
> Next up: set up a Gemini ring and web ring. Then maybe complete the
> trifecta with a Gopher hole.
it?s also on my todo-list
> Anyway, thanks for making Gemini awesome.
>
>
> /Seirdy (gemini://seirdy.one)
---
Previous in thread (2 of 6): 🗣️ Sean Conner (sean (a) conman.org)
Next in thread (4 of 6): 🗣️ Robert "khuxkm" Miles (khuxkm (a) tilde.team)