Question 1

Why is the webhook not triggered when I switch a note to a thought in Blinko?

Accepted Answer

A known bug in Blinko prevents the webhook from firing when you change a note's type (e.g., from 'note' to 'thought' or vice versa). Root cause: the `upsert` function in `server/routerTrpc/note.ts` returns early when `content` is null, and type-only changes omit content, skipping the `SendWebhook` call. To fix, modify the code at approximately line 668–735 as follows:

```ts
if (content == null) {
  SendWebhook({ ...note, attachments }, isRecycle ? 'delete' : 'update', ctx);
  return note;
}
```

This ensures the webhook is triggered even when only the type is updated. Track the issue for a permanent release fix.

Question 2

Why doesn't Blinko load all notes when I scroll to the bottom?

Accepted Answer

First check whether the missing notes were accidentally archived. Open the archived notes view/filter and unarchive them if needed. If notes are simply not triggering pagination because the page has no scrollbar, press Ctrl and scroll the mouse wheel down to zoom out until the scrollbar appears, then scroll to the bottom to load more. Also update Blinko to the latest version, as PR #1069 fixed duplicate-item issues in pagination.

Question 3

How to fix Blinko Markdown export generating 1KB image files with 'Unauthorized' error?

Accepted Answer

This happens because Blinko's Markdown export downloads original images via `/api/file/`, which requires authentication. The export job does not attach a token or cookie, so the API returns `{"error":"Unauthorized"}` and that JSON gets saved as the image file (hence the ~1KB size). Note that `/api/file/?thumbnail=true` is deliberately open for anonymous access, but the original-file endpoint always requires auth. Workarounds: 1. Set the notes to public/shared before exporting, so the image endpoint no longer requires authentication and images export correctly. 2. Manually append a token parameter to image URLs, e.g. `/api/file/pic01.png?token=` — the built-in export does not do this automatically, so you must modify the exported files or the export code yourself. 3. As an alternative, download images via the thumbnail endpoint (`?thumbnail=true`) which works without login.

Question 4

Why does Docker build from source fail with 'Could not resolve' errors for monorepo dependencies?

Accepted Answer

This happens because the esbuild.config.ts in the project is missing many required packages from its external list (e.g., mime-types, zod, dayjs, lodash/submodules, @langchain/*). As a workaround, use the official pre-built Docker image (e.g., ghcr.io/blinko-space/blinko:latest) instead of building from source. To fix the build, add all missing dependencies to the external array in server/esbuild.config.ts and ensure bun install uses the --frozen-lockfile flag in the Dockerfile.

blinko

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects