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.
One of the features I love in XCode is the sticky lines showing the class/method you've scrolled down in.
I love it so much I'm desperate to also have it in Android Studio, turns out it's coming in the next version! (Koala 2024.1.1)
Guess who's now using the canary release 😄
I try now #Logseq and this is #OpenSource and I would like to like it but somewhere I can't manage to understand and use it. I don't just want to write down my thoughts and #ideas, I also want to be able to check off a #todo list… 😐
Wow. I guess I was wrong when I said that we have well and truly enough #Obsidian how-to tutorials out there. Either that or this person doesn’t have the faintest idea how to google properly.
They're working on a DB version in parallel that will provide better scalability, performance and realtime #collaboration (#RTC). They'll charge for RTC.
Unfortunately, this seems to be the end for #orgdown markup as they are implementing #Markdown only now and a conversion feature later on. 😞
Therefore, logseq is not an option for me any more and I'll need to think about a migration strategy for my wife.
The mnemonic I use to remember Markdown link syntax is that the square brackets look a bit like a button and then the round brackets mention the URL as a note afterwards:
@publicvoit
Very nice overview. I agree on most of the points. I must admit i have not tested it as in-depth as you did.
I also tried to import a graph from my org-roam Zettelkasten directory, but the some links were working in the visual analyzer and some were not, though the links in the pages were correct. Did you try something similar as well?
Need to blog about it from an #orgmode perspective.
If there is an actual reason not to use #Emacs - and you really should go for this golden standard - then Logseq using #orgdown syntax is a great alternative.
But still, you get the whole #PIM feature-set with Emacs only. That's for sure.
I really have to say that this is a really good tool once you switch from the #markdown default setting to the much better #orgmode syntax. 😉
I'll migrate the #Joplin data from my previous testrun over to logseq and go with that for the moment.
Don't worry, I'll probably never leave my Org setup. It's for another person's management and knowledge base where #Emacs was no option, unfortunately.
@danyork Well, that's for sure an issue that is not related to the majority or people. 😉
IMHO, there needs to be a one-click solution to create a personal blog including a nice domain. Articles should then be written in a lightweight markup language like #Orgdown or even Markdown (which would be a pity) with a live preview window. On a click on a button, the content is then published.
Only this way, we'd have a chance to promote POSSE to the general public again.
"Only a tiny part of written text is printed on paper, so the What You See is What You Get (WYSIWYG) approach does not make much sense in the digital age. Plain text uses the What You See Is What You Mean (WYSIWYM) approach. "
"Nimm doch Markdown", haben sie gesagt.
"Das ist total einfach", haben sie gesagt.
"Damit arbeitet man ganz flott", haben sie gesagt.
"Das funktioniert in ganz vielen Editoren", haben sie gesagt.