Logseq

614 readers

1 users here now

Logseq is a knowledge management and collaboration platform. It focuses on privacy, longevity, and user control. It is Free Libre Open Source Software (AGPL-licensed).

Logseq offers a range of powerful tools for knowledge management, collaboration, PDF annotation, and task management with support for multiple file formats, including Markdown and Org-mode, and various features for organizing and structuring your notes.

Logseq's Whiteboard feature lets you organize your knowledge and ideas using a spatial canvas with shapes, drawings, website embeds, and connectors. You can visually group and link your notes and external media (such as videos and images), enabling visual thinkers to compose, remix, annotate, and connect content from their knowledge base and emerging thoughts in a new way.

In addition to its core features, Logseq has a growing ecosystem of plugins and themes that enable a wide range of workflows and customization options. Mobile apps are also available, providing access to most of the features of the desktop application. Whether you're a student, a professional, or anyone who values a clear and organized approach to managing your ideas and notes, Logseq is an excellent choice for anyone looking to improve their productivity and streamline their workflow.

founded 2 years ago

MODERATORS

disrooter@lemmy.ml

I think I'm (sadly) done with . It corrupted some data again and when I went to pull the stuff from git I figured it corrupted the .git/config even earlier than that. So now I have to pull the (hdev.im)

submitted 1 month ago by farcaller@hdev.im to c/logseq@lemmy.ml

7 comments fedilink hide all child comments

I think I'm (sadly) done with @logseq. It corrupted some data again and when I went to pull the stuff from git I figured it corrupted the .git/config even earlier than that. So now I have to pull the correct content from an old windows backup, ffs. What if I didn't have a full disk backup?

I like the idea of block references, I love the query engine and the simple UI. But data safety comes first, really. Logseq is a forever beta at this point.

I really like the concepts behind the logseq db version but @obsidian doesn't fuck with my data and you can see good iterative progress of its development. Yeah, it's not opensource. It's open data format, though, something logseq db will have to figure out eventually anyway.

you are viewing a single comment's thread
view the rest of the comments

[–] mroma@fosstodon.org 2 points 1 month ago (1 children)

@farcaller @logseq I know this doesn’t change the fact that the data got corrupted - but can’t you roll back to a previous git commit to restore instead of needing a separate backup?

[–] farcaller@hdev.im 2 points 1 month ago

@mroma @logseq so this is how my git config looks. Why? I don't know. It happens from time to time and I know logseq tries to write that file.

Now, when that file is corrupted, you'll get a notification in logseq UI that it's git autocommit cannot run. So you go and fix the config.

That is, if you notice the notification. My config got corrupted silently 3 weeks ago and that was the last time logseq did the autocommit, too. So yeah, you can roll to the previous good state if you have git history, but logseq can get you into a spot where you don't have any history.

Previously I'd keep logseq in Synology Drive, too, which offered me a point-in-time backup (technically a one-way sync with history, in my case). Since I migrated to a home-made NAS I couldn't find a replacement (I don't really need one with a 40G fiber to my storage, I just access files right on the NAS), so the only place that still had PINT snapshots was my windows backup.