FRIENDS
Friends compatibility with REEID Translate
Friends compatibility with REEID Translate is being evaluated from available plugin evidence. Follows people via RSS and ActivityPub (Fediverse/Mastodon-style) and reads their posts through built-in themes (Mastodon-style, Google Reader-style, and a default view) with dark mode support. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Friends.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Friends is documented in the Other category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Friends compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Follows people via RSS and ActivityPub (Fediverse/Mastodon-style) and reads their posts through built-in themes (Mastodon-style, Google Reader-style, and a default view) with dark mode support.
- Stores followed people as taxonomy terms and caches followed posts in a custom post type (friend_post_cache); unfollowing removes the cached posts for that person.
- Uses standard WordPress storage mechanisms (post types, options, and taxonomies) without creating extra custom database tables.
- Supports multiple feeds per person (e.g., blog and social media feeds) and organizes subscriptions into folders.
- Provides content categorization using WordPress Post Formats and supports viewing posts by a selected format across feeds.
- Implements rule-based filtering of incoming content.
- Can send full-post email notifications from favorite blogs.
- Is extensible so other plugins can add parsers for new feed sources, add themes, and add functionality such as saving posts to a collection or sending them to an eReader.
CONTENT BOUNDARY
Friends capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Friends and REEID Translate FAQ.
What does Friends do according to the available plugin evidence?
Friends has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Friends?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Friends?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Friends in a multilingual WordPress workflow.
REEID documents Friends functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.