Skip to content
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

Expose #job-board via an API #393

Closed
vcarl opened this issue Jul 30, 2024 · 2 comments
Closed

Expose #job-board via an API #393

vcarl opened this issue Jul 30, 2024 · 2 comments
Assignees

Comments

@vcarl
Copy link
Member

vcarl commented Jul 30, 2024

This interacts with the reactiflux.com repo, messages posted that don't meet our validation requirements are not removed from the /jobs page. This is very much not ideal and limits our usefulness as a job space, because spammy and duplicate postings remain.

We should replace the current system with a reflection of the currently-active posts in the server. We monitor as far back as 90 days, with skill ads (forhire posts) kept up for several days.

I'm thinking the simplest way to do this would be to set up a Cloudflare Worker with a KV store to track posts. Since we scan the channel for posts on startup, the lack of persistence isn't a problem. Then, on the website, we can read the list of posts and present a similar experience. Long-term, it would be nice to improve the experience, and maybe consider presenting a list of skill ads that are currently active.

@vcarl vcarl self-assigned this Jul 30, 2024
@vcarl vcarl changed the title #job-board moderation is not reflected on /jobs page Expose #job-board via an API Dec 29, 2024
@vcarl
Copy link
Member Author

vcarl commented Dec 30, 2024

At first I thought we'd need to set up a database for this, but actually I guess not? It's all stored in memory, scanning history for active posts. Maybe it'll make sense to parse further back into history on startup, so we can give more than a single week's backlog, but I don't know that a full-ass database is the way to go there.

@vcarl
Copy link
Member Author

vcarl commented Feb 2, 2025

Shipped in #439

@vcarl vcarl closed this as completed Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant