Feature Request: Calypso / WordPress ActivityPub Integration: Feedback & Suggestions for Enhanced Federation

[Jiwoon-Kim]

What

Synthesized via gpt

📌 Calypso / WordPress ActivityPub Integration Feedback & Suggestions

1️⃣ Federated Reply Block Rendering Issue

Issue:
Federated Reply blocks are not rendered within the WordPress Reader on WordPress.com.
Why it matters:
Since WordPress.com already provides Fediverse integration options, federated replies should appear consistently in Reader feeds to preserve conversation context and interaction consistency.

Reference:
Automattic/wordpress-activitypub#1716

---

2️⃣ Comment HTML/CSS Exposure in Jetpack App Reader

Issue:
When editing comments via the Jetpack app, raw HTML and CSS (including <style> tags) within comments are exposed, potentially causing layout issues and unnecessary code visibility.
Suggestion:
Sanitize comment content or implement a block-based comment rendering system in the mobile app to prevent raw code exposure.

Reference:
wordpress-mobile/WordPress-iOS#24554

---

3️⃣ Reblog via ActivityPub Announce Activity (Not oEmbed)

Feature Request:
Implement native WordPress-to-WordPress Announce (Reblog) functionality using ActivityPub.
Current Problem:
The Jetpack Reblog embeds posts via oEmbed previews, which are incompatible with how the Fediverse handles content sharing (Announce/Boost). This causes duplicate or awkward post rendering on federated timelines (e.g. Mastodon, Misskey) and occasional layout breakage due to theme conflicts.

Expected Behavior:
When reblogging between two ActivityPub-enabled WordPress instances, the reblog action should trigger an ActivityPub Announce activity instead of embedding.

Considerations:

• Prioritize this for cases where both sites have ActivityPub active.
• Optionally integrate with Jetpack Reblog detection logic.

Reference:
Automattic/wordpress-activitypub#1715

---

4️⃣ Centralized WordPress.com Relay & Fediverse Identity Management

Idea:
Introduce a central relay instance (e.g., fedi.wordpress.com) to improve Fediverse interoperability for WordPress.com users and potentially self-hosted sites.
Example structures:

• fedi.wordpress.com/instance-info/mastodon.social
• fedi.wordpress.com/@username@mastodon.social
• fedi.wordpress.com/fediverse_profile/@username@mastodon.social

Benefits:

• Simplify following/follower relationship management.
• Allow opt-in federation routing through WordPress.com for self-hosted sites.

Concerns:

• Complexities in handling multiple domain-based and username-based Fediverse IDs within the WordPress.com ecosystem.

---

5️⃣ WordPress Profile Unification and Federation ID Strategy

Idea:
Unify WordPress.com Reader profiles (e.g., https://wordpress.com/reader/users/kimjiwoon96) with potential Fediverse profile handles.
Note:
Though full Fediverse integration may be challenging, a gradual step could involve decoupling this from broader WordPress.org/self-hosted profile unification efforts and addressing them separately.

---

6️⃣ Microblogging via Jetpack Custom Post Type (e.g., Note/Status/Portfolio)

Proposal:
Extend Jetpack custom post types (like Portfolio) to serve as a microblogging 'Note' post format compatible with Fediverse short posts (equivalent to Mastodon toots).
Advantage:
Allows seamless integration of WordPress.com and self-hosted sites as microblogging nodes within the Fediverse without compromising the standard blog structure.

---

7️⃣ Emoji Rendering Inconsistencies Across Platforms

Issue:
Emoji rendering varies greatly across WordPress platforms (self-hosted, WordPress.com, Jetpack Reader, desktop/mobile apps). Especially problematic with:

• Flag emojis
• Custom emojis from Fediverse platforms (e.g., Misskey reactions)

Why it matters:
If WordPress Reader later supports Fediverse feeds, it will need consistent emoji parsing and rendering, including custom emoji sets.

Suggestion:

• Standardize emoji rendering behaviors across apps and platforms.
• Explore Fediverse emoji compatibility for future federation support.

Reference:
wordpress-mobile/WordPress-iOS#24551

---

📌 추가 제안 (Calypso 관련)

Proposal:
Evaluate applying ActivityPub protocol directly to WordPress Reader itself (as a Fediverse-capable Reader like Mastodon clients) or providing an opt-in fedi.wp.com relay instance for broader federation.

---

Why

refined by gemini

Title: Calypso / WordPress ActivityPub Integration: Feedback & Suggestions for Enhanced Federation

Introduction:
This issue outlines feedback and suggestions to improve the integration between WordPress.com (Calypso), the ActivityPub protocol, and the broader Fediverse. The goal is to create a more seamless, consistent, and powerful federated experience for WordPress.com users. Many of these points stem from observations detailed in Automattic/wordpress-activitypub#1716.

---

1. WordPress Reader as a Fediverse-Aware Platform & Improved Account Integration

• Proposal: Evaluate strategies to make WordPress Reader more deeply integrated with the Fediverse. This could involve:
  • Applying the ActivityPub protocol directly to WordPress Reader, allowing it to function more like a Fediverse client (e.g., for subscribing to and interacting with external Fediverse accounts/feeds, not just WordPress blogs).
  • Providing an opt-in relay instance (e.g., fedi.wp.com as suggested in point Sites: Gap/space missing between sites for every 3rd site #5) that WordPress Reader could leverage for broader and more robust federation capabilities.
• Current Issues This Would Address (Observed when ActivityPub is active):
  • Incomplete Account Integration: Account integration and recognition between self-hosted WordPress sites (using the ActivityPub plugin) and WordPress.com accounts is currently inconsistent when interacting via ActivityPub. For instance, the same user/blog might be perceived as different entities.
  • Missing Notifications in Reader: When federated replies occur between WordPress blogs (e.g., a self-hosted site replying to a WordPress.com blog, or vice-versa, using their Fediverse identities), notifications for these interactions often do not appear in the WordPress.com Reader.
• Why it matters: A more Fediverse-aware Reader would provide a unified experience, ensuring users don't miss interactions and that identities are consistently recognized across federated actions.

---

2. Federated Reply Block Rendering in WordPress Reader

• Issue: Federated Reply blocks (from the ActivityPub plugin) are not rendered within the WordPress Reader on WordPress.com. The content of these blocks is not displayed.
• Why it matters: Since WordPress.com now offers built-in Fediverse integration options, content designed for federation (like federated replies) should appear consistently in Reader feeds. This is crucial for preserving conversation context and ensuring users see the full scope of interactions on their posts.
• Reference: Initial observation in [Automattic/wordpress-activitypub#1716](WordPress.com Federation Experiment and Observation Report wordpress-activitypub#1716).

---

3. Comment HTML/CSS Exposure (Observed in Jetpack App Reader, Potential Calypso Implications)

• Issue: When comments containing rich HTML (potentially from federated sources or edited with advanced tools) are viewed or processed, there's a risk of raw HTML and CSS (including <style> tags) being exposed, especially noted in the Jetpack app reader context.
• Suggestion for Calypso/Reader: Ensure robust sanitization and structured rendering of comment content within the WordPress.com Reader to prevent raw code exposure and maintain a clean UI, regardless of the comment's origin or rich formatting. This might involve a block-based comment rendering approach.
• Reference: Mobile-specific report [wordpress-mobile/WordPress-iOS#24554](WordPress.com Federation Experiment and Observation Report wordpress-mobile/WordPress-iOS#24554). Calypso should ensure its handling is robust.

---

4. Native Reblog via ActivityPub Announce Activity (Not oEmbed)

• Feature Request Summary: Implement native WordPress-to-WordPress "Reblog" functionality using the ActivityPub Announce activity, rather than the current oEmbed-based approach.
• Current Problem: Jetpack Reblog uses oEmbed previews, which are misaligned with the Fediverse's Announce/Boost model. This leads to awkward rendering on federated timelines and potential layout issues.
• Expected Behavior for WordPress.com: When a WordPress.com user reblogs a post from another ActivityPub-enabled WordPress instance (either .com or self-hosted), this action should ideally trigger an Announce activity from their WordPress.com Fediverse identity.
• Relevance to Calypso: The UI/UX for reblogging on WordPress.com and the underlying mechanism (choosing between oEmbed and Announce) would be managed or influenced by Calypso.
• Reference: Detailed proposal at [Automattic/wordpress-activitypub#1715](Feature Request: Implement WordPress-to-WordPress Announce (Reblog) Functionality via ActivityPub wordpress-activitypub#1715).

---

5. Centralized WordPress.com Relay & Fediverse Identity Management

• Idea: Explore introducing a central relay/proxy instance for WordPress.com (e.g., fedi.wordpress.com) to streamline Fediverse interoperability for WordPress.com users and potentially offer services to self-hosted sites.
• Example URL Structures:
  • Instance Info: fedi.wordpress.com/instance-info/mastodon.social
  • User Profile (Proxying): fedi.wordpress.com/@username@mastodon.social or fedi.wordpress.com/fediverse_profile/@username@mastodon.social
• Benefits:
  • Could simplify following/follower relationship management for WordPress.com users interacting with the wider Fediverse.
  • Might allow opt-in federation routing through WordPress.com for self-hosted sites, potentially offering robustness or additional features.
• Concerns: This is a significant architectural consideration with complexities in managing multiple domain-based and username-based Fediverse IDs within the WordPress.com ecosystem.

---

6. WordPress.com Profile Unification and Federation ID Strategy

• Idea: Consider how WordPress.com Reader profiles (e.g., https://wordpress.com/reader/users/kimjiwoon96) align with users' Fediverse identities and a potential unified ID strategy.
• Note: While a full unification of WordPress.org, self-hosted, and WordPress.com profiles with Fediverse IDs is a massive challenge, a phased approach could be considered. This might involve initially focusing on how WordPress.com identities are presented to and interact with the Fediverse.

---

7. Microblogging via Jetpack Custom Post Type (e.g., "Note" or "Status")

• Proposal: Consider extending or introducing Jetpack-powered Custom Post Types (similar to existing ones like Portfolio or Testimonials, but simpler) to serve as a dedicated microblogging "Note" or "Status" post format. This format would be optimized for ActivityPub Note objects.
• Advantage for WordPress.com: Allows WordPress.com blogs to seamlessly function as microblogging nodes within the Fediverse (for short, status-like updates) without altering the primary blogging experience or structure. Calypso would provide the interface for creating these "Notes."

---

8. Emoji Rendering Inconsistencies & Fediverse Compatibility

• Issue: Emoji rendering is inconsistent across WordPress platforms (self-hosted, WordPress.com, Jetpack Reader, desktop/mobile apps). This is especially problematic for:
  • Flag emojis.
  • Custom emojis from Fediverse platforms (e.g., Misskey reactions, Mastodon custom emojis which often use <img> tags).
• Why it matters for Calypso/Reader: If WordPress Reader enhances its Fediverse capabilities (as suggested in point Default to Open #1), it will need consistent and comprehensive emoji parsing and rendering, including support for custom Fediverse emoji sets (often image-based).
• Suggestion for Calypso/Reader:
  • Standardize emoji rendering behavior within the Reader and other Calypso-managed interfaces.
  • Explore robust support for Fediverse custom emojis (e.g., parsing <img> tags with specific classes used by platforms like Mastodon/Misskey for their custom emojis) to ensure faithful display of federated content.
• Reference: Related mobile discussion [wordpress-mobile/WordPress-iOS#24551](Emoji Rendering Issue: Inconsistent Flag Emoji Rendering Across WordPress Self-hosted, WordPress.com, Jetpack Reader, Mobile, and Desktop Environments wordpress-mobile/WordPress-iOS#24551).

---

Conclusion:
These points aim to foster discussion on making WordPress.com a more powerful and integrated citizen of the Fediverse. Enhancing the WordPress Reader's capabilities, ensuring consistent content display, and thinking strategically about identity and content sharing are key areas for improvement.

How

No response

Related Issues
wordpress-mobile/WordPress-iOS#24516
Automattic/gravatar#206

[Jiwoon-Kim]

If WordPress implements a custom emoji feature, it could also create new business opportunities.
In Korea, these are called "emoticons," and there's an active market of character designers creating custom emoji packs.
If WordPress could absorb that market, it would expand both its revenue models and ecosystem.

This could even open up collaboration opportunities with brands like Sanrio or Pokémon through WordPress.com.
In turn, it could pave the way for unique community events — for example, integrating WordPress.org meetups with Pokémon GO's API for location-based marketing campaigns

Imagine wp.org events promoted through Pokémon GO’s API — location-based marketing meets open-source culture. It’s closer than you think.

• Add support for emoji reactions to posts mastodon/mastodon#23035
• arbitrary emojis as reactions mastodon/mastodon#4106
• Pleroma-style emoji reactions mastodon/mastodon#13275
• https://unicode.org/reports/tr51/#flag-sequences

[Jiwoon-Kim]

---

📌 Simple Note — Fediverse Identity Integration Proposal

• Use case:
  Allow users with Mastodon, Misskey, and other ActivityPub accounts to sign up for a WordPress site using their existing Fediverse identity.

• Idea:
  Posts authored by Fediverse users should output a meta tag like:

<meta name="fediverse:creator" content="@thaumiel999@mastodon.social">

• Purpose:
  This could serve as a microblogging-friendly publishing platform for Fediverse users who occasionally want to post longer-form content, integrating better with their existing identity.