home.social

#knowledgemanagement — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #knowledgemanagement, aggregated by home.social.

  1. Socrates argued that writing would damage our memory. He was right, and we only know he said it because his student wrote it down.

    We made that trade so long ago we no longer notice we made it. Which matters, because we are being offered another one.

    New post tomorrow, the last in my Writing as a Technology series.

    #Writing #Memory #Technology #PKM #KnowledgeManagement

  2. Socrates argued that writing would damage our memory. He was right, and we only know he said it because his student wrote it down.

    We made that trade so long ago we no longer notice we made it. Which matters, because we are being offered another one.

    New post tomorrow, the last in my Writing as a Technology series.

    #Writing #Memory #Technology #PKM #KnowledgeManagement

  3. Socrates argued that writing would damage our memory. He was right, and we only know he said it because his student wrote it down.

    We made that trade so long ago we no longer notice we made it. Which matters, because we are being offered another one.

    New post tomorrow, the last in my Writing as a Technology series.

    #Writing #Memory #Technology #PKM #KnowledgeManagement

  4. Socrates argued that writing would damage our memory. He was right, and we only know he said it because his student wrote it down.

    We made that trade so long ago we no longer notice we made it. Which matters, because we are being offered another one.

    New post tomorrow, the last in my Writing as a Technology series.

    #Writing #Memory #Technology #PKM #KnowledgeManagement

  5. Socrates argued that writing would damage our memory. He was right, and we only know he said it because his student wrote it down.

    We made that trade so long ago we no longer notice we made it. Which matters, because we are being offered another one.

    New post tomorrow, the last in my Writing as a Technology series.

  6. Same question, different user, different answer, by design!

    An admin asks about executive pay and gets a cited answer. A regular employee asks the same and honestly gets none: your #MediaWiki chatbot only ever draws on pages the asking user may read.

    No separate permission system: your wiki's existing permissions decide what it may use to answer. Confidential pages stay confidential.

    Learn more at professional.wiki/en/mediawiki

    #Wiki #Privacy #AccessControl #KnowledgeManagement

  7. Choose the AI behind your wiki's answers!

    Configure your #MediaWiki chatbot via the admin panel: pick the provider, from Anthropic and OpenAI to the French Mistral and Swiss Apertus, or your own self-hosted model. Tune the chat features and apply your branding.

    Learn more at professional.wiki/en/mediawiki

    #Wiki #SelfHosted #DataSovereignty #KnowledgeManagement

  8. Ask your wiki in any language!

    The AI Assistant replies in your language, even when the wiki content is in another. A German question on an English wiki gets a German answer, with citations to the English pages it drew from.

    Learn more at professional.wiki/en/mediawiki

    #MediaWiki #Wiki #KnowledgeManagement #Multilingual #i18n

  9. 📝 The Danish Approach to Deepfakes: Can Copyright Protect Digital Identity?

    A critical analysis of the Danish proposal to use copyright law to protect citizens from AI-generated deepfakes, with reflections on the implications for the European regulatory framework.

    🔗 nicfab.eu/en/posts/danish-copy

  10. 📝 Markdown: From 2004 to the AI Era

    Markdown is not just a formatting syntax. It represents a philosophy of digital independence, data portability, and long-term accessibility that aligns with the core principles of privacy and user...

    🔗 nicfab.eu/en/posts/markdown-se

    @daringfireball
    @gruber

  11. 📚 Fifteen years of my personal BibTeX database!

    Fifteen years ago, I started keeping my own BibTeX database — just a plain text file edited manually, line by line.
    Later I switched to JabRef, and everything became much smoother!

    Over the years, the database has grown to almost 2,000 entries — and it’s no longer just a list of references, but a snapshot of the knowledge I’ve interacted with.
    Because I always fill in the Abstract field, full-text search now lets me literally “remember everything.”

    Among all my long-term “personal productivity” projects, this one has turned out to be the most valuable.

    #KnowledgeManagement #OpenScience #BibTeX #JabRef #PersonalKnowledgeBase #LaTeX #ResearchTools #DigitalResearch #DataScience #AcademicLife #Linux