Ein wunderbares Beispiel, weshalb man seine Software in englischer Sprache betreiben soll.
Eine #Confluence-App von #Appfire ("... the leading global provider of software that enhances, extends, and connects the world's leading platforms ...") mit einem Gustostückerl an Fehlermeldung.
Spoiler: "Lösung" im zweiten Bild. Also schaut euch mal das erste (kleinere) genüsslich an und ratet zuerst mit, was es denn bedeuten mag.
My #filemanagement method using 🏷️ is so much more than just a fine solution for #photomanagement. You'll see that it actually addresses many aspects of working with local files in general:
@publicvoit I thoroughly enjoyed this post. The way he stresses the choice tool is less important than your work flow and requirements. And the need to start small and just capture notes.
@sping@publicvoit I was a bit confused when I first read that article, because I thought consult-buffer can do all that and was even mentioned in the article. So now I think the author simply was unaware. Or am I still missing something?
If you would conduct a presentation or a demo for an #engineeringdiary and #knowledgebase, what topic(s) would you mention in any case that might not be one of the obvious candidates?
However, due to my advanced #PIM processes, I rarely write things down on #paper.
I'd love to do so much more if there would be a great #FOSS solution for offline #handwriting#OCR. That would be a great investment by the #stationery industry! 🤔
It still offers better solutions compared to my #Boox#NoteAir#eink tablet.
@gisiger Second, Boox might take advantage of knowing the history of the handwritten letters, turning it into an online OCR process or at least a hybrid one.
This feature doesn't work for me because it replaces the original handwriting and is not adding a transparent OCR layer as typical OCR processes do with printed material.
Furthermore, if the OCR makes mistakes, there is no sane error correcting and re-try mechanism.
For me, this is a demo feature not something I want to use.
I forgot one important #pen and so I had to re-do the photographs: my LAMY AL-star black EMR Stylus with a felt tip which I use on my #BOOX#NoteAir#eink tablet.
@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?
@chfkch The graph is quite large due to the imported notes.org. However, because notes.org's data is corrupt, the graph doesn't make much sense as well.
In certain situations, a large number of tags in the controlled vocabulary are not a bad thing at all if you still limit the number of tags for each file/entity in general.
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.
@publicvoit I'm going to do a fresh test on it. I'm going to create a new graph and try that way. My current instance is broken and I'm not sure why. And this time I want to default to Org syntax.
I stopped using it around march 2023 because 1) there was an AI branch they were working on and I don't want AI in my notes; and 2) they used spec design for a new logo which the artist/designer side of me strongly disagrees with.
Anyone using a #zettelkasten tool like #obsidian, #joplin, #roamresearch etc) - do you really use the graph view and what does it help? How do you integrate it into your workflow?
I first thought I'd try it because I love mindmapping a lot, but I couldn't really make use of the graph so far.
Today, I tested #Joplin because people kept arguing that you keep your #Markdown files as local copies which prevents vendor #lockin.
From what I've seen today, this is not a valid argument. The md files are named with random file names, their content is not just md, it's md + JSON for some meta-data.
From what it seems, without Joplin, you'll lose your structure and your internal and external links. This would be a desaster to migrate to a different tool like #orgmode.