BLURT PUBLISHER
Blurt Publisher compatibility with REEID Translate
Blurt Publisher compatibility with REEID Translate is being reviewed using official plugin documentation. Local signing of Blurt transactions in Direct RPC mode (private posting key used inside WordPress; only signed transactions are broadcast). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Blurt Publisher does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Blurt Publisher is documented in the Security category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Blurt Publisher compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Local signing of Blurt transactions in Direct RPC mode (private posting key used inside WordPress; only signed transactions are broadcast).
- Direct RPC broadcasting to public Blurt RPC nodes (no external plugin endpoint required in Direct RPC mode).
- Optional legacy endpoint fallback mode that sends private posting key to a configured endpoint for a single publication request (used only when Direct RPC is unavailable).
- At-rest encryption of stored private posting keys and legacy endpoint fallback credentials when OpenSSL AES-256-GCM is available; encryption key derived from `BLURT_PUBLISHER_ENCRYPTION_KEY` if defined, otherwise from WordPress auth salts.
- Legacy endpoint request protection mechanisms: HTTPS plus endpoint token, timestamp, nonce, and HMAC signature.
- Optional endpoint key registration flow: plugin generates an endpoint token and HMAC secret, broadcasts a signed Blurt `custom_json` proof containing only hashes of those secrets, and sends the actual token/HMAC secret to the endpoint registration route over HTTPS.
TRANSLATION BOUNDARY
Blurt Publisher capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Blurt Publisher and REEID Translate FAQ.
What does Blurt Publisher do?
Blurt Publisher has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Blurt Publisher have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Blurt Publisher?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Blurt Publisher in a multilingual WordPress workflow.
REEID documents Blurt Publisher functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.