I have started a new project: ProFed.

[zockbursche@social.tchncs.de]

@cdonat how does this mirroring to github and gitlab work? Is it two-way?

[mcwabbit@tenforward.social]

@cdonat
@johannesbeers

[funkylab@mastodon.social]

@cdonat read through the homepage. If you'd allow for some criticism, which I hope to be constructive:
Total overfocus on talking about the protocol; the protocol is still a *means* to an *end*!
You don't even describe what entities should be on that platform (I assume it's employees, freelancers and employers, i.e., humans?) and what kind of relations between these you want to represent. You instead talk of how the server is internally structured – meaningless, because you don't …

[funkylab@mastodon.social]

@cdonat … describe the purpose.
"Professional social network" is way too vague! "Event-based", huh, what kinds of things will be exchanged, event-basedly?
What do people actually *do* on that network? I assume they pronounce some kind of affiliations? What kinds specifically?

You're in too deep in the CS "how" before you answered the "what" and "why".

[rs3@mastodon.social]

@wessi @cdonat following #ProFed, would be a good complement to #FediHired IMO. Great idea

[cdonat@hostsharing.coop]

@zockbursche

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.

[cdonat@hostsharing.coop]

@funkylab

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.

[cdonat@hostsharing.coop]

@rs3 @wessi

Yes, #FediHired was one of the inspirations.

[secbox@chaos.social]

@cdonat This is awesome! Any public servers yet for users to join?

[cdonat@hostsharing.coop]

@secbox No, sorry. ATM there isn't even an implementation complete enough to use for myself, let alone have others use it. Working hard on it.

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.

[odnankenobi@fosstodon.org]

@cdonat I am curious to see the results of that research

[mapto@masto.bg]

@cdonat @funkylab here my take, hopefully some of this could be useful:

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

[mapto@masto.bg]

@cdonat @funkylab Probably the summary and skills are so diverse across career paths that it's not a good idea to try to standadise them in order to match automatically (ambitious potential follow up). 2/4

[mapto@masto.bg]

@cdonat @funkylab Potentially other types of posts like
- events (this is also an ambitious project, probably worth delegating to mobilizon or similar),
- professional insights (regular posts?; without MS and AI risks of shitification are not as big) 3/4

[mapto@masto.bg]

@cdonat @funkylab An interesting question is who posts jobs: do professionals do it from their profiles or you allow organisations to create profiles? Org profiles could potentially be a paid feature. There are lots of quality professionals are already on fedi, so companies might have the reason to pay. 4/4

[zenbeater@beige.party]

@cdonat

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.

[cdonat@hostsharing.coop]

@mapto @funkylab

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.

[cdonat@hostsharing.coop]

@mapto @funkylab

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.

[cdonat@hostsharing.coop]

@mapto @funkylab

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?

[cdonat@hostsharing.coop]

@mapto @funkylab

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