might be overkill/flawed , but maybe something that checks to see using a VLM that the GIF's that are generated/modified etc using the old lib and the new one look similar ish at least?
if you have google's tpu's ... could probably be done
also an agentic flow that generate's gif's that might break the C version or actually cause pointer type exploits and see if similar approaches work or don't in the rust version?
maybe even an agentic red team that tries to do bad things to this through gif's to the library and see what it does?
i'm glad they had a skeptic
might be overkill/flawed , but maybe something that checks to see using a VLM that the GIF's that are generated/modified etc using the old lib and the new one look similar ish at least?
if you have google's tpu's ... could probably be done
also an agentic flow that generate's gif's that might break the C version or actually cause pointer type exploits and see if similar approaches work or don't in the rust version?
maybe even an agentic red team that tries to do bad things to this through gif's to the library and see what it does?
just thoughts... need coffee haha :)
Yes, from the article they basically did all those things
it feels yucky to read LLM generated words on a Google blog, but i guess it's not too distracting. cool write-up though