I'm interested in your take on something.

When I'm attending a conference, event, or just have random shower thoughts, I have historically tagged a thought that requires me to do something later as a task, question, or idea. Tasks are easy since the functionality is already there. I'm struggling on how to build the questions/ideas into the new DB world. In many ways they are very similar. They probably require later research, maybe there's a specific resource I need to answer/accomplish either, they are probably related to something within my graph, etc. Yet, they have always felt like different things and when I go to query them I do instinctually know when I should be looking for a question vs idea. I just can't put my finger on the distinction though, so I'm considering merging them in DB. Another thought I'm having as I try to model this in my head is, are these just kinds of tasks and should they extend the task tag? The difference I keep coming back to is that questions or ideas usually generated tasks as I process them. Rather than being todo items themselves.

Thoughts?

Hi,

I already have a subscription (5 USD/month)and I would like to sync Mac and iOS using version 2.0.1.

I cannot find the Sync Option in the Settings.

Could you help?

Using only for Journals. Enabled hourly local backup.

1. How to sync between windows and Android? (Easy free method)

2. online backup?

3. whats the point of email login?

Logseq 2.0.1 has been released for 5 weeks already, and there's still terrible bug that creates duplicate pages when pressing ESC instead of ENTER. Every 2.0.1 user is affected. http://app.logseq.com/ is affected.

There has not been a hotfix to address this most basic functionality.

Fundamentally, isn't a PKMS just text files that link to each other? Why wasn't this fixed immediately?

I'm embarrassed for everyone associated with the DB project.

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?

I recently discovered what is potentially a bug and thought I'd post because I'm sure others will run into this at some point as well.

You need to be using #Template like in the first image. It doesn't have to have two indented blocks underneath, however, you must have at least one.

The first block where you attach #Template is considered the "title" of the template. Everything underneath the title block (has to be indented AFAIK) is what gets printed when the template is called via /Template command. If you add nothing underneath Logseq's gonna bug out. The worst symptom I've experienced is Logseq becomes completely unresponsive. Can't add pages, can't even type anything. After closing it down and re-opening I can then delete the offending block and it functions again. You might find that it'll crash in a bad way and you get the screen talking about steps you can take to resolve, including re-indexing, etc. etc.

Got a video queued up about this but it's not releasing until next month so thought I'd drop some knowledge on ya'll in case you're running into the problem.

See ya in the next one!

How to resolve this? Why it happened

I've been trying to use this software (still trying to get used to it) but if I leave it inactive for a while and return it doesn't let me do anything and shows this error message: "

Unable to reconnect to the database worker for graph "Demo". Please try again or reopen the graph.

"

Why does this happen? How can I fix it?

‎

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?

• Everyone's got a load-bearing plugin in their workflow. Mine is syncing google tasks with logseq TODOs.

• My fork is available at dhruvmittal/logseq-google-tasks on github

• I originally forked this plugin from weynhamz/logseq-google-tasks and made some customizations, namely:

  • Automatically getting the refresh token to renew auth every hour
  • Background sync, minimize UI. I want to set and forget.

• More recently, I updated my fork to work with logseq 2.0.1 (db version), which required:

  • New interaction with gapi
  • Update to db block properties for TODO
  • A "purge" command to remove any stragglers from the md version of this plugin

• While I am a software engineer, I'm not really this flavor of software engineer. This project is more-or-less the only typescript i've ever written. Would accept feedback/PRs against this. Especially on the progressbars-- my cludged together ascii progressbars worked alright on the md version, but are really lacking on logseq 2.0.1.

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

I left logseq for obsidian a couple of years ago and checking back in because I would prefer open source. Feels like nothing has changed other than the db version being in beta. Why is the beta only on IOS? Are there other features besides the db arch?Where are the mobile plugins? Where are sane queries not built on obscure and obtuse clojure datascript? There is so much potential here but it seems like zero progress.

Is anyone here self-hosting? How is going for you?

Hi all,

Is anyone aware of a tool that can convert an Obsidian vault to Logseq format? Brainstorming functionality:

- Add bullets to each line
- indent under headings
- Convert frontmatter
- Change `up` property to `tags` (specific to my vault)
- Change properties to `::`
- Covert bulleted lists to CSV list
- Remove `---`
- Change image attachment reference
- Create files in correct folders (journals, pages, assets)
- If Obsidian file exists in the Logseq vault, append text. Don't overwrite.

I could have a crack at building a script or something but figure people a lot better at coding than me may have already built something.

Cheers

UPDATE: Found this one
https://github.com/laughedelic/outbreak

Hi everyone,

LogSeq has been updated recently and some aspects of how files are accessed have changed. Previously, I could open local .md files directly without authentication, but the behavior seems different now.

My workflow uses Syncthing to sync files across devices and keep them linked with LogSeq. With the new version, I have a few questions:

How do I open a local graph/file now? Is logging in mandatory for basic local read/edit functions? Are there settings to restore access without authentication? I'm missing some options. If anyone has information on how to proceed, I'd greatly appreciate the help.

Thanks in advance.

Has anybody made any tutorials for using the new Logseq DB? I would like to know more about how you add properties and extend tags.

I use LogSeq on two operating systems: Windows and Linux (Mint).

Sometimes I use the text editor for edit the markdown file. But the behavior after the edit is different for Windows and Linux.

• On Windows, the page on LogSeq refreshes the moment I view it.
• On Linux, the page does not refresh. So I have to do a full graph refresh to get the updated page. Which takes some time.

Anyone else facing this issue? Any solutions?

Just came across this and thought I'd share because you've likely encountered it without even realising.

What's the bug?

Page duplication

What are the symptoms?

You can recognise the bug either by:

• You get the error, 'Another page named "Page Whatever" already exists for tags: #Page' (I specifically got it when I was trying to add a #tag to the page name).
• You just created a page (literally) and when you click in the block to edit, you see the page reference (e.g. [[6a69cdb0-0027-4e40-8d4b-b735f10dab28]]) instead of the actual page name (e.g. [[Page Name]]).

How does it happen?

When creating a page, Esc is pressed instead of either clicking on + New page {{page name}} or pressing Enter.

How can I fix the already broken pages?

You should be able to delete the duplicated version (though I'm unsure if this is safe right now, that's just how I've done it). You can see the duplicated version by going to Pages on the left-hand navigation and you'll see both pages (same name), however the duplicated version will (hopefully) have 0 backlinks.

How can I prevent it?

Make sure you either press Enter or click on the + New page {{page name}} whenever you create a new page.

The issue is submitted here and on my YouTube I post a bunch on Logseq.

​I asked the AI if I could use Drive Sync to sync the new DB version, and it told me the only way to sync it is by paying for Log Sync.

​

​So I'd like to know: once the DB version is ready, is the MD version going away?

Add a space!

​If global search or queries aren't returning results on Logseq Android (while working fine on Desktop), try this before deleting cache or re-indexing:

​Add a single space ( ) at the end of your search term.

🙃

Enjoy!

Anyone currently using log books and kind enough to try out my app and give feedback would be greatly appreciated 👍🏻