> rather than production-hardened.
replyPlease run it through your preferred AI once or twice with instruction to look for bugs. The version of Fc in the main branch has at least a few memory safety bugs that attacker-controlled inputs could exploit.
I'd link a chat history but the tool I used has that feature blocked for some weird reason, and the locals round these parts don't take kindly to copy-pasted AI content...
Thank you. Fuzz safety is definitely on my list. Current focus is to broaden the benchmarks , predictors and preprocessors and see what sticks
replyDoes it assume the floats come from photos or sound or something?
replyIt is intended t obe mainly source agnostic (will try to add custom source predictors too). The idea is to treat input as an ordered stream of doubles and look for numeric structure like repeats, smooth deltas, fixed increments, or low-entropy bits. Target presentlyis scientific/time-series/simulation/analytics data, not photos or sound.
replyisn't sound a time series? I guess it's not usually 64-bit doubles.
reply[dead]
replyWhat do you mean by decode is parallel?
replyIt splits the input into blocks which are encoded separately, so the decoder can fire up multiple threads to decode multiple blocks in parallel.
reply