tobiaseigen

Identify the main ‘activitypub’ plugin topic (most likely the one with the most posts/replies or initial release announcement). Summarize distinct bug reports, feature requests, and recurring support questions in this topic, and recommend clear, logically extractable new topics in appropriate ‘bug’, ‘feature’, and ‘support’ categories. Ensure each recommended extraction is based on meaningful, repeated tangents, providing links for supporting evidence.

ForumHelperBot
Thinking...The user is asking me to identify the main ActivityPub plugin topic on this Discourse forum, and then analyze it to extract meaningful discussions that could be moved to separate topics under bug, feature, and support categories. Let me break down the tasks:
  1. Find the main ActivityPub plugin topic
  2. Summarize bug reports, feature requests, and support questions in that topic
  3. Recommend distinct topics that could be extracted from the main thread
  4. Provide evidence/links for each recommendation

First, I should search for “activitypub plugin” to find the main topic:

Search

Found 60 results for 'activitypub plugin order:likes'

Thinking...Based on the search results, I can see that the main ActivityPub plugin topic is "/t/activitypub-plugin/266794/1" by angus, which has the most posts (840) and views (41689). This appears to be the main topic about the ActivityPub plugin.

Let me read this topic to understand the content, bug reports, feature requests, and recurring support questions.

Read topic

Reading: ActivityPub Plugin

Thinking...To identify the main ActivityPub plugin topic and analyze distinct issues, I'll examine the information from the search results and topic content:

From the search results, I can see that topic #266794 “ActivityPub Plugin” is clearly the main topic with:

  • Most likes (64)
  • Most views (41689)
  • Most replies (444)
  • Created by Angus (likely the plugin author)
  • Tagged as “experimental, activitypub”

This is the primary topic for the plugin announcement and ongoing discussion.

From reading the content of the main topic, I can identify several distinct categories of issues:

BUG REPORTS:

  1. Editing limitations - Posts that have been federated can’t be edited (this is initially by design but seen as a limitation)
  2. Error logs related to undefined methods (model, ap_type)
  3. Issues with content parsing - Notes being shortened/truncated incorrectly
  4. Raw markdown being displayed instead of rendered HTML in federated posts
  5. Issues with deletion of wiki posts
  6. Problems with handling 410 Gone status codes for deleted accounts
  7. 403 Forbidden errors when connecting to certain instances
  8. Authentication errors when connecting to Pleroma instances

FEATURE REQUESTS:

  1. Support for sub-categories - federate content from sub-categories under the parent category
  2. Site-wide actor for federating all public posts
  3. Profile pictures for category actors
  4. Support for editing federated content
  5. Public posts (not just followers-only)
  6. Support for Article type (not just Note)
  7. Support for Like Activity
  8. Tag actors (follow by tag, not just category)
  9. User identity verification with Mastodon
  10. Support for bi-directional federation (replies)
  11. Handling of ActivityPub tags/hashtags
  12. Support for publishing pages

RECURRING SUPPORT QUESTIONS:

  1. How to configure actors for categories
  2. How to handle editing limitations
  3. Audience targeting (public vs. followers-only)
  4. How to verify identity with Mastodon
  5. How to monitor/debug federation issues
  6. Integration with other plugins (e.g., Retort)

The developers have already created a Phase 2 roadmap addressing many of these issues, including:

  • Support for editing federated content
  • Support for restoring deleted notes
  • Public posting (not just followers-only)
  • Improved content parsing
  • Support for Article type
  • Support for replies and interactions
  • Support for Like Activity
  • User identity verification

Based on this analysis, I’ll recommend new topics that should be extracted to improve organization and discoverability.

ActivityPub Plugin Analysis and Topic Extraction Recommendations

After reviewing the main ActivityPub plugin topic (#266794) with its 840 posts and 444 replies, I’ve identified recurring themes that would benefit from extraction into separate topics.

Main Topic

The ActivityPub Plugin is the primary topic initiated by Angus in May 2023, serving as the announcement and main discussion thread. The plugin allows publishing Discourse posts via ActivityPub to federated platforms like Mastodon.

Recommended Topic Extractions

Bug Reports

  1. Content Display Issues

  2. Authentication and Connection Problems

  3. Error Handling for Deleted Accounts

    • Topic Title: “ActivityPub Plugin: Handling Deleted or Moved Accounts”
    • Category: Bug
    • Evidence: Issues with 410 Gone status codes resulting in error logs cluttering admin interfaces.

Feature Requests

  1. Category and Tag Federation

    • Topic Title: “ActivityPub Plugin: Enhanced Category and Tag Federation”
    • Category: Feature
    • Evidence: Multiple discussions about subcategory federation and requests for tag actors.
  2. Content Type and Format Support

  3. Identity Verification and User Management

Support

  1. ActivityPub Plugin Configuration Guide

  2. Federation Troubleshooting

    • Topic Title: “ActivityPub Plugin: Troubleshooting Federation Issues”
    • Category: Support
    • Evidence: Numerous posts showing error logs and requesting debugging assistance.
  3. Plugin Compatibility and Integration

    • Topic Title: “ActivityPub Plugin: Compatibility with Other Plugins”
    • Category: Support
    • Evidence: Issues when used alongside other plugins like Retort and questions about integration with OAuth.

Recent Progress

The development team has made significant progress on a Phase 2 roadmap addressing many issues, including:

  • Support for editing federated content
  • Public posting (not just followers-only)
  • Article type support
  • Improved content parsing
  • Support for bi-directional federation of replies
  • User identity verification

These improvements will resolve many of the concerns raised in the main topic.