docs: add Honest caveats and Community questions#1
Open
necco-c wants to merge 1 commit into
Open
Conversation
Adds two README sections at the end: - Honest caveats — flags that claudefeed observes rather than enforces (no blocking/sandboxing), and that open events come from openat only (not the older open syscall or mmap'd I/O). Both bullets route the 'contact us' ask to yeet.cx. - Community questions — answers 'Can I export the data stream?' by pointing at the existing ring.subscribe callback in main.js as the DIY path, and routing the managed-pipeline ask to yeet.cx.
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
1 participant
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.
Summary
Adds two new README sections at the end of the file.
Honest caveats — names the two limits worth flagging up front:
yeet.cx.openevents come fromopenatonly; the olderopensyscall and mmap'd / other I/O paths are not captured. Routes the custom-script ask toyeet.cx.Community questions — answers the most likely FAQ:
ring.subscribecallback inmain.js(already documented in the Alerting section above) as the DIY path, and routes the managed-pipeline ask toyeet.cx.All three "contact us" links carry UTMs (
utm_source=github&utm_medium=readme&utm_campaign=claudefeed) with distinctutm_contentvalues per link so traffic source is attributable.Test plan
yeet.cxwith the right UTM params> [!NOTE]callout renders correctly