at://did:plc:44ybard66vv44zksje25o7dz/sh.tangled.feed.comment/3mxzxyjqtc622

Back to Collection

Record JSON

{
  "$type": "sh.tangled.feed.comment",
  "body": {
    "$type": "sh.tangled.markup.markdown",
    "original": "Two high-level things:\n\n- an overall termination indicator (\"end of STAR file\") would be nice. I don't have a proposal but can brainstorm something simple.\n- I vaguely wish there were more integrity checks, eg at a per-block level. right now integrity is entirely left to the profile. I don't have a proposal but again can brainstorm something.\n\nSomething I hadn't really picked up on is that requiring ordering of keys makes it possible to detect duplicates without retaining a set of all \"seen\" keys while parsing. I like that.\n\n4-byte magic: yay, I like that.\n\nvarint vs bijou: hmmmm I kind of like bijou and like like boosting friendly proposals like that. but I think that pragmatically varint being in stdlib in so many cases is a pretty strong consideration, so i'd slightly lean towards varint.\n\nsecurity section \"Encountering EOF anywhere [...]\": I think this is intended to mean that you get an EOF error/exception while reading from a stream of bytes, not refering to an \"EOF character\", which doesn't really exist (?) but sometimes folks call ASCII 0x04 / `Ctrl-D` \"EOF\". could clarify this.",
    "text": "Two high-level things:\n\n- an overall termination indicator (\"end of STAR file\") would be nice. I don't have a proposal but can brainstorm something simple.\n- I vaguely wish there were more integrity checks, eg at a per-block level. right now integrity is entirely left to the profile. I don't have a proposal but again can brainstorm something.\n\nSomething I hadn't really picked up on is that requiring ordering of keys makes it possible to detect duplicates without retaining a set of all \"seen\" keys while parsing. I like that.\n\n4-byte magic: yay, I like that.\n\nvarint vs bijou: hmmmm I kind of like bijou and like like boosting friendly proposals like that. but I think that pragmatically varint being in stdlib in so many cases is a pretty strong consideration, so i'd slightly lean towards varint.\n\nsecurity section \"Encountering EOF anywhere [...]\": I think this is intended to mean that you get an EOF error/exception while reading from a stream of bytes, not refering to an \"EOF character\", which doesn't really exist (?) but sometimes folks call ASCII 0x04 / `Ctrl-D` \"EOF\". could clarify this."
  },
  "createdAt": "2026-10-17T04:49:15+03:00",
  "subject": {
    "cid": "bafyreiacms3o4liefzuii6u4x2oo2ty6nn7otfg7n3bygz3ufpoml7yqzq",
    "uri": "at://did:plc:44ybard66vv44zksje25o7dz/sh.tangled.repo.issue/3mxzwsxxf3a22"
  }
}