π Add OmniGlyph to README β a descendant that exists because of your discovery#89
Open
diegosouzapw wants to merge 1 commit into
Open
π Add OmniGlyph to README β a descendant that exists because of your discovery#89diegosouzapw wants to merge 1 commit into
diegosouzapw wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
π Add OmniGlyph to README β a descendant that exists because of your discovery
π Hey!
Before anything else: thank you. Genuinely.
pxpipe is one of those rare projects that doesn't just ship code β it ships a
discovery. You proved, with receipts instead of hype, that a production
model's vision channel can carry dense textual context at a fraction of the
token cost β and, just as importantly, that the conversion has to be decided
per-request by exact billing math, with an honest "it is lossy" section right
in the README. The dense 1-bit rendering, the profitability gate, the free
count_tokenscounterfactual, the fail-closed model allowlist, themeasure-before-you-claim culture: that's a masterclass in engineering honesty,
and it deserves to be loudly credited.
I want to be fully transparent: OmniGlyph
descends directly from pxpipe. This is not an "inspired by" situation β your
codebase was the literal starting point, and I'm proud of that lineage. Your
copyright line stays in our LICENSE,
and our README carries a permanent Acknowledgments section that names
pxpipe as "the discovery this whole project is built on" β and asks our users
to come star yours.
π‘ What OmniGlyph built on top of your foundation
--helpπ€ The ask
Would you be open to a small "Derived projects" note in your README? Even one
line would mean a lot β and it gives your users a pointer to a sibling
implementation of your idea:
π Final words
Whether or not this gets merged: your work matters. The context-as-image idea
was yours, the proof was yours, and every token OmniGlyph saves traces back to
that discovery. Thank you for sharing it with the community β loudly and with
receipts. π
Links:
omniglyph