There used to be a fork which promised to be compatibel: Loam - Visual Studio Marketplace
But the repo is gone/private
any idea why and where to find the last state?
There used to be a fork which promised to be compatibel: Loam - Visual Studio Marketplace
But the repo is gone/private
any idea why and where to find the last state?
The latest state I found (note: this looks older than the version of vscode, but the repo linked there seems deleted) can be found here: logfoam/README.md at master · DonnerWolfBach/logfoam · GitHub
I’m really considering expanding on that work because having two ways (one feature complete via logseq, one fast and convenient via the foam-fork from vscode) would fix a lot of my issues I think
Hey there! I was the developer of loam. I stopped working on it a couple years ago because I switched to Silverbullet for my notes. But I recently switched back to Logseq, which is why I saw your post here.
Sorry about taking the code down; I decided I didn’t like Github’s AI stuff, so I deleted all my repos on there. I went ahead and put the loam repo back, though, so if you want to get the latest version of the my code, feel free. I probably won’t work on loam further, but I’m excited to see any changes/improvements you make to it.
I’ll leave the code up here: https://github.com/CiceroIsBack/loam
(Discourse doesn’t let me post real links because my account is too new).
Hi and thank you!
Figured it might be something like this since the vscode plugin was still online.
How are you experiencing logseq at the moment? Do you have a larger graph (>100MB)? Because for me the performance is so horrible that I decided switching away. See also my comments on Leaving Logseq - Alternative suggestions? - #4 by asc9ybUnb3dmB7ZW