Thank you again. I'll have a look.
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
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.
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
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
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?
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.
@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.
Yes, #FediHired was one of the inspirations. 🙂
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.