Post #2057763

@cdonat in the meantime, I wish you the best of luck! We desperately need a federated "professional network," especially since LinkedIn has become a stinking swamp... I'm not a developer, but I've seen several projects emerge in the Fediverse and have noticed some recurring patterns that lead me to offer you some advice. Knowing other federated software is essential, but it comes AFTER, because the most important thing is to start designing your own software with maximum freedom and leaving room for all those ideas that might be conditioned by too in-depth knowledge of existing Activitypub software. Once you've developed the core of your ideas, it becomes crucial to engage with the community to understand how to build your software. In particular: how some wonderful ideas were implemented,why some ideas proved problematic for development (too much modularity, too many development frameworks, etc.)why some ideas proved problematic for compatibility with other software in the Fediversehow to maintain compatibility with Mastodon, without being trapped and deceived by what risks becoming a "de facto standard." Mastodon, for example, isn't fully compatible with the "page" format and doesn't offer tools for managing Activitypub groups, but "pages" and Activitypub groups are one of the most interesting tools for managing a multi-dimensional fediverse. In this regard, I recommend taking a look at some notable examples: The strengths and weaknesses of Friendica, currently the most powerful software in the Fediverse for managing groups and events.The compatibility issues between software that manage groups (Friendica, Lemmy, Piefed, Mbin, and, for over a year, NodeBB; and the difficulties encountered by Pixelfed and Bonfire).The compatibility issues between software that manage events (Mobilizon, Gancio, Friendica, Eventbridge for WordPress, Bonfire).The cases that (in my opinion) are laying the foundations for the future of the Fediverse over the past year: NodeBB, WAFRN, and Activitypub for WordPress.