#[tantek]that's ok, that's what we have #indieweb-chat for ๐
gRegor, antranigv, gxt, mambang, mro, tiim, blahblah441, barnaby, kaichanvong, mro_, n8chz, jboy, [pfefferle], geoffo and [timothy_chambe] joined the channel; kaichanvong left the channel
#Seirdy_i honestly find that manually re-writing my markdown syntax to flow well in gemini is an excellent way to proofread.
[aciccarello], gRegor, gaussianblue and [KevinMarks] joined the channel
#[tantek]Seirdy_ I feel the same way when I take a plain text prose blog post and rewrite it with HTML and add links ๐
#[tantek]also I find it a bit humorous to have to rewrite markdown syntax bc it's supposed to be transparent/seamless with plain text ๐
#sknebel"can be read as plain text" (not that I'm going to argue that its great at meeting that goal) is not the same as "is equivalent to any other markup format out there" (gemtext isnt just unspecified plain text after all)
#Seirdyi also find that if i'm in the mood for syntax highlighting, gemtext is a lot faster to parse
#Loqisknebel, Seirdy: would you mind moving this conversation (markup, parse) to #indieweb-dev? thanks!
#Seirdyhmm...this isn't really a -dev topic since we're talking bout writing posts and proofreading
#Seirdy[tantek]: thing is, gemini uses gemtext which isn't the same as markdown. links get their own lines, and semantics are defined by the characters at the start of a line (or lack thereof)
#Seirdyit actually makes for a pleasant reading experience
#[tantek]writing posts & proofreading yes. the meta-point from Loqi is still reasonably valid, writers should not have to worry about mark-up, it gets in the way of the creative process
#Seirdysince that way links double as a navigational aid and people are encouraged to give links nice names
#Seirdyit's praxis to make links very short sentences instead of single words in gemtext
#LoqiIt looks like we don't have a page for "gemtext" yet. Would you like to create it? (Or just say "gemtext is ____", a sentence describing the term)
#[tantek]that's a good praxis, and I believe helps accessibility too
#Seirdyinstead of "i like [topic]", in gemtext we say "I like topic" \n "[wikipedia article about 'topic']"
#Seirdyor instead of "seirdy [wrote about topic]" we say "seirdy wrote about topic:" \n "[title of article about topic]"
#Seirdythe only major problem i see with gemtext is that people use preformatted text for code snippets and ascii art. after the triple-backtick, just like markdown, you can add optional text for a programming-language indicator or for alt-text for ascii-art; i do not like this conflation and would rather just avoid non-trivial ascii-art
#Seirdythe ascii-art is mostly something that was imported from gopher culture i think
#petermolnarthe part we you usually advocate for storing data in HTML?
#[tantek]I don't understand your point at all petermolnar, we were talking about how to write text content for an IndieWeb site. if you want to discuss storage formats sure that's more of a #indieweb-dev thing
#petermolnar> how to write text content for an IndieWeb site
#petermolnarby (local, indieweb.org) definition wouldn't an indieweb site need to be in html, so microformats apply?
#[tantek]sure, somewhere in-between authoring and publishing, but hopefully your server / CMS handles that
#Seirdyive seen quite a few personal websites using html generated from gemtext