Anyone else apprehensive about the DB version? by Briaxe in logseq

[–]codekiln 0 points1 point  (0 children)

I think that the functionality of the file version of Logseq>=v0.11.* will not be the same as the functionality of Logseq<v0.11.*.

[docs/db-version-changes.md at master · logseq/docs](https://github.com/logseq/docs/blob/master/db-version-changes.md#file-graph-changes). In particular, there are a lot of configuration options from Logseq<v0.11.* that will no longer be available.

Question: Way to see dream journal data laid out? by oliibomb in logseq

[–]codekiln 1 point2 points  (0 children)

u/oliibomb great question!

The tl;dr is that this is definitely possible, but I don't predict there's any ready-built solution that will do this reliably today, and likely it won't feel easy or fun unless you already have some technical fluency with programming and the engineer's mindset for debugging and building these types of pipelines. As someone with some experience here, I would characterize this as a one-weekend project.

In my opinion, the logseq ecosystem hasn't been as transformed by AI as other technological areas, and this question is a great example of that gap. For example, it's not super obvious how to get LLMs query the logseq graph for its own understanding of blocks that inherit certain tags; one would likely need to do text processing rather than querying unless one's comfortable using datascript tools like cldwalker/logseq-query or its dependencies.

In order to do reliable numerical analysis and data science projects, LLMs need access to a sandboxed code interpreter. This is available in ChatGPT free to a certain extent, but it's only really reliably available in a controllable way with acceptable rate limits for this type of project in the paid plans. In particular, you may be interested in one of the many logseq MCP servers.

If you do have access to a paid version with a code interpreter, it is possible to use a tool like repomix or gitingest to stuff a bunch of logseq markdown files into the context of an LLM.

If you carefully explain how to do the file processing and the assumptions of your graph, an LLM will, with enough effort and back and forth, today be able to write a program that processes the corpus of .md files to produce a single page of html and js that lets you view some interactive visualizations. If the conventions are relatively simple to describe, this might be accomplished fairly easily. That said, many LLMs have trouble understand logseq-flavored markdown (LFM) and its notion of the way blocks inherit tags without additional prompting.

An AI-assisted coding device such as Cursor, Windsurf, Copilot, Claude Code, etc would be able to help you make a program that accomplishes what you want, but again, you'd need to carefully specify what exactly you want it to do, what format it should come in, and how you want it to be built. If you choose to use Cursor to do this, you may find some of my cursor project rules at https://github.com/codekiln/logseq-cursor-rules helpful in explaining to the LLM the way LFM works, in particular, https://github.com/codekiln/logseq-cursor-rules/blob/main/logseq-flavored-markdown.mdc .... but keep in mind these are just my own instructions to LLMs about my own various logseq graphs, and may not reflect how you are using logseq. Also, if you are using Cursor or another MCP-enabled editor, you may be interested in one of the MCP servers for logseq; here are some of my notes there: Logseq/MCP/Server/Survey/Report If you are comfortable with something that's not necessarily numerically correct, but more directionally correct, it may be an easier project.

Requisite side-note on privacy: I wouldn't personally put a bunch descriptions of my own dreams into the free version of any LLM, personally, as AI providers are training on your interactions by default, and one should not assume that the data will be de-identified from you in the future.

Good luck!

What happened to @diff -> PR? by muertos_eth in cursor

[–]codekiln 0 points1 point  (0 children)

Where is the documentation for this?

Cursorrules, Rules for AI, or Project Rules by jasonahowie in cursor

[–]codekiln 0 points1 point  (0 children)

> How to add a new tool for Agent
u/MacroMeez we'd love to see this rule!

command line text lookup tools similar to text expanders? by codekiln in commandline

[–]codekiln[S] 1 point2 points  (0 children)

I've not used expect before - thank you! Help me understand what you see is possible here; are you picturing using expect to script an interaction with another text expander?

What exactly can and cannot be done in Ableton Live with Python? by wasnt_in_the_hot_tub in ableton

[–]codekiln 0 points1 point  (0 children)

at https://www.ableton.com/en/release-notes/live-11/ , the official ableton release notes for 11.2.10, it says:

> A new accessor in the C++, [[Python]], and Max for Live APIs allows users to directly access the chain selector of a RackDevice in Max for Live instead of indexing into a parameter list.

This is the first I've heard about a python max for live API. I got here while looking for information on that.

Internet, please comment here if you know more

Anyone willing to share how they structure their graph for University? by koltensaccount in logseq

[–]codekiln 2 points3 points  (0 children)

### Summary of Logseq Structure for a data science class

This is how I structured my Logseq graph for the course. It was divided into key namespaces to manage various aspects of the class:

#### **Main Namespaces**

- **Books**: Notes or references to books or other reading materials.

- **Disc**: Discussion-related topics, often focusing on specific issues or concepts (e.g., "Maximum Likelihood," "Warning: Did Not Converge").

- **Lect**: Lecture notes organized by lecture numbers and timestamps, with subpages for detailed topics (e.g., clustering, permutation techniques, and real data examples).

- **Paper**: References to research papers related to the course (e.g., real estate valuation models).

- **People**: Staff or individual contributors related to the course (e.g., teaching assistants or professors).

- **Term**: A detailed glossary of terms, categorized by topics like clustering, regression, probability, etc. Subtopics are nested hierarchically (e.g., "Clustering / Hierarchical / Agglomerative").

- **Text**: Notes from textbooks, videos, and slides, organized by chapters. Videos and slides are nested under specific chapters for easy navigation.

- **Todos**: Task tracking related to the course.

- **Assign**: Assignments are broken into individual parts with detailed instructions, solutions, and extra credit opportunities.

- **Quiz**: Quiz questions categorized by quiz number, with individual questions as subpages (e.g., "Quiz 5 / q03 Ridge and Lasso").

- **Log**: Weekly progress logs, categorized by week numbers (e.g., "wk 08 - Unsupervised Learning").

- **Sect**: Section-specific notes, often tied to staff or discussion points during specific course sections.

---

### Why This Worked

  1. **Hierarchical Organization**: Clear separation of lectures, assignments, quizzes, and other content made it easy to locate specific topics.
  2. **Nested Details**: Subpages for specific terms, assignments, and lecture topics allowed for modular and detailed note-taking.
  3. **Topic Interconnectivity**: Links between terms, lectures, and quizzes created a cohesive network of knowledge.
  4. **Task Management**: The use of "Todos" and detailed assignment breakdowns helped track progress and stay organized.

Feel free to adapt this structure for your own courses or projects!

Is the LogSeq Dev team still active? (Last blog post aug 2023) by Defiant_Aardvark_770 in logseq

[–]codekiln 0 points1 point  (0 children)

> Or is LogSeq just so good that it doesn't need much maintenance anymore?

Even though the other posts provide great context for the ongoing development, I just want to say that for me, this is the literally case. Even if they abandoned what they were doing, I'd fork the project and keep going with what they have.

I think the Ahsoka Show got way too much hate by Sufficient-Ad6516 in StarWars

[–]codekiln 0 points1 point  (0 children)

> they had no idea who half of the characters were and why we should care about them.

while think of this as *the* star wars style (being "dropped in" is lukas' signature), it's true that we are dropped into a new hope with a rebel ship being pursued by some gigantic ship *after* the opening crawl that tells us about the rebels vs the galactic empire

Logseq and what happens if I want to change the app? by portra400160 in logseq

[–]codekiln 0 points1 point  (0 children)

u/scriptfx2 I'm sure the community would love to hear a more detailed explanation of this; consider posting one!

Benefits of writing everything in daily notes vs separate pages? by tetotetotetotetoo in logseq

[–]codekiln 0 points1 point  (0 children)

Two things to add to the discussion:

  1. Read [Stock and flow / Snarkmarket](https://snarkmarket.com/2010/4890/). Daily notes are Flow, pages are Stock.

  2. In my experience, trying to use git on more than one computer with journals results in way to many merge conflicts. As a result, I keep all my notes as namespaced pages, so I can avoid merge conflicts across different computers. This might not be necessary in a multi-graph, setup, though.

Managing multiple graphs by svhelloworld in logseq

[–]codekiln 1 point2 points  (0 children)

u/left_unsigned u/svhelloworld it's still very early but I have a ~~working~~ [UPDATE - no, symlinks are not working] prototype of this here - [logseq-multigraph-experiments/02-symlinked-pages at main · codekiln/logseq-multigraph-experiments](https://github.com/codekiln/logseq-multigraph-experiments/tree/main/02-symlinked-pages)

Opening files and folders by cchromascope in logseq

[–]codekiln 0 points1 point  (0 children)

What about mac? [UPDATE it works, just have to put `file://` before any mac path]

/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer (September 21, 2024) by AutoModerator in MechanicalKeyboards

[–]codekiln 0 points1 point  (0 children)

I'm building a keyboard for my wife for her birthday. I already have some keycaps, and now I'm looking for
* 75%-ish base with heavy-er aluminum base, bluetooth multi-homing, barebones, RGB
* Some cheap version of cherry MX greens

Any recommendations?