Are you a student in the Netherlands with an active interest in #pkm and you cannot afford a ticket to the #pkmsummit2026 in Utrecht on 20 & 21 March? I'm donating 1 ticket to this conference. Let me know if you are interested, after reading https://www.zylstra.org/blog/2026/01/get-a-free-ticket-for-pkm-summit-2026/
Are you a student in the Netherlands with an active interest in #pkm and you cannot afford a ticket to the #pkmsummit2026 in Utrecht on 20 & 21 March? I'm donating 1 ticket to this conference. Let me know if you are interested, after reading https://www.zylstra.org/blog/2026/01/get-a-free-ticket-for-pkm-summit-2026/
Guide pratique d'artisanat numérique à l'Université | projet perso
Aujourd'hui, ajout d'un nouveau bonus : approfondir avec Pandoc : utilisation des fonctions --template et --reference-doc avec Pandoc, automatisation de tout cela avec Zettlr.
I sync my #Obsidian vault for free. Between desktop and mobile.
How? An Obsidian vault is just markdown files, so any file sync works. 3 options ⬇️
1️⃣ Google Drive, One Drive, or any other cloud provider.
2️⃣ Peer to peer tools such as SyncThing Fork or Resilio.
3️⃣ GitHub & co.
Read more: https://bryanhogan.com/blog/how-to-sync-obsidian
#ObsidianMD #PKM
https://bryanhogan.com/blog/how-to-sync-obsidian
First day of adopting the #LogSeq style journaling approach in #SilverBullet, that is:
- Create a page for the day
- Primarily take notes on that page as an outline
- Mention people and topics as page references
- Rely on Linked Mentions later from those pages, that now automatically collect (relevant) information. This works better in #SilverBullet now that child nodes are also kept as part of the linked mention snippet.
Let's see how this goes!
Guide pratique d'artisanat numérique à l'Université | projet perso
Aujourd'hui, ajout d'un nouveau bonus : approfondir avec Pandoc : utilisation des fonctions --template et --reference-doc avec Pandoc, automatisation de tout cela avec Zettlr.
My article about " #Markdown Is a Disaster: Why and What to Do Instead" from https://karl-voit.at/2025/08/17/Markdown-disaster/ was listed on the entry page of #HackerNews yesterday.
It hurts me to read through the comments. One part of the people who commented obviously didn't read the article they're commenting on.
And another part of the commenters does mix up #Orgmode, the Elisp implementation within #Emacs, with orgdown, the lightweight syntax which is actually the topic of this article. This part of the discussion is totally missing the whole point of my article: practical issues related to Markdown; choosing any other #LML which doesn't come with those downsides. #Orgdown was just one example of many which I wanted to mention because it is one of the least known alternatives outside the Emacs bubble.
🤷
RE: https://graz.social/@publicvoit/115875810144458821
I really do like how #SilverBullet is explaining the consequences of using their version of #Markdown on https://silverbullet.md/Markdown ( #CommonMark).
With statements like that, people learn about the consequences of using that tool.
They can either accept this or think about the negative effects before investing too much energy and data.
I really urge any ( #MD-)tool to include such a warning statement on their project page. It's for the benefit of your users.
One of the reasons why I most probably would recommend switching to SilverBullet if you - for some reason - can't use #orgmode with #Emacs which is IMO the optimum tool for many set of requirements: https://karl-voit.at/2021/01/18/tool-choices/
I'll migrate my wife's #PKM from #logseq (recent changes are a no-go to me) to SilverBullet or preferably Emacs. My upcoming #GLT26 Org-mode workshop (no recording) will tell her.
Fedi hive minds, please brainstorm with me.
I am looking into migrating to Obsidian MD from my existing notetaking app.
How do you utilise its overwhelming list of functions? How do you make it suits your purpose?
#obsidian #ObsidianMD #notetaking #pkm #personalknowledgemanagement
Federating knowledge: exploring ways to bridge wikis and notes
Join the workshop at #39C3!
NEW DATE: day 4, TODAY at 13:40 @ Free Knowledge Habitat Workshop Area.
Most people and organisations have their very own way of acquiring, organising, archiving, sharing, and collaborating on knowledge repositories. A broad spectrum of opinions and approaches resulted in a diverse and rich ecosystem of knowledge management solutions. Nevertheless, this also implies scattered and disconnected knowledge sources. What would it mean to build bridges among wikis and federate knowledge?
This workshop is going to be heavily centred on a twofold discussion, exploring the challenge of federated knowledge starting from two questions.
- What does it mean to federate knowledge repositories?
- Instead of pursuing a silver-bullet solution to embrace all use-cases, what would it mean to foster and enable interoperability for different software?
These questions stem from years of questioning and wondering how to integrate my personal note-taking and collective, participatory knowledge management at work, in organisations, institutions, and informal collectives. Recently, I began actively researching this topic as I started playing with the MediaWiki API to cross-synchronise my local Markdown notes and the XPUB wiki, the public learning wiki of the Experimental Publishing master. I am puzzled by taking advantage of the potential of a specific software (in this case, MediaWiki) while fearing of being locked-in.
Some further, more specific, insights and questions:
- Local-first approaches and software (e.g. Reflection)
- Interesting experiments based on existing protocols, such as Ibis
- What do we take of semi-open and obscure yet very cool initiatives like Anytype
- The power and the limits of plain-text: how to enable collaboration on simple Markdown files and build on top of it, as Obsidian does
Cc: @modal @p2panda @obsidian @wikimediaDE @dweb
#knowledge #FreeKnowledge #wiki #MediaWiki #API #Obsidian #Anytype #Ibis #IbisWiki #Reflection #CCC #Federation #federatedKnowledge #docs #PKM #knowledgeManagement #personalKnowledgeManagement #collectiveKnowledgeManagement #DWeb #decentralization #ActivityPub
Federating knowledge: exploring ways to bridge wikis and notes
Join the workshop at #39C3!
NEW DATE: day 4, TODAY at 13:40 @ Free Knowledge Habitat Workshop Area.
Most people and organisations have their very own way of acquiring, organising, archiving, sharing, and collaborating on knowledge repositories. A broad spectrum of opinions and approaches resulted in a diverse and rich ecosystem of knowledge management solutions. Nevertheless, this also implies scattered and disconnected knowledge sources. What would it mean to build bridges among wikis and federate knowledge?
This workshop is going to be heavily centred on a twofold discussion, exploring the challenge of federated knowledge starting from two questions.
- What does it mean to federate knowledge repositories?
- Instead of pursuing a silver-bullet solution to embrace all use-cases, what would it mean to foster and enable interoperability for different software?
These questions stem from years of questioning and wondering how to integrate my personal note-taking and collective, participatory knowledge management at work, in organisations, institutions, and informal collectives. Recently, I began actively researching this topic as I started playing with the MediaWiki API to cross-synchronise my local Markdown notes and the XPUB wiki, the public learning wiki of the Experimental Publishing master. I am puzzled by taking advantage of the potential of a specific software (in this case, MediaWiki) while fearing of being locked-in.
Some further, more specific, insights and questions:
- Local-first approaches and software (e.g. Reflection)
- Interesting experiments based on existing protocols, such as Ibis
- What do we take of semi-open and obscure yet very cool initiatives like Anytype
- The power and the limits of plain-text: how to enable collaboration on simple Markdown files and build on top of it, as Obsidian does
Cc: @modal @p2panda @obsidian @wikimediaDE @dweb
#knowledge #FreeKnowledge #wiki #MediaWiki #API #Obsidian #Anytype #Ibis #IbisWiki #Reflection #CCC #Federation #federatedKnowledge #docs #PKM #knowledgeManagement #personalKnowledgeManagement #collectiveKnowledgeManagement #DWeb #decentralization #ActivityPub
You were such an encouragement to me, throughout, @kate. ❤️ Your writing influenced me to stay rooted in my own authenticity, too. @harold - you were such a wonderful guide toward richer #PKMastery and #PKM.
#SilverBullet 2.3 released: Share, Libraries, Library Manager and Repositories
So I've been working on an AI assistant for Logseq, a note taking app. Think of this like a "Cursor for Logseq".
I'm quite happy as to where it's at right now, but I have a long way to go.
A thing I've decided I *really* like about #TiddlyWiki is you can have however many wikis for however many topics, projects, whatever. You don't need—and should maybe avoid—one singular digital garden. More like a garden here, a few planter boxes there, maybe help out a community p-patch down the block.
#SilverBullet 2.3 released: Share, Libraries, Library Manager and Repositories
A thing I've decided I *really* like about #TiddlyWiki is you can have however many wikis for however many topics, projects, whatever. You don't need—and should maybe avoid—one singular digital garden. More like a garden here, a few planter boxes there, maybe help out a community p-patch down the block.