@pauby Yes, most #Obsidian users don't think of the effects of proprietary syntax extensions and lost tool features to work with their files when the tool isn't available anymore.

I'm writing a longer blog article about those more or less subtle lock-in effects of proprietary tools like Obsidian which are using alleged(?) open file formats for storage.

@bammerlaan as a #markdown #note taker and #editor, #joplinapp seems fine, but with a few caveats.

There are no readily available undo and redo buttons, the image note taking took a long time to save and the first thing I saw when opening a note was a request for location data... that kind of rubs me the wrong way.

But it's got notebooks and it's got tags - and weirdly enough, a plugin system? Like if they redo this app in modern design with optimization, it'll definitely be a contender.

@Xhuul I haven't found any decent #Markdown editor yet that convinced me.

And yes, I prefer Emacs with #orgmode.

I even write my text in Org and use the export-to-MD functions to generate the appropriate #MD.

That also saves me from remembering the MD-specifics of the current export target. I always mix up the MD flavors currently at hand because I need to use different MD-enabled tools on a daily basis and all of them have their special markup variants - sometimes it's even necessary to use, e.g., different table syntax (within the same MD tool!) for different table properties such as line breaks and stuff. It's really a bad mess with MD.

Btw: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/

#Markor is a mainstay for #Android #Markdown editors. It bridges the gap between document writer and note taker by separation of concerns.

As an editor, it has some fairly complex features, like making custom tables to illustrate data.

But it's also old in design and usability. Had to bump up the text size for my own convenience, but still doesn't out compete any of the other editors (like #OpenNote) in that regard.

What can I say about #SimpleMarkdown? It's simply... #markdown. No #editor bar or gestures to make text bold, underline, etc. Readability is obviously not a priority.

It does what it needs to do, and that's letting the user do everything - no guard rails, no organization, just "do it yourself" as a design principle. It could easily be someone's pick for #stock #Android apps.

#QuillPad is a note takers note taker - with #Markdown! This is great if you're a #developer who sponge off your notes to fill personal wikis to get information and discoveries consolidated quickly.

It's also a neat replacement for #GoogleKeep on #Android, as one of it's features is to tie notes with reminders.

So far my favorite contender within #Android #Markdown editors is #OpenNote (version 1.5.95, com.yangdai.opennote) because of its simple design and good use of screen real estate.

It's modern #Material #design (if I'm not mistaken) becomes more apparent in the settings screen, which illustrates what the various settings do quite nicely.

It's important to me that the editor doesn't take me out of the writing process. The editor is not WYSIWYG, but I still feel it works.

@muchanchoasado muy bien, lo preguntaba por verificar que no sucediera lo mismo que cuando se usan símbolos unicode tomados de un generador "fancy text" (como en textkool.com), ya que dichos símbolos son interpretados de formas inesperadas por lectores de pantalla (me enteré por ti y dejé de usarlos).

Eso significa que puedo seguir aprovechando #markdown sin causar problemas.

@askesis

o que eu gosto do #qoto, além do #markdown e do #latex (infelizmente agora inexistentes), é da grande quantidade de caracteres (mais de 65 mil) suportada em cada mensagem.

Não gosto de contar caracteres e nem de resumir/sintetizar minhas ideias postadas no #mastodon.

@lexLohr Für mehr #Markdown im #Fediverse.
Geschrieben von einer Instanz mit der #Mastodon #GlitchSoc
@selfhtml @aardrian