Logseq

Logseq is a free, open-source, privacy-first note-taking and knowledge management application supporting Markdown and Org-mode syntax. Founded in 2020 by Tienson Qin, the app emphasizes local-first data storage with bi-directional linking, block-level referencing, and an outliner-based interface. Available on Windows, macOS, Linux, Android, and iOS.

11/ 100
Healthy
1No Decay→Stable

Score generated by AI agents based on publicly cited evidence and reviewed by the project maintainer. Not independently validated. Last assessed 2026-10-29.

Score History

MilestoneCriticalMajor
Passion Project Launch (2020–2022) · 4/100Passion Project LaunchVC-Backed Expansion (2022–2024) · 9/100VC-Backed ExpansionDatabase Rewrite Limbo (2024–2026) · 11/100Database Rewrite LimboOG and DB Split (2026–present) · 11/100OG and DBSplit10075502502020202220242026-10Passion Project Launch (2020–2022) · 4/100VC-Backed Expansion (2022–2024) · 9/100Database Rewrite Limbo (2024–2026) · 11/100OG and DB Split (2026–present) · 11/100491111MilestonesFounded (2020)Seed funding ($4.1M) (2022)Split into Logseq OG and database Logseq (2026)Events

Timeline events are AI-curated from public reporting. Score trajectory is derived from documented events.

Passion Project Launch
4/100
2020-02-01 – 2022-05-05

Tienson Qin starts Logseq in February 2020 as an open-source outliner that stores notes as local Markdown and Org-mode files; it reaches the Hacker News front page in November 2020 and Product Hunt in June 2021. A desktop alpha, PDF annotation, flashcards, an Android build and an iOS app follow, with no ads, no fees and fully open AGPL code. The main blemish is reliability: an April 2022 forum thread collects repeated data-loss reports.

VC-Backed Expansion
9/100+5
2022-05-05 – 2024-04-23

Logseq announces a $4.1M seed round and keeps expanding, making Whiteboards and a Query Builder public in March 2023 and adding Smart Merge for Sync that August. It also introduces donor-gated access, opening the Sync beta first to Open Collective Sponsors in 2022. Privacy and reliability gaps accumulate: on-disk encryption is dropped and a plaintext cache is reported in November 2022, a CLA request prompts relicensing debate in January 2023, and November 2023 brings unwritten-edit data loss and a publish-feature data exposure. The database rewrite begins quietly in late 2022.

Database Rewrite Limbo
11/100+2
2024-04-23 – 2026-04-24

Version 0.10.9 in April 2024 is the last numbered release for just over a year, and days later Tienson Qin apologizes for building the database version without communicating it well. Forum threads ask why the app is not updating and whether the project is dead, and some users discuss moving to Obsidian or Affine. Maintenance releases resume in May 2025, the database version reaches mobile and real-time collaboration alpha in July 2025, and a public roadmap, end-to-end encrypted sync and page publishing follow by January 2026, while the file-based app receives only maintenance.

OG and DB Split
11/100
2026-04-24 – present

Logseq splits into Logseq OG, the Markdown app limited to security and Electron upgrades with no new features, and a database app that becomes the main version. The database app adds a read-only Markdown Mirror and custom sync servers, opens its beta and real-time sync to monthly supporters in July 2026, and reaches beta 2.0.2 in October, though August beta bug reports describe deleted user data. The product stays free and ad-free with no forced migration, while its future rests on a successor still in beta.

Alternatives

Local-first Markdown note-taking app with a large plugin ecosystem and active development. Optional Sync starts at $4/month billed annually ($5 billed monthly). Logseq’s file-based notes use Markdown, but block references and structure can need conversion when switching. Not open-source, but local-first.

Notion30/100

All-in-one workspace with databases, wikis, and project management. Cloud-based rather than local-first, so a significant privacy tradeoff. Moderate switch — requires importing notes and rebuilding structure. A free plan is available for individuals.

Open-source (AGPL), privacy-focused note-taking app with end-to-end encrypted sync. Supports Markdown with notebooks rather than an outliner structure. Self-hostable sync or paid Joplin Cloud (Basic €2.99/month, with an annual-billing discount).

Dimensional Breakdown

Summaries below were written by AI agents based on the cited evidence. They are editorial interpretations, not independent research findings.

User Value Erosion
Logseq's file-based app still works as a free, capable outliner, but since April 2026 it is Logseq OG, limited to security and Electron upgrades with no new features, after a gap of just over a year between numbered releases in 2024–25. New development goes to the database app, which opened to monthly supporters in July 2026 and reached beta 2.0.2 in October with substantial reliability fixes, yet August 2026 beta reports described bugs that deleted user data, including about 1,223 blocks in one graph. Long-running sync and data-loss complaints and the lack of a generally available successor keep this above the minimal band, but nothing has been paywalled or degraded for monetization.
How It Got Here
Logseq launched in early 2020 as an outliner with bi-directional linking and local Markdown storage, and feature velocity was strong through 2021–2023: PDF annotation and flashcards arrived in August 2021, mobile apps followed by April 2022, and version 0.9.0 in March 2023 brought Whiteboards and a Query Builder. Reliability was the persistent weakness, with prominent data-loss threads in April 2022 and November 2023, and the experimental on-disk encryption feature was dropped in November 2022. The database rewrite, begun in late 2022, then absorbed the team: after version 0.10.9 in April 2024 no numbered release appeared for just over a year, and forum threads by September 2024 asked whether the project was dead. Maintenance releases resumed in May 2025, and the database version advanced through alpha, adding end-to-end encrypted sync, page publishing and an Android overhaul. In April 2026 Logseq split the product: the Markdown app became Logseq OG, limited to security and Electron upgrades, while new features go only to the database app. That app opened to monthly supporters in July 2026 and reached beta 2.0.2 in October, but August 2026 issue reports described beta bugs that deleted user data, including about 1,223 blocks in one graph. The file-based app still works, but its feature development has ended and its successor is not yet generally available.
Business Customer Exploitation
Shareholder Extraction
Lock-in & Switching Costs
Twiddling & Algorithmic Opacity
Dark Patterns
Advertising & Monetization Pressure
Competitive Conduct
Labor & Governance
Regulatory & Legal Posture

Dimension History

2020Passion Project Launch2022VC-Backed Expansion2024Database Rewrite Limbo2026OG and DB SplitUser Value1233Biz Exploit0000Shareholder0111Lock-in1111Algorithms0111Dark Patterns0011Advertising0111Competition1111Labor/Gov1111Regulatory0111
Timeline (43 events)
major2020-02-01

Tienson Qin begins building Logseq as side project

Tienson Qin begins building Logseq as an Org-mode web outliner so he can check tasks and capture ideas on his phone. In a November 2020 Hacker News discussion, he says he has worked on it since February and subsequently added backlinks, a graph, and block embeds inspired by Roam Research. He confirms that the project uses Clojure/ClojureScript and works directly with plain-text Markdown and Org-mode files.

minor2020-11-14

Logseq reaches Hacker News front page

Logseq is featured on Hacker News, generating developer interest as a privacy-first, open-source alternative to Roam Research. The discussion highlights features like backlinks, graph views, and block embeds.

minor2021-02-20

Community begins asking about Logseq's business model

A long-running forum discussion begins about Logseq's business model, with the team explaining they plan to keep the core app free while charging for advanced features, storage, and collaboration. They acknowledge Logseq may not make money for the first 2-3 years, relying on Open Collective donations and planned premium features.

major2021-04-30

Logseq releases Desktop APP 0.0.1 alpha

Logseq publishes its Desktop APP 0.0.1 alpha release on GitHub. The project had previously been available as a web application supporting Markdown and Org-mode files with backlinks inspired by Roam Research.

minor2021-06-02

Logseq launches on Product Hunt

Logseq launches on Product Hunt as a 'joyful, open-source outliner' working on local plain-text Markdown and Org-mode files. The launch brings wider visibility to the project beyond the developer community, attracting PKM enthusiasts seeking open-source alternatives.

major2021-08-06

PDF annotation and spaced repetition flashcards added

Logseq adds PDF annotation support allowing users to highlight text within PDFs and create block references from annotations, along with a spaced repetition flashcard system. These features significantly expand Logseq's appeal to researchers and students, making it competitive with specialized tools.

major2021-12-08

Logseq publishes an Android alpha build

Logseq publishes the mobile-0.1.1 Android alpha build, extending the local-graph app to Android. Its release notes include a fix for a crash on Android 10. Multi-device workflows still depend on third-party file synchronization.

major2022-04-13

iOS app launches on Apple App Store

After months of beta testing through TestFlight, Logseq goes live on the iOS App Store, making the knowledge management tool available across all major desktop and mobile platforms. The launch completes Logseq's cross-platform story, though multi-device sync remains dependent on third-party services.

major2022-04-24

Users report repeated data loss, trust in Logseq erodes

A prominent forum thread titled 'Data loss happened twice, I can't trust Logseq anymore' accumulates dozens of replies from users experiencing data loss across platforms. Reports describe notes disappearing, sync conflicts overwriting content, and the app failing to write edits to local files. The thread remains active for over two years.

critical2022-05-05

Logseq raises $4.1M seed round from prominent tech leaders

Logseq announces a $4.1M seed round led by Stripe CEO Patrick Collison, Shopify founder Tobias Lutke, and former GitHub CEO Nat Friedman, with participation from Craft Ventures, Matrix Partners China, Day One Ventures, and A16Z GP Sriram Krishnan. TechCrunch and VentureBeat report the tool is used at Google Brain, Meta, Tesla, MIT, Stanford, and Harvard.

minor2022-06-06

Community GPT-3 plugin launches in the Logseq marketplace

A community developer announces that the logseq-plugin-gpt3-openai plugin has arrived in the marketplace, enabling GPT-3 text summarization and generation via the OpenAI API. Users supply their own API keys. In a later reply, the developer confirms that selected input goes to OpenAI and advises against using sensitive information.

major2022-10-10

Logseq Sync beta initially limited to Sponsors

A forum reply clarifies that Logseq Sync beta access is open to Open Collective Sponsors, with Backers to follow later. Later replies in the same discussion describe Backer access in December 2022 and March 2023. Sync is an early-access benefit for recurring contributors rather than a generally launched subscription service.

major2022-11-10

On-disk encryption feature deprecated in v0.8.10

Logseq removes the experimental on-disk encryption feature from the codebase after v0.8.10, citing maintenance burden and conflicts with Logseq Sync. Users who relied on the feature discover their notes are readable in plaintext at ~/.logseq/graphs, contradicting Logseq's privacy-first positioning. The team suggests third-party encryption tools like VeraCrypt as alternatives.

major2022-11-10

Security issue: notes cached in plaintext outside graph directory

Users discover that Logseq stores a plaintext transit file of all graph content at ~/.logseq/graphs, outside the user's chosen notes directory. This means even users who encrypt their notes folder have unencrypted copies elsewhere on disk. The issue contradicts Logseq's 'you control your data' philosophy and remains unresolved.

minor2022-12-20

Whiteboards feature announced for early backers

Logseq announces Whiteboards, integrating the Tldraw drawing library for spatial note-taking. The feature is initially rolled out to financial backers as early access, with plans to make it publicly available. Whiteboards aim to make visual canvases first-class citizens alongside pages and blocks.

major2023-01-30

Community debates a CLA request and possible AGPL relicensing

A January 30 forum post reports that Logseq had emailed contributors weeks earlier asking them to sign a Contributor License Agreement, quoting the explanation that AGPL is "so viral" that some companies ban it. Participants discuss Google's AGPL policy while debating retaining AGPL, dual licensing, and the possibility of proprietary relicensing.

major2023-03-29

Whiteboards and Query Builder become publicly available

Following v0.9.0 on March 28, Logseq announces that Whiteboards and a new simple Query Builder are available to all users. The Whiteboards feature works across desktop and mobile apps and is visible on the web in published graphs.

minor2023-05-14

Community calls for clearer development roadmap

A forum user asks for clearer communication of Logseq's development strategy and planned work, describing the Trello kanban as more developer-facing than user-facing. A team member replies that a new vision page is in progress and discusses documenting roadmap items and release references. Users follow up asking about the vision page in October 2023 and February 2025.

minor2023-08-18

Logseq 0.9.14 introduces Smart Merge for Sync

Version 0.9.14 adds experimental Smart Merge to reduce overwriting or losing edits when one user edits a page across devices. The feature requires manual enabling and re-indexing on each device, and the team recommends backups. It addresses a recurring multi-device editing problem without guaranteeing that data loss cannot occur.

major2023-11-17

Unrecoverable data loss from edits not written to files

A macOS user reports edits not being written to Markdown files or backups, then disappearing from Logseq after about a minute. Replies report similar losses, including after a re-index or restart; a later browser user also reports unwritten notes on a Windows C drive. The reports undermine confidence that notes visible in the app have reached local storage.

major2023-11-19

Privacy violation found in export/publish feature

A GitHub issue reports that Logseq's export/publish feature for 'public pages' inadvertently includes private information about the graph that should never be public. For a privacy-focused app, the bug is described as 'absolutely devastating' since many users may have already leaked private data without knowing.

critical2024-04-23

Version 0.10.9 beta released before a year-long release gap

Logseq releases Desktop/Android v0.10.9, labelled Beta Testing, with Linux ARM64 support and bug fixes. It remains the latest numbered release until May 2025, while development focuses on the database rewrite. Android users also question the absence of newer beta APK releases during the gap.

major2024-04-29

Logseq explains database rewrite after limited communication

Tienson Qin publishes a post explaining the database version and its progress, apologizing for spending "almost all the time on developing it without communicating it well with the community." A later migration review identifies this as his first official explanatory post and dates planning to late 2022, roughly a year and a half earlier.

minor2024-07-12

Community asks why Logseq has not updated for two months

A forum user says the source code appears not to have been updated for two months and asks about the project’s status. The question reflects concern about the release gap while work concentrates on the database version; the gap between numbered releases eventually lasts over a year.

major2024-09-02

Logseq project status thread asks whether the project is dead

A forum thread titled "Logseq project status?" opens with a user asking whether a lack of improvements means the project has serious problems or is dead. Replies explain the focus on the database version and discuss slow or buggy sync, development activity, and the difficulty of communicating progress. Later participants describe the existing version as saturated and discuss the new version’s timetable.

minor2025-01-03

2024: A Year of Logseq reviews a user’s note-taking workflow

A personal review describes Logseq’s diary, queries, templates, flashcards, whiteboards and task workflows. The author uses Autosync for Google Drive on Android and reports occasional synchronization file conflicts. The review values the core note-taking experience; the separate migration analysis documents the release stagnation.

minor2025-04-16

Logseq Pro FAQ leaves room for paid local features

A Logseq forum thread quotes the FAQ as saying Logseq Pro would include sync with Logseq storage, real-time collaboration and other future features, and that some future local features might be included in Pro as well. The FAQ explains that a local feature does not have to rely on Logseq's servers. It describes a possible subscription scope; no paid local features had launched.

minor2025-04-27

Logseq migration journey analysis highlights challenges and delays

A comprehensive analysis documents the database migration journey, noting the DB rewrite began in late 2022 but the first official communication came only in April 2024. The piece highlights how the migration created uncertainty, paused feature development, and led users to explore alternatives, while acknowledging the technical necessity of the architectural change.

major2025-05-06

Version 0.10.10 breaks year-long release freeze

Logseq releases v0.10.10 after just over a year since v0.10.9, followed by v0.10.11 on May 21 and v0.10.12 on May 26. The 0.10.11 release fixes major regressions from 0.10.10. Development remains focused on the database version.

major2025-07-10

DB version mobile app and RTC alpha opens for testing

Logseq announces that both the new DB-based mobile app (iOS) and Real-Time Collaboration (RTC) sync are ready for alpha testing, beginning with sponsors, backers, and contributors. The Android DB mobile app remains in development. This represents the first tangible output of the multi-year database rewrite available to early users.

major2025-08-29

Article describes users considering Obsidian and Affine amid Logseq delays

A Medium article describes some users discussing experiments with or migration to Affine and Obsidian amid Logseq’s database transition and development delays. It discusses the friction for users invested in existing workflows. Community tools for converting Logseq notes to Obsidian are documented separately on GitHub.

major2025-09-18

Logseq 0.10.14 closes a remote-code-execution vulnerability

Logseq's Desktop/Android 0.10.14 beta release for the file-based app states that it closed GHSA-92h5-2358-7xjv, a security vulnerability allowing remote code execution. The release also bumps pdf.js to version 4.2.67.

minor2025-11-28

Logseq publishes official product roadmap

Logseq posts its official product roadmap on the discussion forum following earlier community calls for clearer development plans. The linked roadmap lists work such as Markdown/database two-way sync, Android native experience, and E2EE password storage.

major2025-12-07

End-to-end encryption delivered for real-time collaboration

Logseq’s November 16–December 6 changelog announces full end-to-end encryption for synced graphs in Real-Time Collaboration. The E2EE password is integrated with system keychains on desktop and mobile. Page Publishing and the Android experience overhaul are documented in the following changelog, separately sourced in evidence.

major2026-01-11

Logseq DB changelog adds page publishing and an Android overhaul

Logseq's December 6, 2025 to January 11, 2026 changelog describes a page publishing system on Cloudflare Workers with password-protected pages, custom domains and search, and a major overhaul of the Android app's interface. It also adds hourly automatic backups for database graphs on desktop, while disabling built-in Git backup for database graphs; users can still use external Git.

critical2026-04-24

Logseq splits into maintenance-only Logseq OG and a database-first Logseq

Logseq announces that file-based Markdown graphs move to Logseq OG, which will receive security and Electron upgrades but no new features, while the new database app becomes the main version with faster development and new features. Users are not forced to migrate and can run both apps side by side. The same post says iOS TestFlight and new Sync invites have gone to $15-a-month Open Collective sponsors, with backer invites to follow.

minor2026-04-26

Logseq DB update adds custom self-hosted sync servers

Logseq's April 26, 2026 database update focuses on more dependable sync, command-line graph management and large-graph performance. It says self-hosted sync can now point Logseq at a custom sync server URL, and lists more robust graph downloads, search indexing and page rendering.

major2026-05-16

Logseq ships a read-only Markdown Mirror for database graphs

Logseq's May 16, 2026 update acknowledges that database graphs living in SQLite are harder to use with backups, grep, version control and other Markdown editors, and introduces an opt-in Markdown Mirror that writes a plain Markdown projection of a graph to disk and keeps it updated. The mirror is read-only; a two-way version was still in development on a feature branch.

major2026-07-13

Logseq opens DB beta and real-time sync to monthly supporters

Tienson Qin invites all active monthly Open Collective sponsors and backers to test the Logseq DB beta and real-time collaboration sync, signing in with the email tied to their membership. Testers are directed to the web app and to desktop and Android beta releases, and asked for feedback on sync reliability, conflicts and mobile behavior.

minor2026-08-04

Issue reports DB graph validation silently deleting property values

A GitHub issue reports that the database app's Validate graph operation runs fix-up passes by default that can retract user property values with no notification and no mention in the validation report, and without refreshing the displayed value. A follow-up on October 27, 2026 says the behavior was still present on the current master branch.

major2026-08-20

DB graph bug deletes embed targets, costing one user about 1,223 blocks

An issue reports that deleting or cutting a Node embed in a database graph removed the embedded target content instead of the embed. The reporter says it cost about 1,223 blocks on a production graph, recoverable only from a backup 20 minutes old. The issue was closed as completed on August 26, 2026.

major2026-10-07

Logseq 2.0.2 beta focuses on DB editing and data-integrity fixes

Logseq releases Desktop APP 2.0.2 (Beta Testing) for the database version, promising smoother editing, faster startup and more reliable workflows. Its fixes, ordered by impact on data integrity, include preserving unsaved edits, restoring deleted blocks and pages with undo/redo, and restoring mobile cloud-graph download and sync triggers.

minor2026-10-20

Logseq's rebuilt native iOS app opens for testing

Logseq announces that a rebuilt native iOS app, replacing its previous WebView-based app, is ready for testing. The company says it stores the database and assets in Logseq's own app directory for more reliable local storage, and cautions that the testing build may contain bugs.

Evidence (43 citations)

D3: Shareholder Extraction

D6: Dark Patterns

Logseq Pro — Paid Local Features DiscussionLogseq Discussion Forum · 2025-04-16
What Is Logseq's Business Model? — Community FAQLogseq Discussion Forum · 2021-02-20

D7: Advertising & Monetization Pressure

D10: Regulatory & Legal Posture

Logseq Privacy Discussion — 2025 Re-VisitPrivacy Guides Community · 2025-11-18
Privacy Question for Logseq SyncLogseq Discussion Forum · 2023-06-11
Why Logseq AI and How to Preserve Privacy?Logseq Discussion Forum · 2023-05-04
Scoring Log (6 entries)
fact-audit2026-10-29FABRICATION FOUND

Checked 69 original items including three alternatives, plus all prose and identity fields. 8 verified, 45 corrected (26 date-only), 15 re-sourced, 1 duplicate removed; five source splits preserve true details. Strict inventedDetails: (1) a 13-month/over-13-month gap to May6 2025 is contradicted by April23 2024 and May6 2025 primary release dates (379 days), https://github.com/logseq/logseq/releases/tag/0.10.9 and https://github.com/logseq/logseq/releases/tag/0.10.10; (2) Joplin Cloud $2.99/month currency is contradicted by official €2.99 pricing, https://joplinapp.org/plans/. These labels record factual contradictions, not intent. Ordinary wrong dates and paraphrased titles are not counted invented. Seventeen unsupported claims/inferences are logged individually in work/lead-decisions.json, including bounded alternative checks; repeated claims are counted once. Known date inconsistency in ACCEPT evidence29 was corrected from the shared source while resolving FIX timeline12; other ACCEPT items count verified. Verified lower-bound funding totals retained.

regrade2026-10-29CONFIRMED

11→11. No current dimension moved: all 10 re-scored from criteria and confirmed (D1 3: OG feature freeze and DB-beta data-loss bugs are stagnation/reliability issues, not paywalling or degradation for monetization; D4 1: DB graphs in SQLite offset by read-only Markdown Mirror, self-hosted sync and OG's continued plain-file support). Trajectory worsening→stable (last 12 months: OG limited to maintenance, but DB beta, E2EE sync, publishing, Markdown Mirror and native iOS testing advanced). Since Feb 2026: Apr 24 2026 split into maintenance-only Logseq OG and database-first Logseq; Apr–May DB updates (custom sync servers, Markdown Mirror); Jul 13 DB beta + RTC sync opened to monthly supporters; Aug 2026 DB-beta data-loss issues (#1068 open, #1105 ~1,223 blocks, closed); Oct 7 beta 2.0.2; Oct 20 native iOS testing; no pricing, legal, regulatory, labor or funding events found. Eras: 'Passion Project Launch' kept; 'VC-Backed Expansion' re-dated 2022-05-01→2022-05-05 (seed announcement) and re-scored 5→9 (recalibration from era events: D1 1→2 Nov 2022/Nov 2023 encryption removal and data loss, D5 0→1 plaintext cache and publish leak, D7 0→1 Sponsor-gated Sync beta, D10 0→1 privacy lapses); 'DB Rewrite Dominates Development' (2024-01-01, no inflection event) and 'Development Freeze Fallout' (2026-02-19, assessment date) merged into 'Database Rewrite Limbo' re-dated to 2024-04-23 (v0.10.9, last release before the year-long gap) and relabeled, scored 11; new era 'OG and DB Split' at 2026-04-24. Candidate cand:q4-3 misdated 0.10.14 to 2026-09-18; GitHub API shows published 2025-09-18, added as historical event. Skipped Publish-fix commit candidates (commit pages carried no verifiable detail) and the Nov 2025 changelog (minor). D2 evidence gap filled with marketplace README; D8 gained a primary source (Markdown Mirror PR). Alternatives rechecked, no change needed.

restore-check2026-10-29NO CHANGE

Checked 7 removed/trimmed candidates: 0 restored, 0 partly restored, 7 confirmed removed, 0 already present. timeline:update:10 — CONFIRMED REMOVED: The September 24 original and archive expose only an early-access update heading and publication date. They do not establish availability. The October 10 discussion describes Sponsors first, with later Backer access. The official setup guide describes recurring donations and a future subscription system, not first-service priority. No qualifying source establishes the removed timing or priority claim. Existing encrypted-sync and donation context remains intact. Sources read: https://opencollective.com/logseq/updates/update-for-backers-early-access-to-logseq-sync, https://web.archive.org/web/20260311123500/https://opencollective.com/logseq/updates/update-for-backers-early-access-to-logseq-sync, https://discuss.logseq.com/t/native-sync-for-backers/11465.json, https://blog.logseq.com/how-to-setup-and-use-logseq-sync/. timeline:update:14 — CONFIRMED REMOVED: The release notes establish the features, not a measured peak in development velocity. The April 2024 founder announcement and April 2025 Solanky analysis support rewrite focus and development delays, which are already retained at current timeline indices 22 and 27 and in narratives. They do not establish the candidate’s March 2023 high-water-mark characterization. Sources read: https://github.com/logseq/logseq/releases/tag/0.9.0, https://discuss.logseq.com/t/why-the-database-version-and-how-its-going/26744, https://solanky.dev/blog/logseq-migration-journey-challenges-delays-and-hopes/. timeline:update:15 — CONFIRMED REMOVED: Original thread is dated May 14, 2023 and contains a substantive staff response about the vision page, version fields, and documentation. Earlier FAQ includes user complaints about outdated Trello, but also staff references to public commits and Trello updates. User comments cannot establish the absolute dropped claims under the restore evidence rules. Later communication problems are already retained separately. Sources read: https://discuss.logseq.com/t/call-for-more-clarity-on-logseqs-roadmap/17756.json, https://discuss.logseq.com/t/is-there-a-public-roadmap-for-logseq-development/322.json, https://discuss.logseq.com/t/why-the-database-version-and-how-its-going/26744. timeline:update:16 — CONFIRMED REMOVED: Archived original thread was published January 30, 2023 and describes an email sent weeks earlier. Current contribution instructions establish the signing requirement but do not document an observed friction outcome. The email and relicensing debate are already retained. No qualifying source establishes the dropped causal outcome or April introduction. Sources read: https://web.archive.org/web/20260401004858/https://discuss.logseq.com/t/on-the-agpl-license-and-the-idea-to-move-away-from-it/14716, https://github.com/logseq/logseq/blob/master/CONTRIBUTING.md. timeline:update:20 — CONFIRMED REMOVED: Original thread and linked GitHub report document unwritten edits and losses after restart/re-index, but not the claimed cache-clearing/corruption mechanism. Both original reports are dated November 17, 2023. Reports of loss across systems are already retained. Search leads did not provide qualifying confirmation of the dropped mechanism. Sources read: https://discuss.logseq.com/t/edits-in-logseq-not-being-written-to-local-files-unrecoverable-data-loss/23031.json, https://github.com/logseq/logseq/issues/10510. timeline:update:26 — CONFIRMED REMOVED: Full original review was published January 3, 2025 and discusses personal workflows and occasional file conflicts. It does not provide the claimed development or competition analysis. That analysis belongs to the separately cited April 27, 2025 Solanky article, already retained at timeline 27 and evidence 1/21. No restoration or duplicate entry is warranted. Sources read: https://www.moratilla.com/personal/tools/2025/01/logseq/, https://solanky.dev/blog/logseq-migration-journey-challenges-delays-and-hopes/. evidence:update:4 — CONFIRMED REMOVED: Same original review and source search as timeline:update:26. January 3 date and personal-review label accurately describe the page. Separately sourced stagnation evidence is already retained; do not mislabel the Moratilla page or add a duplicate. Sources read: https://www.moratilla.com/personal/tools/2025/01/logseq/, https://solanky.dev/blog/logseq-migration-journey-challenges-delays-and-hopes/. Original/Wayback checks preceded bounded searches (18 queries in 7 calls; the two Moratilla candidates share research). Unavailable archives were not treated as evidence. Full dropped-subclaim decisions and search queries: work/restore-decisions.json. No qualifying support for the removed specifics; no score changes or removals. General rewrite/stagnation facts already retained do not validate the removed peak, attribution, or absolute statements.

Deep Enrichment2026-03-15
Alternatives Review2026-02-21GOOD
Initial Scoring2026-02-19