The part that would bother me most is not the ban itself, but having no idea what to change. “Policy violation” could mean VPN, billing risk, location, or actual usage.
"Under-16 social media ban" sounds narrow.
In practice it means building an age-checking layer for the whole web, then hoping it only gets used for children.
The headless WebKit on DRM approach is interesting. How heavy is it in practice on the flipper one's soc, whats the idle and active memory footprint? Asking because WebKit's memory behavior on constrained devices tends to be the thing that bites you later, not the CPU
Immediate-mode in pure C is a nice constraint. how does it handle text rendering, do you bring your own atlas or is there something built in? Thats usually the part that balloons the dependency footprint.