i only really made this so i can link to it on this post on my comment. whatever-

Explanation Time! ⏱

the idea here is that those “code blocks” aren’t regular code blocks, but a special syntax which the LM writes so that the UI can present that as verifiable “hyperlinks” with exact text to the actual source.

so here, the LM specified exactly which lines it wants to highlight.

meaning: its not hallucinating, and if it is, you notice it because the highlighting is wrong or doesnt match at all.

we essentially use the LM as a “highlighter” rather than a regurgitator, making mistakes obvious and correct answers immediately verifiably correct, cuz u can see the source.

explanation done-

i like mockups. and godot. so here we are.

this uses the solarized theme which looks somewhat close to the claude theme they use. somewhat close.

whatever something something ai bad or whatever, is this what u need to hear? sigh

i hope u have a nice day <3

this is very much a post i first posted on the Qwen community but then i decided that this stuff doesnt belong on blahaj zone and moved it here… oh well.

  • maria [she/her]@lemmy.blahaj.zoneOPEnglish
    2·
    28 days ago

    i know that generally, quoting stuff from files works well. the point here is less about being useful but more about being 100% verifiable.

    indexing things with line numbers absolutely works, but u gotta actually put line numbers in the tool output. Meaning, the read_source_code should return the line number at the start if each line, e.g.

    1:extends Control
2:
3:# comment here
4:and so on

    it eats up tokens, but does make line index hit rate almost always correct.