Who wants to add #Journelly to the tool page of #orgdown?
https://xenodium.com/journelly-open-for-beta
https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org
Or even assess its od support?
Of course, if you do have long-time plans for your personal #knowledgemanagement, you should not use proprietary tools like #Obsidian, #OneNote, #Evernote and alike.
You also should think of switching to a much better (learnability, portability/compatibility, typobility, logic, featureset) markup syntax like #orgdown which is used in #Emacs #Orgmode (among other tools).
But if you start with Org-mode, you need to know the right way of doing it, as so many web pages recommend. Here's my take:
#UOMF: The Right Way to Use #OrgMode
https://karl-voit.at/2021/08/30/the-org-mode-way/
ad syntax/Markdown/Orgdown/#LML: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
A specific blog post about the #lockin effects of Obsidian and Co (despite using some tool-specific flavor of MD) is in the making. (Please don't start a religious discussion here.)
@ajlewis2 @ellane @feralthoughts @hbowie @reichenstein
Just for clarification: same holds true for any other markup supported by pandoc, not just #Markdown.
However, if you stick with a syntax language that doesn't come with this explosion of flavors, you have less issues converting your data - in some cases you don't even have to convert at all any more.
The issue with Markdown is that its original form defined a small minimum of elements and each tool defined its own potentially incompatible extensions. With other #LML, the "original" or its standard defines the maximum set of elements and therefore, there is no need for "flavors" and no data loss or conversion effort.
HTH
@amoroso My thoughts:
- They mix up Markdown with the general term lightweight #markup language (as if #Markdown is the only #LML syntax)
- They ignore all other markup syntax examples such as (La)TeX, HTML, ...
- great screenshots of Word for DOS upwards 
- the title should be "#WYSIWYG vs. LML" (instead of the Word vs. Markdown story)
- no mentioning of other LML examples
Well it looks, as if we're settling for a mediocre standard again.
Related: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
Nice #Emacs #orgmode video about its basic features:
https://www.youtube.com/watch?v=QlYQijQCNHU (1h32min)
You can use that as a #tutorial.
I just finished my first version of #tootsnoop - a #Mastodon #statistics tool:
https://gitlab.com/publicvoit/tootsnoop
It shows you the x topmost boosts, favs, replies to your messages of the last y days.
Its text output format is #orgdown, the syntax of #orgmode. Perfect for #Emacs users and easy to read for the rest of us.
Have fun!
@publicvoit@graz.social Nur damit ich es richtig verstehe:
Du sagst, dass #Markdown schlecht ist, weil es zu wenig Syntax bietet. Die Erweiterung der Syntax durch z. B. #Obsidian Plugins (ja, die funktionieren nur in Obsidian) oder Flavours setzt du mit einem Lock-In Effekt gleich.
#Orgdown ist wesentlich besser, da es mehr Syntaxelemente bereit hält. Die Elemnte, die fehlen, können durch module hinzugeführt werden.
#Orgdown funktioniert aber nur mit #Emacs #Orgmode?
(Sorry, da kenne ich mich nicht mit aus)
Mein Feedback zur Podcastepisode #FocusOn Linux 140 zu Org-Tools https://karl-voit.at/2024/12/22/Feedback-FocusOnLinux-Org/
With #Markdown, the original (inconsistently designed) #LML syntax format is a minimal set that made much sense when used when typing emails and so forth. Later-on, various tools needed more syntax elements for obvious reasons. Those syntax add-ons extended the original Markdown. However, they were not standardized.
This resulted in a zoo of very similar but incompatible set of Markdown flavors. Those differences cause information loss by moving from one "Markdown" tool to another "Markdown" tool because Markdown is not Markdown in most cases.
In contrast to that, #orgdown, the syntax of #Emacs #orgmode, as the one and only original form has - by far - the largest set of syntax elements and various extensions by modules. Any other adaptation of this syntax in other tools chose a real sub-set of the original syntax elements. This makes data transitions much smoother, is less error-prone and causes less data loss.
More on that: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
@pandoc Great idea!
Let's introduce one slightly change at a time and in a few years we could transform #Markdown into #orgdown without anybody noticing and finally get a consistently designed and easy to learn lightweight #markup language with excellent tool support. 
https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
https://gitlab.com/publicvoit/orgdown
@ellane Oh, congrats to this new universe of opportunities. 
Coming from that direction, you might want to read:
https://karl-voit.at/2017/09/23/orgmode-as-markup-only
...still related to the syntax & following related to tooling:
https://karl-voit.at/orgmode/
https://karl-voit.at/2020/01/20/start-using-orgmode/
Meanwhile, I'm writing in #Orgdown & generate any #Markdown from that because there's no MD tooling that is able to compete.
Btw, I'll publish an article on lock-in effects related to MD-based tools like #Obsidian.
@pludikovsky When people are in favor of #Markdown, they either do mean the concept of lightweight #markup languages (#LML) in general (yeah!) or they do not really know many other LMLs in comparison.
Furthermore, people voting for MD often do ignore the obvious downsides of that ecosystem because they have already overcome some of them, ignoring the majority of people who still need to learn that LML in future. 
@pludikovsky Here is my summary why I do think that #Markdown is not a good lightweight #markup language compared to #orgdown (or the syntax of #orgmode): https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
Org Mode Syntax Is Intuitive, Easy to Learn and Remember
Org Mode Syntax Is Standardized
Org Mode Syntax Is Consistent
Org Mode Syntax Can Be Easily Typed
Org Mode Syntax Makes Sense Outside of Emacs
Org Mode Syntax Has Excellent Tool Support (If You Want)
... and for most of those arguments, Markdown is worse.
Has somebody using #Emacs #orgmode already implemented a workflow to get #Firefox #bookmarks into an #orgdown file (one bookmark = one org heading)?
Bonus for having the reverse workflow as well: (periodically) exporting the Org bookmarks (as headings) into the places.sqlite file of a Firefox profile.
I'd like to use a workflow where each #Mastodon message that gets bookmarked by me is automatically screenshotted to PNG, archived in a local directory and its text content + image descriptions get added to a text file (preferably #orgdown) together with a link to the screenshot and the original message URL.
Somebody willing to volunteer? 
aka t0rt0i53 ⁂ 
