dankomaconv.js

Converters for producing DankomaJSONL data.

• GitHub
• Documentation

Installation

As a library:

npm install dankomaconv

For the command-line tools, install globally:

npm install -g dankomaconv

You can also run them directly with npx:

npx dankomaconv

Command-line tools

dankomaconv.js provides several command-line converters. Most of them read input from stdin and write DankomaJSONL to stdout.

| Command | Description | | ---------------- | ------------------------------------ | | bili2dankoma | Convert Bilibili danmaku data | | nico2dankoma | Convert NicoNico danmaku data | | ytchat2dankoma | Convert YouTube live chat data | | legacyfix | Convert/fix legacy DankomaJSONL data | | bilidanmafetch | Fetch Bilibili danmaku directly |

Basic usage

Most converters follow this pattern:

X2dankoma < source > dankoma.jsonl

For example:

bili2dankoma < danmaku.bin > dankoma.jsonl

nico2dankoma < danmaku.json > dankoma.jsonl

ytchat2dankoma < chat.json > dankoma.jsonl

legacyfix works the same way:

legacyfix < old.jsonl > dankoma.jsonl

Because the converters use standard input and output, they can also be chained with other Unix tools:

cat source.dat | bili2dankoma | legacyfix > dankoma.jsonl

bilidanmafetch

bilidanmafetch is different: it fetches the danmaku from Bilibili directly instead of reading from stdin.

bilidanmafetch <vid> [page] > dankoma.jsonl

The default page is 1:

bilidanmafetch BV1kx411c7UF > dankoma.jsonl

To fetch a specific page of a multipart video:

bilidanmafetch BV1kx411c7UF 3 > dankoma.jsonl

Authentication is provided through the BILI_COOKIE environment variable.

It must contain a SESSDATA cookie:

export BILI_COOKIE='SESSDATA=...; bili_jct=...'

Then:

bilidanmafetch BV1kx411c7UF > dankoma.jsonl

Logs are written to stderr, while the generated DankomaJSONL is written to stdout. This means it is safe to redirect or pipe the output:

bilidanmafetch BV1kx411c7UF > dankoma.jsonl

or:

bilidanmafetch BV1kx411c7UF | gzip > dankoma.jsonl.gz

Output format

All converter commands produce DankomaJSONL on stdout.

Each line represents one danmaku record.

I'd probably put this **above the existing documentation link section or immediately after it**, because the README now answers the "what the fuck do I actually run?" question without making users dig through `doc/doc.md`.