Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Social Page Profiles Use Transaction-Bound Text Safety
Repositories: partners-api, partners.furries.ph, social.furries.ph
Status: Local implementation only; the additive migration, Git-connected release, and database certification remain required
What’s Changed
- Public Page names, summaries, and Markdown descriptions now use the revision-only community text-safety check inside the Page database transaction. This preserves the existing low-request API budget while asking authors to revise matching text rather than silently removing it or penalizing an account.
Validation
- The 50-assertion source policy contract, API TypeScript check, and diff checks pass locally. The local Supabase database is unavailable, so migration execution and database certification remain release gates. No deployment or direct upload occurred.
Social Identity Setup Adds a Revision-Only Safety Check
Repositories: partners-api, social.furries.ph
Status: Local implementation only; Git-connected release and authenticated production measurement remain required
What’s Changed
- Profile names and usernames now pass through the same bounded community text-safety check when a member creates or changes a Social profile. Setup still asks only for email, profile name, username, and password; a match requests a revision and cannot penalize the account.
Validation
- The 44-assertion source policy contract, API TypeScript check, and diff checks pass locally. No deployment or direct upload occurred.
Social Bios Now Share Community Text-Safety Checks
Repositories: partners-api, social.furries.ph
Status: Local implementation only; Git-connected release and authenticated production measurement remain required
What’s Changed
- A public Social bio now uses the same revision-only text-safety check as posts, warnings, image descriptions, and filenames. A match asks its author to edit the bio; it cannot silently remove content or create an account penalty.
Validation
- The 41-assertion source policy contract, API TypeScript check, and diff checks pass locally. No deployment or direct upload occurred.
Moderation Dashboard Uses a Leaner API Bootstrap
Repositories: partners-api, moderation.furries.ph
Status: Local implementation only; Git-connected release and authenticated production measurement remain required
What’s Changed
- The moderation dashboard bootstrap now reuses its verified staff-access result instead of resolving it twice. This keeps the same permissions and visible dashboard data while restoring the established free-plan request envelope.
Validation
- The 10-assertion moderation request-budget contract, API TypeScript check, and diff checks pass locally. No deployment or direct upload occurred.
Social Adds Filename Checks Before Media Reaches Sanity
Repositories: partners-api, partners.furries.ph, social.furries.ph
Status: Local implementation only; the additive migration, Git-connected release, and database certification remain required
What’s Changed
- An uploaded image filename is now checked before bytes reach Sanity. A current revision-only text rule asks the member to rename and retry; the filename is not retained or shared.
- The check shares the existing exact-hash media gate, so it does not add a normal upload database request. Exact human-confirmed prohibited hashes continue to use the existing reversible review hold.
Validation
- The 38-assertion text-policy contract, exact-media quarantine contract, API TypeScript check, and diff checks pass locally. No migration publication, direct upload, or deployment occurred.
Moderation Separates Link and Text Rule Navigation
Repositories: moderation.furries.ph
Status: Local implementation only; Git-connected Cloudflare Pages release and authenticated staff verification remain required
What’s Changed
- Staff who can view policies now have separate sidebar links for deterministic Link rules and revision-only Text rules.
- Both panels remain on-demand and outside the normal moderation polling loop, so this does not add an automatic request or change policy authority.
Validation
- Moderation type checking, tests, and a fixture-backed policy-manager browser render pass locally. No direct upload or deployment occurred.
Social Defaults to a Member's Following Feed
Repositories: social.furries.ph
Status: Local implementation only; Git-connected Cloudflare Pages release remains required
What’s Changed
- Signed-in members now land on their chronological Following feed, rather than an algorithmic or generic discovery timeline.
- Visitors who have not signed in still see the public local feed without an unexpected sign-in prompt. No ranking system, recommendation data, or additional API request was added.
- The Local, Following, and Friends controls now expose their selected state to assistive technology.
Validation
- Social type checking, 45 tests, production build, and a fixture-backed signed-in browser render pass locally. No direct upload or deployment occurred.
Social Closes a Public Content-Warning Safety Gap
Repositories: partners-api, social.furries.ph
Status: Local implementation only; Git-connected deployment and database-backed release certification remain required
What’s Changed
- A visible post content warning now receives the same bounded safety checks as the post body and poll labels when a member creates or edits a public post.
- That includes contact-information warnings, link and mention limits, deny-listed link destinations, duplicate controls, and a member-visible request-to-revise when a current text-safety rule applies. It adds no AI decision, hidden score, or account penalty.
Validation
- The text-policy contract, public-contact contract, and API TypeScript check pass locally. No migration publication, direct upload, or deployment occurred.
Social Makes Event Activity an Explicit Privacy Choice
Repositories: social.furries.ph
Status: Local implementation only; cross-user privacy certification and Git-connected Cloudflare Pages release remain required
What’s Changed
- Editing a Social profile name or username no longer reads or writes Regosite event-disclosure preferences.
- Members must deliberately open Event activity settings before Social requests the small permitted event projection, and save that privacy setting independently. It remains private by default.
Validation
- Social type checking, 45 tests, the production build, and a synthetic signed-in profile render pass locally. No direct upload or deployment occurred.
Social Adds a Bounded Repost Burst Guard
Repositories: partners-api, partners.furries.ph
Status: Local implementation only; the additive migration and Git-connected Cloudflare Pages release remain required
What’s Changed
- A member can create up to 20 new reposts in one rolling minute. At the documented threshold, Social gives a short cooldown rather than a score, report, content action, or account penalty.
- Retrying an already active repost stays idempotent and does not use the allowance. The service performs the check and write in one transaction, so concurrent requests cannot bypass it.
Validation
- The 11-assertion repost-velocity source contract and API type check pass locally. The local Supabase container is unavailable, so migration execution and database advisors remain release gates. No direct upload or deployment occurred.