The Feed is where GCCR’s social layer meets the open web: images, screenshots, and moments shared beyond the live channel. Moderation at human speed cannot scale to every post the instant someone taps publish. On-device safety gates run first — locally, before upload — to catch obvious policy violations and give the poster immediate feedback instead of a silent takedown hours later.
The problem
Community radio attracts creativity and chaos in equal measure. A single explicit screenshot or slur baked
into an image can harm listeners, trigger store-policy risk, and burn moderator goodwill. Sending every image
to a cloud classifier solves accuracy for big platforms but introduces latency, cost, and “why is my screenshot
on your server?” friction. Hobbyists and operators deserve safety tooling that feels like part of the app — not
surveillance bolted on after the fact.
What GCCR does
- Pre-publish screening. When you attach media to a Feed post, the app checks it on your device before the publish completes.
- Visual content gate. Disallowed imagery is flagged locally; blocked posts don't go public in that state.
- Text-in-image scan. Words hidden inside screenshots and memes get checked — not just the picture you meant to show.
- Clear user feedback. When a gate trips, you see why publication stopped and can edit or choose a different image — no mystery failures.
- Limited operator bans. On-device gates are a first line for Feed publish. Per our Terms, Dialer's Apps does not run general content moderation; operator bans focus on underage use and child sexual abuse material.
Why this is hard in a browser
Screening tools are heavy. Running them inside a web app means juggling memory on older phones and tuning
thresholds so legitimate posters aren't constantly blocked. GCCR optimizes for fast local checks and
conservative blocking at publish time — accepting that perfection is impossible but silent failure is worse.