Sloppy

Community-reported labels and filtering for AI-generated web content.

Sloppy lets you contribute community reports about suspected AI-generated or AI-assisted web content and choose how those reports affect your browser. It is not an automatic AI detector: community judgments are opinions, not proof of how content was made. Report a domain, a page, or selected text, image, audio or video. Choose Slop, Not Slop or Unsure, with six optional AI-use labels. One installation has one current report per target; edits replace that report rather than creating extra votes. Community results show totals, labels and honest unrated or disputed states. Unsure does not enter the Slop/Not Slop ratio. Open My Reports from the toolbar popup to manage confirmed reports and local pending work. Filter by scope, vote or status, edit votes and labels without revisiting a target, and delete your contribution. Readable host, protocol, page path and element-tag details stay on your installation. Use Open website, Open page or Open parent page to revisit a known target in a new tab. Find a reported page matches an address you supply against your saved report hashes locally, without sending the address or changing your vote or ranking choices. Old addresses cannot be recovered automatically. Saved links omit query strings and fragments; query-dependent pages may need their original address. Offline work remains visibly pending. Retry sends the current choice; discard removes only local work, and a timed-out request may already have reached the server. Community Rankings shows current opted-in domain reports in three views: Most Reported, Most Slop and Most Not Slop. Each domain report has a separate, initially unchecked choice to include it in public rankings. This deliberately shares the normalized hostname. Ordinary reporting works without participation; existing reports remain excluded, and page/element reports never count. Most Reported needs five current reports, including Unsure. Agreement views need five eligible Slop/Not Slop votes and at least 60% agreement, and order by the lower bound of a 95% Wilson interval. This ranking heuristic accounts for sample size; it is not a probability of AI origin. Counts are installation reports, not verified independent people, and credentials do not prevent coordinated voting. Ranking totals can differ from ordinary community totals. New lists may honestly be empty. Automatic checks, warnings, recoverable blocking and reversible hiding start off. Choose personal thresholds, cache duration and local domain overrides. Page-changing features request optional website access; manual reporting works without broad website access. Matching dynamic content is best-effort. Warning/block screens offer recovery controls, and hidden content can be revealed. Community requests wait for Sloppy’s disclosure and consent. Desktop Firefox also requires native optional data permissions; denial or revocation stops private sync, rankings and pending retries. Domain sharing still requires the separate per-report choice even if community access is enabled. Linkable target hashes, reports and installation authorization reach the configured HTTPS API. Raw page URLs, text, HTML, cookies, form contents and media URLs are not uploaded. Hashes are not inherently anonymous. Infrastructure processing and backup retention are explained in the policy. Delete individual reports in My Reports or the popup. Settings can delete this installation’s server reports before clearing local data; failure preserves retry identity and work. Revocation or uninstall alone does not delete reports. Deleted records may remain in encrypted backups beyond seven days when pruning fails. There are no Sloppy accounts, ads, telemetry, AI service or purchases. Screenshots show illustrative reports in an isolated test database, removed after verification. Published by magara corp. · magara-corp@proton.me