-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add additional sources (comment here to suggest another source) #23
Comments
As suggested here: https://news.ycombinator.com/item?id=39624542 and here: https://news.ycombinator.com/item?id=39692590 Add support for scraping workdays' career portals, eg (from: https://news.ycombinator.com/item?id=39692590) Here's some with tech jobs listed: |
Another is greenhouse.io: https://boards.greenhouse.io/remotecom Same as workday, there doesn't seem to be a public master list - each company lists their own jobs on their own sub-folder. |
@christosgousis and @GiorgosPapageorgiou contributed a new source, It's a good example for adding new sources. I'm also realizing a whole "sources" section might be necessary in the future |
========
Idea: create a p2p network of jobs - anyone in the network can post a job, the rest of the network gets the job listing and processes/matches it locally
This would allow that anyone that runs a scraper, can add listings to the network. How do we prevent it from getting flooded by a malicious actor (someone who wants to spam the network)? How do we curate the listings?
One way would be for the local nodes are responsible for filtering the things they receive. There could be filtering nodes as well, that individual nodes could subscribe to
What would be the incentive to post a job? Well all companies want to post job, so they would do it for free probably
What would be the incentive to filter the jobs? For the individual is easy, they don't want to get spammed with jobs
How about for the filtering nodes that want to act as a sort of aggregator and curator? Why would they do it?
That could also be LLM-based, but it would have a cost. Unless for example, the individuals contribute back their own filtered jobs
Maybe the nodes could signal to the network that their node made a match with the post, thus validating the usefulness of the post
Users could mark posts as spam, that would filter out that job, it would add the job to a list of spam that could help an LLM-filter, and it would also mark the poster node as spamming (black list it)
The text was updated successfully, but these errors were encountered: