julian.kiedaischandClaude Opus 5.5
4b33e36580
From 16 KB a picture's or binary file's entry names its bytes by their SHA-256 instead of holding them; the bytes are on F, content-addressed (GET/POST /blobs with the session's grant, from the editor's origin, at most 16 MiB). A document's blob side says where they are: the editor's fetches and uploads, the room thread's asks F's main thread, and a start waits for the ones asked for; without a side everything stays in the document. Text stays Y.Text. A blob whose bytes are not there is never written back empty. A blob F has not got yet is asked for again a few times, and a running room reads late bytes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
17 lines
310 B
JSON
17 lines
310 B
JSON
{
|
|
"name": "@mdg-filius/doc",
|
|
"version": "0.0.0",
|
|
"private": true,
|
|
"license": "GPL-3.0-only",
|
|
"type": "module",
|
|
"exports": {
|
|
".": "./src/index.ts"
|
|
},
|
|
"dependencies": {
|
|
"@mdg-filius/core": "0.0.0",
|
|
"@mdg-filius/fls": "0.0.0",
|
|
"@noble/hashes": "2.4.0",
|
|
"yjs": "^13.6.33"
|
|
}
|
|
}
|