adjust pricing #remoteok job posts and sticky job posts based on how many sticky job posts there are so that the frontpage doesn’t get covered fully with sticky jobs and new job flow is balanced

fix sticky job post if bumped didn’t become sticky #remoteok

unset sticky week and sticky month if job is bumped otherwise frontpage gets clogged with sticky posts again #remoteok

remove sticky job cache because DB is now fast enough to do it on load (thanks @daniellockyer) #remoteok

manage to figure out how to add sticky jobs into SQL query by doing ORDER BY max(coalesce(epoch,0),coalesce(epoch_bumped,0),(coalesce(is_sticky_day,0)+86400),(coalesce(is_sticky_week,0)+604800),(coalesce(is_sticky_month,0)+2592000))) so that we don’t need to “manually” add the sticky jobs on top with code but it just sorts it straight into db (86400 is 24h, 604800 is 7 days, 2592000 is 30 days etc.) #remoteok

fix bug job not sticky because company bumped a sticky job from >12 months ago but the SQL that gets sticky for performance only checked <12 months ago jobs #remoteok

raise sticky job pricing #remoteok and base it on total current sticky jobs instead of only total current sticky for month jobs

fix if admin saved job post it would reset the epoch_sticky_day, epoch_sticky_week, epoch_sticky_month time and put the job back on top #remoteok

find solution for if company adds sticky (24h/7d/30d) during editing job it won’t sticky cuz sticky based on posting date not when sticky was added; solution = sticky boolean value can be a timestamp instead (0 = false, 1 = true, 1601993989 is timestamp of sticky time) and it checks that when showing stickies and resets timestamp of job to edit #remoteok (complex af)

fix if admin edits sticky job post it resets the timer and puts it back to top #remoteok

fix bug that showed sticky job post on top of individual job post #remoteok

stop offering sticky monthly because it makes frontpage too clogged with old job posts #remoteok, keep sticky weekly

cache sticky jobs to drop WAIT time by 25% #remoteok

disable auto giving sticky to BIG companies (by checking Clearbit) for scraped jobs because there is too many sticky jobs now #remoteok

auto update page if new jobs posted since page loaded and didn't scroll within 10 seconds #remoteok

fix when companies who post a job that’s sticky for a day/week/month edit their job post, the sticky gets disabled, this is because I hid the checkboxes for the already purchased sticky (because I wanted to avoid it getting charged extra for them again), then the AJAX would send the edits but it’d not include the sticky, so it’d disable them. Now instead code in backend to check for the diffs in features selected and charge $ based on that. Difficult. #remoteok

fix sticky job closed still would show because pulling sticky jobs is a diff part of code #remoteok

fix closed job showing on frontpage if sticky because removeClosedJobs() wasn’t run on $stickyJobs #remoteok

fix admin can NOT unsticky a job once it’s sticky #remoteok

fix bug sticky jobs bumped didn’t show up as sticky due to SQL typo #remoteok