ActivityPub Support

Currently, Chirp has a small user base, which renders the platform unusable for anyone seeking a serious microblogging platform. Integrating with the ActivityPub protocol would grant Chirp users access to the rest of the fediverse, significantly increasing Chirp's user base.

Implementing ActivityPub support before production would be beneficial to identify and resolve any federation issues beforehand. During the beta phase, federation would need to occur on the main chirpsocial.net domain to avoid difficulties migrating users from handles like "@harley@beta.chirpsocial.net" to "@harley@chirpsocial.net."

While integrating ActivityPub might be challenging, the rewards of joining the fediverse are vast. This integration would also allow users to host their own Chirp instances, further reducing the load on the main server.

This is a nice to have feature, but I believe the benefits of adding ActivityPub support outweigh the extended development time.

[Tantomile]

Honestly, I feel like adding chirp to the fediverse/ActivityPub network would ruin the environment that we currently have, and make chirp no different then the dozens of other fediverse clients.

Perhaps a limited system like Threads' to allow for external users to see posts from chirp could make sense.

I also doubt that enough users would host their own federated chirp servers to have any significant impact on server performance.

Frankly, my opinion is that there are enough ways to access the fediverse already, and we don't need to turn chirp into just another fediverse client.