Any idea what happened to Loam, the Foam fork working on Logseq compability?

General
1

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?

2

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

3

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).

1 Like
4

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

5

Honestly, it’s been fine for me of late. I have a 625MB graph, with about 1100 pages, 400 journals, and about 300MB of assets across 300ish files (mostly PDFs). I had previously had performance issues, which is why I had experimented with silverbullet, but have now switched back to Logseq full-time, and am loving it again.

I think two changes in my usage have helped:

  1. I’m not working with large pages; most of my pages are pretty atomic (zettelkasten-like), and if I need to make lots of large changes, I typically switch over to vim or VS Code and make the change there.
  2. I’ve stopped using Logseq Sync. This was a major issue for me, because I wanted something seamless that I didn’t have to manually do (so git wasn’t an option), but it also had to be reliable (Logseq Sync kept deleting my files). But I finally figured out how to reliably set up Syncthing on my iPhone, and now that’s running like a charm.

I can’t say as I’m particularly a fan of the direction Logseq DB is going (I really like having plain text files as the backend), nor am I completely sold on Logseq MD as it currently is. But for now it’s the best thing I’ve found.

What are you currently using?

6

cool work on loam! i had checked that project out some time back

the more notetaking solutions i’ve looked at the more it’s apparent to me that you need a db backend to get any reasonable performance. the one thing i’ll say for logseq db is that the devs tried to make MD work as long as they could and still are making interoperability into their roadmap (e.g., full sync from markdown to db and back seamlessly so folls can get the best of both worlds)