I have a pretty solid daily journal habit in Logseq as long as I'm sitting at the laptop. Morning pages, meeting dumps, end of day review, all of that sticks. The pages look full and i can query them later without much friction.

The problem is anything that shows up when I'm not at the desk. Yesterday i was in the grocery store parking lot and had a clean idea for how to restructure my project pages so the queries stop returning orphan blocks. I pulled my phone out with a bag of frozen peas under one arm, unlocked it one handed, opened the default notes app, and typed three words before the bag slipped. The peas hit the asphalt and split open. Spent the next minute picking frozen peas out of a cold puddle next to the cart return with my free hand going numb. By the time i got back to the phone the lock screen was up again and the thought was just gone. I sat in the car trying to reconstruct it and only got something about orphans which is useless on a daily page.

Current workaround is a pinned note on my phone called for logseq later that i dump fragments into when i remember. maybe twice a week i copy paste the whole mess into whatever daily is open and try to clean it. Most of it stays as raw dump blocks under an inbox heading and i never touch it again. Mediocre and i know it. The stuff that actually mattered still dies between the parking lot and the desk.

Is there a cleaner bridge between those away from keyboard moments and the daily page that doesn't just create another rotting inbox?

‎

CURRENT SITUATION

In my understanding, in order to sync a Logseq DB graph between two devices (e.g. PC and phone), currently we have 2 (+1) ways:

• Logseq’s Official Sync — convenient, but cloud-based and paid.
• Self-hosted sync — possible, but setting up and maintaining a sync server is too technical for many users.
• Two-way Markdown sync + a file-sync tool — potentially useful once two-way Markdown sync is available, but it would still require additional setup (for example, configuring Syncthing on both devices).

THE FEATURE REQUEST

BUT as the title suggests, it would be fantastic to have a fourth option:

• Automatic peer-to-peer (P2P) synchronization over the local network (LAN/Wi-Fi). This would provide a truly zero-config, local-first alternative. Since the data never leaves the local network, it perfectly aligns with the privacy and local-first values of the Logseq community.

>A particularly interesting reference implementation is Anytype. Its Any-Sync protocol supports local-first, peer-to-peer synchronization and uses mDNS for discovering devices on the same local network. Synchronization can then happen directly between peers without requiring remote infrastructure.
Here are some links I’ve found in this comment:
- Protocol Overview
- anyproto/any-sync

For users who primarily use Logseq on two devices in the same home or office network, this could be a very convenient alternative to both cloud sync and self-hosted infrastructure.

Is this doable?

I've been in the habit of pasting in files as assets over the years - meeting transcripts, notes,. Things that I want a permanent copy of, not jut a link.

They used to (old .md files version) show up as a link [name[(../path/to/assset/file.foo) But now, this creates a node in the page, with text of the file name, and an #asset tag. There's no direct link to the asset, and I'm clearly too slow to figure out how to get to the file, or make the text in the page a live link to the content.

I can navigate to the #Asset page, which shows a table of all assets. Where i can painstakingly search for the one I want, and open from there. But why no live link on the page where it was created?

What am I missing here?

Thirteenth Mang is doing an amazing job with Logseq DB video tutorials 👌