All talks: https://emacsconf.org/2024/talks/
Unlocking linked data: replacing specialized apps with an Org-based semantic wiki
https://emacsconf.org/2024/talks/links - Abhinav Tushar - Track: General
Watch/participate: https://emacsconf.org/2024/watch/gen/
Q&A: Etherpad
IRC: https://chat.emacsconf.org/#/connect?join=emacsconf,emacsconf-gen or #emacsconf-gen on libera.chat network
Guidelines for conduct: https://emacsconf.org/conduct
See end of file for license (CC Attribution-ShareAlike 4.0 + GPLv3 or later)
----------------------------------------------------------------
Notes, discussions, links, feedback:

• This looks very useful, thanks for your work
• Looks really handy! One of the biggest inhibitors to my usage has been figuring out how to collect things on mobile without friction. Will check it out!+1
• Thank you all!
• A few project links from the talk:
  • https://github.com/lepisma/org-roam-exts
  • https://github.com/lepisma/pile-android

----------------------------------------------------------------
Questions and answers go here:

• Q: Have you thought about doing the cosine similarity and sentence transformer calculations in Elisp so you don't need a separate Python process?  In my experience having to set up and manage additional state throws people off track.
  • A: I do want to try removing the dependency. But I haven't yet done any work in that direction. Mostly the problem is that model (for transformers) runtimes are much easier available in other languages. But if there is an ONNX runtime (or dynamic module) for Elisp, we should be able to do this.
  • Thanks, I can try writing an ONNX runtime module, this can be useful for several Emacs tasks besides semantic linking.
• Q: So far I have not used packages such as org-roam because I do not like the idea that it might become unmaintained some day. So I keep to the basic features in org for my workflow. Did you consider this aspect?
  • A: I thought about this too. But I have found the internals of org-roam simple enough that I don't think maintaining a fork is any hassle. Anyway it uses features already available in org-mode. The only development addition it does is, IMO, to maintain an SQLite index.
    • Thank you for your advice. I'll take another look at org-roam. And thank you for your talk. It was quite inspiring to me.
• Q: this is very cool and seems a bit influenced by logseq, which i am trying to transition away from and on to org roam. have you looked into somehow embedding the contents of a "linked" node into the parent itself? this is something that i miss quite a lot from logseq, where the contents were/could be transparently embedded and made for a nicer review experience
  • A: I haven't used logseq. When you say embedding, do you mean like document transclusion? Or something else?
  • yes, something like transclusion. quite useful for example in daily journalling where one can just dump the notes instead of figuring out a location. and then link them afterwards in the right file/node.
  • In some way, the org-roam buffer I showed shows linked nodes with nearby content. But I haven't done any work on transclusion till now.
  • This may be relevant to your question https://github.com/Vidianos-Giannitsis/Dotfiles/blob/master/emacs/.emacs.d/libs/zettelkasten.org#logseq-like-tagging-functionality. I don't remember exactly what it does because I don't use it myself, but I was curious to try and hack it after a discussion and it was relevant to how Logseq does transclusion in linked documents.
    • ooh, thanks for the link. this looks rather interesting :)
• Q: How did you do the similarity search?
  • A: Similarity, as of now, is just using embedding vectors from a locally running transformer model and then matching using cosine scores. Code is here https://github.com/lepisma/org-roam-exts/tree/master/org-roam-sem
• Q: Is your ml model for topics like "family members" available somewhere?
  • A: https://github.com/lepisma/org-roam-exts/tree/master/org-roam-sem the model I am using is a simple lightweight embedding transforme model. See this line https://github.com/lepisma/org-roam-exts/blob/a71f2ec3bb6bd9d2b21ab5fd70ec45fa18128896/org-roam-sem/src/org_roam_sem/featurize.py#L17C7-L17C77
• Q: is your org-roam config public? (init.el stuff) I've found vanilla org-mode not the most ergonomic. Thanks!
  • A: Do you mean https://github.com/lepisma/org-roam-exts
  • Also some of my writing config is here -> https://github.com/lepisma/rogue/blob/master/lisp/r-writing.el

----------------------------------------------------------------
Next talks:

• General: Emacs regex compilation and future directions for expressive pattern matching https://pad.emacsconf.org/2024-regex
• General: Survival of the skillest: Thriving in the learning jungle https://pad.emacsconf.org/2024-learning
• General: About Blee: enveloping our own autonomy directed digital ecosystem with Emacs https://pad.emacsconf.org/2024-blee

Questions/comments related to EmacsConf 2024 as a whole? https://pad.emacsconf.org/2024
----------------------------------------------------------------
This pad will be archived at https://emacsconf.org/2024/talks/links after the conference.
Except where otherwise noted, the material on the EmacsConf pad are dual-licensed under the terms of the Creative Commons Attribution-ShareAlike 4.0 International Public License; and the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) an later version. Copies of these two licenses are included in the EmacsConf wiki repository, in the COPYING.GPL and COPYING.CC-BY-SA files (https://emacsconf.org/COPYING/)
By contributing to this pad, you agree to make your contributions available under the above licenses. You are also promising that you are the author of your changes, or that you copied them from a work in the public domain or a work released under a free license that is compatible with the above two licenses. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION.