Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Showing release notes 901-910 of 1463
2026-08-3006:37
Social Notifications Now Offer a Calmer Catch-Up View
Repositories: social.furries.ph
Status: Local implementation only; Git-connected release remains required
What’s Changed
- Equivalent follows, reactions, replies, and quotes in the on-demand notification inbox now appear as one readable catch-up item. Post-related activity includes an Open post link that uses the normal visibility gate when selected. Opening the inbox uses one API request; members can separately choose Mark caught up when they want to save read state. This does not add notification polling, ranking, or suppression. Moderator notices remain separate so their current decision and independent-review action are always visible.
Validation
- Social type checking, 56 unit tests, production build, diff checks, and mixed-inbox/browser-action fixtures passed locally. No deployment or direct upload occurred.
2026-08-3006:37
Social's Empty Following Feed Offers Explicit Discovery Choices
Repositories: social.furries.ph
Status: Local implementation only; Git-connected release and Starter Pack curation publication remain required
What’s Changed
- Members with no posts in their chronological Following feed now get two clear choices: individually review curated people and Starter Packs, or browse the separate chronological local timeline. The product does not automatically follow anyone or enable a ranked recommendation feed.
Validation
- Social type checking, 52 unit tests, production build, diff checks, and an authenticated fixture-backed browser render passed locally. No deployment or direct upload occurred.
2026-08-3006:37
Public Social Event Cards Can Add a Calendar Reminder
Repositories: social.furries.ph
Status: Local implementation only; Git-connected release and event-projection publication remain required
What’s Changed
- Public event cards can now download a standard calendar file from the event details already shown on screen. This does not register anyone, create an RSVP, store a location, or send another API request; the canonical Furries PH event page remains the source of event and registration details.
Validation
- Social type checking, 52 unit tests, production build, diff checks, and a fixture-backed browser download passed locally. No migration, deployment, or direct upload occurred.
2026-08-3006:37
Profile and Page Markdown Editing Reaches Composer Parity
Repositories: social.furries.ph
Status: Local implementation only; Git-connected release remains required
What’s Changed
- Bio and Page-description editors now have the same Markdown formatting controls and help as post composition. They edit only Markdown source, preview through the existing safe renderer, and do not add a browser HTML sink or another API request.
Validation
- Social type checking, 52 unit tests, production build, diff checks, and a fixture-backed profile editor render passed locally. No deployment or direct upload occurred.
2026-08-3006:37
Moderation Actions Now Require a Recorded Notice Decision
Repositories: moderation.furries.ph, partners-api, partners.furries.ph
Status: Local implementation only; additive database migration, authenticated role testing, and Git-connected Cloudflare Pages/Worker release remain required
What’s Changed
- Before a moderator confirms a Social action, the dashboard now states the exact scope of that action and requires a recorded decision about the affected member notice.
- The chosen decision is retained with the replay-safe action receipt and in the restricted case history. Choosing to send a notice separately deliberately does not send a message automatically.
- Reporter identity remains protected, and account actions continue to affect Social participation only—not sign-in, Rego, registrations, or shared Friends records.
- Individual post/profile cases also show current Social participation and public-profile state with counts for the displayed case only. They do not become a member directory or expose contact, Rego, Friends, private-content, or unrelated-case data.
- Moderators can save a small set of private browser-local queue views. Administrators can search the audit entries they have explicitly loaded; the search stays metadata-only and does not add polling or a global audit lookup.
- The audit history is now fetched only when an administrator asks for it, in newest-first pages of up to 100 metadata entries. A browser session can load at most five pages; it remains outside the activity poll and does not expose audit detail.
- Content/account/closure actions also require a short moderator rationale. It remains in the restricted action receipt and case history, is never sent automatically to a member, and cannot include reporter identity or private evidence.
- If an action result is interrupted, its review dialog remains open. Retrying without changing the reviewed action uses the same receipt command; changing the action inputs starts a new review command instead of silently reusing the old one.
- On narrow screens, moderation keeps its labeled vertical navigation and wraps queue controls instead of collapsing the workbench into unlabeled icon tabs.
Validation
- The Worker type check, static moderation API contract, and moderation dashboard type check, tests, production build, plus fixture-backed case-detail and audit-page renders pass locally. No database migration, direct upload, or deployment occurred.
2026-08-3006:37
Social Signup Adds Server-Verified Human Checks
Repositories: social.furries.ph, partners-api
Status: Local implementation only; Git-connected release, Cloudflare Turnstile configuration, and the additive canonical-account migration remain required
What’s Changed
- Social signup now uses Cloudflare Turnstile before an account is created. The public website receives only the widget site key; the API Worker verifies the short-lived token, action, and Social hostname using its private secret. After Auth, one database transaction checks public identity policy, claims the username, and links or creates the shared member profile—avoiding a second profile record and keeping the signup request budget bounded. If production verification is not configured, signup safely asks members to try later rather than silently accepting unverified requests.
Validation
- Social type checking, 47 unit tests, the 14-assertion Worker contract, API TypeScript check, diff checks, and a fixture-backed signup form render passed locally. The database migration has not been applied locally or remotely. No deployment or direct upload occurred.
2026-08-3006:37
Topic Feeds Give Viewers a Content-Warning Choice
Repositories: social.furries.ph
Status: Local implementation only; Git-connected release remains required
What’s Changed
- Content-warning cards in community topic feeds now offer Show content in place. This matches Home, profile, Page, and conversation views while keeping the warning, thread link, and a viewer’s decision local to their browser.
Validation
- Social type checking, unit tests, production build, diff checks, and a fixture-backed topic browser render passed locally. No deployment or direct upload occurred.
2026-08-3006:37
Social Password Recovery Stays in the Shared Account
Repositories: social.furries.ph, partners-api
Status: Local implementation only; Git-connected release and Supabase Auth redirect configuration remain required
What’s Changed
- Members can request a Social password-reset link without revealing whether an account exists. The link returns to the Social Pages app, which removes its one-time recovery credential from the browser address before showing the new-password form. The existing API remains the only dynamic runtime and retains the recovery-session requirement for changing a password.
Validation
- Social type checking, 47 unit tests, production build, the seven-assertion API recovery contract, diff checks, and a fixture-backed browser render passed locally. The API TypeScript check is pending because that local checkout lacks its
tscexecutable. No deployment or direct upload occurred.
2026-08-3006:37
Page Timelines Respect Content Warnings
Repositories: social.furries.ph
Status: Local implementation only; Git-connected release remains required
What’s Changed
- A Page post with a content warning now conceals its text, media, poll, quote, and topic context until each viewer deliberately selects Show content. This fixes an inconsistent Page-timeline display without changing the post’s audience, reach, or moderation state.
Validation
- Social type checking, 46 unit tests, production build, diff checks, and a fixture-backed Page browser render pass locally. No deployment or direct upload occurred.
2026-08-3006:37
Social Bios Ask Before Sharing Possible Contact Details
Repositories: partners-api, social.furries.ph
Status: Local implementation only; Git-connected release and authenticated production measurement remain required
What’s Changed
- When a public Social bio resembles an e-mail address or Philippine mobile number, the member sees a category-only warning and can remove it or explicitly confirm they have consent to publish it. The check does not retain the possible contact detail or take an automatic moderation action.
Validation
- The 14-assertion contact-safety contract, 50-assertion text-policy contract, API type check, Social type check, 46 unit tests, production build, and a fixture-backed browser render pass locally. No deployment or direct upload occurred.