#markuplanguages — Public Fediverse posts on home.social

OOTS @[email protected] · 2025-11-26 · 16:39 UTC

PSA (in case you where not yet aware of it):
#YAML is the #JavaScript of #markuplanguages .

Proof:
"There are ~~5~~ ~~6~~ NINE (or 63*, depending how you count) different ways to write multi-line strings in YAML."
Source: https://stackoverflow.com/questions/3790454/how-do-i-break-a-string-in-yaml-over-multiple-lines/21699210#21699210

I rest my case.

#yaml #javascript #markuplanguages

lia @[email protected] · 2025-09-24 · 09:00 UTC

A #Fediverse tech idea I've been considering for a while.

Hashtags can sometimes be annoying, right? Their primary application is finding posts related to a certain topic, including following one. Therefore, if I look for "horses", I want to find everything horse-related.

The following hashtags should therefore lead to the same set of posts:
- #horse
- #horses
- #equines
- #equine
- #horsetodon

Right? But that's not a reality. Some people tag with one of them, with multiple, or with none at all.

Similarly, #Döner, #Doener and perhaps even #Doner should lead to the same set of posts, right? And what about British-American-splits like how #Localization is #Localisation, and perhaps even #l10n as well? And #LGBT, #LGBTQ, #LBGTQ+, #LGBT+, #LGBTQIA and so on and so on also really should be one hashtag.

So what to do?

I propose:
We should introduce a second symbol for something like "fuzzy hashtags". Not the '#' symbol, but another; perhaps '&' or '~'.

That way I could tag my post '~horse', and it could appear on all hashtag feeds concerning the different spellings of horses! Or I could search for such a fuzzy hashtag.

The different variants could be crowdsourced, or overridden by instance mods. You could also opt-out of that system - your posts showing up in fuzzy searches, most likely.

This would also fix languages like German, where you have many inflected forms: #Männer #Mann #Mannes #Manns #Männern #Männers and so on should all lead to the same result.

Behold what I have to do to sign off on this post:
#MarkupLanguages #MarkupLanguage #Markup

#fediverse #horse #horses #equines #equine #horsetodon

lia @[email protected] · 2025-09-24 · 09:00 UTC

A #Fediverse tech idea I've been considering for a while.

Hashtags can sometimes be annoying, right? Their primary application is finding posts related to a certain topic, including following one. Therefore, if I look for "horses", I want to find everything horse-related.

The following hashtags should therefore lead to the same set of posts:
- #horse
- #horses
- #equines
- #equine
- #horsetodon

Right? But that's not a reality. Some people tag with one of them, with multiple, or with none at all.

Similarly, #Döner, #Doener and perhaps even #Doner should lead to the same set of posts, right? And what about British-American-splits like how #Localization is #Localisation, and perhaps even #l10n as well? And #LGBT, #LGBTQ, #LBGTQ+, #LGBT+, #LGBTQIA and so on and so on also really should be one hashtah.

So what to do?

I propose:
We should introduce a second symbol for something like "fuzzy hashtags". Not the '#' symbol, but another; perhaps '&' or '~'.

That way I could tag my post '~horse', and it could appear on all hashtag feeds concerning the different spellings of horses! Or I could search for such a fuzzy hashtag.

The different variants could be crowdsourced, or overridden by instance mods. You could also opt-out of that system - your posts showing up in fuzzy searches, most likely.

This would also fix languages like German, where you have many inflected forms: #Männer #Mann #Mannes #Manns #Männern #Männers and so on should all lead to the same result.

Behold what I have to do to sign off on this post:
#MarkupLanguages #MarkupLanguage #Markup

#fediverse #horse #horses #equines #equine #horsetodon

lia @[email protected] · 2025-09-24 · 09:00 UTC

A #Fediverse tech idea I've been considering for a while.

Hashtags can sometimes be annoying, right? Their primary application is finding posts related to a certain topic, including following one. Therefore, if I look for "horses", I want to find everything horse-related.

The following hashtags should therefore lead to the same set of posts:
- #horse
- #horses
- #equines
- #equine
- #horsetodon

Right? But that's not a reality. Some people tag with one of them, with multiple, or with none at all.

Similarly, #Döner, #Doener and perhaps even #Doner should lead to the same set of posts, right? And what about British-American-splits like how #Localization is #Localisation, and perhaps even #l10n as well? And #LGBT, #LGBTQ, #LBGTQ+, #LGBT+, #LGBTQIA and so on and so on also really should be one hashtag.

So what to do?

I propose:
We should introduce a second symbol for something like "fuzzy hashtags". Not the '#' symbol, but another; perhaps '&' or '~'.

That way I could tag my post '~horse', and it could appear on all hashtag feeds concerning the different spellings of horses! Or I could search for such a fuzzy hashtag.

The different variants could be crowdsourced, or overridden by instance mods. You could also opt-out of that system - your posts showing up in fuzzy searches, most likely.

This would also fix languages like German, where you have many inflected forms: #Männer #Mann #Mannes #Manns #Männern #Männers and so on should all lead to the same result.

Behold what I have to do to sign off on this post:
#MarkupLanguages #MarkupLanguage #Markup

#fediverse #horse #horses #equines #equine #horsetodon

lia @[email protected] · 2025-09-24 · 09:00 UTC

A #Fediverse tech idea I've been considering for a while.

Hashtags can sometimes be annoying, right? Their primary application is finding posts related to a certain topic, including following one. Therefore, if I look for "horses", I want to find everything horse-related.

The following hashtags should therefore lead to the same set of posts:
- #horse
- #horses
- #equines
- #equine
- #horsetodon

Right? But that's not a reality. Some people tag with one of them, with multiple, or with none at all.

Similarly, #Döner, #Doener and perhaps even #Doner should lead to the same set of posts, right? And what about British-American-splits like how #Localization is #Localisation, and perhaps even #l10n as well? And #LGBT, #LGBTQ, #LBGTQ+, #LGBT+, #LGBTQIA and so on and so on also really should be one hashtag.

So what to do?

I propose:
We should introduce a second symbol for something like "fuzzy hashtags". Not the '#' symbol, but another; perhaps '&' or '~'.

That way I could tag my post '~horse', and it could appear on all hashtag feeds concerning the different spellings of horses! Or I could search for such a fuzzy hashtag.

The different variants could be crowdsourced, or overridden by instance mods. You could also opt-out of that system - your posts showing up in fuzzy searches, most likely.

This would also fix languages like German, where you have many inflected forms: #Männer #Mann #Mannes #Manns #Männern #Männers and so on should all lead to the same result.

Behold what I have to do to sign off on this post:
#MarkupLanguages #MarkupLanguage #Markup

#markup #markuplanguage #markuplanguages #manners #mannern #manns

lia @[email protected] · 2025-09-24 · 09:00 UTC

A #Fediverse tech idea I've been considering for a while.

Hashtags can sometimes be annoying, right? Their primary application is finding posts related to a certain topic, including following one. Therefore, if I look for "horses", I want to find everything horse-related.

The following hashtags should therefore lead to the same set of posts:
- #horse
- #horses
- #equines
- #equine
- #horsetodon

Right? But that's not a reality. Some people tag with one of them, with multiple, or with none at all.

Similarly, #Döner, #Doener and perhaps even #Doner should lead to the same set of posts, right? And what about British-American-splits like how #Localization is #Localisation, and perhaps even #l10n as well? And #LGBT, #LGBTQ, #LBGTQ+, #LGBT+, #LGBTQIA and so on and so on also really should be one hashtah.

So what to do?

I propose:
We should introduce a second symbol for something like "fuzzy hashtags". Not the '#' symbol, but another; perhaps '&' or '~'.

That way I could tag my post '~horse', and it could appear on all hashtag feeds concerning the different spellings of horses! Or I could search for such a fuzzy hashtag.

The different variants could be crowdsourced, or overridden by instance mods. You could also opt-out of that system - your posts showing up in fuzzy searches, most likely.

This would also fix languages like German, where you have many inflected forms: #Männer #Mann #Mannes #Manns #Männern #Männers and so on should all lead to the same result.

Behold what I have to do to sign off on this post:
#MarkupLanguages #MarkupLanguage #Markup

#fediverse #horse #horses #equines #equine #horsetodon

tajpulo @[email protected] · 2025-02-15 · 10:33 UTC

I did not have much leisure time recently. But now I found two days to be back at the topic of #markupLanguages.

Wow, I just found a markup language implementation using the Smalltalk programming language (or Pharo language). This is really rare theses times and I did not even recognize its syntax.

https://github.com/pillar-markup/pillar

#Microdown

#markuplanguages #microdown

tajpulo @[email protected] · 2024-11-26 · 19:21 UTC

The space of #markupLanguages is so awkward.

There are people sitting down and write a specification for so-called #Markdown.

Then people sit down and see the obvious problem: fragmentation. Everyone writes parsers with different behavior due to underspecification.

So other people write a spec: http://vfmd.github.io/vfmd-spec/specification/#procedure-for-identifying-html-tags

They spend weeks writing a spec to fix fragmentation problems.

And in the end you cannot add id attributes to anchors. What the heck?

They just reinvent a worse wheel.

#markuplanguages #markdown

tajpulo @[email protected] · 2024-11-26 · 15:57 UTC

Well, “Episode 21: Keynote — John McCarthy” actually has a recording and he gives that quote at timestamp 1:13:15:
http://www.oopsla.org/oopsla2007/index56d8.html
http://www.oopsla.org/podcasts/Keynote_JohnMcCarthy.mp3

“When W3C decided not to use #LISP format but to imitate #SGML for that [it] showed a certain capacity to make mistakes” *laughter* “which they probably hadn't lost”

Conclusion: the first part is similar, but the second part of the original quote is unfamiliar.

Isn't the WWW a wonderful to be able to research this? #markupLanguages

#lisp #sgml #markuplanguages

dodothedev🦤💻 @[email protected] · 2024-04-17 · 21:52 UTC

After only 4 hours of sleep last night and in an attempt to not sleep at my desk, I was looking at trying out @joplinapp for my notes (till I can understand how to set up Emacs on multiple devices efficiently) because I wanted to start writing notes on my Music learning.

During a cursory investigation, I found it has an extension for ABC Notation (https://abcnotation.com/) and fell down that interesting rabbit hole.

#music #joplin #abcNotation #markupLanguages #Emacs