feat(protocol/activitypub): rebuild activitypub engine protocol and provider

[FrankLi123]

Summary

This PR is about implementing the relay subscription solution for ActivityPub data collection. This solution is compatible with most of the common Relay URLs that either end with '/inbox' or without.

Guide: How to Run a Mastodon Worker locally ?

• Get a Public URL endpoint forwarding to localhost:{port number} and input it as the mastodon endpoint in config.yaml. You can use a tool like Ngrok to expose a server at a port. e.g., "https://your-subdomain.ngrok.app".

• Add a Relay service list and a port as a parameter in config.yaml for local development. Relays aggregate messages from different servers, and the port is where your input endpoint will forward requests. You can add multiple relay URLs in config.yaml or default relay URLs will be used if none are specified:

  • config.yaml -> component -> federated -> id: mastodon-core -> parameters

• ex:

  federated:
    - id: mastodon-core
      network: mastodon
      worker: core
      endpoint: https://domain:port
      parameters:
        relay_url_list: ["https://relay.fedi.buzz/instance/mastodon.social","https://relay.intahnet.co.uk/inbox"]

Default Relay Service List:

"https://relay.toot.io/inbox",
"https://relay.infosec.exchange/inbox",
"https://relay.intahnet.co.uk/inbox",
"https://relay.fedi.buzz/instance/mas.to",
"https://relay.fedi.buzz/instance/mastodon.online",

(note): messages from relay.fedi.buzz server do not contain "share" type object.

Main Modified Components

• mastodon/client.go: Functions for relay service interaction and received relay message handling
• activitypub/data_source.go: implementation of the core data collection process with the HTTP server

Technical Implementation

• HTTP Server: Built on Echo framework to handle ActivityPub endpoints
• Mimic as a mastodon instance with Authentication: Dynamic RSA key pair generation for secure relay communication with other mastodon servers
• Message Processing: In-memory message channel for ActivityPub object processing

Future Improvements:

• Implement monitoring and client stability in another PR

Checklist

• The commit message follows Angular Contributing guidelines;
• Tests for the changes have been added (for bug fixes / features);

Does this PR introduce a breaking change?

• Yes
• No

Other information

[HenryQW]

Remember to update and close this: RSS3-Network/Docs#9

[brucexc]

Remember to update and close this: RSS3-Network/Docs#9

Please pay attention to this comment: RSS3-Network/Docs#9 (comment).