HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
logseq
nbb-logseq
Clojure2022–2025
logseq / nbb-logseq

nbb-logseq

nbb with features enabled for logseq

3Distinct people
5Mentions
0Explicit recommenders
176GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

nbb with features enabled for logseq

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2022-06-14 16:17:37 UTC to 2025-02-26 03:26:09 UTC.

01232022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

5 sources
When Logseq is running locally, you can use its [local http server](https://docs.logseq.com/#/page/local%20http%20server) to do this. https://github.com/logseq/nbb-logseq is useful for automations and is already used to create github actions e.g. https://github.com/logseq/publish-spa. In the upcoming database version, nbb-logseq is able to read and write Logseq graphs completely independent of the app - https://github.com/logseq/docs/blob/feat/db/db-version.md#sc...
In Show HN: A terminal tool for Logseq journal entries
Hey Everyone! Really appreciate this discussion. Here's some extra context. Logseq is an open source notetaking app (similar to Roam) that has a feature where you can publish your notes as a static site. It has some advanced features where you can attach data to pages and bullet points (like some basic bio info, like name, site, twitter, tags) that you can query. There are some public graphs out there, but they're hard to find and figure out who made them. The main goal is just to create a "link ring" where we can find each other. This spec suggests a standard page on each graph called [[logseq-social/profile]] That way, when you find a public graph, you can go there to find out about its author and who they follow. You can download that page to your notes, and a simple logseq query makes the bio information of each user you save show up
Read the rest
on your follower list. The idea is really simple, just agreeing on a convention for a "profile" page on logseq that has some standard tags. Logseq has a really powerful plugin system that can have a whole react app in it, so down the line you could make a UI for friending, browsing, etc when more people have public graphs. Plus, there's now tooling to host your logseq notes as a programmatic api. So having some metadata standards opens up some interesting possibilities. https://github.com/logseq/nbb-logseq/tree/main/examples/fly-... There's lots of other stuff out there like this, but since this is just public static data there's hopefully a way to make it interoperable with existing solutions. If anyone knows of a good existing "bio" or link ring schema, I would be interested in taking a look. I have other fun ideas like hosting graphs on IPFS, or even some day having every logseq bullet point block be an immutable record on ipfs for use by everyone. Another example out there is agora, which seems to be somewhat compatible with markdown flat files that logseq uses https://anagora.org/agora-editor
In Let's build a decentralized social network together with Logseq

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.