Thank you again. I'll have a look.

For the issues that most annoy developers, you can search the discussions on Mastodon, among the issues on Friendica and Lemmy's GitHub.

As I said, I'm not a developer, but it's clear that the discussions regarding the W3C working group on Activitypub are very important, but you surely already know that...

As for failures, there should be a whole thread dedicated to this topic, especially since the concept of failure is very relative...

Thank you very much. I'm still incredibly impressed by the quality of feedback I get here.

Do you have any links on the failed projects? It would be great to be able to learn more from them.

Also links about details on incompatibilities would be very helpful. I'll have to worry about Mastodon compatibility as much as possible. Simply because it is the silver back gorilla in the #Fediverse

Fair enough! I also like the previous logo better, through I do agree with the rationale for the new one.

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 Fediverse
• how 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:

1. The strengths and weaknesses of Friendica, currently the most powerful software in the Fediverse for managing groups and events.
2. 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).
3. The compatibility issues between software that manage events (Mobilizon, Gancio, Friendica, Eventbridge for WordPress, Bonfire).
4. 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.

I don't really like this symbol as a symbol for the #Fediverse

It looks like isolated snowflakes. Probably not exactly, what the fediverse is supposed to be. It is about connection, and people bold enough to leave the centralized silos. Neither snowflakes, nor isolation, isn't it?

I don't have a logo for #ProFed yet, though. Ideas are welcome, of course.

Also worth considering:

https://symbol.fediverse.info/en

Edit: For a name, I propose GuildFed for consideration.

Thank you very much. Yet another instance of very constructive feedback. This is the #Fediverse at its best.

I did spend some thoughts on the name.

1. It should not clash with the big existing professional network(s).
2. The name should convey, what it is.
3. It should be reasonably catchy.

Of course I'm happy to read other, maybe better options.

I don'^t think, it would be reasonable to make that a paid feature, because I'm working on an open protocol. But actually I did think in a similar direction:

1. Have them pay for company-accounts on my installation of the system. They are free to set up their own instance, and others can also set up one, and sell accounts.
2. Help providers of their software to integrate with our architecture. If they use ProFed code directly, they have to accept the AGPL.

2/2

In the beginning we can't rely on companies, or recruiters to post jobs on a fediverse system. Most of them don't even know of it at all. So we'll use job scrapers. You will be able to set up a scraper for jobs you might be interested in, and other do similar. Then you see your, and their results, and vice versa.

The architecture does allow for recruiters, or companies to feed in their own job descriptions directly, but we can't start with only that.

1/2

The talk about events on my website seems to be confusing. I have to change that. Those events are internal. I use an event sourced architecture, where in a simple installation all producers, and consumer of the event run in the same process. But it can be split e.g. to different Kubernetes pods for bigger installations as well.

I don't have any particularly specific plans on professional insights. My current idea is to rely on groups for that. Do you have any better ideas?

I don't plan automatic matching, but two way federated search engines.

As described before the results will com as a feed, you can subscribe. That gives Nodes in the search network time to e.g. check results from other servers, or rate limit them, etc. So some of the complexity of federated search can be mitigated that way.

So the match still has to be made by humans.

Thank you very much for your feedback. I'll answer them in each post to keep the context.

Those two are in the list already. I've extended Person with a CV, that is not the same, but adjacent to the h-resume microformat.

For jobs I plan to start with a scraper, that feeds a federated search engine, whose result is not immediate, but a feed. That way, I can avoid some of the complexities of federated search. But it is still not trivial.

Hi! Very much interested in this. We need an ActivityPub alternative to business social networks. Nolto was such a letdown.

I can only hope you know what you are getting into in terms is potential scale! I'm no (good) coder, but I'm happy to support in other ways.

It's commendable that you are taking this slowly and first figuring out the basics together with the community.

My only suggestion would be, for now, to think of alternative names for the network. ProFed is not bad actually, but is it something that will stick into people's heads? Maybe.

1. Two principal requirements:
- CVs (personal profiles separated in sections, some of which standard - summary, career and education timelines, list of evidence-based key skills) and
- jobs (postings, again with sections, again summary, and skills, responsibilities). These should be possible to disabled when the search ends. 1/4

I hope to soon have it good enough to use it for myself. Then the next goal is to make it usable for others in their own installations. Only then I look forward to be able to provide an instance for others to use.

If anyone volunteers to run such an instance, get in touch and I'll make sure to push features you need for that.

Yes, #FediHired was one of the inspirations.

Thank you very much for your feedback. It is very welcome for sure. I'll take my time later today and see, how I might be able to work them into the webpage.

No, it's not two way. Just what I push on Codeberg is mirrored to GitHub, and GitLab. Those mirrors are for visibility, development happens on Codeberg.