Is there already an ActivityPub vocabulary for job openings, or cvs?
General Discussion
15
Posts
3
Posters
47
Views
-
You could, for example, use h-resume with ActivityPub.
ActivityPub is, in some ways, just another JSON-LD name-space.
Just use h-resume as another JSON-LD name-space along with ActivityPub.
Yes, as a starting point, that's what I thought as well. Just if there already would have been sinething, I wouldn't try and reinvent the wheel.
One issue with blindly adopting #h-resume is, that in an #ActivityPub context, you usually don't just state "here is my resume", but also e.g. "I have a new job", which then is an update to your resume. A use case, that never existed for h-resume.
So there's still work to do. But it's definitively a good start.
-
Yes, as a starting point, that's what I thought as well. Just if there already would have been sinething, I wouldn't try and reinvent the wheel.
One issue with blindly adopting #h-resume is, that in an #ActivityPub context, you usually don't just state "here is my resume", but also e.g. "I have a new job", which then is an update to your resume. A use case, that never existed for h-resume.
So there's still work to do. But it's definitively a good start.
Regarding:
"but also e.g. "I have a new job""You could either do that with a custom Object type.
Or, using an existing Object type — such as Note, or one of the others.
-
Regarding:
"but also e.g. "I have a new job""You could either do that with a custom Object type.
Or, using an existing Object type — such as Note, or one of the others.
Are you thinking of coding something for this?
-
Are you thinking of coding something for this?
I'm still in the phase of finding out, if there might already be all the tools available, but it seems, I won't get around writing at least some code for it.
I'll probably start extending an existing AP implementation, or using a library, instead of writing everything from scratch. But nothing is set in stone yet. Do you have any suggestions?
-
I'm still in the phase of finding out, if there might already be all the tools available, but it seems, I won't get around writing at least some code for it.
I'll probably start extending an existing AP implementation, or using a library, instead of writing everything from scratch. But nothing is set in stone yet. Do you have any suggestions?
@cdonat @reiver my main concern with such a system is it encourages the centralisation and the "big instance" problem, because of the nature of job ads and CV/resume posters. If you're looking for a job, you want your CV federated to as many potential employers as possible, and if you're hiring, you want your job as to be seen as much. I love the idea but without a good relay network it would be difficult to make it cohesive.
-
@cdonat @reiver my main concern with such a system is it encourages the centralisation and the "big instance" problem, because of the nature of job ads and CV/resume posters. If you're looking for a job, you want your CV federated to as many potential employers as possible, and if you're hiring, you want your job as to be seen as much. I love the idea but without a good relay network it would be difficult to make it cohesive.
I get your concerns. As @reiver already pointed out, the issue could be solved by federated search engines. They can also have federated indices.
Please allow me to respond with a longer thread, to describe my vision. It might change, over time, of course.
1/n
-
Let's assume I set up a search engine, that uses a hand full of sources known to me, that indexes software developer positions in Switzerland, because that covers broadly, what I'm interested in.
Other search engines as well as AP-Users can then subscribe to a query at my search engine. Whenever my crawler finishes, it publishes the newly found jobs, that match their queries.
2/n
-
Let's assume I set up a search engine, that uses a hand full of sources known to me, that indexes software developer positions in Switzerland, because that covers broadly, what I'm interested in.
Other search engines as well as AP-Users can then subscribe to a query at my search engine. Whenever my crawler finishes, it publishes the newly found jobs, that match their queries.
2/n
Now the other search engines have a new source. I can also subscribe to their search engines with my search term, and so find job openings, that I wasn't aware of before, because they have other sources.
After I add a job opening from those other search engines to my index, I also match it to my subscribers queries, and push it to them. Since I don't forward jobs, that I already have in my index, this breaks possible loops.
3/n
-
Now the other search engines have a new source. I can also subscribe to their search engines with my search term, and so find job openings, that I wasn't aware of before, because they have other sources.
After I add a job opening from those other search engines to my index, I also match it to my subscribers queries, and push it to them. Since I don't forward jobs, that I already have in my index, this breaks possible loops.
3/n
In the opposite direction, a search engine for recruiters can work similarly. They query known instances for resumes, that match their broad query and then use AP to distribute their results. The federated results can be used by the search engine admin to extend the list of known instances.
4/n
-
In the opposite direction, a search engine for recruiters can work similarly. They query known instances for resumes, that match their broad query and then use AP to distribute their results. The federated results can be used by the search engine admin to extend the list of known instances.
4/n
As job seeker, I subscribe to query, that describes the jobs, I'm interested in, and find job openings in my feed.
As recruiter, I subscribe to a query, that describes the candidates for my job openings, and will find matching candidates in my feed.
5/5
-
@cdonat @reiver I like the idea in principal, do you see those secondary subscribe actions as manual or automatic? I can see pros and cons to both but I feel automatic is the way forward for adoption, perhaps with an option to queue like moderation tools would have for those who don't want it? I'm getting into details here but I feel like a recommendation in the protocol/design doc would be worthwhile. How about multiple CVs for the same person? I have alt. ones for types of jobs for instance.
-
@cdonat @reiver I like the idea in principal, do you see those secondary subscribe actions as manual or automatic? I can see pros and cons to both but I feel automatic is the way forward for adoption, perhaps with an option to queue like moderation tools would have for those who don't want it? I'm getting into details here but I feel like a recommendation in the protocol/design doc would be worthwhile. How about multiple CVs for the same person? I have alt. ones for types of jobs for instance.
The idea currently isn't in the state, that I started thinking of that. 🙂 It's good to discuss all these details, I haven't thought about yet. Thank you for that.
Automatic subscription: I think, we have to distinguish between user, and search engine. The search engines will probably want to add new subscriptions automatically. The user probably wants to only subscribe to his chosen search engine.
-
@cdonat @reiver I like the idea in principal, do you see those secondary subscribe actions as manual or automatic? I can see pros and cons to both but I feel automatic is the way forward for adoption, perhaps with an option to queue like moderation tools would have for those who don't want it? I'm getting into details here but I feel like a recommendation in the protocol/design doc would be worthwhile. How about multiple CVs for the same person? I have alt. ones for types of jobs for instance.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Yes.
If no one on, say, mastodon.social is following you then none of your posts will show up in the global timeline there or in searches or in hashtags.
Also if you have few followers your posts will receive few boosts so hardly anyone will follow you.
So we end up with a handful of wildly popular accounts dominating the conversations which mostly happen on the big instances. Centralised power. Bad.
The threadiverse solves this. People don't follow other people, they join communities and it's their membership that determines where the federation traffic goes. So nearly every instance has all the conversation and everyone is on an equal footing.
-
@EveHasWords@toot.cat Thanks, that's actually what I was suspecting! 😀 And thanks for the tagpush.app suggestion too, I hadn't thought of that.
-
@contrapunctus If you're on a server that gets followed by people across a wide swath of the fediverse, your posts will go out to all the servers that have someone who follows someone on your server.
Provided you're not blocked by the admin on their side.
That means the best "reach" is on the biggest servers.
There are ways to get around that, though. Using tags that are followed by a tagpush.app account will get your posts boosted to servers that otherwise might not see it.
Probably the best way to improve your visibility without moving servers (assuming your server is a factor) is to get followers from a lot of different servers.
-
-
@contrapunctus yes; if you want to reach a lot people, get a lot of followers.
-
Does choice of server affect the reach of your posts? (Assuming you use the same hashtags.)
Obviously you don't want to be posting from a server that's blocked by vast swathes of the network.
But are there any other factors?
#FediHelp #ActivityPub
-
#Museums in the Fediverse: Experiments with #Tainacan, #ActivityPub, and WebSocial
"The crucial decision is between the policy that defends the common interest and deliberately favors the emergence of new digital institutionalities on the network, and the blind policy that, through inaction, allows the evolution of the digital environment to occur randomly, at the whim of the interests of large foreign technology companies."
-
@kariboka among other options yes: https://docs.bonfirenetworks.org/deploy.html
