Platform Guide

How discovery, requests, favorites/bookmarks, premium logic, and support work
Updated: March 9, 2026

1. Discovery Overview

The platform connects posts, members, groups, and shows to help you discover content quickly with cross-linked context.

Tip: Use search filters together with favorites for faster navigation.

2. Cloud Keywords and Relationships

Keyword cloud data is weighted from recent activity and relationship edges.

  • Node size reflects relative keyword weight.
  • Edges reflect relationship strength between entities.
  • Rankings can shift as new data is indexed.
  • Refreshing can surface newly weighted terms.

3. Requests Workflow

Requests can be submitted from /requests, with duplicate checks to avoid fragmented demand.

Similarity Detection
Show-name similarity, date windows, and overlap checks identify likely duplicates.
Voting Signal
Existing requests can be upvoted to consolidate support for the same target.

4. Favorites: Members and Shows

Favorites and bookmarks (My Highlights) personalize your feed and make it easier to revisit important posts.

  • You can favorite both members and shows, and bookmark individual posts.
  • Favorite updates appear in notifications while bookmarks are grouped in My Highlights.
  • Read tracking reduces duplicate alerts.
  • Favorites limits depend on account tier.

5. Filoz Premium Logic

Premium status is validated against the Filoz API and unlocks premium-only notification options.

  • Verification links your account email to premium entitlement.
  • The "Email me about new posts for favorite shows/members" option is available only for verified premium users.
  • If premium verification fails or expires later, that email option is automatically disabled.

6. Contact, Tickets, and Replies

The contact center uses ticket threads so messages and replies stay grouped.

Ticket Reference Format
Ticket IDs use an RQ prefix plus date and sequence to stay sortable and unique.
Email Threading
Replying by email can append to the same ticket when reference matching succeeds.
CAPTCHA is required on contact and request submission flows to reduce abuse.

7. Notifications

The notification panel combines favorite post updates and unread ticket-reply highlights.

  • Unread ticket replies are surfaced as a dedicated section.
  • Lists are intentionally capped for compact display.
  • Opening items marks them as read based on context.

8. Security and Access Controls

  • Role-based access controls separate frontend and backoffice permissions.
  • 2FA can be enabled with email codes or authenticator apps.
  • Verification middleware protects sensitive actions.

9. Need Help?

If your issue is not covered here, open a support ticket from the contact page.

Include clear details and relevant URLs so the team can resolve your request faster.