YAML s highly-underrated. Just sayin’

#programming #markup

YAML s highly-underrated. Just sayin’

#programming #markup

“Why The Heck Are We Still Using Markdown?”, Burak Güngör (https://bgslabs.org/blog/why-are-we-using-markdown/).

Via HN: https://news.ycombinator.com/item?id=47629903

On Lobsters: https://lobste.rs/s/nn403y/why_heck_are_we_still_using_markdown

#Markdown #HTML #Text #Rants #CommonMark #RichText #Markup

New hVmark Release: v1.6.0

I added two new markers: code and centered text. And the latter accomplishes the task in the most deprecated way possible.

https://github.com/HisVirusness/hvmark

hVmark is my tiny, opinionated markup language: MIT-licensed, intentionally strict, and built to power HisVirusness.com.

#markup #webdev #indieweb #smallweb #esolang #markdown

Ik werk steeds vaker met Markup (md) files in plaats van doc of odf.

Dat levert kleinere bestanden op die ook zonder speciale software (Word, Libreoffice) nog te lezen (en bewerken) zijn.

Die omvang voor dat ene bestand maakt niet zo veel uit, maar als je er honderden of meer hebt, dan scheelt dat enorm.

Tevens voor de toekomst minder afhankelijk van de dan beschikbare software.

Geïnspireerd door dit artikel van @martijnaslander

https://world.hey.com/martijnaslander/de-meedogenloze-consequenties-van-digitaliseren-in-plaats-van-informatiseren-08eef934

#markup #archivering #digitale

You can use this site to refresh your markdown skills
On this Server we can write with the beautiful markdown attributes in our toots. I also use markdown when I make my descriptions on GitHub.

#Markdown #syntax #language #markup #programming #GitHub #technology

https://www.markdownguide.org/basic-syntax/

It occurs to Us that just how horrible the #markup situation for #Matrix is isn't very common or accessible knowledge, so here's a summary from a nerd who loves tinkering with markup.

For background, unlike the common asmuption, Matrix doesn't actually work with #MarkDown (#CommonMark), but defines a narrow set of HTML tags and attributes to be supported and it's the client's job to convert markdown to HTML before sending. And, before We say anything bad about it, We absolutely love the idea, if it were executed properly, it would completely blow every other chat platform out of the water with how powerful the markup is while remaining just as accessible to the average user.

Of course, this is #mtarix we're talking about, so what actually happens is that
1. "Implement any of these tags at your convenience. We do not care how many or which." ( https://spec.matrix.org/latest/client-server-api/#mroommessage-msgtypes )and
2. even if you follow the """strongly advised""" set to a tee, there's still so much behavior left undefined that even when things are "supported", there is no guarantee that anything but the most basic of markup will result in messages that look anything alike.